<<< Back




Choose the help section for Windows NT: Windows NT FAQ


  • Windows NT FAQ (Part 1)
  • Windows NT FAQ (Part 2)
  • Windows NT FAQ (Part 3)
  • Windows NT FAQ (Part 4)

  • How to make launch of 16bit programs in a separate address space automatic?

    1. Run Regedt32.exe.
    2. Open the registry key
      HKLM \ SYSTEM \ CurrentControlSet \ Control \ WOW \
    3. Set DefaultSeparateVDM to "yes".

    How to create a new Emergency Repair Disk or update information on a previously created one?

    1. Run the RDISK.EXE program from the% SYSTEMROOT% \ SYSTEM32 directory.
    2. Click the Update Repair Info button first.
    3. At the end of the upgrade process, click the Create Repair Disk button.
    To enable SAM and SECURITY RDISK.EXE registry keys to be updated, start with the / S switch.

    After changing some parameter in the Control Panel, the computer began to "slow down" at boot. Why?

    Most likely, you have disabled the Remote Procedure Call (RPC) Service. Set the startup of this service back to Automatic and reboot.

    Advice for the future: do not change those parameters whose values ​​you do not know, it will not become better, but worse - easily.

    Why are not Win16 programs running?

    • You may have overloaded the% PATH% environment variable or included it in the autoexec.nt file.
    • The file command.com is corrupted, destroyed, or replaced with a file of a different version.
    • The ver.dll file is destroyed, corrupted, or overwritten by a file of a different version.
    • In the file % systemroot% \ system32 \ autoexec.nt there is a call to share.exe (or vshare.exe ).
    • Perhaps there is too little room for the environment variables. Try to insert the following line into the config.nt file:
      Shell =% systemroot% \ system32 \ command.com / p / e: 4096
    • The WOW files may be corrupted. Restore your Windows NT installation, and reinstall the Service Pack.

    Why, after denying access to system directories, the group Everyone Windows NT refuses to boot?

    In English, the word "Everyone" means "Everything". You have denied access to everyone , including an operating system that has a built-in SYSTEM account. It will only help restore information about file protection. Run WINNT.EXE from the distribution and select the Repair mode.


    Service Packs

    How to install hotfixes for the English version on Russian NTWS?

    1. Unpack the required fix by running it with the / x key.
    2. In the directory in which you unpacked the fix, find the file with the extension .inf . Open it in any editor (double-click in the Explorer you will open it in Notepad).
    3. In the [Strings] section, change the value of LangTypeValue = 9 to LangTypeValue = 25 and save the file.
    4. Now you can install the fix by simply running hotfix.exe .

    Can I install the Nth Service Pack without installing the previous Service Pack?

    Yes. Since each subsequent Service Pack includes the previous ones.

    Problems with printing pages with a resolution of 600dpi after installing on the machine SP3

    It is advisable to save somewhere before installing SP3. The contents of the \% SystemRoot% \ SYSTEM32 \ SPOOL \ DRIVERS \ W32X86 \ 2 \ directory, and after installation, return all files to the location. If you did not save these files before installing SP3, try to track down their old versions.


    Disks, file systems

    How to switch from FAT to NTFS?

    Run the program CONVERT.EXE from the directory
    % SYSTEMROOT% \ SYSTEM32. It should be noted that you do not need to format the partition for conversion.

    How to switch from NTFS to FAT?

    There is no non-destrucive method for today. You can only switch from NTFS to FAT by creating a backup and formatting the disk (partition) using FAT.

    How to make boot floppy for Windows NT, which will allow to access mirrored disks?

    1. Format the floppy from under WIndows NT
    2. Copy it to ntdetect.com and ntldr from your root directory
    3. If you are using a SCSI card without BIOS, copy the SCSI driver from the system32 \ drivers directory to the ntbootdd.sys file on the floppy disk.
    4. Create the following boot.ini by pattern:

      [Boot loader]
      Timeout = 0
      [Operating systems]
      Default = scsi (0) disk (0) rdisk (0) partition (1) \ winnt = "Windows NT Server"

      Attention! You should be familiar with the rules of writing ARC-paths in order to correctly write the last line!

    Can I enable HPFS wildcards in Windows NT 4.0?

    Yes, you need to do the following:
    1. Take from the Windows NT 3.51 distribution the driver pinball.sys and copy it to % systemroot% \ system32 \ drivers .
    2. In the registry key HKLM \ SYSTEM \ CurrentControlSet \ Services add a pinball connection.
    3. In the created pinball add values:

      Name A type Value
      ErrorControl REG_DWORD 0x1
      Group REG_SZ Boot file system
      Start REG_DWORD 0x1
      Type REG_DWORD 0x2

    4. To restart a computer.

    What do the lines in boot.ini (multi (0) disk (1) ...) mean?

    The following text is a translation of fragments from Microsoft Windows NT Resourse Kit, copyrights belong to Microsoft.
    Only those fragments that relate to x86-based computers are listed.

    Naming conventions Advanced RISC Computing (ARC) are the standard for locating files or programs on disk drives: hard disks (HDD) or floppy (FDD, floppy).

    On x86 computers, the ARC paths in boot.ini describe the location of the boot partition for each installed copy of Windows NT.

    ARC-ways are of two types:

    • Multi (W) disk (X) rdisk (Y) partition (Z) \% systemroot%
    • Scsi (W) disk (X) rdisk (Y) partition (Z) \% systemroot%

    Multi (W) disk (X) rdisk (Y) partition (Z)

    Syntax multi () means that the Windows NT system must rely on the BIOS when booting the system files. That is, NTLDR, the bootloader, will use BIOS INT 13 interrupt calls to find and load Ntoskrnl.exe and other necessary files to download the system.

    The parameters W, X, Y, and Z have the following values:

    • W is the controller serial number, always equal to 0.
    • X is not used in multi () , is always 0.
    • Y is the serial number of the disk connected to the controller. This parameter can be set to 0 or 1 when using the standard IDE controller (or SCSI with BIOS enabled), or from 0 to 3 when using the dual-channel EIDE controller.
    • Z is the partition number. Unlike all other parameters whose values ​​start from zero, the minimum value of the partition number (Z) is 1.

    Theoretically, the multi () syntax can be used to boot Windows NT from any drive in the computer. At the same time, these disks must be correctly recognized through the standard interface INT 13, which is not supported in every system. Most BIOS can "see" with INT 13 only one controller.

    In the configuration with IDE or EIDE disks, the multi () syntax supports up to four disks. When using only SCSI - the first two drives on a SCSI controller whose BIOS is booted first. If your computer uses both IDE (EIDE) and SCSI, the multi () syntax can only be applied to IDE or EIDE disks.

    Scsi (W) disk (X) rdisk (Y) partition (Z)

    Using the syntax scsi () tells Windows NT to load the SCSI driver and use it to access the boot partition.

    On x86 computers, this driver is called Ntbootdd.sys and is located at the root of the system disk (usually C :) . Ntbootdd.sys is a copy of the driver used to boot the SCSI controller.

    The parameters W, X, Y, and Z have the following values:

    • W is the serial number of the controller (in the order in which the driver determines it).
    • X - SCSI ID of the disk containing the boot partition.
    • Y - SCSI logical unit number (LUN) of the disk containing the boot partition. Y is overwhelmingly equal to 0.
    • Z is the partition number. Unlike all other parameters whose values ​​start from zero, the minimum value of the partition number (Z) is 1.

    If you use the syntax scsi (), the value of W depends on Ntbootdd.sys. Each SCSI driver used in Windows NT can have its own way of determining the serial number of the controller. Although usually this order coincides with the order of BIOS load (if, of course, the BIOS on the controllers is enabled).

    If you use more than one controller and their models are different, only those controllers that are supported by the Ntbootdd.sys driver should be considered to determine the W parameter. For example, if you have one Adaptec 2940 using Aic78xx.sys, and one Adaptec 1542 using Aha154x.sys, the W parameter will always be 0.

    • If you boot Windows NT from disk to Adaptec 2940, Ntbootdd.sys should be a copy of Aic78xx.sys.
    • If you boot Windows NT from disk to Adaptec 1542, Ntbootdd.sys should be a copy of Aha154x.sys.


    Automatic registration (autologon)

    How to make the system boot bypassing Logon (do autologon)?

    1. Run the program% SYSTEMROOT% \ System32 \ regedt32.exe.
    2. Open the registry key HKLM \ SOFTWARE \ Microsoft \ WindowsNT \ CurrentVersion \ Winlogon
    3. Set the values:

      Name A type Value
      AutoAdminLogon REG_SZ 1
      DefaultUserName REG_SZ Username
      DefaultPassword REG_SZ User password (must be non-empty!)
    Naturally, this user must exist and have the right to Logon Locally.

    If you use a Novell Netware client, the autologon procedure will change slightly. In addition to the above steps, create or edit the following parameters in the HKLM \ SOFTWARE \ Novell \ NWGINA \ Logon Screen registry key:

    Name A type Value
    NetWareAutoAdminLogon REG_SZ 1
    DefaultNetWareUserName REG_SZ Username
    DefaultNetWarePassword REG_SZ User password (must be non-empty!)

    Autoline is switched on by car. Is it possible to register under a different name in this case?

    Yes. When the system boots, hold down the Shift key.

    If the system is already loaded, you can use one more way: lock the console, then unlock it using a different name and password. However, remember: only administrators have the right to unlock the console, so this method is by no means universal.


  • Windows NT FAQ (Part 1)
  • Windows NT FAQ (Part 2)
  • Windows NT FAQ (Part 3)
  • Windows NT FAQ (Part 4)