


######     ####    ############            Microsoft
#######    ####    ############
########   ####        ####        Windows New Technology (NT)
#### ####  ####        ####
####  #### ####        ####         Frequently Asked Questions
####   ########        ####
####    #######        ####               October 1992
####     ######        ####

-----------------------------------------------------------------------

			   TABLE OF CONTENTS


1.      GENERAL INFORMATION

1.1.    Obtaining the Windows NT beta release
1.2.    Manuals for the Windows NT SDK update
1.3.    Development Issues belong in the MSWIN32 Forum
1.4.    Obtaining the Windows NT DDK Preliminary release

2.      INSTALLATION AND SETUP

2.1.    Flexboot keeps returning to Flexboot instead of MS-DOS.
2.2.    Windows NT Boots, Looking for the Wrong Boot Directory:
2.3.    NTFS on MIPS R4000
2.4.    Windows NT needs 600K free
2.5.    PS/2 Model 90 Locks up or has BOOT I/O on install
2.6.    PS/2 hangs when searching for SCSI adapter
2.7.    $WIN_NT$.~LS directory
2.8.    Setup fails when booting from text to GUI setup

3.      HARDWARE INFORMATION

3.1.    System Requirements
3.2.    Hardware Compatibility List (HWFEED.TXT)
3.3.    MIPS Installation
3.4.    Full Screen MS-DOS Support for MIPS
3.5.    Device Driver Requests
3.6.    DELL Machine Only Recognize 16 MB of Memory
3.7.    Bernoulli and Removable Media Not Supported
3.8.    Adaptec AHA 1542B Driver Can Cause Fatal System Error
3.9.    SoundBlaster/AudioPro
3.10.   Cannot Print to LPT1
3.11.   Installing a CD player after Windows NT has been installed.
3.12.   Activating CD Audio
3.13.   SCSI and ESDI drives greater than 1024 cyl.
3.14.   Windows NT will not install on IBM PS/2 Model 90 and 95
	Systems
3.15.   Soundblaster Pro only supported in Mono mode
3.16.   Additional Video drivers like the 8514 and ATI Ultra
3.17.   TSENG Labs ET4000 doesn't sync
3.18.   Can't play audio CD's with Future Domain SCSI Controller

4.      TECHNICAL INFORMATION

4.1.    IBM MOST Not Supported with Windows NT Flexboot
4.2.    Couldn't find NTLDR
4.3.    MS-DOS Device Drivers in CONFIG.SYS
4.4.    The System Uses Between 70 and 130 threads.
4.5.    How the LibPath environment variable works
4.6.    File Compression Programs and Drivers
4.7.    WOW Apps that don't work
4.8.    /S switch is disabled from Remove Directory (RMDIR)
4.9.    Using fault tolerance mirroring in Windows NT
4.10.   OS/2 subsystem takes priority
4.11.   ANSI ESC not supported for a command prompt
4.12.   Extended and Expanded memory for MS-DOS applications.
4.13.   File System Conversion.
4.14.   Change the default startup operating system
4.15.   Time Zone Problem

5.      NETWORK INFORMATION

5.1.    TCP/IP Support
5.2.    Replication
5.3.    Network fails to start

6.      COMMON ERROR MESSAGES

6.1.    Error 0000001E
6.2.    NTVDM error when running MS-DOS or WIN3.1 Apps
6.3.    Error 0x00000069 or Error 0x00000067
6.4.    Fatal System Error 0x0000000A
6.5.    System Error F002
6.6.    Setup fails with a SCSI read request error
6.7.    Error X00000022 - Generic Bugcheck
6.8.    Fatal Kernel Error 006E or 0071.

Other Files of Interest. These files can be found in the WINNT forum in
			 the library specified :

       General Information :

	1092HW.TXT      Library 1       Latest Hardware Compatibility
					List for the October release

	1092HW.DOC      Library 1       Word for Windows version of
					1092HW.TXT.

	HWFEED.TXT      Library 1       Feedback form to request support
					for a device from Microsoft

	WINNT.CAT       Library 1       List of all files available in
					WINNT forum libraries.

       Bug Reporting :

	BUGREP.TXT      Library 3       Template you can use to report
					bugs to Microsoft

	SAMPLE.TXT      Library 3       Sample, completed BUGREP.TXT
					file for guidance

	REPRTREG.EXE    Library 3       Dumps configuration information
					from registry to a text file.



=====================================================================
1.      GENERAL INFORMATION
=====================================================================

1.1.    Subject : Obtaining the Windows NT beta release

Question : How can I get the beta version of Windows NT?

Answer : There are two programs: The Win32 Preliminary SDK for Windows NT
	 and the Windows NT Beta program.

   I. Win32 Preliminary SDK for Windows NT

      The Win32 Preliminary SDK for Windows NT is offered for
      software developers who need to either develop applications
      for the Windows NT operating system or to port existing
      applications to 32-bit.

      The Win32 Preliminary SDK for Windows NT provides you with
      access to the broader capabilities of the Win32 API with
      features such as preemptive multitasking, multi-threading,
      32-bit flat memory model,and security. By purchasing the Win32
      SDK you will receive preliminary and final versions of the
      Windows NT operating system and SDK tools in addition to
      preliminary versions of a C/C++ compiler. For complete system
      requirements please download the Win32 Preliminary SDK
      data sheet (SDKDAT.DOC or SDKDAT.RTF in Library 1 of the
      MSWIN32 forum) and the hardware compatibility list
      (1092HW.TXT in Library 1 of the WINNT forum).

      The cost of the Win32 SDK with printed documentation is $399. A
      CD-only version containing the documentation in PostScript format
      is also available for $69. To order from within the U.S, please
      call Microsoft Developer Services at (800) 227-4679 ext. 11771. In
      Canada, call (800) 563-9048. In all other countries, contact your
      local Microsoft representative.


 II. Windows NT Beta Program

      Distribution of Microsoft Windows NT, October Beta is currently
      only available to a limited  number of sites.  However, we will
      increase the number of beta sites over the coming months.  If
      you wish to register your interest in the program, you may
      choose to do one of the following:

      1) Send a letter to

	   Microsoft Corporation
	   One Microsoft Way
	   Redmond, WA 98052
	   Attention: Microsoft Windows NT Beta Program 4/1

      2)   Send a facsimile to (206) 936-7329 to the attention of
	   "Microsoft Windows NT Beta Program, 4/1".  Please send only
	   typed or printed submissions.

       In either case you should include:

	 Name:
	 Company Name:
	 Title:
	 Address (no p.o. boxes):
	 Phone/Fax#:
	 Hardware configuration:
	 Any other related information:

	 This does not automatically ensure your enrollment in the Beta
	 program, however we will seriously consider all inquiries.


=====================================================================

1.2.    Subject : Manuals for the Windows NT SDK update

Question : I didn't get any manuals or release notes in my SDK update
	   for October. How do I get them?

Answer : Documentation for the SDK is included on the CD-ROM in the
	 \DOC\ENDUSER directory. Please check the README.TXT in the \DOC
	 directory for a complete listing of Programming References and
	 other documentation that is included with your CD-ROM.



=====================================================================

1.3.    Subject : Development Issues belong in the MSWIN32 Forum

Question : Where should I ask questions about the Win32 SDK? Can I ask
	   them WINNT Forum?

Answer : SDK programming questions are answered in the MSWIN32 Forum.

	 WINNT is dedicated to end-user issues about Windows NT (for
	 example installing/setting up the Windows NT operating system
	 itself), MSWIN32 is dedicated to developer issues about Windows
	 NT (for example installing/setting up the SDK for Windows NT,
	 API questions, etc)

	 The more we can all stick to the organization for the
	 forums/sections that the release notes mention, the easier it
	 will be for all forum readers to efficiently get to the info
	 they need.  Thanks!

=====================================================================

1.4.    Subject : Obtaining the Windows NT DDK Preliminary release

Question : How can I get the Preliminary Release of the DDK for Windows NT?

Answer : The Preliminary DDK will be available before the end of
	 November.  The cost is as follows:

	 DDK CD-ROM only                                        $69
	 DDK CD-ROM with hard-copy documentation               $399

	 This pricing includes updates and the final version of the DDK.
	 The documentation will be included on the CD in both Postscript
	 and Write format, and all the device driver functions will be
	 documented in Winhelp.

	 If you are in the US and currently own the Win32SDK, you will
	 be receiving a mailing on the DDK in mid-November which will
	 include 4-page product datasheet and an order coupon.   To
	 order from within the U.S, please call Microsoft Developer
	 Services at (800) 227-4679. In Canada, call (800) 563-9048. In
	 all other countries, contact your local Microsoft
	 representative.

	 International customers should contact their local MS office
	 for ordering, pricing and availibility information.

	 One other important change which you should be aware of.
	 Everyone who purchases the hard-copy documentation for the DDK
	 will receive the new book "Inside Windows NT" from MS Press.
	 This book will not be on the CD.




=====================================================================
2.      INSTALLATION AND SETUP
=====================================================================

2.1.    Subject : Flexboot keeps returning to Flexboot instead of MS-DOS.

Question : Whenever I select the Flexboot to boot MS-DOS it keeps returning
	   me to the selection menu?

Answer : This happens when installing Windows NT over a previously
	 existing Windows NT installation without doing a MS-DOS SYS C: to
	 the active partition. When Windows NT installs it will read the
	 boot sector from the drive and create a BOOTSECT.DOS that
	 Windows NT will use when you select the PREVIOUS operating
	 system choice.

	 If, for some reason, the install process reads a Windows NT
	 boot sector and uses this to create the BOOTSECT.DOS, it will
	 use the previous Windows NT boot sector when you select the
	 Previous operating system from Flexboot.

	 There are two ways to fix this:

	 1) If you have a previous copy of BOOTSECT.DOS, simply replace
	    the current version with the previous version.

	 2) If not, you will need to recreate the boot sector for MS-DOS by
	    booting from a MS-DOS diskette and executing SYS C: from that
	    disk. Doing this will also remove the Flexboot feature from
	    your system and you will need to reinstall Windows NT to
	    re-enable this feature.

=====================================================================

2.2.    Subject : Windows NT Boots, Looking for the Wrong Boot Directory:

Question : Windows NT looks in the wrong boot directory. Why?

Answer : This can happen for a few reasons. 

	 1) There  has been an installation of the Beta release over an
	    earlier release of Windows NT.  The boot.ini file is not
	    updated correctly.

	    Solution: Make sure that the boot.ini file contains
	    references to the WINNT directory rather than the NT
	    directory i.e.

		 C:\WINNT\ rather than C:\NT\

	 2) The IBM MOST utility for OS/2 2.0 is installed on the hard
	    drive.

	    Windows NT uses  logical partitioning.  The MOST partition
	    is an unknown partition type.  When an unknown partition
	    type sits between the base partition and the Windows NT
	    partition, it can set the logical partitions off by one.
	    MOST is not supported with Windows NT.

	    You should install Windows NT on a machine that  does not
	    have the MOST utility installed.

=====================================================================

2.3.    Subject : NTFS on MIPS R4000

Question : Can I convert my MIPS system partition to NTFS?

Answer : No. The ARC specification requires that the system partition be
	 FAT.  This is done so that HAL.DLL and OSLOADER.EXE will be
	 accessible regardless of the media type.  If you want to use
	 NTFS on a MIPS machine, create a small system partition (1M or
	 larger) to hold HAL.DLL and OSLOADER.exe.  The rest of the disk
	 can be used as an NTFS partition.  The installer correctly puts
	 HAL.DLL and OSLOADER on the system partition.

	 Note: DO NOT use CONVERT.EXE on the system partition. It will
	 convert it to NTFS and the system will not boot.  If this
	 happens, your only option is to run ARCINST.EXE from the
	 install CD-ROM and reformat the system partition as FAT.


=====================================================================

2.4.    Subject : Windows NT needs 600K free

Question : When I start up Windows NT, it gives the following error :

	   Windows NT has found only xxxxK of low memory, 600K of low
	   memory is required to run Windows NT. You may need to upgrade
	   your computer or run a configuration program provided by the
	   manufacturer.

Answer : In order to start Windows NT there must be at least 600K of low
	 memory to start it. You may have to do some configuration
	 changes to get this to work correctly.

=====================================================================

2.5.    Subject : PS/2 Model 90 Locks up or has BOOT I/O error on install

Question : When I am installing the October beta release of Windows NT
	   on my PS/2 model 90, right after it copies default.$, it
	   either locks or returns a BOOT I/O error.

Answer : Chances are, your system is a OLF version PS/2 Model 90. The
	 October Beta release of Windows NT will not install on a
	 version OLF. It is important to us to get this problem
	 resolved, and we are moving toward a solution as fast as we
	 can.

	 You may check the version of your PS/2 90 by examining the
	 front right-hand corner of the PS/2's case through the back, or
	 by removing the case cover and viewing the label directly.

===========================================================================

2.6.    Subject : PS/2 hangs when searching for SCSI adapter

Question : While installing the October beta release of Windows NT on my
	   PS/2, it hangs right after it searches for 3rd party SCSI
	   adapters. What should I do?

Answer : Check to see if your IBM SCSI adapter has a 1991 BIOS chip. At
	 this time, it is not possible to install the October Beta
	 release of Windows NT on a machine that has this chip set. It
	 will be necessary for you to use either another supported SCSI
	 adapter or an IBM adapter with a BIOS date other than 1991.

	 You may check the date of your SCSI BIOS by examining the card
	 and looking at the end of the adapter closest to the front of
	 the machine. You should be able to see a chip that has a paper
	 sticker on the contains the SCSI BIOS date.

=====================================================================

2.7.    Subject : $WIN_NT$.~LS directory

Question : After I attempted to install, Windows NT left a directory
	   named "$WIN_NT$.~LS" on my hard disk. What is it? Is it OK to
	   delete it?

Answer : This is a temporary directory created by the WINNT.EXE
	 installation program. The WINNT.EXE program copies all the
	 setup files it needs to your hard disk, then reboots into
	 Windows NT and runs setup off of  your hard drive.

	 When Setup is completed, it should remove these temporary
	 files, but if you encounter an error during setup or when setup
	 tries to remove these files, they will remain on your disk.

	 In any case, it is OK to delete the entire $WIN_NT$.~LS tree from
	 your hard drive.

=====================================================================

2.8.    Subject : Setup fails when booting from text to GUI setup

	See Fatal Kernel Errors 0000006E and 00000071 in the 
	"COMMON ERROR MESSAGES" section.

=====================================================================
3.      HARDWARE INFORMATION
=====================================================================

3.1.    Subject : System Requirements

Question : What are the minimum hardware requirements to run Windows NT?

Answer : Windows NT operating system:

   The first beta release Windows NT operating system requires an Intel
   80386 system or higher with at least 8 MB of RAM (12 MB is
   recommended for this release), or ACE/ARC compatible RISC-based
   computer with 16 MB of RAM such as a MIPS R4000. This system should
   have about 35 MB of free disk space for Windows NT, plus 20 MB for
   virtual memory paging file. This does not include disk space for
   applications.

   Win32 SDK development environment:

   For Win32 SDK development, an 80386 33 MHz CPU (or higher) and 12MB
   total of RAM is strongly recommended.  A total of 100MB available
   hard disk space (includes 20MB for a swap file) is required for
   complete installation of the operating system, SDK tools, and C/C++
   compiler.

   The Win32 SDK is only available on CD-ROM and requires a CD-ROM
   drive and SCSI adapter.

=====================================================================

3.2.    Subject : Hardware Compatibility List (HWFEED.TXT)

Question : How do I know if my hardware is supported and what do I have
	   to do to get support?

Answer :  Microsoft provides a list of hardware that has been tested and
	  is known to work with Windows NT. It has been posted on
	  Compuserve, forum WINNT, Library 1, filename : 1092HW.TXT. For
	  your convenience the hardware list is also available in Word
	  for Windows format and called 1092HW.DOC. The Hardware listed
	  in this file has been tested on the October release of Windows
	  NT and is supported.

	  Microsoft does not claim that hardware not on this list will
	  not run; however, it has not been tested and it is not
	  supported at this time.

	  If you would like to get support for your hardware, in the
	  WINNT forum, Library 1, there is a form - HWFEED.TXT. Fill out
	  this template with the hardware you need support for and mail
	  it via CompuServe mail to the Internet address listed in the
	  form. Information from these surveys is compiled by the
	  development team to help clarify where support is needed most.

	  Also, since many drivers are being written by third party
	  companies, contact your vendor to indicate that you need a
	  driver for their hardware to run under Windows NT. This will
	  help expedite the process external to Microsoft as well.

=====================================================================

3.3.    Subject : MIPS Installation

Question : Windows NT will not work on my MIPS machine.

Answer : The October release of Windows NT requires an upgrade to your
	 MIPS machine.  All manufacturers are aware of this upgrade.  If
	 they have not contacted you already, please contact them
	 regarding it. The machine's CPU must also have an R4000
	 revision 2.0 or greater.

=====================================================================

3.4.    Subject : Full Screen MS-DOS Support for MIPS

Question : How do I get Full screen MS-DOS support on my MIPS Machine?

Answer : Full screen support is not and will not be provided with
	 Windows NT on MIPS systems.

=====================================================================

3.5.    Subject : Device Driver Requests 

Question : Is there a driver yet for my hardware?

Answer : Microsoft's standard means of releasing drivers is with their
	 CD releases. Although Microsoft is not committed to continue
	 this practice, currently all fixed, updated, or new device
	 drivers are being posted on the CompuServe Forum: WINNT,
	 Library 2. Microsoft is currently making every attempt to keep
	 this library updated with drivers as they become available. If
	 you have hardware that is not currently supported, or does not
	 have a driver posted in WINNT, Library 2; please make a device
	 driver request by filling out the HWFEED.TXT form (appendix B
	 to this FAQ) and mail it to Microsoft at winnthw@microsoft.com.
	 ( "internet:winnthw@microsoft.com" if you are sending mail from
	 CompuServe).

	 Please be aware that because of Microsoft's support demands
	 right now, this is a one way alias; Microsoft will not  respond
	 directly to you to confirm that they have received your
	 request.

	 The hardware compatibility list and HWFEED.TXT file can be
	 found in WINNT, Lib 1 on CompuServe as 1092HW.TXT and
	 HWFEED.TXT.


=====================================================================

3.6.    Subject : DELL Machine Only Recognize 16 MB of Memory

Question : Windows NT does not  recognize memory above 16MB on my
	   Dell machine.

Answer : The ISA Dell 486D/50 25/50Mhz has a BIOS problem which prevents
	 it from seeing greater than 16MB of RAM under NT.

	 The ISA Dell 486D/50 25/50Mhz machine does not see greater than
	 16Mb of RAM under Windows NT.  This is a known problem with the
	 BIOS of the Dell machine.

	 If your machine  demonstrates this problem, please contact Dell
	 to receive their A08 BIOS upgrade.

=====================================================================

3.7.    Subject : Bernoulli and Removable Media Not Supported

Question : Can I use my Bernoulli drive even though it is not listed in
	   the hardware compatibility list?

Answer : Bernoulli boxes and removable SCSI drives were not tested with
	 this release of Windows NT, and do not appear on the hardware
	 compatibility list.  Since the release there is evidence that
	 Windows NT has some problems with these devices.  Microsoft is
	 aggressively pursuing this matter in hopes of having it
	 resolved by the next release.

=====================================================================

3.8.    Subject : Adaptec AHA 1542B Driver Can Cause Fatal System Error 

Question : Help! I am having problems and I have an Adaptec controller.

Answer : There is a known problem with the Adaptec AHA-1542B driver which
	 causes fatal system errors under some circumstances.

	 The problem is triggered by simultaneous I/O with the floppy
	 and the hard disk.  This will be corrected in the next release.
	 To avoid this you may want to use an alternative floppy
	 controller and disable he one on the Adaptec.

=====================================================================

3.9.    Subject : SoundBlaster/AudioPro

Question : How can I get my SoundBlaster/AudioPro card working 
		    properly?

Answer : Many times this problem can be solved by installing the
	 Creative Labs driver supplied on the Windows NT Setup CD.
	 However, there are some 486 systems and some system chip sets
	 that are not fully compatible with the SoundBlaster/AudioPro
	 card.  If find the following answer does not get your
	 SoundBlaster card working - file a bug report.

      1) The Creative Labs Sound Blaster driver may not be installed
	 yet. You may use the Control Panel's Drivers option to install
	 the Creative Labs Sound Blaster 1.X driver (that is provided on
	 your Windows NT CD) After installing you should configure the
	 driver for the proper IRQ and address.

      2) There may be an IRQ conflict with another device. Either change
	 the IRQ setting on the other device or on the sound card. The
	 default settings for the sound card is DMA 1, IRQ 7 and port
	 220h (note however that LPT1 also uses IRQ 7).  We suggest
	 physically changing the SoundBlaster to IRQ 2 and then using
	 the Control Panel's Drivers option to reconfigure the Creative
	 Labs Sound Blaster 1.X driver to IRQ 2.

      3) You can play WAV files but not MID files. This usually means
	 you still need to install the AD-LIB MIDI driver. The MIDI
	 driver may be installed via the Control Panel's Drivers option.

=====================================================================

3.10.   Subject : Cannot Print to LPT1

Question : I cannot print to LPT1:!  If I type "MODE LPT1:" it claims the
	   device is not found.  What is wrong?

Answer : Typically LPT1: uses interrupt 7 which is also the default
	 setting of the SoundBlaster sound card.  You may be
	 experiencing a IRQ conflict with this or another device.  If
	 you are unable to resolve the conflict you can disable one of
	 the devices in the Registry.

	 The utility REGEDIT is provided to alter the Registry Database.
	 Note: in many cases you must be logged on as 'Administrator' to
	 alter some of the Registry settings.  Hardware configuration
	 (driver) settings can be altered under the Registry branch:

	 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

	 The SoundBlaster can be disabled or enabled by changing the
	 value of the "Start" entry for ...\Sevices\Sndblst  to the
	 appropriate start value (Start=0x4 to disable, Start=0x1 to
	 enable).

	 Similarly, the parallel driver can be  disabled/enabled by
	 changing the "Start" entry for ...\Services\Parallel  to 0x4 or
	 0x1 as above.

=====================================================================

3.11.   Subject : Installing a CD player after Windows NT has been
		  installed.

Question : If you install a new CD player after Windows NT has been
	   installed, what section of the registry do you edit so that
	   NT recognizes the new CD?  And what are the values?

Answer : The utility REGEDIT is provided to alter the Registry Database.
	 Note: in many cases you must be logged on as 'Administrator' to
	 alter some of the Registry settings.  Hardware configuration
	 (driver) settings can be altered under the Registry branch:

	 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

	 Make sure the driver for your SCSI adapter is enabled by
	 checking that the "Start" value for it is set so "Start=0".

	 Also be sure to set the "Start" value for SCSICDRM to 0. You
	 can find this listed under "...\Services\Scsicdrm".
	
	 If the drive doesn't support SCSI-2 CD Audio, then you may want
	 to enable the CDAUDIO driver as well. You can find this listed
	 under ...\Services\Cdaudio.

=====================================================================

3.12.   Subject : Activating CD Audio

Question : My supported SCSI CD-ROM drive doesn't play AUDIO CD's, what
	   should I do to get it to work?

Answer : The scsicdrm.sys is the primary SCSI CD-ROM driver supplied by
	 Windows NT. This driver covers most SCSI-II CD-ROM drives and
	 should work under the following conditions.

      1)  The drive is a SCSI-II CD-ROM drive.

      2)  The SCSI controller is supported and NOT Fd850 (sorry). (a
	   bug has already been filed on the FD850 SCSI controller)

      3)  The scsicdrm start value is enabled in the registry. You may
	  check this by running REGEDIT. The information is under

	   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Scsicdrm.

	   The Start value should be set to 0 for this key (0x4 = disabled).

	   * Please reboot for the new Registry start value to take
	   effect

	   NOTE: There are some SCSI-I drives that are supported through
	   CDAUDIO.SYS (Pioneer DRM-600, NEC Intersect, Denon, and
	   Hitachi are just a few).  This driver can be enabled in the
	   Control Panel. The CDAUDIO.SYS should be enabled in addition
	   to SCSICDRM.SYS.

	   The CDAUDIO key is under .....\Services\Cdaudio. The CDAUDIO
	   Start value should be set to 1 to enable this special driver.

=====================================================================

3.13.   Subject : SCSI and ESDI drives greater than 1024 cyl.

Question : Can you have SCSI drives and ESDI drives > 1024 cyl.

Answer :  ESDI uses CHS (cylinder, sector, head) address.  SCSI uses RBA
	  (relative block address) addressing.  Normally, you do not
	  worry about a 1024 cylinder limit with SCSI, until the SCSI
	  drive becomes very large (> 1 GB). Then there is a problem.
	  Some SCSI cards have a jumper for > 1GB support.  Find out if
	  your card can assert this jumper.

	  The ESDI interface has a 1024 cylinder limitation.  Some
	  controller cards get around this by  implementing a
	  translation scheme in the onboard controller BIOS. Windows NT
	  (and other protected mode OS's) must duplicate the code found
	  in these BIOS chips inorder to duplicate this behavior.
	  Unfortunately, there are many ways of performing this
	  translation and thus we must incorporate all of these schemes
	  in our standard AT disk driver.  As you have probably guessed
	  by now, we have not included such support for all known ESDI
	  translation schemes.

	  Some ESDI controllers implement this translation in hardware
	  thus it is totally transparent to the system allowing the
	  standard driver to work unchanged.  Consult your
	  controller's documentation to see if such translation is
	  performed by the BIOS or the hardware.

=====================================================================

3.14.   Subject : Windows NT will not install on IBM PS/2 Model 90 and
		  95 Systems

Question : Why do I get the following error when installing Windows NT:

	   BOOT: I/O Error reading disk
	   Please insert another disk

Answer : Windows NT will not install if the configuration includes an
	 IBM SCSI adapter card with the 1991 BIOS chip.  In order to
	 install you need the IBM SCSI adapter card with the 1990 BIOS
	 or another type altogether.  To determine if your machine has
	 this adapter card open up your PS/s and look at the SCSI card.
	 At the edge of the card towards the front of the machine is a
	 chip with a white label on it. If it is dated 1991 then you may
	 not be able to install the October release.


=====================================================================

3.15.   Subject : Soundblaster Pro only supported in Mono mode

Question : My Soundblaster PRO will only play in Mono! Why?

Answer : The SoundBlaster Pro is only supported in Mono mode in the
	 October Release. This support is provided through version 1.x
	 of the SoundBlaster drivers. Work is currently in progress for
	 a Windows NT driver that will support SoundBlaster Pro in
	 stereo, however, there is no word on the availability of such
	 driver at the current time.


=====================================================================

3.16.   Subject : Additional Video drivers like the 8514 and ATI Ultra

Question : Why isn't there a video driver supplied with the October
	   Release of Windows NT to support my 8514 or ATI Ultra? 
	   How do I get one?

Answer : Microsoft is aware that many of our customers require
	 additional video drivers like the 8514, the ATI Ultra and
	 256/32768/65536 color SVGA drivers  We are sorry to say that
	 these drivers are not available at this time. After these
	 drivers have been completed and passed testing, we will release
	 them to the the public. We are sorry for any inconvenience that
	 this may be causing you and are working to complete them as
	 quickly as possible.

	 Please see the Hardware Compatibility List (HWFEED.TXT) section
	 of this FAQ for more info on making your driver needs known.

=====================================================================

3.17.   Subject : TSENG Labs ET4000 doesn't sync

Question : I installed the TSENG ET4000 drivers and now my video is out
	   of sync.

Answer : You need to load the interlaced driver.  Boot MS-DOS and rename
	 the ET4000.SYS driver in \winnt\system\drivers to ET4000.BAK.
	 Then copy ET4000I.SYS from \I386 on the CD-ROM to
	 \winnt\system\drivers. Rename this file ET4000.SYS and reboot.
	 Your monitor should then be able to sync correctly.


=====================================================================

3.18.   Subject : Can't play audio CD's with Future Domain SCSI Controller

Question : When I try to play audio CD's I get  the error :

	   CdRom0:ReadTOC failed  0xC000018

	   I'm using a supported CD-ROM drive and a supported Future
	   Domain Controller.

Answer : This is a known problem with the Future Domain SCSI Controller
	 driver. Microsoft is aware of this problem and is looking into
	 it. As soon as the driver is completed and tested, we will make
	 it available to the public.




=====================================================================
4.      TECHNICAL INFORMATION
=====================================================================

4.1.    Subject : IBM MOST Not Supported with Windows NT Flexboot

Question : How do I make Windows NT coexist on my hard drive with OS/2 2.0?

Answer : As indicated in the release notes, Windows NT is not compatible
	 with IBM's MOST utility. Microsoft does not intend to support
	 IBM's MOST boot scheme with Windows NT's Flexboot, and has no
	 plans to support installation on a drive with MOST installed on
	 it.

	 However, what you can do is install OS/2 using the dual boot
	 capability. Boot MS-DOS, and then boot OS/2.

=====================================================================

4.2.    Subject : Couldn't find NTLDR

Question : When I select to start Windows NT from Flexboot it comes up with
	   the following error:

	   BOOT: Couldn't find NTLDR
	   Please insert another disk

Answer : In order for Flexboot to start the NTLDR must be in the root of
	 the C Drive. If this file is missing you will get this error
	 message. To fix this simply copy the NTLDR from the CD or the
	 Floppies to the root of the C drive. If you are copying from
	 the CD ROM, you will find NTLDR in the I386 directory and can
	 copy it by going to the CD ROM Drive and entering :

	 Copy \I386\NTLDR C:\

	 Or if you have a floppy install set, you will find the NTLDR on
	 DISK 2 of the Install set as : NTLDR.$  This is the compressed
	 version of the Windows NT Loader and must be expanded with :

	 EXPAND NTLDR.$ C:\NTLDR.

=====================================================================

4.3.    Subject : MS-DOS Device Drivers in CONFIG.SYS

Question : What are the requirements of a device driver that is loaded in
	   the CONFIG.SYS?

Answer : Device drivers loaded in CONFIG.SYS are for the use of VDMs
	 only, and are MS-DOS device drivers, not VDDs.  So only MS-DOS and
	 Win16 programs can make use of the device drivers loaded there.
	 Also, since VDMs don't have access to much of the physical
	 hardware they do under MS-DOS, many device drivers won't work (and
	 will probably cause the VDMs to hang or die on startup).

=====================================================================

4.4.    Subject : The System Uses Between 70 and 130 threads.

Question : My system is using a lot of threads.  Is this normal?

Answer : With this release of Windows NT, the Performance Monitor will
	 show that the system running without any active applications
	 will use somewhere between about 70 and 130 threads.  This is
	 normal for this release.  The majority of these threads are
	 system threads.  The exact number observed will depend on the
	 system options that are in effect. For example, about 16
	 additional threads will be used if LanmanServer and
	 LanmanWorkstation services are active.

=====================================================================

4.5.    Subject : How the LibPath environment variable works

Question : Shouldn't the 'LibPath' environment variable work the same as
	   the 'Path' environment variable? 'Path' appends the 'User
	   environment' to the 'System environment', however 'LibPath'
	   does not.  It seems rather inconsistent.

Answer : 'LibPath' is not a typical enviroment variable and does not
	 work as it would under OS/2. It is only used by the system to
	 scan for device drivers during startup. Windows NT uses the
	 'Path' environment variable to locate DLLs just like Windows
	 3.x does.

=====================================================================

4.6.    Subject : File Compression Programs and Drivers

Question :  Is Windows NT compatible with my hard disk compression driver?

Answer : As indicated in the release notes, you cannot place Windows NT
	 on a partition with Stacker or any other compression or
	 partition products.  In general, Windows NT will not be able to
	 access data on a disk that requires a driver in the CONFIG.SYS
	 file for MS-DOS unless a similar driver has been installed for
	 Windows NT.

=====================================================================

4.7.    Subject : WOW Apps that don't work

Question : My Win 16 Application is not working and works on MS-DOS
	   fine. What should I do?

Answer : File a bug report using the BUGREP.TXT template from Library 3
	 (Problem Reports) of the WINNT forum and upload the completed
	 form to back to the same library. The report will be passed on
	 to Windows NT development so they can look into and attempt to
	 correct the problem.

	 More detailed instructions for reporting bugs can be found
	 elsewhere in this document and a SAMPLE.TXT is available for
	 your convenience.

	 Be sure to include all error messages, unusual behaviors, and
	 steps to reproduce all of the problems. The more information
	 you include, the easier it will be to reproduce and correct any
	 bugs in the operating system. Be sure to file a separate report
	 for each problem that you encounter.

	 If your problem is a low-level (and non-Setup) problem, you can
	 use the REPRTREG.EXE program (also in Library 3) to create an
	 ASCII dump of your registry. Generally you only want to include
	 the HKEY_LOCAL_MACHINE part of the registry since the whole
	 registry dump can exceed 700K. When in doubt, we recommend not
	 including it since we can ask you for it if we need it. We are
	 working on a better way to get this information and will
	 hopefully have it implemented soon.


=====================================================================

4.8.    Subject : /S switch is disabled from Remove Directory (RMDIR)

Question : Why isn't /S working with RMDIR ?
Answer : This option is disabled in the October Beta release 
	 because there were problems that came up which were to late to
	 be fixed. When this option is used in this release, the command
	 returns 'invalid switch -"S"'.

=====================================================================

4.9.    Subject : Using fault tolerance mirroring in Windows NT

Question : Why am I unable to select the "Establish Mirror" option under
	   Disk Manager in the October Beta release of Windows NT?

Answer : As mentioned in the October beta release notes, p. 25, only LAN
	 Manager for Windows NT will support mirroring of hard drive
	 partitions. Therefore, the option to select the "Establish
	 Mirror" menu item will only be enabled in LAN Manager for
	 Windows NT.


===================================================================== 

4.10.   Subject : OS/2 subsystem takes priority

Question : Whenever I run my bound application it runs under the OS/2
	   subsystem and not the MS-DOS subsystem?

Answer : Bound applications are designed and built so that they can be
	 run under either OS/2 or MS-DOS. The OS2 SubSystem is not
	 available on MIPS, therefore, bound applications will run as
	 MS-DOS applications on MIPS.

	 When a bound application is run under Windows NT on an 80x86,
	 it will automatically run under the OS2 SubSystem if it is
	 available.

	 The OS2 SubSystem is available by default on an 80x86. In order
	 to force bound applications to run as a MS-DOS application, it
	 will be necessary to disable the OS2 SubSystem using REGEDIT.
	 This is not advised unless there is a very specific need to do
	 so.

	 More Information:

	 The utility REGEDIT is provided to alter the Registry Database.
	 Note: in many cases you must be logged on as 'Administrator' to
	 alter some of the Registry settings.

	 In order to disable the OS2 Subsystem start REGEDIT and go to
	 the key:

	 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
	 SessionManager\SubSystems

	 Find the value "Optional: REG_MULTI_SZ OS2 Posix"

	 Double click on that value and remove the word "OS2". This will
	 tell Windows NT to not load the OS/2 subsystem when it boots.
	 Reboot your system for the change to take effect

	 Once this is done, bound applications will run as MS-DOS
	 applications. Running an OS/2 application will result in the
	 following message

		"Cannot connect to OS2 SubSystem"

	 WARNING:
	 RegEdit is a very powerful utility that facilitates directly
	 changing the Registry Database. Using RegEdit incorrectly can
	 cause serious problems, including hard disk corruption. It may
	 be necessary to reinstall the software to correct any problems.
	 Microsoft does not support changes made with RegEdit. Use this
	 tool at your own risk.

=====================================================================

4.11.   Subject : ANSI ESC not supported for a command prompt

Question : Why can't I get ANSI ESC codes to work with my command prompt?

Answer : This is by design. The development team found this to be a
	 performance issue. Updating the console for ANSI ESC sequences
	 was slowing down the updates of the screen. The decision was to
	 not slow down the console to do this. In addition, Windows NT
	 is a GUI, not CUI (Character User Interface). Similar
	 functionality can be provided through the console API.

	 MS-DOS applications requiring ANSI can be used by putting a
	 copy of ANSI.SYS from MS-DOS on the hard disk and adding the
	 line:

	 DEVICE=C:\ANSI.SYS

	 in the CONFIG.SYS.

=====================================================================

4.12.   Subject : Extended and Expanded memory for MS-DOS applications.

Question : How do I give my MS-DOS applications Extended or Expanded
	   memory?

Answer : As with Windows 3.1, a Program Information File (PIF) can be
	 created for applications which need resources beyond those
	 supplied to MS-DOS applications by default.  See Chapter 8
	 (Other Application Environments) in the October 1992 Microsoft
	 Windows NT System Guide for more information about using PIF
	 files.

=====================================================================

4.13.   Subject : File System Conversion.

Question : Can I convert my current file system to NTFS without
	   reformatting the drive?

Answer : Yes.  The command-line utility, CONVERT.EXE, can be used to
	 convert existing HPFS or FAT drives to the NTFS format.  Note
	 that no other conversions are supported at this time. It is
	 only possible to convert FAT or HPFS to NTFS.  To convert from
	 NTFS back to FAT or HPFS, it is necessary to backup your drive,
	 reformat it, and then restore the files back to it.

	 Example : To convert drive "D:" from FAT to  NTFS format, issue
		   the command:

	 "CONVERT D: /FS:NTFS"

=====================================================================

4.14.   Subject : Change the default startup operating system

Question : Why doesn't the change of  the startup Operating System
	   through the System applet in the Control Panel work?

Answer : The settings of the Default Operating System and Timeout  are
	 stored in the BOOT.INI file. If it is READ ONLY, it can't be
	 changed. In order to change these values, it is necessary to
	 change this file by using ATTRIB BOOT.INI -r after booting MS-DOS.
	 Once the READ ONLY attribute has been cleared, you can then
	 change its values via the System tool in the Control Panel or
	 by editing it with a text editor.

=====================================================================

4.15.   Subject : Time Zone Problem

Question : Why is the time zone for Anchorage at GMT -9:00?

Answer : The Time Zone for Anchorage, Alaska should be GMT -9:00 and
	 Yukon should be GMT -8:00. This would be more accurate since
	 Anchorage is four hours different from the East Coast and one
	 hour different from California. Yukon, Alaska should be the
	 same as Vancouver and US Pacific Time.

	 According to the maps in the :

	 The World Almanac and Book of Facts 1992

	 The time zone for :

	 Yukon should be GMT -8
	 Alaska should be GMT -9
	 Hawaii should be GMT -10



=====================================================================
5.      NETWORK INFORMATION
=====================================================================

5.1.    Subject : TCP/IP Support

Question : Does the October Beta release of Windows NT has complete
	   TCP/IP support?

Answer : The October Beta Release of Windows NT contains full TCP/IP
	 support for Windows NT. The machines running Windows NT with
	 the TCP/IP protocol stack will be able to communicate with LAN
	 Manager 2.x Servers and Workstations. Windows NT will also have
	 an extensive set of TCP/IP utilities including Telnet, ftp,
	 rcp, rsh, etc. Third party vendors have shown interest in
	 providing the host software for the TCP/IP utilities.


=====================================================================

5.2.    Subject : Replication

Question : I noticed on Windows NT machines, the replicator service only
	   allows you to import files/directories.  Does that mean to
	   actually use replication (which requires some server
	   exporting data) a LAN Manager for Windows NT or LAN Manager
	   for OS/2 server will be required?

Answer : Yes. You must have a LAN Manager for Windows NT system to use
	 the file replicator.

	 Clarification:  Here are the rules involving Windows NT systems
	 and replication:

	 - You must have a LAN Manager for Windows NT system to EXPORT
	   with the file replicator.

	 - The WinNT systems can IMPORT from a LAN Manager for Windows
	   NT exporter.

	 - OS/2 Lanman systems can IMPORT from a LAN Manager for Windows
	   NT exporter.

	 - LAN Manager for Windows NT systems can also IMPORT from other
	   LAN Manager for Windows NT systems (or even the same
	   machine). OS/2 LM (EXPORT) >> NT (IMPORT)  is not supported

=====================================================================

5.3.    Subject : Network fails to start

Question : After installing Windows NT, my network fails to come up.
	   What is wrong?

Answer : Please see page 30 of the Release Notes for October 92 Beta
	 release of Windows NT.
	
	- Check for interrupt conflicts
	- Check for memory conflicts
	- Check for duplicate machine name
	- Check the proper configuration settings for your appropriate
	  network card.

	If you are still having problems, contact Microsoft Product
	Support Services using Section 3 (Windows NT Setup) of the WINNT
	forum on CompuServe as described in Microsoft Windows NT October
	1992 Beta Program Support Notes.



=====================================================================
6.      COMMON ERROR MESSAGES
=====================================================================


6.1.    Subject : Error 0000001E

Question : I am getting error 0001E. What do I do?

Answer : Unknown at this time. Microsoft is looking into the cause 
	 of this error and will post it here when it is resolved.

=====================================================================

6.2.    Subject : NTVDM error when running MS-DOS or WIN3.1 Apps

Question : Why can't I run MS-DOS or Win 3.x apps?

	   Error  received : Insufficient memory or Disk Error in NTVDM

Answer : There are a few possible causes to this problem:

	 a) Increase the swap file size to the 20MB minimum.
	 b) Make certain that the video card is on the hardware
	    compatibility list and if not run in vanilla VGA.
	 c) Something else not identified at this point


=====================================================================

6.3.    Subject : Error 0x00000069 or Error 0x00000067

Question : I get Error 0x00000069. What do I do?

Answer : This is a initialization error, which happens when Windows NT
	 tries to talk with the HD controller.  It can be caused by any
	 number of things.  Things to try:

   * If the card allows, slow down the DMA transfer rate.

   * Make sure both ends of the SCSI bus are terminated.

   * Make sure there are no IRQ, or memory address conflicts.

   * Make sure you're aren't using a faulty or un-supported driver i.e.
     the FD 1680 SCSI controller is supported, but there is a problem
     with that driver which will be fixed and posted on CompuServe in
     WINNT, Library 2.

     A list of supported devices can be found in WINNT, Library 1,
     1092HW.TXT.

   * Make sure that NTDETECT.COM is in the root of the booting
     partition. Missing files from Windows NT can cause an Error 69.

=====================================================================

6.4.    Subject : Fatal System Error 0x0000000A

Question : What do I do about :

	   Fatal system error 0x0000000A
	   IRQL expected to be less than or equal

Answer : This usually indicates that you have changed the interrupt
	 settings on a card and it now disagrees with what's indicated
	 as the interrupt setting that you entered during setup. It is
	 possible that you have installed a new card since you installed
	 Windows NT or, that you possibly have an interrupt conflict
	 with some other piece of hardware in your system.

=====================================================================

6.5.    Subject : System Error F002

Question :  I get System Error F002.

Answer : If you receive a System error F002,this probably means that
	 your hardware is faulty; for example, you may be experiencing a
	 memory failure.

	 This error is generally caused by a hardware incompatibility
	 in the machine which may be caused by one of the following:

	 1) Memory parity errors
	 2) some card asserts an I/O channel check on the bus,usually VGA
	    or net cards 
	 3) math coprocessor had an error

	 If this occurs, run the manufacturer's diagnostic procedure.

=====================================================================

6.6.    Subject : Setup fails with a SCSI read request error

Question : Why do I get the following error when installing NT:

	   "SCSI read request failed Arc status 8 Srb status 0084"

Answer : There are possible FAT or other file system problems on the
	 drive which autocheck is not handling.  Please run a diagnostic
	 check on the file system such as chkdsk or other 3rd party
	 application. It is possible that there is a partition problem
	 or cross linked files on the disk.  Try correcting these and
	 then rerun setup.

=====================================================================

6.7.    Subject : Error X00000022 - Generic Bugcheck

Question : I get the error  X00000022 - Generic Bugcheck. What should I do?

Answer : Unknown at this time.  Microsoft is looking into the cause 
	 of this error and will post it here when it is resolved.

=====================================================================

6.8.    Subject : Fatal Kernel Error 006E or 0071.
		 
Question : Why do I receive the following error messages when booting
	   from text to GUI setup?

	   Messages are:

	   BOOT: I/O Error reading disk
	   Please insert another disk

		  -OR-

	   Fatal Kernel Error 0000006E
	   Fatal Kernel Error 00000071

		  -OR-

	   The system freezes at the blue screen with no error message.

Answer : If you are on a turbo system or any multi speed CPU system
	 please turn off the turbo or operate at the lowest CPU setting
	 after the text portion of setup has copied the files to the
	 hard drive until the GUI portion of setup resumes copying files
	 to the hard drive.  It is important that if this error occurs
	 that you fill in a bug report template including full machine
	 configuration information so that development can fix this
	 problem as soon as possible. The template can be found in
	 WINNT, Library 3, as BUGREP.TXT. There is a sample report to
	 use as a guideline as well (SAMPLE.TXT). Upload the completed
	 report to Library 3 and it will be passed on to development for
	 review.

		     
