Windows NT 4.0 -- TECHNICAL SUPPORT

Installing and Configuring NT

Chapter 1: Overview of NT
Chapter 2: Installing NT
Chapter 17: NT Boot Process
Chapter 3: Configuring NT Environment -- Registry
Appendix: Configuring NT -- install /remove hardware

Chapter 1: Overview of NT

NT refers to two different products - NT Server and NT Workstation.

A logical grouping of typically no more than 10 computers that can share resources. As part of a workgroup, each computer running NT has its own directory database; resources and user accounts are managed at each computer.

An administrative unit of NT Directory Services. A domain contains (at least) a NT Server computer configured as PDC. The PDC maintains a dirctory database that stores all of the account and security info for the domain.

In each domain, there must be one and only one PDC, zero or more BDC (at least one BDC is recommanded)

The logical link that combines domains into one administrative unit: a trust relationship, or trust.

Domain: all domain controllers maintain a common directory database, so user can log on from any computer that is in the domain.

Workgroup: each computer maintain its own directory database, so a separate user account for each user must exist in each computer's directory database.

Differences between NT Server and NT Workstation:

Area  NT Workstation  NT Server
Simultaneous connections 10  Unlimited
(limited only by Client Access License - CAL)
Maxium RAS sessions 1 256
Replication Import only Import and export
Multiprocessor  2 4 (32 with OEM)
Internet services Peer Web Services Internet Information Server
Network server  No (personal web server only) Yes
F&P Sharing for Macintosh  No Yes
Disk fault tolerance No Yes (RAID 1, 5) 
Domain logon validation
(Directory Service)		 No Yes

More Detail on Differences between NT Server and NT Workstation:

Area NT Workstation NT Server
     
  No Administrative Wizards
  No License Manager
  No Migration Tool for NetWare
  No Network Client Administrator
  No Server Manager
  No System Policy Editor
User Rights Policy 10 basic and 17 advanced 11 basic and 16 advanced
More on Disk Fault Tolerance Does not have native support for fault tolerant  volume structures -- such as disk mirroring, disk duplexing, or disk striping with parity ; Can 
do disk striping without parity.		 Native support for fault tolerant  volume structures -- such as disk mirroring, disk duplexing, or disk striping with parity
User Manager (User Manager 
for Domains in NT Server)		 Users, Local Groups Users, Local Groups, Global Groups ; "Select Domain" ; 
"Trust Relationships" ; 
Networking Client Service for NetWare  Gateway (and Client) Services 
for NetWare
File and Print Service for NetWare Does not come with; must purchase extra  Does not come with; must purchase extra
Supports SQL Server, SMS, SNA, Proxy, Exchange Server No Yes

NT Network Services -- NT Server vs NT Workstation

Service NT Workstation NT Server
Computer Browser

Yes
NetBIOS Interface
Remote Access Service
RPC Configuration
Server
Workstation
RPC support for Banyan
SAP Agent
SNMP Service
Simple TCP/IP Services
Microsoft TCP/IP Printing
Network Monitor Agent
DHCP Relay Agent

No

Yes
Gateway (and Client) Services for NetWare
Microsoft DHCP Server
Microsoft DNS Server
Microsoft Internet Information Server
Network Monitor Tools and Agent
Remoteboot Service
RIP for Internet Protocol
RIP for NWLink IPX/SPX compatible transport
Services for Mac
Windows Internet Name Service
Microsoft Peer Web Services

Yes

No

 

Differences between NT Workstation and Windows 95

Area  NT Workstation Windows 95
     
Certified for C2 Security Yes No
Requires secured logon Yes No
Runs DOS Applications Most; DOS applications CANNOT have direct access  to the CPU Yes
Can run 16 bit apps in separate  address space Yes No
Uses DOS and Win16 device drivers No Yes
Multiplatform Yes No
Multiprocessors Yes  No
Win16 applications Yes Yes
DOS applications Yes Yes
POSIX and OS/2 applications Yes  No
File systems NTFS, FAT16 FAT16, FAT 32
Plug and play No  Yes
Application/memory protection Yes Yes
Internet services  Peer Web Services Personal Web Server
RAS Inbound and outbound Inbound with Plus! and Outbound 

Chapter 2

Installing Windows NT

 

Hardware requirement

MS supports only the devices listed on the HCL (Hardware Compatibility List).

NT provides the NT Hardware Qualifer (NTHQ), i.e. Hardware Query Tool 4.0 for Windows to determine the hardware on an Intel x86-based computer. Make a NTHQ disk by running Makedisk command included in the installation CD's \Support\HQTool folder. The NTHQ disk is bootable and runs in DOS.

Minimum NT hardware requirement:

  • Intel x86-based (80486/33 or higher)
    • 486 / 33 MHz (or faster) or Pentium-based system
    • RAM: 16 MB for NT Server; 12 MB for NT Workstation
    • Free hard disk space (typical installation): 125 MB for NT Server, 110 MB for NT Workstation
      Note: Required disk space varies according to cluster/sector size.
    • VGA or higher-resolution display adapter
    • Microsoft Mouse or compatible pointing device
    • 3.5 disk drive
      Note: El Torito does not require the computer to have floppy disk because you can start computer from a bootable compact disk.
    • CD-ROM drive or access to a CD-ROM over a computer network
  • RISC-based
    • Alpha AXP, MIPS R4x00 or PowerPC processor
    • RAM: 16 MB
    • Free hard disk space: 160 MB for NT Server, 110 MB for NT Workstation
    • VGA or higher-resolution display adapter
    • CD-ROM drive (required)
    • Microsoft Mouse or compatible pointing device.

    • Note: NT 4.0 does not yet support Plug and Play. NT can automatically detect many kinds of hardware devices, but does not change hardware settings, such as the IRQ and DMA channels and base memory addresses. You may need to (manually) make sure there is no hardware setting confilictions.

    NT Partitions

    System partition -- hardware-specific boot files in the active partition, must be on a primary partition (ordinarily drive C:\).

    Boot partition -- contains the operating system files and its supporting files (i.e. the \Winnt\System32\... folder heirarchy). Can be located on an extended partition.

    If both the hardware-specific files and the operating system and its supporting files are installed on one partition, then that partition would be both the system and boot partition.

    Setup find "Unknown Partition Types" -- if you are installing NT on a hard disk that already contains stripe sets, volume sets, or any areas allocated for fault tolerance (disk mirroring and disk srtiping with parity), they appear on the Setup screen as partions of an unknown type.

    Selecting File System - NTFS vs FAT

    NTFS -- can only be accesed by NT. Choose when:

    FAT -- can be accessed by NT, Windows 95, MS-DOS, and OS/2. Choose when:

    Windows NT File Systems -- NTFS vs FAT

      NTFS Considerations FAT Considerations
    Security
  • Supports complete NT security, so you can specify who is allowed various kinds of access to a file or directory.
  • Files are not protected by the security features of  NT.
    • Activity log
  • Keeps a log of activities to restore the disk in the event of power failure or other problems.
  • FAT file systems do not keep a log.
    • Support multiple file forks for Macintosh files
    • Yes
    • No
    Hot fixing (bad sector remapping)
    • Yes
    • No
    Maximum File/Partition size
  • 4 GB to 64 GB, depending on the size of your clusters.
  • 4 GB.
    • File compression
  • Supports flexible per-file compression.
  • File compression is not supported.
    • Operating system compatibility
  • NT only
    Note: Although DOS connot see NTFS, DOS applications running under NT can.
  • Allows access to files when your computer is running another OS, such as MS-DOS or OS/2.
    • Huge Partitions (>4GB)
  • Yes
    •
  • No
    •

    Hot fixing -- or bad cluster remapping, means to repairs HD failures on the fly without returning an error message to the calling application.

    Note:

    A partition larger than 4GB cannot be created during NT installation! and how to make one?

    Why -- when creating a partition during installation, the partition is always formatted as FAT. Even if you choose to farmat the partiotion as NTFS, the initial format is FAT. At the end of the installation, the system starts and convert the partition to NTFS. Because FAT has a maximum partition size of 4 GB, a problem occurs when you want to create an NTFS partition larger than 4 GB during installation.

    Solutions:

    Choose Server Role During Setup

    NT Server can be configured to be one of: PDC, BDC, or Stand-alone (Member Server)

    PDC

    Note: A domain can contain one and only one PDC. When you configure a computer as a PDC, you are creating a domain. And if the computer is to be configured as a PDC, you must also choose either the Per Server or Per Seat licensing mode.

    BDC

    Stand-Alone or Member Server

    Joining a Domain or Workgroup

    for a BDC, a member server, or a NT Workstation computer to join a domain, a computer account for that computer must be created.

    for BDC -- a computer account on the PDC must be created prior to or during the installation of the BDC (NOT after).

    Stand-alone and NT Workstation computer -- can join a domain at any time: prior to, during or after installation.

    Join a workgroup does not require a computer account because there is no centralized administration of the computer and user accounts in a workgroup.

    Choosing a Licensing Mode -- Server only

    Per Server -- CALs are assigned to the server. The number of CALs determined the number of simultaneous connections that can be made to that server.

    Per Seat -- A CAL is purchased for each client computer. With a Per Seat license, a client can access any resources on any computer running NT Servers across the entire network, and can log on to multiple servers simultaneously. This means unlimited number of computers can have access to a single server, provided each computer is licensed with the Per Seat Licensing Mode.

    A user can legally connect to any server in the network from any client computer for which a CAL has been purchased. If thePer Seat licensing option is chosen, it will not prevent clients from connecting to a serve if the number of simultaneous client connections exceeds the number of Per Seat licenses that have been purchased.

    The Per Seat Licensing mode is often the most economical one for networks in which clients ordinarily connect to more than one server.

    ONE SERVER = PER SERVER Licensing
    MULTIPLE SERVERS = PER SEAT Licensing

    Per Server option:

    Number of simultaneous connections needed to Server1
    Number of simultaneous connections needed to Server2
    Number of simultaneous connections needed to ServerN
    Total simultaneous connections needed to all Servers: A = server1+server2+...+serverN
    (A is the number of Per Server CALs needed?)
     
    Per Seat option:
    Number of seats (computers) that access any server is the number of CALs needed -- B

    Adding a Computer Account to a Domain

    Only users who have the user right add workstations to a domain can create a computer account. By default, members of the Administrators, Domain Admins, or Account Operators groups have this right.

    Computer accounts are created/deleted through the Server Manager >>Computer >>Add to Domain /Remove from Domain

    the computer can join the domian during NT installation, or after installation (for member server and NT workstation computer only. BDCs must join a domain prior or during installation) by using Control Panel (local computer) >> Network >> Identification >> Change >> Member of ... type in the name of Workgroup or Domain

    >> Create Computer Account in the Domain, supply a user account that has been granted the Add Workstations to Domain user right (Administrator and Server Operator have this right by default) and appropriate password.

    Note: If the computer has had NT installed on it, or for some other reason needs to rejoin the domain, then the computer account must be deleted and recreated at the domain controller (because of a new SID created in installing an NT). If this is not done, an error message refers the administrator to check the computer account on the domain.

    Logging on to a Computer or Domain

    you can choose to log on to the local computer or to the domain. If log on to the local computer, you can view the shared folders on another computer in the domain, but cannot access them unless connect to them and specify a valid domain user account and password.

    To map a network drive: --> NT Explorer >> Tool >> Map Network Drive >> Path, type in a universial naming convention (UNC) path for the domain resource, e.g. \\Server1\SharedFolder2 >> enter password when prompted.

    You cannot choose to log on to the local computer if it is a Domain Controller (no such choice for you to choose at all). You can only log on to the domain, or another domain if appropriate trust relationship exist with other domain. This is because the local directory services database on any DC is the same domain directory services database.

    Unlike logging on to a computer that is a member of a domain, you cannot choose other workgroups to log on to. The use name and password you enter is validated agasinst the local directory services database on that computer.

    If you want to join a different workgroup, use Control Panel >> Network >> Identification >> Change >> Member of ... type in the name of the Workgroup you want to join.

    How do I trick install into thinking I have a network adapter card installed?

    Note: If you do not have an adapter already installed, select MS Loopback Adapter -- a software device that fools NT into thinking a real NIC exists. Once you physically install a NIC, you can install the correct drivers and remove this facade.

    Installing NT Server from a Network Share

    Server-based Installation -- When need to install NT on multiple computers, you can streamline the installation by utilizing a network share containing NT source files. This method is known as a server-based installation.

    WINNT and  WINNT32 Setup Switches (Winnt32 does not have /f /l switches)

    PARAMETER DESCRIPTION
    /b install without the Boot floppies; Requires additional 4~5MB HD space
    must use this switch if not to use the installation CD -- by copying the \I386 directory to the hard drive first.
    /f Prevent verfying files as they are copied; Use this switch to accelerate installation.
    This command cannot be used with Winnt32.exe
    /i:inf_file Specifies the file name for the setup information file. Default is DOSNET.INF
    /o Creates boot floppies and starts the installation??
    /x Prevents setup from making Setup boot disks. Use this when you have created Setup boot disks already.
    /ox Creates Setup boot floppy disks only -- does not start install
    /s:sourcepath Specifies the source of the NT setup files. This must be a fully qualified path in the form drive_letter:\path or  \\server_name\share\path. The current directory is the default source for the installation files.
    /t:drive  Force setup to place the temporary files on the specified drive.
    /U:answer_file Specifies an unattended installation and lists the optional script file.
    /UDF:id, [UDF_file]    Specifies the identifier that is to be used to apply sections of the UDF_file in place of the same section in the answer_file. If no UDF is specified, the Setup program will prompt the user to insert a disk that contains a file called $UNIQUE$.UDF. If a UDF is specified, Setup will look for the identifier in that file.
    /I Creates $Winnt.log - a log file that lists any errors during copy to temporary folder.
    This command cannot be used with Winnt32.exe

    To Install NT when CD-ROM is not on HCL -- must use the /b switch

    Note:

    Unattended NT and Application Installation

    In an unattended setup, the Setup program runs over a network, using the Winnt.exe /u or Winnt32.exe /u. The /u switch is used to specify an answer file (Unattend.txt) -- a script used to automate the installation.

    How to create a answer file --
     
    use Setup Manager (Setupmgr.exe in the installation CD's \support\deptools\platform folder), or modify the sample unattend.txt using a text editor.
     
    A sample unattended setup answer file (unattend.txt) is included in NT installation CD's respective platform folder (for Intel-x86, in the \i386 folder)
     
    What are included in a answer file?
     
    An unattend.txt includes the following settings:

    General

    • User Information -- user name, organization name, computer name and product ID
    • General -- hardware settings, upgrading or installing? if to run a program during setup
    • Computer Role -- PDC, BDC or Member Server
    • Install Directory -- the default, or to ask the user, or to a specified directory
    • Display Settings
    • Time Zone
    • License Mode

    Networking

    • General -- configure the networking during setup or from the Setup Manager program
    • Adapter -- select the adapter cards
    • Protocols -- install what protocols and set their parameters
    • Services -- install what services and set their parameters
    • Internet -- install what Internet services
    • Modem -- configure the modem connected to the computer

    Advanced

    • some more settings usually do not need to change. Such as if to convert the NT installation partition from FAT to NTFS.
     
    Sample Syntax for using a answer file:
     
    "WINNT /S:d:\i386 /U:c:\unattend.txt" 
     
    the /S switch is required to define the source of the distribution files when /U is used.
     
    How many answer files do you need ?
     
    Create several answer files if setting up different hardware (PCs & laptops)
    Creating and using UDF
     
    UDF is created by hand using a text editor. It begins with a section that defines IDs for each computer and what sections of UNATTEND.TXT need modification for a specific computer.
    If you intend to use a UDF to customize the installation process for several computers, you will need to provide unique settings for at least the computer name for each computer.
     

    Use a single answer file (Unattend.txt) for the info that applies to all users, and use one or more UDFs to supply info that is specific to a single computer or a small group of computers. Note a single UDF can contain specified settings for many computers, which are identified by the [UniqueIDs]. Therefore --

    You usually use only one UDF and several unattended files for installing NT on many different hardware platforms and configurations

    Sample Syntax of using answer and UDF files
     
    if you have an unattended answer file named unat1.txt, and an UDF file named udf1.txt which contains a unique ID of u1; and the installation files reside on a network share mapped as the F: drive's \i386 folder:
     
    WINNT /S:F:\i386 /U:c:\unat1.txt /UDF:u1,udf1.txt

    Situations of using answer files, UDF and Sysdiff

    Upgrading and Removing NT

    Upgrading

    Install NT 4.0 with existing NT 3.51 for dual boot

    Install NT 4.0 into a new directory and reinstall applications. Previous settings in NT 3.51 will NOT copied to NT 4.0.
     

    Dual-boot --

    You will have to use dual-boot, when using some Plug-n-Play utilities--

    Many Plug-n-Play configuration utilities for network adapters, modems, video adapters, and other hardware devices will not run under NT, which does not allow direct access to hardware resources. These programs will have to reside in a FAT partition in order to be access from MS-DOS.

    Use the following chart to decide which directory option is best for your installation:

    Previous OS and NT Installation Directory Migrates settings? Supports multiple-boot?
    Windows NT
    Same directory
    New directory
    Yes
    No
    No
    Yes
    Windows 95
    Same directory
    New directory
    N/A
    No
    N/A
    Yes
    Windows 3.x/ WfW
    Same directory
    New directory
    Yes
    No
    Yes??
    Yes

    Removing NT

    You can use either of the following methods to remove NT:

    Note: NO version of FDISK can remove an NTFS logical drive in an extended partition. Some MS-DOS FDISK cannot even delete an NTFS partition.

    Removing NT 4.0 from NT-DOS or NT-Win95 dual boot (FAT partitioin)

    Chapter 17: NT Boot Process

    Overview of the NT Boot Process
    Troubleshooting the Boot Process
    Last Known Good Configuration
    Emergency Repair

    Overview of the NT Boot Process

    platform filename what it does where
    Intel x86 Ntldr loads the NT OS System partition root

    all required for the NT Boot Disk
    Boot.ini builds the Boot Loader Operating System Selection menu
    Bootsect.dos contains the boot sector that was on the HD before NT installing. Loaded by Ntldr if another OS, such as DOS, Win9x, OS/2 1.x instead of NT is selected
    Ntdetect.com examines the hardware and build a list of it. This info is passed back to Ntldr to be added to the registry later in the boot process
    Ntbootdd.sys this driver access devices attached to the SCSI adapter during boot sequence. exists only when system boots from a SCSI HD and the BIOS on the SCSI adapter is disabled.
    Intel x86

    RISC

    		 Ntoskrnl.exe kernel file, starts the NT load phrase systemroot\System32
    Hal.dll Hardare Abstraction Layer, hides platform-specific hardware issues from NT. Is loaded after the Ntoskrnl.exe
    System a collection of system configuration settings. Controls which device drivers and services are loaded during initialization process systemroot\System32\config
    Device drivers such as Ftdisk (fault tolerance) and Scsidisk systemroot\System32\Drivers
    RISC Osloader.exe OS loader; equivent to Ntldr. os\nt40
    *.pal (Alpha only) contain PAL code, software subroutines that provide an OS with direct control of the processor os\nt40

    Note: Bootsect.dos exists ONLY on a dual-boot system; it contains info of the boot sector before NT installation.

    NT is loaded and initialized in four phrases:

    kernel load >>kernel initialization >>services load >>Win32 subsystem start

    1. Before loading NT kernel --

    1. Ntldr switches the processor from real mode into 32-bit flat memory mode.
    2. Ntldr starts the appropriate mini-file system drivers.
    3. Ntldr read the Boot.ini file, displays the Boot Loader Operating System Selection menu for user to select the operating systems contained in it.
    4. Ntldr loads the operating system selected by the user, or the default OS if no selection made.

      If an OS other than NT was selected (on a dual-boot computer), Ntldr loads and runs Bootsect.dos and passes control to that OS; the NT boot process ends at this point.
    5. Ntldr runs Ntdect.com. Ntdect.com scans the hardware and sends the list of it back to Ntldr for later inclusion in the registry under HKEY_LOCAL_MACHINE\HARDWARE
    6. Ntldr loads Ntoskrnl.exe -->

    2. Load Phases

    1. Kernel load -- begins when Ntoskrnl.exe is loaded. Then hal.dll (hardware abstration layer) is loaded.

      This portion of boot sequence occurs when the screen clears after Ntdetect.com has run, and progress dots (......) are displayed across the top of the screen. It is possible to display the names of the drivers being loaded on this screen by adding an /sos switch to the appropriate OS line in Boot.ini.

    2. Kernel initialization -- initializes the kernel and the drivers that were loaded during the kernel load phase. This stage occur when screen is painted blue.
    3. Service load -- starts the Session Manager (Smss.exe), which starts the higher-order subsystems and services for NT.
    4. Win32 subsystem start -- starts Winlogon.exe, which starts the Local Security Authority (Lsass.exe) and display the Ctrl+Alt+Del logon dialog box.
    5. User logs on.

    Note:

    Troubleshooting the Boot Process

    Most problems related to booting are caused by required files that are either missing or corrupted, or when incorrect system configuration changes are made.

    Note: Emergency Repair process (needs both NT Setup floppy disks and ERD, and maybe the installation CD too), or NT Boot Disk, can be used to recover the system and boot files, as would happen in the following situations, and return the computer to a bootable state.

    Symptom -- before the Boot Loader Operating System menu, the following message appears: 

    BOOT: Couldn't find NTLDR
Please insert another disk.
    Problem/Solution -- the NTLDR is missing. Use NT Boot Disk or ERD to replace the missing or corrupted file

    Symptom -- after the Boot Loader Operating System menu, the following message appears: 

    NTDETECT V4.0 Checking Hardware...
NTDETECT failed
    Problem -- the Ntdetect.com is missing.

    Symptom -- after the Last Known Good prompt, the following message appears: 

    NT could not start because the following file is missing or corrupt:
\winnt root\system32\ntoskrnl.exe
Please re-install a copy of the above file.
    Problem -- the Ntoskrnl.exe or Boot.ini is missing, or the NT path name in the Boot.ini is incorrect.


    Symptom     -- after the Boot Loader Operating System menu, the following message appears: 

    I/O Error accessing boot sector file
multi(0)disk(0)rdisk(0)partition(1):\bootss
    Problem -- the Bootsect.dos is missing, and the system has multiple-boot configuration.
    Note: Bootsect.dos stores partition info specific to the computer. This file cannot be borrowed from another computer. Bootsect.dos exists ONLY on a dual-boot system

    [boot loader]
    timeout=18
    default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="NT Server Version 4.00"
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="NT Server Version 4.00 [VGA mode]" /basevideo /sos
    C:\="Microsoft Windows"

    /basevideo -- is an optional parameter to allow user to boot the NT with a standard VGA driver.
    /sos -- to display device loaded during boot sequence
    C:\="Microsoft Windows"     -- for dual-boot between NT and Windows

    Other configuration options for loading NT

    /NoSerialmice=COMx, COMy, -- disable the serial mouse detection on COM port(s)
    /SCSIordial:n -- selects which SCSI controller to boot the OS when two identical controllers are in teh computer.
    /Maximum:n -- limits the amount of memory that NT will use
    /NoDebug -- do not monitor debugging info. This may give OS slight performance enhancement.
    /CrashDebug -- enable automatic recovery and restart (these can also be set from the Control Panel)

    The applet in Control Panel >>System >>Startup/Shutdown >>System Startup ... can only be used to change the options for the default OS and timeout value. To modify all other options, such as change the display of "NT Server Version 4.00" to "NT Server 4.0 for MCSE" you need to edit the Boot.ini manually.

    Solution to Boot.ini problems -- manually edit the Boot.ini file, correct the incorrect path or file names.

    Symptom -- after the Last Known Good prompt, the following message appears: 

    NT could not start because the following file is missing or corrupt:
<winnt root>\system32\ntoskrnl.exe
Please re-install a copy of the above file.
    Problem -- the Ntoskrnl.exe or Boot.ini is missing, or the NT path name in the Boot.ini is incorrect.
     
    Note: NT can boot successfully even when the Boot.ini file is missing, only if NT is installed in the default folder of:

    multi(0)disk(0)rdisk(0)partition(1)\Winnt, or
    scsi (0)disk(0)rdisk(0)partition(1)\Winnt

    Therefor, when the above message appears on a system where NT is installed in the default folder, you can deduce the problem is NOT due to missing the boot.ini file. More likely missing Ntoskrnl.exe or the path name is incorrect.

    Symptom -- after the Last Known Good prompt, the following message appears: 

    OS Loader V4.0
    NT could not start because of a computer disk hardware configuration problem.
    Couldn't read from the selected boot disk. Check boot path and disk hardware.
    Please check the NT (TM) documentation about hardware disk configuration and your hardware reference manuals for additional information.
     
    Problem -- invalid device in the path to NT in the Boot.ini file, e.g. when mixed up multi with scsi

    Symptom -- A "new" operating system: NT(default) appears on the Boot Loader Operating System Selection menu

    Problem -- the path name for the default parameter in the [boot loader] section does not match any of the path names in the [operating systems] section.

    Decide when to use NT Boot Disk, and when to use ERD (ER process)? only certain files (such as the afore-listed) can be loaded from a floppy disk, all other files are accessed from the hard disk. For example, if the NT kernel (Ntoskrnl.exe) or other files are corrupt or missing, the NT Boot Disk is of no use.

    If this is the case, use the Emergency Repair process to restore the missing or corrupt files.

    Last Known Good Configuration

    NT provides two configurations in which you can start your computer:

    There are only two conditions that cause the system to load the Last Known Good configuration:

    The Last Known Good control set is used ONLY to recover from problems caused by incorrect device or hardware configurations, such as when you installed a new device driver, video driver, or accidentally disabled a critical device driver and causes the NT not able to start. It does not solve problems caused by corrupt or missing drivers or files (in this case, use ERD or Boot Disk instead).

    Use the Last Known Good does not help in these situations:

    If you are having problems with startup, and think the problems might be related to the changes that you made to your configuration, do not log on. Instead, restart the computer; when you see the following message on the screen:

    press the SPACEBAR to invoke the Hardware Profile/Configuration Recovery menu.

    Note: If the Last Known Good is used, all configuration changes you made the last time you were logged on to the NT computer are lost.

    Emergency Repair Disk Utility

    You can use the Emergency Repair Disk utility (Rdisk.exe, in systemroot\System32 folder) to update the repair info for NT on your hard disk (stored in folder systemroot\Repair), or to create a new Emergency Repair Disk (ERD) using the repair info currently saved on your hard disk.

    The repair info on your hard disk or your ERD can be used to reconstruct NT system files, system configuration, and startup environment variables (i.e. appears in the Boot Loader Operating System Selection menu) if they become damaged. ERD or the Emergency Repair folder can return the NT system to the state of the last Emergency Repair update. (the \Repair folder and the ERD contains the same things -- most are info in the registry entries)

    It is strongly recommended that you create and update an ERD every time you make significant changes to your hardware or software setup. The Repair Disk utility should not be used as a backup tool.

    Note:

    Default._ a copy of the Default hive from the registry.
    Sam._ a copy of the Securiry Account Manager (SAM) from the registry.
    Security._ a copy of the Securiry hive from the registry.
     
    Setup.log -- another file included in the Emergency Repair foler and ERD, used to verify files on the system.

    Need what -- to repair a NT installation, NT Setup needs either the configuration info that is saved in the systemroot\Repair folder, or on the ERD. To perform the emergency repair process, you also need the following:

    How to perform a repair process, start NT Setup with the original Setup disks or CD, or winnt.exe, just as you did originally >>in the text-based Setup sceen that asks whether to install or repair files, type r to repair >>use the ERD as prompted ... you choose which of the tasks to be performed:

    [X] Inspect registry files -- Setup replaces one or more registry files with the files that were created when NT was first installed, or when the Emergency Repair folder or ERD was last updated. All changes made to the system since installation or the last update to the repair files are lost.
    [X] Inspect startup environment -- if NT is installed but does NOT appear in the bootable systems, select this option. ERD is needed for this option.
    [X] Verify NT system files --
    [X] Inspect boot sector -- select this option if NO system that is installed on the computer boots. Setup copies a new boot sector to the hard disk.

    Note: If the original Setup disks cannot be located, use winnt.exe /ox or winnt32.exe /ox to create a new set. The /ox switch creates Setup disks only, without performing the entire installation.

    Chapter 3: Configuring NT Environment

    NT registry
    Modifying Setting Using Control Panel
    Modifying System Settings Using Control Panel
    Modifying System Settings Using Registry Editor

    NT Registry

    Abstract From <<all road to NT >>

    NT Registry Objectives

    The Registry is not a record of an NT system configuration. It contains values that are not the the system defaults, AKA, data in the Registry -- is the exception. NT supports a maximum registry size of 108 MB.

    Hive Description
    HKEY_CLASSES_ROOT Establishes OLE file associations (retained for  backward compatibility)
    HKEY_CURRENT_USER Displays user profile information for the user  currently logged in
    HKEY_LOCAL_MACHINE Manages hardware and software configuration,  installed drivers, and security
    HKEY_USERS Provides user profile information for all users
    HKEY_CURRENT_CONFIG Displays the currently used hardware profile (a  subset of HKEY_LOCAL_MACHINE)
    HKEY_DYN_DATA ?? Provides temporary storage for the state of dynamic events and performance information

    NT Registry Tools

    Regedit - can be used search for keys, values, and data throughout the entire Registry at once.
    Regedt32 - can only search for keys. However, REGEDT32 can be used to alter any security settings

    NT Registry Backup Tools

    Modifying Setting Using Control Panel

    Many settings in the registry are configured using the programs in Control Panel.

    Modifying System Settings Using Control Panel

    Control Panel >> System

    A hardware profile stores the configuration for a set of devices and services. NT can store different hardware profiles to meet a uesr's needs. For example, a portable computer user could create hardware profiles for docked and undocked state, and choose appropriate profile when starting the OS.

    NT uses a process called demand paging to swap data between RAM and one or more paging files (Pagefile.sys) located on one or more hard drives.

    Default Size of Paging File:

    Configuring the Paging File:
    Control Panel >> System >> Performance >> Virtual Memory >> Change

    Options to improve system performance:

    Setting Environment Variables

    Control Panel >> System >> Environment

    Environment Variables are info about drive, path, or file name for NT to control the behavior of various applications. For example, the TEMP specifies the location where applications place temporary files.

    The Environment tab displays two types of enviroment variables currently in effect:

    Any user can add, modify, or remove a user environment variable, but only an administrator can add, modify, or remove a system environment variable.

    By default, NT searches the C:\Autoexec.bat (NOT Autoexec.nt !), if one exists, and sets any environment statements. For example, the PATH statement in the C:\Autoexec.bat is automatically appended to the default system path every time any user logs on.

    NT sets environment variables in this order:

    1. Autoexec.bat variables
    2. System environment variables
    3. User environment variables

    The priority order is User environment variables > System environment variables > Autoexec.bat. For example, if the line "SET TMP=C:\" is placed in Autoexec.bat and a user variable "TMP=X:\TEMP" is set, the User variable overrides the prior setting. Therefore, the TMP environment variable is equal to X:\TEMP.

    To prevent NT from searching the C:\Autoexec.bat (ONLY administrators can do it)

    Adding and Removing NT Components

    Modifying System Settings Using Registry Editor (regedt32.exe vs regedit.exe)

    Important Points:

    Appendix: Configuring NT

    System settings affect every user of the system, only member of the Administartors group can modify them.

    To create additional Hardware Profiles: >>Control Panel >>System >>Hardware Profiles >>choose an existing one >>Copy...

    You modify which device and services to use with that profile from the Device and Services icons in the Control Panel. Both have a HW Profiles... button for this task.