Monster Media 1993 #3/MONSTER.ISO/win/nt/ntfaqoct.txt

Text File | 1993-10-30 | 75.6 KB | 2,046 lines

######     ####    ############            Microsoft
#######    ####    ############
########   ####        ####       Windows NT and Advanced Server
#### ####  ####        ####
####  #### ####        ####         Frequently Asked Questions
####   ########        ####
####    #######        ####               October 1993
####     ######        ####



This document provides answers to frequently asked questions about
Windows NT. (Last update: 10/18/93.)


Table of Contents

1.      GENERAL INFORMATION
1.1.    Obtaining Windows NT,  NT Advanced Server, and the Win32 SDK
1.2.    Windows NT and Windows NT Advanced Server 3.1 Update
1.3.    Obtaining the Windows NT Resource Kit
1.4.    Windows NT Support via an Internet Address
1.5.    Development Issues Belong in the MSWIN32 Forum
1.6.    Making a Suggestion to be Added to Windows NT
1.7.    Security Certification Specifications
1.8.    Obtaining SNA Server for Windows NT Beta SDK
1.9.    Articles for Windows NT and Windows NT Advanced Server
1.10.   Public Domain for Windows NT
1.11.   Available Software and Hardware for Windows NT
1.12.   Fax Software for Windows NT
2.      INSTALLATION AND SETUP
2.1.    Installing Windows NT Over Previous Installation
2.2.    Selections in boot loader keep returning to the boot loader Menu
2.3.    Windows NT Boots but Looks in Wrong Boot Directory
2.4.    Converting the system partition to NTFS on MIPS R4000
2.5.    Windows NT Needs 600K Free
2.6.    What is the $WIN_NT$.~LS Directory
2.7.    Setup Fails When Switching from Text to Graphics
2.8.    Emergency Repair Disk on Unsupported CD-ROM
2.9.    MIPS Installation not working
2.10.   Updating LAN Manager 2.x Network to Advanced Server
3.      HARDWARE INFORMATION
3.1.    System Requirements for Windows NT/Windows NT Advanced Server
3.2.    Hardware Compatibility List (HWFEED.TXT)
3.3.    Full Screen MS-DOS Support on MIPS Machines
3.4.    Device Driver Requests
3.5.    DELL Computer Only Recognizes 16 MB of Memory
3.6.    Limits of Support for Removable Media
3.7.    Sharing Communication Port Interrupts
3.8.    DMA Speed on an Adaptec 154x SCSI Controller
3.9.    AMI SCSI Controllers
3.10.   Adaptec 154x SCSI Controller BIOS Versions
3.11.   Installing the Sony CDU-31a CD-ROM with Windows NT
3.12.   MediaVision ProAudio Spectrum (PAS16) Sound Card
3.13.   Using Sound Blaster Pro With the Sound Blaster 1.x Driver
3.14.   Installing the Sound Blaster CD-ROM Driver for Windows NT
3.15.   Adding a CD-ROM After Installing Windows NT
3.16.   SCSI and ESDI Drives with More Than 1024 Cylinders
3.17.   Archive Python Tape Drive - No drive detected
3.18.   NEC CD-ROM Slow Downs
3.19.   ATI Driver Won't Display a Higher Resolution
3.20.   Trouble-Shooting ATI Problems
3.21.   Display 16 and 32 Bit Color Modes in ATI Adapters
3.22.   UART Support
3.23.   System Hangs on Micronics Motherboard with Ultrastor U34F
3.24.   S3 Based Video Card and High Resolutions
3.25.   Intel SatisFAXion 400/i Modem
3.26.   TIGA Drivers for Windows NT
3.27.   No Speaker Driver for Windows NT
4.      TECHNICAL INFORMATION
4.1.    Couldn't Find NTLDR
4.2.    How the LibPath Environment Variable Works
4.3.    File Compression Programs and Drivers (Doublespace)
4.4.    Troubleshooting 16-bit Windows Applications Under Windows NT
4.5.    Using fault tolerance mirroring in Windows NT
4.6.    OS/2 Subsystem Takes Priority
4.7.    ANSI.SYS Support
4.8.    Extended and Expanded Memory for MS-DOS Applications
4.9.    Converting File Systems without Reformatting
4.10.   Removal of NTFS
4.11.   CHKDSK /F on an NTFS Drive
4.12.   MS-DOS Device Drivers in CONFIG.SYS
4.13.   Replacing Boot Sector Without Reinstalling
4.14.   Microsoft Visual C++ (MMD.386 virtual device driver not loaded)
4.16.   What is Win32s?
4.17.   Recreating a Post Office
5.      NETWORK INFORMATION
5.1.    TCP/IP Support
5.2.    Replicator Service only allows me to Import files
5.3.    Network Fails To Start
5.4.    Using Telnet in Windows NT
5.5.    LAN Manager and Windows NT Domains
5.6.    Windows NT Advanced Server Upgrade
5.7.    Difference Between Workgroup and Domain
5.8.    Network Drives Display Slowly in Open Dialog Box
5.9.    Network Directory Listing Enumeration
5.10.   RAS and TCP/IP
5.11.   Connecting to a Novell Server
6.      COMMON ERROR MESSAGES
6.1.    Error 0000001E
6.2.    NTVDM Error
6.3.    Error 0x00000069 or 0x00000067
6.4.    Fatal System Error 0x0000000A
6.5.    System Error F002
6.6.    Setup Fails with SCSI Read Request Error
6.8.    LogErrorEntry Error (UniqueId=300)
7.      OTHER FILES ON COMPUSERVE



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

1.1.    Obtaining Windows NT,  NT Advanced Server, and the Win32 SDK

Question:

How do I obtain Windows NT, Windows NT Advanced Server, and the Win32
SDK?

Answer:

These products are available now through resellers or direct from
Microsoft by calling Microsoft Inside Sales at [phone]. In
Canada, call [phone]. In all other countries, contact your local
Microsoft representative. The Win32 SDK now contains the Windows NT DDK.

=====================================================================
1.2.    Windows NT and Windows NT Advanced Server 3.1 Update

Question:

How can I get the Windows NT and Windows NT Advanced Server 3.1 Update?

Answer:

The Windows NT and Windows NT Advanced Server 3.1 Update (CSD version
001) is now available in Library 2. From Library 2, you can download the
UPDATE.TXT which contains a list of bugs that have been fixed in the
update and instructions on how to create your update disk set.  There
are two files containing the update for both Windows NT and Windows NT
Advanced Server. For 5.25 inch 1.2 MB disks, query on S14321 or
CSD525.EXE. For 3.5 inch 1.44 MB disks, query on S14322 or CSD35.EXE.
These are both compressed, self-extracting files that include complete
installation instructions.

NOTE: These files are very large (approximately 6.5 MB).

You can access the Microsoft Software Library from a variety of services:
- Internet: FTP.MICROSOFT.COM, WINNT\SUP-ED\FIXES\CSD001 directory.
- CompuServe: MSL forum. - GEnie, Microsoft OnLine: Software Library.
- Microsoft Download Service (MSDL): [phone].

If you are unable to access these services, contact Microsoft Product
Support Services.

=====================================================================
1.3.    Obtaining the Windows NT Resource Kit

Question:

How can I obtain the Microsoft Windows NT Resource Kit?

Answer:

The Microsoft Windows NT Resource Kit is available now in bookstores and
software stores and directly from Microsoft Press services at
(800)-MSPRESS.  In Canada, call (416)-293-8141.  There are three updated
Windows NT Resource Kit Utilities located in Library l of the WINNT
forum on Compuserve in the file RESKIT.ZIP.

=====================================================================
1.4.    Windows NT Support via an Internet Address

Question:

Is there an Internet address that I can submit questions to?

Answer:

No - at least not with full Microsoft support.

The only official location for support from Microsoft is on CompuServe
in the WINNT and MSWIN32 forums. However, there are several other places
where you can get some peer support, (including some MS personnel in
their own time).  These include the [e-mail] mailing list (send
mail to ntdev- [e-mail] to join) and three newsgroups on
UseNet: "comp.os.ms-windows.nt.setup" "comp.os.ms-windows.nt.misc"
"comp.os.ms-windows.programmer.win32" Knowledgebase articles, drivers
and fixes may be found on  "ftp.microsoft.com", as well bug report forms
and instructions on how to use them.  Please remember that these are not
official venues for support, and, as a result, support is not
guaranteed; the level of support you receive may vary.

=====================================================================
1.5.    Development Issues Belong in the MSWIN32 Forum

Question:

Where should I ask questions about the WIN32 SDK?  Can I ask them in the
WINNT Forum?

Answer:

WIN32 SDK programming questions are answered in the MSWIN32 Forum.

WINNT is dedicated for end-user issues about Windows NT (for example,
installing the Windows NT operating system itself), while MSWIN32 is
dedicated to developer issues about Windows NT ( installing the
Development Tools portion of the WIN32 SDK for Windows NT, API
questions, etc.).

The more closely you follow this policy the easier and faster it will be
for all forum members to get the information and help they need. Thanks!

=====================================================================
1.6.    Making a Suggestion to be Added to Windows NT

Question:

I would really like to see a feature added to Windows NT. How do I go
about making this suggestion? Is there a procedure in place to make such
suggestions?

Answer :

Microsoft is always interested in hearing your commentary and
suggestions.  Suggestions can be made by telling a Microsoft
representative who will pass the suggestion on to the Windows NT
development team for evaluation.

=====================================================================
1.7.    Security Certification Specifications

Question :

How can I obtain the security certification specifications ?

Answer :

For information on operating system security certification
specifications, contact the following source:

   National Computer Security Conference (NCSC) at [phone]

The following documents are available:

 - The Orange Book (Trusted Computer System Evaluation Criteria). This
   document explains standalone operating system security ratings and
   requirements.

 - Red Book (Trusted Network Interpretation). This document extends to
   security ratings in networks.

NCSC has many other informative publications. Costs are minimal
(approximately $3.00 U.S.).

=====================================================================
1.8.     Obtaining SNA Server for Windows NT Beta SDK

Question:

How can I obtain  SNA Server for Windows NT Beta SDK?

Answer:

The preliminary SNA Server SDK is available from Microsoft Inside Sales
[phone] for $495.  Licensed users of the prerelease SDK will get
a free upgrade to the final SDK product, scheduled to ship at the same
time as SNA Server.

=====================================================================
1.9.    Articles for Windows NT and Windows NT Advanced Server

Question:

Where can I find articles for Windows NT and Windows NT Advanced Server
on Compuserve?

Answer:

Articles for Windows NT and Windows NT Advanced Server can be found on
Compuserve by using GO MSKB.

=====================================================================
1.10.   Public Domain for Windows NT

Question:

What happened to the public domain section in the WINNT forum? Where are
the public domain and shareware applications for Windows NT now ?

Answer:

Most of the files in the public domain section of the WINNT forum used
the preliminary Windows NT SDK APIs. Many of those files will no longer
work correctly under the released product of Windows NT unless they are
recompiled using the released version of the Windows NT SDK.

All public domain and shareware for Windows NT are now available in
Library 14 of the WINFUN and WINSHARE forums on Compuserve. Please use
the GO command to GO WINFUN to view Library 14 (Win NT Games/FUN) or GO
WINSHARE to view Library 14 (Win NT Utils/Apps).

=====================================================================
1.11.   Available Software and Hardware for Windows NT

Question:

Where can I find a list of  Windows NT applications, hardware, etc.
under development or currently available?

Answer:

For information regarding 3rd party products available for Windows NT,
you might want to check the Microsoft WIN32 Products & Services Catalog
for Windows NT.  This catalog (Part #098-52530) can be obtained by
calling Toll Free 1-800- 426-9400 or mailing:
        Microsoft Corporation
        One Microsoft Way
        Redmond, WA   98052-6399

=====================================================================
1.12.   Fax Software for Windows NT

Question:

 I am looking for FAX software for NT, can you recommend any?

Answer:

We cannot recommend any particular products, but here is a partial list
of FAX software from the Win32 Products & Services Catalog.

Product                 Source                Phone
FaxTalk Plus for Windows NT        Thought Communications        800/437-6324
LanFax Redirector               Alcom Corp.                     415/694-7000
CIT Family Gateway              Computer Image                  916/753-9540
CorporateFax Server             Computer Image                  916/753-9540
FaxFacts                        Copia Intl.                     708/682-8898
Fax Associate                   EMCI                            508/752-1241
Siren Fax NT                    Siren Software                  415/322-0600


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

2.1.    Installing Windows NT Over Previous Installation

Question:

Can I install Windows NT over my previous (beta) version of Windows NT?

Answer:

Please refer to SETUP.TXT (included on the Windows NT CD and on Disk 4
of the installation disks)  for complete installation details before
installing Windows NT.

=====================================================================
2.2.    Selections in boot loader keep returning to the boot loader Menu

Question:

Whenever I choose MS-DOS from the  boot loader menu, it keeps returning
me to the  boot loader menu. Why?

Answer:

This can happen when installing Windows NT over a previously existing
Windows NT installation without using the MS- DOS SYS command to
activate the partition. When Windows NT installs, it reads the drive
boot sector to create the BOOTSECT.DOS file. It then uses BOOTSECT.DOS
when you select the previous operating system choice from the Boot
loader menu to restore the original partition information.

If you install Windows NT over another copy of Windows NT, BOOTSECT.DOS
may contain a copy of the Windows NT partition information and not the
MS-DOS partition information. Each time you select the previous
operating system, the Windows NT partition information is loaded and
executed.

There are two ways to fix this:

- If you have a previous copy of BOOTSECT.DOS, replace the current
  version with the previous version.  Note that you cannot use the
  BOOTSECT.DOS file from other machines. This file contains hardware
  specific information and cannot be used across machines.

 - If not, you need to recreate the boot sector for MS-DOS by booting
   from an MS-DOS diskette and running SYS C: from that disk.  Doing
   this removes the Boot loader feature from your system.  To re-enable
   Boot loader, see the entry titled Replacing Boot Sector Without
   Reinstalling, in the Technical Information section.

=====================================================================
2.3.    Windows NT Boots but Looks in Wrong Boot Directory

Question:

Windows NT looks in the wrong boot directory. Why?

Answer:

This can be caused by a few different things:

 - Make sure BOOT.INI refers to the correct Windows NT directory.

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

Windows NT uses logical partitioning. When an unknown partition type
(MOST for example) 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.

Install Windows NT on a machine that does not have the MOST utility
installed.

=====================================================================
2.4.    Converting the system partition to 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 formatted as an NTFS
partition. The installer correctly puts HAL.DLL and OSLOADER on the
system partition.

Warning: Do not use CONVERT.EXE on the system partition. It will convert
it to NTFS and the system will no longer boot. If this happens, your
only option is to run ARCINST.EXE from the installation CD-ROM and
reformat the system partition as FAT.

=====================================================================
2.5.    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.
You may have to perform some configuration changes to rearrange the
hardware memory mapping so that 600K of low memory is available.

=====================================================================
2.6.    What is the $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 alright 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 from your
hard drive.

This directory is normally deleted after a successful installation of
Windows NT. If Setup should fail for some reason, this directory is left
on your hard drive. You can safely delete this directory.

=====================================================================
2.7.    Setup Fails When Switching from Text to Graphics

See the entry titled, Fatal Kernel Error 006E or 0071 During Setup, in
the Common Error Messages section.

=====================================================================
2.8.    Emergency Repair Disk on Unsupported CD-ROM

Question:

Can I use the Emergency Repair disk if I install Windows NT from an
unsupported CD-ROM configuration or over the network?

Answer:

Unfortunately, this is not possible currently. The repair disk will not
function correctly in this case, because Windows NT has no way to access
the original installation media from Setup.

You can create an Emergency Repair disk by installing from either CD or
floppy. If you install from floppy (or from a Setup share created by
floppy), you need the original Setup floppies to use the Emergency
Repair disk. If you install from CD (or from a Setup share created by
CD), you need the original setup CD to use the Emergency Repair disk.

=====================================================================
2.9.    MIPS Installation not working

Question:

Why doesn't Windows NT work on my MIPS machine?

Answer:

MIPS machines require a hardware update in order to run Windows NT. The
CPU must have an R4000 version of 2.0 or later. Please contact your
hardware manufacturer if you have not already obtained an update.

=====================================================================
2.10.   Updating LAN Manager 2.x Network to Advanced Server

Question:

 I have servers with Lan Manager 2.0c and above installed.  How can I
begin planning and convert my system over to Windows NT Advanced Server?


Answer:

The Windows NT Advanced Server Upgrade is available today at $595, and
can be obtained at most retail outlets, from  your local Solution
provider or your MS Network Reseller.  You can get more information on
the Windows NT Advanced Server Upgrade product by calling Microsoft
Inside Sales at [phone].  The Upgrade product currently contains
the Windows NT Advanced Server product and the Planning Guide.   For
customers that buy the Upgrade product today, the complete Upgrade
Utilities and the Upgrade Guide will be made available through
fulfillment free of charge (There is a fulfillment coupon in the box).
The complete Upgrade Utilities and the Upgrade Guide will ship with the
Upgrade product box in October.

Customers can begin planning their Upgrade to Windows NT Advanced Server
using the Planning Guide today.  The ACLCONV and PORTUAS utilities are
included in the Windows NT \System32 directory and can be used to do a
subset of the complete upgrade; convert file system, upgrade user
account information and restore security information.  However, usage of
these utilities is not documented in the Windows NT end-user
documentation.  It is highly recommended that customers wait for the
complete Upgrade Utilities and Upgrade Guide before attempting a
large-scale upgrade.

The complete Upgrade Utilities, in addition to the above, will also
restore or check any LAN Manager parameters that have Windows NT
equivalents, restore net use's or shares, restore UPS settings, allow
upgrading to single enterprise logon, backup scheduled commands, upgrade
MAC volumes, offer enhanced Sytos + read capabilities, and upgrade
replication and logon scripts.  There is a file, LMUPGD.EXE, in Library
1 of the WINNT forum on Compuserve which explains the features of the
Lan Manager to Windows NT Upgrade


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

3.1.    System Requirements for Windows NT/Windows NT Advanced Server

Question:

What are the minimum hardware requirements to run Windows NT and Windows
NT Advanced Server?

Answer:

Windows NT has the following hardware requirements:

        An x86-based microprocessor (386/25 or higher) with 12 MB or
        more of RAM for this release, or an ARC-compatible RISC-based
        computer with 16 MB of RAM such as the MIPS R4000, MIPS R4400,
        or DEC Alpha.

        A hard disk with approximately 75 MB of free disk space for
        Windows NT (92 MB on an ARC computer), 20 MB of which will be
        used for the virtual memory paging file.

Windows NT Advanced Server has the following hardware requirements:

        An x86-based microprocessor (386/33 or higher) with 16 MB or
        more of RAM for this release, or an ARC-compatible RISC-based
        computer with 16 MB of RAM such as the MIPS R4000, MIPS R4400,
        or DEC Alpha.

        A hard disk with approximately 90 MB of free disk space for
        Windows NT (110 MB on an ARC computer), 20 MB of which will be
        used for the virtual memory paging file.

=====================================================================
3.2.    Hardware Compatibility List (HWFEED.TXT)

Question:

How do I know if my hardware is supported and what do I have to do to
get it supported?

Answer:

Microsoft provides a list, 0793HW.TXT, of tested hardware that is known
to work with Windows NT. It has been posted on CompuServe in Library 1
of the WINNT forum. For your convenience the hardware list is also
available in Word for Windows format, called 0793HW.DOC and in a Windows
Help file, called HCLHLP.ZIP. The Hardware listed in these files have
been tested on Windows NT and are fully supported.

Any absence from this list does not imply that the hardware will not
work with Windows NT, only that it is untested and not supported at this
time.

The form, HWFEED.TXT, is provided as a means for you to request support
for your hardware. It is also in Library one of the WINNT forum. You can
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.    Full Screen MS-DOS Support on MIPS Machines

Question:

How do I get full screen MS-DOS support on my MIPS Machine?

Answer:

Full screen support will not be provided under Windows NT on MIPS
systems.

=====================================================================
3.4.    Device Driver Requests


Question:

Is there a driver available for my hardware yet?

Answer:

Microsoft posts all new, fixed and updated drivers in Library 2 of the
WINNT forum on CompuServe. Microsoft is 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 and mailing it to Microsoft at
[e-mail] (INTERNET:[e-mail], if sending mail
from CompuServe).

Please note: Because of current support demands, this is a one way
alias; Microsoft will not respond directly to you to confirm that your
request has been received.

The hardware compatibility list, 0793HW.TXT, and HWFEED.TXT files can be
found in Library 1 of the WINNT forum on CompuServe.

=====================================================================
3.5.    DELL Computer Only Recognizes 16 MB of Memory

Question:

Why doesn't Windows NT recognize any memory above 16MB on my Dell
machine?

Answer:

Some DELL machines have a BIOS problem which prevents it from seeing
greater than 16MB of RAM under Windows NT. If your machine demonstrates
this problem, please contact Dell to obtain the latest BIOS upgrade
applicable to your particular Dell model.

=====================================================================
3.6.    Limits of Support for Removable Media

Question:

I see some removable media drives on the hardware compatibility list,
but I'm having some problems. What are the limits of support for
removable media?

Answer:

Under Windows NT, Bernoulli drives and removable SCSI drives support a
subset of the functionality that is provided for fixed media devices:
Only a single partition can be created on a removable drive. Also, while
removable FAT volumes can be freely exchanged, removable NTFS volumes
require that a system restart when you change the media. Microsoft is
aware of the problems currently surrounding removable media and is
working to improve the situation for future releases.

=====================================================================
3.7.    Sharing Communication Port Interrupts

Question:

Can I share communication port interrupts?

Answer:

Windows NT supports two communication ports sharing the same interrupt
on non-MCA machines. However, only one port can be in use at a time. A
communication port will not be created if another type of device is
using the same interrupt.

=====================================================================
3.8.    DMA Speed on an Adaptec 154x SCSI Controller

Question:

Can I set the DMA speed on an Adaptec 154x SCSI controller?

Answer:

Currently the AHA154X.SYS driver has a hard-coded DMA transfer rate of
5.0 MB. Even if you change jumper settings, the driver still transfers
data at this rate.

=====================================================================
3.9.    AMI SCSI Controllers

Question:

What issues should I be aware of when installing Windows NT with an
American Megatrends SCSI controller?

Answer:

The following information was provided by Clyde Washburn & Co. (American
Megatrends Distributors):

- Installation in the Adaptec emulation mode may be accomplished by
  setting the controller 32-Bit Driver Mode to Disabled.

- New ROMs are now in Beta testing which will allow operation with
  32-Bit Driver Mode Enabled as a Bustek Family Controller.  Expected
  availability is 1-2 weeks.  Please _email_ to 70305,1211 if you wish
  to be notified when available-- do NOT leave Forum messages for that
  purpose.  We will need to know exactly _which_model_ controller you
  have: Series 15 (original AMI cached SCSI), Series 44 (later
  custom-chip version), Series 441 (Fast SCSI version of Series 44), or
  Series 48 non-cached Fast SCSI).  It is anticipated that you will be
  able to either purchase a ROM Update Kit, or download the necessary
  files -- the latter will require the ability to burn both 27C256
  (256k) and 27C010 (1 Mb) EPROMs.

=====================================================================
3.10.    Adaptec 154x SCSI Controller BIOS Versions

Question:

Are there any issues regarding Adaptec 154x SCSI controller BIOS
versions?

Answer:

The 1988 version 3.08 Adaptec 154x BIOS has a problem with the
Scatter/Gather feature. This problem is detected by the Adaptec driver
and the feature is disabled. If you have this BIOS version a message is
displayed informing you that the Scatter/Gather feature has been
disabled. If you get this message, you can contact the Adaptec BBS
(408-945-7727) and get the most recent version, 3.20, of the BIOS at no
cost.

BIOS versions after 3.08 do not have this problem.

The latest 154x BIOS also supports drives that are larger than 1GB (even
under MS-DOS). Windows NT supports this option.

=====================================================================
3.11.   Installing the Sony CDU-31a CD-ROM with Windows NT

Question:

How do I install the Sony CDU-31A CD-ROM drivers for use with Windows
NT?

Answer:

The Sony CDU-31A CD-ROM is not by default available for setup or for use
with Windows NT. However, there is a driver and setup information for
this CD-ROM on the Windows NT CD-ROM.

Note: Most Gateway 2000 computers that ship with the Sony CDU-31A CD-ROM
drive come with the Sony COR-334 host adapter.  This host adapter is an
OEM version of the Sony CDB-334 and is identical to this card in all
respects.

The factory defaults for the Sony COR-334 and CDB-334 are: I/O base port
address set to 340 hex, DMA channel set to none, and IRQ set to none.
No IRQ setting is necessary for the card to operate correctly under
MS-DOS, and therefore most COR- 334 and CDB-334 adapters are not
configured for an IRQ. However, Windows NT requires the use of an IRQ.
Use the instructions in the README.TXT file to configure the adapter for
use with Windows NT. The driver and installation instructions are
located in the following directory on the CD:

    \drvlib\storage\sony_31a\x86 (or MIPS)

=====================================================================
3.12.    MediaVision ProAudio Spectrum (PAS16) Sound Card

Question:

How can I get my ProAudio Spectrum sound card to work under Windows NT?

Answer:

If a MediaVision sound card has a SCSI interface, the CD-ROM interface
is supported by the drivers provided with Windows NT.  If the
MediaVision sound card contains a proprietary CD-ROM interface, then the
CD-ROM interface is not supported by the drivers currently available.
The only PAS 16 board that is currently supported by Windows NT is the
50-pin SCSI version.  This board uses the driver TSLCDR.SYS under
MS-DOS.

=====================================================================
3.13.   Using Sound Blaster Pro With the Sound Blaster 1.x Driver

Question:

What considerations should be made when using my Sound Blaster Pro with
the Sound Blaster 1.x driver?

Answer:

When using the Sound Blaster 1.x driver provided with Windows NT to run
with the Sound Blaster Pro, the DMA channel must be set to 1.  Note:
The Sound Blaster 1.x driver only supports mono sound, not stereo.
There are updated drivers for the Sound Blaster Pro available on GO
PACVEN.

=====================================================================
3.14.   Installing the Sound Blaster CD-ROM Driver for Windows NT

Question:

How do I install the driver for my Sound Blaster CD-ROM drive?

Answer:

The Windows NT CD includes a driver for the CD-ROM interface on the
Creative Labs Sound Blaster card. This driver is included only on the CD
(not on the floppy disks) and is located in the
DRVLIB\STORAGE\MKECR5XX\X86 directory. This driver also supports the
Panasonic CR-52x family of CD-ROM drives and the Panasonic CR-56x family
of CD-ROM drives.  More information on installation is contained in the
README0.TXT file included with the driver.

NOTE:  The Sound Blaster CD-ROM driver (MKECR5XX) that ships with
Windows NT is for accessing data, MIDI, and .WAV files only.  It is not
compatible with either the Media Player (CD Audio option) or the CD
Player utilities provided with Windows NT and cannot play CD Audio
files.

Neither the Sound Blaster Pro or the most prevalent CD-ROM drives that
accompany the sound card and its proprietary interface (Panasonic CR-521
and the CR-561) support Multimedia (CD Audio) operation in Windows NT.

=====================================================================
3.15.   Adding a CD-ROM After Installing Windows NT

Question:

What do I need to do to make Windows NT recognize my new CD-ROM?

Answer:

From the Services application in Control Panel, locate the Scsicdrm and
Cdaudio entries. Set the Startup value for Scsicdrm to System so the
service starts when the system boots. If your CD-ROM does not support
SCSI-2 CD Audio, set Cdaudio Startup to System. Note: Some SCSI-1
CD-ROMs require the Cdaudio service as well.

To start these services without restarting Windows NT, highlight them
one at a time and press the Start button.

=====================================================================
3.16.   SCSI and ESDI Drives with More Than 1024 Cylinders

Question:

Can I use SCSI drives and ESDI drives with more than 1024 cylinders?

Answer:

SCSI uses RBA (relative block address) addressing. Normally, you do not
need to worry about a 1024 cylinder limit with a SCSI drive until it
becomes very large (greater than 1GB). Some SCSI cards have a jumper for
greater than 1GB support. Check you SCSI documentation to see if your
SCSI controller has this feature.

ESDI uses CHS (cylinder, head, sector) addressing and 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 operating systems) must duplicate
the code found in these BIOS chips in order to duplicate this behavior.
Unfortunately, there are many ways of performing this translation,
making it necessary to incorporate them all in the standard AT disk
driver. Support for every ESDI translation scheme was not included in
Windows NT.

Note: Some ESDI controllers implement this translation in hardware,
making it totally transparent to the system and allowing the standard
driver to work without change. Check your controller documentation to
see which type of translation is provided by your hardware.

=====================================================================
3.17.   Archive Python Tape Drive - No drive detected

Question:

Why do I get the following error?

   Archive Python: No drive has been detected.
   Make sure a drive is attached and power is on.

Answer:

The Archive Python driver was not installed. From the Options menu of
Windows NT Setup choose Add/Remove Tape Devices to install the proper
driver.

=====================================================================
3.18.   NEC CD-ROM Slow Downs

Question:

When my NEC CD-ROM plays audio CDs Windows NT slows down dramatically.
Why?

Answer:

It was recently discovered that NEC Intersect CD-ROM readers have
switches that enable disconnects during accesses to the reader. This
switch is off by default, disabling disconnects. Because of this, while
your CD-ROM is being read, no other devices on that SCSI bus can be
accessed. Since reads from a reader can take a significant amount of
time, having this switch off can noticeably degrade system performance.
This slow-down may occur even if you are not using the CD-ROM reader.

The switch is number 5 and should be set to ON. It can be found in a
little box labeled SW1.

=====================================================================
3.19.   ATI Driver Won't Display a Higher Resolution

Question:

Why can't I make my Windows NT ATI drivers display higher resolutions?

Answer:

The ATI driver uses the monitor resolutions that the adapter has been
physically configured for on the card itself. This prevents the driver
from setting the monitor to a resolution it may not support. Use the ATI
INSTALL utility to configure the monitor settings for the desired
resolutions. Note: The driver will not display a resolution that the
adapter does not have enough memory for.

=====================================================================
3.20.   Trouble-Shooting ATI Problems

Question:

I loaded Windows NT ATI driver and it does not function correctly.  How
do I track down the problem?

Answer:

If you have ROM BIOS shadowing enabled, disable it. Make sure you do not
have a conflict between the memory base address or I/O port address
assignment for the ATI card. Make sure you do not have any other
peripheral devices set to the same settings. Look out for conflicts
between your ATI card and a SCSI controller in the area of I/O port
address assignment particularly. Use the event logger to determine when
a conflict has occurred and what I/O addresses are in conflict.

=====================================================================
3.21.   Display 16 and 32 Bit Color Modes in ATI Adapters

Question:

I have an ATI card that I want to display 16 bit or 32 bit color. It
does not work. Is there something wrong with the driver?

Answer:

16 and 32 bit color modes are currently only available when the memory
aperture is enabled. Check to make sure that the memory aperture is
enabled. If you are using an ISA ATI card in an EISA PC (or any PC), be
advised that the aperture can only be enabled if you have 12MB or less
of system memory. (This is an ISA addressing restriction.) To display 16
bit or 32 bit color in an EISA PC, you need one of ATI's EISA card
products. The same applies to MicroChannel (MCA) PCs. Contact ATI for
information on how to obtain the correct card.

=====================================================================
3.22.   UART Support

Question:

Does Windows NT support 16550 UART chips?

Answer:

Windows NT will work with a 16550 UART chip. FIFO support will be
enabled by default if detected on the machine. However, if you
experience dropped connections, or loss of characters during high
transmission speed, we recommend disabling the FIFO support.

=====================================================================
3.23.   System Hangs on Micronics Motherboard with Ultrastor U34F

Question:


How can I make Windows NT work on my system that has a Micronics 486
VESA local bus motherboard with an Ultrastor U34F local bus controller?

Answer:

There are two ways to work around this problem. You can disable the
external cache on your motherboard. Or, you can return your motherboard
to Micronics for repair. Micronics is aware of this problem and has a
fix available. The reference number for the Micronics fix is VLBA03.
Micronics can be reached at [phone].

This problem is caused by a timing conflict between Windows NT, the
Ultrastor controller, and the Micronics motherboard. Note: This problem
does not occur on Micronics MX30 motherboards or ISA bus controllers
from Ultrastor.
=====================================================================
3.24.   S3 Based Video Card and High Resolutions

Question:

I have an S3 based video card, when I try to use the high resolution
drivers included with Windows NT my screen turns an orange color and the
logon box is black, what's wrong?

Answer:

You have a device configured to address 02E8 (COM 4).

The S3 graphics controller chip uses the port address 46E8 for one of
its register sets. When only the first 10-bits of this 16-bit address
are decoded in any operation the address appears as hex port address
02E8, which is a popular hex port address for a COM 4 serial port. This
results in an address conflict and can prevent COM 4 from functioning
and also strange colors or unpredictable behavior in Windows NT.

=====================================================================
3.25.   Intel SatisFAXion 400/i Modem

Question:

How do I get my Intel SatisFAXion 400/i modem to work under Windows NT?

Answer:

The Intel SatisFAXtion 400/i is not currently supported under Windows
NT.  Please contact Intel for information regarding the availability of
a device driver for this modem.


=====================================================================
3.26.   TIGA Drivers for Windows NT

Question:

Are there TIGA drivers for Windows NT?

Answer:

We do not have support for the TIGA cards at this time.  Check GO MSL
for any new or updated drivers.

=====================================================================
3.27.   No Speaker Driver for Windows NT

Question:

Will there be a speaker driver for Window NT?

Answer:

In the current release of Windows NT, there is no support for a PC
speaker driver.  The very nature of this driver prohibits its use.  A
preemptive multitasking operating system will not allow enough CPU
cycles to generate the sound.  The sound is generated by pulse with
modulation which requires 100% of CPU time while the sound is being
played.  Sound cards offload this to their DAC chips.


===================================================================== 4.
TECHNICAL INFORMATION
=====================================================================
4.1.    Couldn't Find NTLDR

Question:

When I select Windows NT from Boot loader it comes up with the following
error:

   BOOT: Couldn't find NTLDR
   Please insert another disk

Answer:

In order for Boot loader to start 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 installation set, you can find NTLDR as NTLDR.$
on disk 2. To expand this file and copy it to the correct location, type
the following:

   expand ntldr.$ c:\ntldr.

=====================================================================
4.2.    How the LibPath Environment Variable Works

Question:

I used to use the LIBPATH environment variable to search for DLL files.
The environment variable is no longer available under Windows NT. What
do I use as a replacement?

Answer:

There is no Win32 or NT LIBPATH environment variable or Registry entry
under Windows NT. DLLs are found just like executable files (EXE files)
on the path.

=====================================================================
4.3.    File Compression Programs and Drivers (Doublespace)

Question:

Is Windows NT compatible with my hard disk compression driver?  Does
Windows NT support MS-DOS 6.0 Doublespace?

Answer:

You cannot place Windows NT on a partition with Stacker, DoubleSpace
(Microsoft MS-DOS 6.0) or any other compression or partitioning
software. 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.  Windows NT supports
the MS- DOS FAT file system and applications.  It does not support
Doublespace, the integrated data compression technology available with
MS-DOS 6.0.  We are looking to make this technology available in a
future release of Windows NT.

=====================================================================
4.4.    Troubleshooting 16-bit Windows Applications Under Windows NT

Question:

My 16-bit Windows application is not working under Windows NT. What
should I do?

Answer:

Many different 16-bit applications designed to run under Windows 3.1
have been tested with Windows NT.  When you are troubleshooting a 16-bit
application that is not working properly under Windows, the following
items should be taken into consideration:

- If possible, verify that the application works correctly under Windows
  3.0 and 3.1.

- If the application requires a VxD (virtual device driver), it will not
  work properly under Windows NT.

- If the application requires Windows 3.0 or 3.1 to be running in 386
  enhanced mode, the application will not function properly on either
  the DEC Alpha or MIPS versions of Windows NT at this time because
  these platforms currently emulate only the Intel 80286 architecture.

- Check Print Manager to see that a default printer has been selected.
  Some applications (such as Microsoft Word version 2.0 for Windows)
  will not function properly under Windows NT unless a default printer
  has been selected.

- Make sure that any dynamic link libraries (DLLs) used by the
  application are both current and locatable by the application (either
  in the system path or explicitly defined within the application or
  working directory.)

Try other standard trouble-shooting steps such as the following:

 - Remove unnecessary device drivers - Remove unnecessary hardware -
   Boot with clean AUTOEXEC.NT and CONFIG.NT files - Use standard device
   drivers in Windows NT (Standard VGA, etc.)

If normal trouble-shooting procedures do not help, 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.

=====================================================================
4.5.    Using fault tolerance mirroring in Windows NT

Question:

Why am I unable to choose the Establish Mirror or Stripe Set With Parity
options under Disk Administrator in Windows NT?

Answer:

Only Windows NT Advanced Server supports the hard disk fault tolerance
options of mirroring (which includes duplexing) and striping with
parity.



=====================================================================
4.6.    OS/2 Subsystem Takes Priority

Question:

Why is that 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 CPU, it
automatically runs under the OS2 SubSystem if available.

The OS2 SubSystem is available by default on an 80x86. In order to force
bound applications to run as an MS-DOS application, use the FORCEDOS
command. It can be found in your \%SystemRoot%\system32 directory.


=====================================================================
4.7.    ANSI.SYS Support

Question:

Does Windows NT support the use of ANSI.SYS?

Answer:

Windows NT does support the use of ANSI.SYS for backward compatibility
with MS-DOS-based applications which require it. However, when you start
a Command Prompt, you are not running ANSI.SYS, so escape sequences do
not function.

1. Add the following line to your CONFIG.NT file in your
   %SYSTEMROOT%\SYSTEM32 directory:

      device=%systemroot%\system32\ansi.sys

2. Start a command prompt.

3. Run COMMAND.COM from MS-DOS 5.0. Note: This must be the version that
   comes with MS-DOS 5.0. If you just type COMMAND, the system starts
   another CMD.EXE from Windows NT. Check the version with the VER
   command. It should be "MS-DOS 5.00," not "Windows NT Version 3.10."
   Also, remember to include extra environment space if you are going to
   use the PROMPT variable.

You should now be able to send ANSI escape sequences. To test this, try
the following example:

   prompt $e[J

This should clear the screen.

Note: When you type EXIT at the command prompt, only COMMAND.COM is
exited; you need to type EXIT a second time to close the Windows NT
command prompt.

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

4.8.    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 11 (Other Application Environments)
in the Windows NT System Guide for more information about using PIF
files.

=====================================================================
4.9.    Converting File Systems without Reformatting

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.

For example: To convert drive "D:" from FAT to  NTFS format, type the
following command:

    convert d: /fs:ntfs

=====================================================================
4.10.    Removal of NTFS

Question:

How do I remove my NTFS partition from my C Drive?

Answer:

The CONVERT utility cannot change an NTFS-formatted drive to a drive
formatted by another file system. It is necessary to reformat an NTFS
drive in order to change the file system. If Windows NT is not installed
on the NTFS partition you are trying to remove, use the FORMAT command
from a Windows NT command prompt to change the file system, or use the
Disk Administrator to remove the partition directly.

Windows NT does not permit you to format the drive that it is installed
on. To reformat a drive containing Windows NT:

1. Start Windows NT Setup.
2. Choose Custom Installation.
3. If Setup suggests a path in which to install Windows NT, press N to
   select a new location. 4. When Setup asks you to select the partition
   where you would like to install Windows NT, choose the NTFS drive you
   want to reformat and press P to delete the partition. 5. Either continue
   from here using the setup program to recreate and format the partition
   or exit Setup and use the FDISK and FORMAT commands to complete the
   process.

=====================================================================
4.11.   CHKDSK /F on an NTFS Drive

Question:

Why won't Windows NT let me run CHKDSK /F on NTFS formatted drives?

Answer:

There are two reasons for this:

1. If you see the message

      Cannot lock the current drive.

   make another drive current. For example, if you are trying to run
   CHKDSK /F on the D drive, make C current by typing "C:" and ENTER
   before issuing the CHKDSK command.

2) If you see the message

      Cannot lock the drive for single user.

   it indicates that there are open files on the drive you are
   attempting to check.  If Windows NT is not installed to the drive in
   question, simply be sure that all applications that might have files
   open on the drive are closed. If you have a page file on the drive,
   that too must be moved by using the Virtual Memory application in
   Control Panel. You should then be able to run CHKDSK with the /F
   option.

   If Windows NT is installed to the NTFS drive for which you are trying
   to run CHKDSK /F, then it will not be possible to fix errors without
   restarting Windows NT.

   When CHKDSK /F is unable to execute, it prompts the user with a
   message similar to the following:

     Chkdsk cannot run because the volume is in use by another
     process.  Would you like to schedule this volume to be
     checked the next time the system reboots? (Y/N)

   If you choose Y, CHKDSK /F is executed the next time Windows NT is
   started.

=====================================================================
4.12.    MS-DOS Device Drivers in CONFIG.SYS

Question:

How do I load device drivers in CONFIG.SYS for my MS-DOS applications?
Are there drivers that I will not be able to load?

Answer:

You can only use device drivers in CONFIG.SYS that touch parts of the
system that are emulated by the Windows NT VDM (Virtual DOS Machine)
code. This is why ANSI.SYS works (because the display is an emulated
device) but ASPI drivers don't (since the hardware is not emulated.)

If you have some software that requires a device driver, it is likely
that the vendors who produced it need to write a VDD (Virtual Device
Driver) for that driver, and possibly a Windows NT Device Driver to
support that VDD. The information required to write these drivers can be
found in the Windows NT DDK.

=====================================================================
4.13.   Replacing Boot Sector Without Reinstalling

Question:

How do I replace my Windows NT boot sector without reinstalling Windows
NT?

Answer:

1. Boot from the floppy setup disk you used to install Windows NT.
2. Choose the option to use the emergency repair disk that was created
   during installation.
3. Be sure the option to "verify boot files on your C: drive" is
   selected.
4. Proceed with the repair operation.

If the Emergency Repair disk is not available, use the MKSECT.ZIP
utility which is available in Library 1 of the WINNT forum on
CompuServe.  If neither of the above are options for you, reinstall
Windows NT.

=====================================================================
4.14.    Microsoft Visual C++ (MMD.386 virtual device driver not loaded)

Question:

Why do I get the following error when I run the Microsoft Visual C++
compiler Windows NT?

   MMD.386 virtual device driver not loaded.

Answer:

Visual C++ requires a driver in the SYSTEM.INI file which is specific to
Windows 3.1.  You can not use the compiler in this fashion under Windows
NT. Please refer to the MSLANG forum for more information.

=====================================================================
4.15.   Microsoft Visual C++ (XXXX.EXE is not a valid Windows NT
application)

Question:

Why do I get the following error message when I run a Microsoft Visual
C++ utility under Windows NT?

  XXXX.EXE is not a valid Windows NT application.

Answer:

Visual C++ apps requires that you fix the executables in order for them
to run correctly under Windows NT.  You can get the fix from Library l
of the MSLNG32 forum.  The file is called b2fix.exe.  It is a
self-extracting archive and contains instructions on how to use this
utility to fix the problem.  This program is a NOT supported by
Microsoft, but only provided so that MSVC will operate properly under
Windows NT.

=====================================================================
4.16.   What is Win32s?


Question:

 I know what Win32 is but what is win32s?

Answer:

Win32s is an operating system extension that allows Win32 applications
for Windows NT to run on Windows 3.1 and Windows for Workgroups. This is
done by adding some extra DLLs to Win31 and keeping the differences
between Windows NT and Win31 in mind while writing your Win32s code
(such as preemptive multitasking, memory management, and security).
There is a booklet in the Win32 SDK that covers Win32s.

=====================================================================
4.17.   Recreating a Post Office


Question:

I deleted the WGPO subdirectory.  I assumed that I would be able to
recreate it.  It turned out to not be as easy as expected. Is there any
way of recreating my mail system short of reloading Windows NT?

Answer:

Yes, by editing the Registry database.  Before editing the Registry
database,  CAUTION: you might want to back up (export) any mail you want
to retain before proceeding with the following:

1. Using File Manager, delete the postoffice directory and all
   subdirectories in it.  The default name of the Windows NT postoffice
   directory is WGPO and it can be located in the root directory or a
   subdirectory of any available partition on the hard disk drive.

WARNING: Using Registry Editor incorrectly can cause serious,
system-wide problems that may require you to reinstall Windows NT to
correct them. Microsoft cannot guarantee that any problems resulting
from the use of Registry Editor can be solved. Use this tool at your own
risk.

2. Start Registry Editor (REGEDT32.EXE) and select the following subkey
   to highlight it:

      HKEY_CURRENT_USER\Software\Microsoft\Mail\Custom Commands

      HKEY_CURRENT_USER\Software\Microsoft\Mail\Custom Messages

      HKEY_CURRENT_USER\Software\Microsoft\Mail\Microsoft Mail

3. Press the DELETE key on your keyboard, or choose Delete from the Edit
   menu, and then press ENTER to confirm the action.  One subkey at a time.

The next time you start MS Mail, you will have the option of connecting
to an existing postoffice, or creating a new postoffice, and then
continuing with the rest of the initial MS Mail setup.


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

5.1.    TCP/IP Support


Question:

Does Windows NT have complete TCP/IP support?

Answer:

Windows NT contains full TCP/IP support. Machines running Windows NT
with the TCP/IP protocol stack are able to communicate with LAN Manager
2.x servers and workstations. Windows NT also has an extensive set of
TCP/IP utilities including Telnet, ftp, rcp, rsh, and others. Utilities
not included with Windows NT will be provided by third party vendors.

=====================================================================
5.2.    Replicator Service only allows me to Import files

Question:

On Windows NT machines, the replicator service only allows me to import
files or directories. To use export replication, do I need a Windows NT
Advanced Server or LAN Manager for OS/2 server?

Answer:

Yes. You must have a Windows NT Advanced Server system to export with
the file replicator. These additional rules apply to replication under
Windows NT:

 - Windows NT systems can import from a Windows NT Advanced Server
   exporter.

 - OS/2 LAN Manager systems can import from a Windows NT Advanced
   Server.

 - Windows NT Advanced Server systems can import from other Windows NT
   Advanced Server systems (or even the same machine).

 - OS/2 LAN Manager exporting to Windows NT is not supported.

=====================================================================
5.3.    Network Fails To Start

Question:

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

Answer:

Please refer to Chapter 18 of the Windows NT System Guide, titled
"Troubleshooting". Also, check for the following:

 - Interrupt conflicts
 - Memory conflicts
 - Duplicate machine names
 - Correct network configuration and card settings

If you are having difficulties still, please refer to the document
bundled with your Windows NT package, titled "Your Guide to Service and
Support for Microsoft Windows NT".

=====================================================================
5.4.    Using Telnet in Windows NT

Question:

How can I use Telnet in Windows NT?

Answer:

Telnet was implemented as a Windows NT Service. You can start the Telnet
service by typing TELNET at the command prompt. This starts the Telnet
service and Terminal, the front-end for Telnet. The normal Telnet
commands can be issued from Terminal. For more information on Telnet
commands, refer to the online command reference or the Windows NT
documentation.

=====================================================================
5.5.    LAN Manager and Windows NT Domains

Question:

Why do I get an error when I use my LAN Manger 2.x domain name in the
Domain name field in Windows NT Setup?

Answer:

The Domain entry in Windows NT network setup refers to a Windows NT
Advanced Server domain. In order to participate in a LAN Manager 2.x
domain, you need to specify the LAN Manager 2.x domain name as the
workgroup name. After you do this, you should be able to see LAN Manager
2.x servers from File Manager and from the command prompt by typing NET
VIEW.

Note: Windows NT Advanced Server is a separate product which provides
additional enterprise-wide, domain-based network management and advanced
fault-tolerance features. LAN Manager 2.0 and WFW do not pass domain
names on the network. This problem was addressed in LAN Manager 2.1 and
thus LM 2.0 and LM 2.1 may behave differently when NET USE or NET LOGON
commands are issued.

=====================================================================
5.6.    Windows NT Advanced Server Upgrade

Question:

Will there be a Windows NT Advanced Server upgrade that allows me to
upgrade my Windows NT workstation?

Answer:

Such an upgrade package will not be made available at this time due to
the importance of other priority features (such as LAN Manager 2.x and
Windows 3.x upgradability). This will become a priority in future
versions of Windows NT.



=====================================================================
5.7.    Difference Between Workgroup and Domain

Question:

What is the difference between a Domain and a Workgroup in Windows NT?

Answer:

The primary differences between a Workgroup and a Domain are in the
storage location of user accounts and which machine handles account
validation. In a Workgroup, the account information is maintained and
validated on each workstation locally. In a Domain, account information
is maintained on a primary server (domain controller) or replicated
across a group of servers; Account permissions are validated by the
servers and are consistent across the entire Domain.

LAN Manager 2.x servers may also be members of a Windows NT Advanced
Server domain.

=====================================================================
5.8.    Network Drives Display Slowly in Open Dialog Box

Question:

Why does it take some time before all the network drives appear in the
Open dialog box?

Answer:

In Windows NT, the common dialog box, Open, is multi-threaded. When you
use either the Open or Save options from a File menu, the dialog box is
displayed and a thread is initiated to enumerate network drives. The
dialog box can finish painting before the enumeration thread if there
are many network connections in use.

=====================================================================
5.9.    Network Directory Listing Enumeration

Question:

Do I have to wait until the entire directory is enumerated before I can
access files or switch to other drives?

Answer:

No. As soon as you see the Open dialog box, you can switch to other
drives and access files. If network drive letters or files do not appear
immediately, you can still access them by typing them into the File Name
field.

=====================================================================
5.10.   RAS and TCP/IP

Question:

Does RAS for Windows NT or Windows NT Advanced Server support TCP/IP
utilities such as Telnet?

Answer:

No. RAS for Windows NT does not support TCP/IP or the Sockets Library
from a RAS client at this time. You cannot run any TCP/IP utilities that
rely on this functionality over a RAS connection.

RAS does support NBF, IPC, RPC, Mail Slots (2nd class), Named Pipes, and
MS LAN Manager (Winnet API set). Any applications which rely on this
connectivity should work over a RAS connection.

The Windows NT RAS Server does provide gateway functionality for
protocol converting. The following will work:

- RAS Client [Windows NT or RAS 1.x] dials into a Windows NT RAS Server
  using NBF.

- RAS Server gateway component receives the frame from the NBF stack.

- The RAS Server gateway sends the frame down whatever protocols are
  installed on the server [ie. TCP/IP] and then out on the LAN wire.

- Another LAN Server running TCP/IP could receive the frame and respond
  to the RAS client via the RAS Server.

In this way, RAS Clients can take advantage of the connectivity of
TCP/IP over RAS.

=====================================================================
5.11.   Connecting to a Novell Server

Question:

How do I connect my Windows NT workstation to a Novell server?

Answer:

Currently, Microsoft does not include redirection connectivity to Novell
Netware servers as shipped with Windows NT. Novell is currently in the
process of developing their requester for Windows NT which will allow
Windows NT client workstations to connect to Netware servers.  Novell
has released beta versions of the requester (available in the NOVFILES
forum).

Windows NT does come with NWLINK which should not be confused with the
requester Novell is developing.  NWLINK allows use of Windows NT as an
application server with current MS-DOS, Windows, or OS/2 NetWare clients
(for applications such as SQL Server, SNA Server, and RPC supporting SPX
and Novell NetBIOS over IPX). NWLINK does not support the ability to do
remote file and print I/O.  For more information on NWLINK see pages
609-614 of the Windows NT Advanced Server Manual or pages 505-510 of the
Windows NT manual.



===================================================================== 6.
COMMON ERROR MESSAGES
=====================================================================
6.1.    Error 0000001E

Question:

What should I do about error 0001E?

Answer:

This error is caused by an exception error that is not handled at any
level. It generally refers to a file system problem. Run CHKDSK or
another similar utility on the drive in question. If your hardware is on
the hardware compatibility list, please submit a bug report.

=====================================================================
6.2.    NTVDM Error

Question:

When I run MS-DOS or Windows 3.1 applications, I receive the following
error message. Why?

   Insufficient memory or Disk Error in NTVDM or NTVDM Error's.

Answer:

Try the following:

 - Increase the swap file size to at least 20MB.
 - Make sure the video card is on the hardware compatibility list
   (0793HW.DOC). If it is not, try using the standard VGA driver.
 - Verify that the WOWEXEC.EXE is not corrupted by copying over a clean
   copy.

=====================================================================
6.3.    Error 0x00000069 or 0x00000067

Question:

I get Error 0x00000069. What should I do?

Answer:

This is an initialization error that occurs when Windows NT tries to
talk with the hard drive controller. It can be caused by many things.
Try the following work arounds:

 - Slow down the DMA transfer rate on the controller.

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

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

 - Make sure you are not using a faulty or unsupported driver.

 - Make sure NTDETECT.COM is in the root of the boot drive partition.
   Missing Windows NT files can also cause Error 69.

=====================================================================
6.4.    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
an adapter such that the setting now disagrees with the setting you
specified during Setup. It is possible that you have installed a new
card since you installed Windows NT or, that you have an interrupt
conflict with some other piece of hardware in your system. In addition,
try the following:

 - Disable all CPU caching, BIOS shadowing and use non-turbo mode. If
   successful, re-enable these one at a time to determine which caused
   the problem.

 - On EISA systems, incorrect configuration files (for ISA devices) can
   cause this error. If you are using generic configuration files for
   ISA devices, check their validity or remove them completely.

=====================================================================
6.5.    System Error F002

Question:

What is System Error F002?

Answer:

System Error F002 is usually generated when there is a faulty piece of
hardware, like a bad memory chip. It can also be caused by a hardware
incompatibility caused by one of the following:

 - Memory parity errors
 - Adapter asserting an I/O channel check on the bus, (VGA or network
   cards)
 - Math coprocessor error

If any of these occur, run your computer manufacturer's system
diagnostic utilities.

=====================================================================
6.6.    Setup Fails with SCSI Read Request Error

Question:

Why do I get the following error during Windows NT Setup:

    SCSI read request failed Arc status 8 Srb status 0084

Answer:

AutoCheck is unable to resolve file system or FAT problems on the drive.
Run a diagnostic utility such as CHKDSK on the file system and fix any
problems you find. Afterwards, reinstall Windows NT.

=====================================================================
6.8.    LogErrorEntry Error (UniqueId=300)

Question:

What should I do about a LogErrorEntry error with UniqueId 300?

Answer:

If you receive the following error during the installation of Windows NT
on a machine with an Adaptec 1542b card, remove the BUSLOGIC.SYS file
from the Setup disk and reinstall.

     LogErrorEntry: logging SCSI error packet. ErrorCode=Internal
     adapter error.  PathId=0,TargetID=0,Lun=0,UniqueId=300.


=====================================================================
7.    OTHER FILES ON COMPUSERVE
=====================================================================


These files can be found in the WINNT forum in the specified library:

Library 1
=========
NEWUPS.TXT  1  2K 15-Oct-93 New Uploads in WINNT (last 30 days)
NTTCP.EXE  1  257K 13-Oct-93 Internetworking With TCP/IP on NT
MSL.ZIP 1 65K 8-Oct-93 Catalog of Software Library
LMUPGD.EXE 1 45K 8-Oct-93 Lan Manager to Windows NT Upgrade Data Sheet
INDEX.ZIP 1  2K 8-Oct-93 Index of Files in WINNT as of 10/08/93
RESKIT.ZIP 1 57K 4-Oct-93 Three Updated Windows NT Resource Kit Utils
BUGRPT.TXT 1 1K 1-Oct-93 Report form for product problems/suggestions
MENU.ZIP 1 1K 30-Sep-93 Microsoft map of the new Compuserve menu structure
MENU.TXT 1 4K 30-Sep-93 Microsoft map of the new Compuserve menu structure
MSNREL.TXT 1 22K 29-Sep-93 Microsoft Develops New Portfolio of Tech.
MSNREL.ZIP 1 7K 10-Sep-93 Microsoft Develops New Portfolio of Tech.
WINNT.TXT 1 4K 31-Aug-93 One-Line descriptions of the files in WINNT
WINNT.CAT  1    9K 31-Aug-93 Directory listing of the WINNT Forum
SAMPLE.TXT  1    5K 27-Aug-93 Sample Bug Report Template (BUGREP.TXT)
OS2APP.ZIP   1    1K 31-Aug-93 Text File List of OS/2 Apps
OS2API.ZIP   1   21K 31-Aug-93 OS/2 1.x APIs supported by Windows NT
OS2AP.ZIP    1    4K 31-Aug-93 Excel Spreadsheet of OS/2 apps
BUGREP.TXT  1    3K 31-Aug-93 Bug Report Template for Windows NT
HCLHLP.ZIP  1  147K 19-Aug-93 Windows NT v3.1 HCL WinHelp File
0793HW.ZIP  1   46K 03-Aug-93 Final Windows NT v3.1 HCL
0793HW.TXT  1   92K 03-Aug-93 Final Windows NT v3.1 HCL
NTREL.DOC  1   10K 27-Jul-93 Press announcement of Windows NT
SNADAT.ZIP  1   65K 14-May-93 SNA Server product info
ASINFO.ZIP  1 59K 23-Apr-93 Info sheet on Windows NT Advance Server
NT_NW.ZIP 1 92K 08-Apr-93 Using Windows NT in NetWare Environments
W32CA2.ZIP 1 203K 12-Jan-93 Text catalog of 32-bit Windows NT apps
W32CAT.ZIP 1 239K 04-Jan-93 WinWord catalog of 32-bit Windows NT apps
DOSNT.OS2   1    3K 11-Dec-92 How to install DOS, NT, and OS/2 2.0.
BOOTNT.TXT  1   11K 03-Nov-92 Boot NT from OS/2 boot manager
DSNTOS.TXT  1  4K 02-Oct-92 LOADING DOS NT & OS2 ON SAME SYSTEM
HWFEED.TXT 1 3K 16-Sep-92 Form to use to send suggestions for H/W supp.
CONFIG.ZIP 1 4K 30-Jul-92 Os/2 Subsystem Config.sys and custom device drive

Library 2
=========
CSD525.EXE   1   6,288K 8-Oct-93 NT _NTAS CSD 001 Update Complete Disk
Set for 5.25
UPDATE.TXT  1  9K 7-Oct-93 Windows NT _Advanced Server Update README
FIRST
RUNME5.EXE  1  79K 7-Oct-93 NT _NTAS Update for 5.25 Disk Set Disk 1
RUNME3.EXE  1  79K 7-Oct-93 NT _NTAS Update CSD001 Disk 1 of 6
P1_5_6.EXE   1   573K 7-Oct-93 NT _NTAS Update for 5.25 Disk Sets Disk 6
P1_5_5.EXE   1   1,152K 7-Oct-93 NT _NTAS Update for 5.25 Disk 5
P1_5_4.EXE   1   1,144K 7-Oct-93 NT _NTAS Update for 5.25 Disk 4
P1_5_3.EXE   1   1,127K 7-Oct-93 NT _NTAS Update for 5.25 Disk 3
P1_5_2.EXE   1   1,103K 7-Oct-93 NT _NTAS Update for 5.25 Disk 2
P1_5_1.EXE   1   1,090K 7-Oct-93 NT _NTAS Update for 5.25 Disk 1
P1_355.EXE   1   722K 7-Oct-93 NT _NTAS Update for 3.5 Disk Sets Disk 5
P1_354.EXE   1   1,409K 7-Oct-93 NT _NTAS Update for 3.5 Disk 4
P1_353.EXE   1   1,406K 7-Oct-93 NT _NTAS Update for 3.5 Disk 3
P1_352.EXE   1   1,407K 7-Oct-93 NT _NTAS Update for 3.5 Disk 2
P1_351.EXE   1   1,230K 7-Oct-93 NT _NTAS Update for 3.5 Disk 1
CSD35.EXE    1   6,272K 7-Oct-93 NT _NTAS CSD 001 Update Complete Disk
Set for 3.5
T348I.ZIP   2   15K 19-Aug-93 WDL : Trantor T348 Miniscsi Plus Driver
(Intel)
SNY31M.ZIP  2   37K 19-Aug-93 WDL : Sony CSU 31a CD-ROM Driver (MIPS)
SNY31I.ZIP  2   27K 19-Aug-93 WDL : Sony CDU 31a CD-ROM Driver
MKECR5.ZIP  2   25K 19-Aug-93 WDL : Panasonic CR-52x & CR-56x CD-ROM
driver
IBM4MI.ZIP  2   65K 19-Aug-93 WDL : IBM 2.0GB 4mm Tape Drive Driver
(Intel)
CPQVGI.ZIP  2   17K 19-Aug-93 WDL : Compaq AVGA Video Driver (INTEL)

Library 3
=========
OS2TOO.ZIP    1    115K 14-Oct-93 OS /2 Utilities
SAMPLE.TXT  3 5K 31-Aug-93 Sample Bug Report Template (BUGREP.TXT)
BUGREP.TXT  3 3K 31-Aug-93 Bug Report Template for Windows NT.
GR.ZIP 3 26K 09-Apr-93 GR.EXE : Command-line Registry retrieval program

Library 4
=========
SMBTRC.EXE  4   97K 29-Aug-93 SMBTRACE : Network Diagnostic Tools
RG2INI.EXE  4   72K 29-Aug-93 REGINI.EXE : Registry Change by Script
Utility
PVIEW.EXE   4   66K 29-Aug-93 PVIEWER : Process and Thread Viewer for
Windows NT
PSTATS.EXE  4   48K 29-Aug-93 PSTAT.EXE : Process & Thread Status
Utility
MKSECT.EXE  4   19K 29-Aug-93 MKSECT Reinstall Flexboot for MS-DOS 5.0 &
Windows NT
FIFO.EXE    4   19K 29-Aug-93 FIFO Enable Tool for 16550 UART Chips on
Windows
EXETYP.EXE  4   42K 29-Aug-93 EXETYPE character based utility to
identify the Operating System
DRIVER.EXE  4   53K 29-Aug-93 DRIVERS.EXE : Drivers display utility
DETECT.EXE  4   33K 29-Aug-93 NTDETECT : Startup Hardware Detector
BROWST.EXE  4   59K 29-Aug-93 Browstat Utility for Viewing Browser
information
DELPRT.EXE  4   78K 27-Aug-93 DELPART Partition Removal Software

Library 5
=========
WEEK56.ZIP  5  446K 26-Jul-93 Messages from Week 56 of WINNT 7/16 - 7/23
WEEK55.ZIP  5  492K 21-Jul-93 Messages from Week 55 of WINNT 7/9 - 7/16
WEEK54.ZIP  5  353K 12-Jul-93 Messages from Week 54 of WINNT 7/2 - 7/9
WEEK53.ZIP  5  470K 06-Jul-93 Messages from Week 53 of WINNT 6/25 - 7/2
WEEK52.ZIP  5  455K 28-Jun-93 Messages from Week 52 of WINNT 5/18 - 6/25
WEEK51.ZIP  5  441K 21-Jun-93 Messages from Week 51 of WINNT 6/11 - 6/18
WEEK50.ZIP  5  497K 21-Jun-93 Messages from Week 50 of WINNT 6/04 - 6/11
WEEK49.ZIP  5  427K 07-Jun-93 Messages from Week 49 of WINNT 5/28 - 6/04
WEEK48.ZIP  5  544K 02-Jun-93 Messages from Week 48 of WINNT 5/20 - 5/28

Library 6
=========
<NONE>