SETUP.TXT
=========
This file contains information about problems that may occur
while running Windows Setup and describes problems that can
occur when using terminate-and-stay-resident (TSR) programs
or drivers with Windows or Windows Setup. If you are using
a TSR or if you encounter problems setting up Windows version
3.1, read this document BEFORE running Setup again.
General Setup Notes
====================
This section includes notes on specific system configurations
that may prevent Setup from installing Windows successfully.
A solution to each problem is provided.
If you are using a hardware or software product listed here,
follow the proposed recommendations before running Setup.
MS-DOS Screen Savers
---------------------
If you are using an MS-DOS screen saver, you should disable
it before running Setup. These screen savers can cause problems
when running Setup.
COMPAQ Computer with MS-DOS Version 5.0 and EGA or VGA
---------------------------------------------------------
If you are using the upgrade version of Microsoft MS-DOS
5.0, check your CONFIG.SYS file to make sure the following
drivers appear in this order:
HIMEM.SYS
EMM386.EXE
ANSI.SYS
Note: If you are using the COMPAQ version of MS-DOS 5.0,
HIMEM.EXE is used in place of HIMEM.SYS and CEMM.EXE
is used in place of EMM386.EXE.
If ANSI.SYS is loaded before HIMEM.SYS or EMM386.EXE (or if
you are using COMPAQ MS-DOS 5.0 before HIMEM.EXE or CEMM.EXE),
Setup may restart your system before Windows is installed.
Also, if you are using the DOS=HIGH,UMB command line to load
MS-DOS into upper memory, loading EMM386.EXE (or CEMM.EXE)
before loading ANSI.SYS will create the maximum amount of
upper memory space on a COMPAQ computer.
AT&T Safari Computer
--------------------
If you have an AT&T Safari computer, you cannot maintain two
versions of Windows (version 3.0 and version 3.1) on your
system. You must upgrade over version 3.0. If you set up
Windows 3.1 in its own directory, Windows will not use the
special drivers required for it to run on the Safari computer.
Using the TIGA Display Driver
-------------------------------
If you are using the TIGA display driver, you must load the
TIGACD.EXE MS-DOS driver manually before running Setup
to upgrade Windows. Otherwise, Windows will not upgrade
your system properly.
After successfully setting up Windows, you can increase the
amount of conventional memory available to non-Windows
applications when Windows is running in 386 enhanced mode
by loading TIGACD.EXE from the WINSTART.BAT file. The
WINSTART.BAT file runs only in 386 enhanced mode. If you
want to run Windows in standard mode, you must load
TIGACD.EXE manually. For more information, see the README.WRI
online document.
Displays That Are Incompatible with Windows Version 3.1
-------------------------------------------------------
Certain display adapters can cause problems with Windows
version 3.1. The most serious problem is a system
failure while running Windows Setup. If you encounter this
problem, run Custom Setup, and then select one of the standard
display types, such as VGA, provided with Windows version 3.1.
With other display drivers, Windows may be set up successfully
but TrueType fonts may not appear correctly on your screen.
An updated driver may be available in the Windows Driver
Library or from your display vendor or manufacturer. For
information about obtaining the Windows Driver Library,
see "Getting Started with Microsoft Windows."
The following display adapters may cause problems:
- ATI Graphics Ultra and Vantage
NOTE: These adapters are 8514/a-compatible and run well
with the 8514/a driver provided with Windows 3.1.
- All DGIS display adapters (Direct Graphics Interface Standard)
from Graphic Software Systems, including the following:
NEC MultiSynch Graphics Engine (MGE)
Zenith Z-649
HP IGC-10, IGC-20
GSS 1000 Series
NOTE: Some DGIS-based adapters are TIGA-compatible and
run well when used with the appropriate TIGACD.EXE
MS-DOS driver and with the TIGA driver provided with
Windows 3.1.
- HP Ultra VGA
- IBM Image Adapter/A
- Matrox MG Series/M-WIN Series
- Palettized VGA 640x480, 16-color (provided with Windows
Multimedia Extensions version 1.0)
- Radius SVGA MultiView
- All RGDI (Renaissance Graphics Device Interface) display
adapters from Appian, Inc., including the following:
Appian Rendition II, IIe, II/XE, and III
Appian GV1024
Decpc 433
- All S3 adapters, including the following:
Orchid Fahrenheit 1280
STB WIND/X
Diamond Stealth VRAM
Using Stacker
-------------
If you are using Stacker to compress your hard disk, there are
certain steps you need to take before setting up Windows.
* If you want to use a swap file with Windows, you must
set up the swap file on the uncompressed drive. When
setting up Stacker, you can leave at least 1 megabyte (MB)
of disk space uncompressed for storing system files. To
leave enough space for the swap file, it is recommended
that the amount of uncompressed disk space equal at least
twice the amount of system memory. For example, if your
system has 4 MB of memory, you should leave at least 8 MB
of disk space uncompressed.
If Stacker is already set up on your system and there is not
enough uncompressed disk space for a swap file, you can run
the STAC utility provided with Stacker to increase the amount
of uncompressed disk space. For more information, see your
Stacker documentation.
* If you are using Stacker version 2.0 or later, Windows Setup
modifies your CONFIG.SYS and AUTOEXEC.BAT files. When Setup
is finished making the modifications, it displays a message
at the end of the Windows portion of Setup notifying you of
the modifications. If you have used Stacker to swap your
startup drive, when you restart your system Stacker will
ask whether you want to update to the new version of the
CONFIG.SYS or AUTOEXEC.BAT file. It is recommended that you
update.
If you are using a version of Stacker earlier than 2.0, you
may need to modify your CONFIG.SYS and AUTOEXEC.BAT files
yourself. For more information, see "Modifying Your CONFIG.SYS
and AUTOEXEC.BAT Files Yourself," following this topic.
* For best performance, do not use SMARTDrive to cache the
compressed drive. You only need to cache the uncompressed
drive. You can include options on the SMARTDRV.EXE line of
the CONFIG.SYS file to specify which drives to cache.
For example, if the Stacker swap utility swaps drives C and
D so that C is compressed and D is uncompressed, you would
include the following line in your CONFIG.SYS file:
device=\windows\smartdrv.exe C- D+
For more information about swap files and using SMARTDrive, see
Chapter 14, "Optimizing Windows," in the "Microsoft Windows User's
Guide."
Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself
---------------------------------------------------------
When you set up Windows, Setup usually places the HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE files in the Windows directory.
If the Windows directory is on a disk that is not available
when you start your computer, such as a removable or nonlocal
disk, or if Setup detects one of the following conditions,
Setup does not modify the CONFIG.SYS or AUTOEXEC.BAT file:
- Your boot drive has been modified by a disk-compression
utility.
- Your CONFIG.SYS file contains references to block device
drivers.
- There is not enough available space on your hard disk to
copy the files.
- The files are already installed on your system and Setup
cannot overwrite them (they are read-only).
Instead, Setup writes proposed changes to the CONFIG.WIN and
AUTOEXEC.WIN or the CONFIG.00x and AUTOEXEC.00x files.
In this case, you must either move the HIMEM.SYS, SMARTDRV.EXE,
and EMM386.EXE files to a drive that is available when you start
your computer, or use a text editor to modify your CONFIG.SYS or
AUTOEXEC.BAT file so that any references to HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE appear after the device=
command line used to load the drivers for your disk drives. Refer
to the CONFIG.WIN and AUTOEXEC.WIN or the CONFIG.00x and
AUTOEXEC.00x files for the proposed changes.
Setting Up XGA on a PS/2 Model 75 or 90
-----------------------------------------------------
If you have a PS/2 model 75 or 90 with an XGA, Windows
Setup will configure the display adapter for 16-color,
640x480 resolution. Do not change this configuration
during Setup. Specifying a different XGA configuration
while setting up Windows may cause Setup to fail.
After you have successfully installed Windows, you can
configure your XGA to use a different resolution or 256 colors,
if your monitor supports it. For more information on how to do
this, see the topic "IBM XGA" in the README.WRI online
document.
If you are using the plasma screen on the PS/2 model 75, use
ONLY the 640x480, 16-color configuration. If you change this
configuration, you will be returned to the MS-DOS prompt when
you try to start Windows.
Correcting the "Out of Environment Space" Error Message
-------------------------------------------------------
If you receive an "out of environment space" message when
starting Windows, you can either:
* Increase the size of your environment by adding the SHELL=
command line to your CONFIG.SYS file. See your MS-DOS
documentation for more information about the SHELL command
and modifying your CONFIG.SYS file.
* Move the SET commands in your AUTOEXEC.BAT file
to the beginning of the file so that they run before the
commands that load terminate-and-stay-resident (TSR)
programs or drivers, such as SMARTDrive.
If Windows Setup Does Not Detect Your Network
---------------------------------------------
If you have a network installed and Setup specifies "No
Network" in the System-Information screen, Setup is not
able to detect your network. For Setup to detect certain
networks, the directory that contains the network program
files must be included in your path.
This is a known problem with these networks: 3Share, 3Open,
LAN Manager, and MSNet. If your path does not include the
directory where the network files are located, you can either:
* Add the directory to the PATH line in your AUTOEXEC.BAT
file.
* Run Custom Setup and specify the full path for your
network in the System-Information screen.
Using Terminate-and-Stay-Resident (TSR) Programs and Drivers
with Windows Version 3.1
=============================================================
The Program Listing section of this document lists several
terminate-and-stay-resident (TSR) programs and drivers that
are known to cause problems when running with Windows version
3.1. Some of the problems you may encounter include system
failures or an incorrect display of information on your screen.
In some cases, special steps are provided to solve the problems.
While setting up Windows version 3.1, Windows Setup searches
the AUTOEXEC.BAT and CONFIG.SYS files for references to TSR
programs and drivers, in addition to scanning memory for TSRs
that are currently running. If Setup detects a TSR that is
known to cause problems when running with Windows version 3.1,
a message appears, asking whether you want to continue or quit
Setup.
If you receive such a message, do the following:
1. Locate your TSR in the Program Listing section of this document
and use the information to determine if the situation encountered
prevents Windows Setup from successfully installing Windows 3.1.
2. If the situation does not affect Windows Setup, you can continue
setting up Windows 3.1 by following the instructions on your
screen.
If the situation does affect Windows Setup and prevents it from
installing Windows on your computer, follow the instructions
on the screen to quit Setup, and then complete the following
steps.
3. Quit the TSR and remove all references to it from your
AUTOEXEC.BAT and CONFIG.SYS files. For more information,
see the documentation for your TSR.
4. Restart your computer.
5. Run Windows Setup again.
After Windows is successfully set up, you may want to restore
your TSRs.
Not all TSRs or drivers included in the Program Listing section
are detected by Setup. The TSRs and drivers that Setup detects
are in the SETUP.INF file, listed under the names "incomptsr1"
and "incomptsr2".
Program Listing
===============
This section describes some problems, discovered during testing,
that you might encounter while using a TSR with Windows version 3.1.
It does not include all possible problems that can occur.
386MAX
------
The documentation for 386MAX recommends against setting the
EXT parameter below 64. If you set this parameter to 0, Windows
Setup and Windows running in standard mode will fail.
See the README.WRI online document for more information
about running 386MAX with Windows 3.1.
386MAX Disk-Cache Utility (QCACHE.EXE)
--------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed
with Windows 3.1, instead.
All Charge 386 Version 3.1
--------------------------
ALLEMM4.SYS is a memory manager that causes problems with
Setup and Windows 3.1. If you encounter problems running
this program with Windows, it is recommended that you use
EMM386.EXE and HIMEM.SYS, provided with Windows 3.1, to
manage memory instead.
Anarkey Version 4.00
--------------------
With some memory configurations, Anarkey version 4.00 running
with Windows 3.1 in 386 enhanced mode may cause unpredictable
system failures. In rare cases, this program can also corrupt
hard-disk data. In addition, Windows 3.1 might not start when
this program is running.
Do not run Windows 3.1 in 386 enhanced mode when Anarkey version
4.00 is running. Version 4.01 may correct these problems. Contact
Moderne Software for a free upgrade of Anarkey 4.01.
Anarkey Version 4.01
--------------------
If Anarkey version 4.01 is loaded before starting Windows in
standard mode, it is not available in any MS-DOS Prompt that
you start from Windows. In this case, it is recommended that
you load Anarkey from each MS-DOS Prompt, as needed.
Do not load Anarkey HIGH before starting Windows in 386
enhanced mode. If you load Anarkey HIGH, your system may
fail when you try to start an application.
APPEND (MS-DOS)
---------------
Do not use the APPEND utility with Windows 3.1. It prevents
Windows and Windows applications from creating valid
Well-Formed-Path (WFP) names for the files they are using.
(A WFP is the complete name of a file, including the drive
letter and full path specification, starting from the root
directory.)
ASP Integrity Toolkit Version 3.7
---------------------------------
This product is a virus-protection program that can cause
problems when running Windows Setup, including system
failure, automatic restarting of the system, and the inability
to use the keyboard. You should turn off protection in the
toolkit before setting up Windows 3.1. For information about
how to do this, see your ASP Integrity documentation.
NOTE: Setting up Windows is considered a system-administration
task. The ASP Integrity Toolkit documentation instructs
you to turn off protection when performing these types
of tasks.
Autocon Version 2.0e
--------------------
Autocon enables you to select up to fifty different configurations
when starting your system. To do this, it modifies the CONFIG.SYS
and AUTOEXEC.BAT files, based on information in its database
(AUTOCON.DAT), when you restart your system from within
AUTOCON.
Windows Setup modifies only the first section in the CONFIG.SYS
and AUTOEXEC.BAT files. If you want to use specific configurations
with Windows, you must run Autocon and then manually edit the
configurations in the database that you want to use. You must do
this after setting up Windows. For your changes to take effect,
you must restart your system from within Autocon. For more
information, see your Autocon documentation.
Bootcon Version 1.60
--------------------
Using Bootcon, you can maintain different system-configuration
information in your CONFIG.SYS and AUTOEXEC.BAT files. You can
then select the configuration you want to use from a menu when
starting your system.
Windows Setup modifies only the first section in the CONFIG.SYS
and AUTOEXEC.BAT files. You must edit the sections of those files
that contain the configurations you want to use after you set up
Windows. For more information, see your Bootcon documentation.
BOOT.SYS
---------
Using BOOT.SYS, you can maintain different system-configuration
information in your CONFIG.SYS and AUTOEXEC.BAT files. You can
then select the configuration you want to use from a menu when
starting your system.
Windows Setup modifies only the first section in the CONFIG.SYS
and AUTOEXEC.BAT files. You must edit the sections of those files
that contain the configurations you want to use after you set
up Windows. For more information, see your BOOT.SYS documentation.
CACHE.EXE Disk-Cache Utility
----------------------------
Do not use two disk-cache utilities with Windows 3.1. It is
recommended that you use SMARTDrive, provided with Windows 3.1,
and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If CACHE.EXE is detected,
Setup removes it from the CONFIG.SYS file for you.)
CACHE.SYS Disk-Cache Utility
----------------------------
This disk-cache utility will not work properly with SMARTDrive.
It is recommended that you use SMARTDrive, provided with
Windows 3.1, and remove all references to other disk-cache
utilities from your CONFIG.SYS and AUTOEXEC.BAT files. (If
CACHE.SYS is detected, Setup removes it from the CONFIG.SYS file
for you.)
CED Version 1.0e
----------------
Using CED with Windows 3.1 may cause problems, including
system failure. It is recommended that you do not use CED
with Windows 3.1.
Central Point Anti-Virus Version 1.1 (VSAFE.COM/VSAFE.SYS)
----------------------------------------------------------
VSAFE.COM/VSAFE.SYS should not be loaded when you set up
Windows 3.1. Otherwise, Setup may not run properly. After
you set up Windows 3.1, you can load VSAFE.
Because Windows uses the disk for memory swapping, you should
turn off the VSAFE write-protection option when running Windows.
For more information, see the Central Point Anti-Virus
documentation.
CMDEDIT.COM Version 2.0 (Date 12-6-91)
--------------------------------------
If this command-line editor is loaded before starting Windows,
it may cause a General Protection Fault when running multiple MS-
DOS Prompts in 386 enhanced mode. Also, it cannot be loaded
from an MS-DOS Prompt within Windows when Windows is
running in standard mode.
Cubit Version 3.01
------------------
When using Cubit with Windows 3.1, do not compress the
Windows SYSTEM directory or any file that is loaded from
the CONFIG.SYS file. Compressing these files could cause
problems.
Before upgrading to Windows 3.1, make sure that the earlier
version of Windows is uncompressed on your hard disk. You
may recompress the files after you have successfully set up
Windows 3.1.
Data Physician Plus Version 2.0 (VirALERT)
------------------------------------------
It is recommended that you do not set up Windows while
VirALERT is running. If you do, VirALERT will display a
warning message every few seconds while Setup is running.
After you have set up Windows, you can run VirALERT. Press
ALT+V to display the VirALERT menu. You can use the commands
on this menu to disable and enable VirALERT.
DOSCUE.COM Command-Line Editor
------------------------------
The DOSCUE command-line editor produces unexpected results
when used with Windows version 3.1. It is recommended that you
do not use this editor with Windows 3.1.
Doubledisk Version 2.5
----------------------
Windows 3.1 may try to access "phantom" disk drives if you use
Doubledisk with Windows 3.1. Phantom drives occur when you
use Doubledisk to create a compressed drive. For example, if you
have drives A, B, and C on your computer and you use Doubledisk
to create drive F, Windows 3.1 (and MS-DOS) recognize drives D
and E as valid drives, even though they do not actually exist. You
can use the DRVOFF utility to prevent Windows from recognizing
phantom drives. Contact Vertisoft to order a copy of the DRVOFF
utility.
FASTOPEN (MS-DOS)
-----------------
FASTOPEN is a RAM resident utility. Problems involving the
file allocation table (FAT) may occur if FASTOPEN is used
together with disk de-fragmenting utilities. In low-memory
situations, you may need to remove FASTOPEN for Windows
3.1 to run properly.
Flash Disk-Cache Utility (FLASH.EXE)
-------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
Graphics (MS-DOS)
-----------------
Loading Graphics from an MS-DOS Prompt within Windows can cause
unexpected results when printing. The active MS-DOS Prompt will
send its output to the printer. Switching between MS-DOS Prompts
may result in mixed printing jobs.
HPEMM386.SYS and HPEMM486.SYS
-----------------------------
These expanded-memory managers are incompatible with Windows
when it is running in 386 enhanced mode. If you plan on running
Windows in 386 enhanced mode, it is recommended that you use
EMM386.EXE to manage memory instead.
HPMM.SYS - HP Memory Manager
----------------------------
When HPMM.SYS is running, you cannot set up Windows 3.1 or
run it in standard mode. You should remove all references to
HPMM.SYS from your CONFIG.SYS and AUTOEXEC.BAT files before
setting up Windows 3.1.
Hyperdisk Disk-Cache Utility
----------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
IBM VDISK.SYS (RAM Disk Utility)
--------------------------------
VDISK.SYS is incompatible with Windows because it occupies
extended memory required to run Windows. This utility prevents
any XMS-compatible memory manager from loading.
IEMM.SYS Memory Manager
-----------------------
The IEMM.SYS memory manager is incompatible with Windows.
It is recommended that you remove all references to IEMM.SYS
from your CONFIG.SYS and AUTOEXEC.BAT files and use
EMM386.EXE, provided with Windows 3.1, to manage memory
instead.
ICACHE.SYS Disk-Cache Utility
-----------------------------
Do not use two disk-cache utilities with Windows version
3.1. It is recommended that you use SMARTDrive, provided with
Windows 3.1, and remove all references to other disk-cache
utilities from your CONFIG.SYS and AUTOEXEC.BAT files. (If
ICACHE.SYS is detected, Setup removes it from the CONFIG.SYS
file for you.)
IBMCACHE.SYS Disk-Cache Utility
-------------------------------
Do not use two disk-cache utilities with Windows version
3.1. It is recommended that you use SMARTDrive, provided with
Windows 3.1, and remove all references to other disk-cache
utilities from your CONFIG.SYS and AUTOEXEC.BAT files. (If
IBMCACHE.SYS is detected, Setup removes it from the CONFIG.SYS
file for you.)
Intel Expanded-Memory Emulator (ILIM386.SYS)
--------------------------------------------
The ILIM386.SYS expanded-memory emulator, provided with the
Intel Inboard/386 product, is incompatible with Windows 3.1.
It is recommended that you remove all references to this emulator
from your CONFIG.SYS and AUTOEXEC.BAT files before setting
up Windows 3.1.
JOIN (MS-DOS)
-------------
Do not add or remove "joined" drives while running Windows 3.1.
If you use the JOIN command before starting Windows 3.1 and
do not change the state of the joined drives from an MS-DOS
Prompt within Windows, Windows 3.1 will work properly.
It is recommended that you do not use joined drives at all if
you plan on running Windows.
KBFLOW TSR by Artisoft
----------------------
If you load the KBFLOW TSR utility provided by Artisoft
before starting Windows 3.1, your system may fail when
starting or using an MS-DOS Prompt from within Windows.
KEYB.COM (MS-DOS)
-----------------
If you use command-line options to load KEYB.COM, it is
recommended that you load it before starting Windows.
After it is loaded, you can change the keyboard configuration
from an MS-DOS Prompt within Windows any time. If you do not
load KEYB.COM before starting windows, you may encounter
problems using a KEYB command that includes an option in an
MS-DOS Prompt. However, you can use the KEYB command without
options at any time to display code-page information.
Lansight Version 2.0
--------------------
Lansight is a utility that you can use to control and monitor
other workstations attached to a Novell network. In some cases,
version 2.0 of Lansight may cause the workstation running
Windows 3.1 to fail.
Lasertool Control Panel Version 2.2
------------------------------------
If you load version 2.2 of the Lasertool Control Panel
program (PCPANEL.EXE) from Windows 3.1, your system may fail.
This program works properly if you load it before starting
Windows.
Le Menu Version 1.0
-------------------
When using Le Menu version 1.0 with Windows 3.1, environment
information such as PATH, PROMPT and WINDIR may be lost
if you start an MS-DOS Prompt from within Windows. If you
want to start Windows 3.1 by using a Le Menu menu command,
it is recommended that you set up Windows 3.1 as a Batch-File
menu command so that COMMAND.COM will load before starting
Windows 3.1. For more information, see your Le Menu documentation.
LOCKIT Version 3.3 (PC Vault, Secure It)
----------------------------------------
Version 3.3 of these programs strip out spaces from the load=
command line in the WIN.INI file. Later versions may correct
this problem.
Logitech Mouse Software Version 5.0/6.0 (CLICK, LOGIMENU)
----------------------------------------------------------
If you want to use CLICK and LOGIMENU from an MS-DOS
Prompt within Windows, you must load the TSRs from that
MS-DOS Prompt, even if you loaded the TSRs before starting
Windows. When you quit Windows, you must reload the TSRs
for them to work properly from the MS-DOS prompt outside of
Windows, even if you loaded them from an MS-DOS Prompt within
Windows.
Mace Disk-Cache Utility (MCACHE.SYS)
------------------------------------
This disk-cache utility will not work properly with SMARTDrive.
It is recommended that you use SMARTDrive, provided with Windows 3.1,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If Mace is detected, Setup
removes it from the CONFIG.SYS file for you.)
Maximizer Memory Manager (MAXIMIZE.COM)
---------------------------------------
If you are using the Maximizer memory manager, you may not be able
to set up or start Windows. Make sure that you are using only one
memory manager with Windows 3.1. It is recommended that you use
HIMEM.SYS and EMM386.EXE, which are installed with Windows 3.1,
to manage memory instead.
MIRROR (MS-DOS)
-----------------
If MIRROR is loaded from Windows 3.1 by using the Run command in
standard mode, you cannot remove it from memory by using the
MIRROR /U command. This will cause an error message to appear.
NDOSEDIT.COM (Date 1-1-84)
--------------------------
You may have problems loading this command-line editor. Also,
it may cause unexpected results when running with Windows 3.1.
NetRoom Memory Manager (RM386.SYS)
-------------------------------------------
With some older versions of NetRoom, you may encounter
problems setting up Windows. In this case, contact Helix
Software for a newer version of NetRoom.
Newspace Version 1.07
---------------------
This disk-compression utility is incompatible with Windows
3.1 and may cause several problems.
Norton Anti-Virus Version 1.0
-----------------------------
If you load version 1.0 of Anti-Virus before setting up Windows,
Setup may fail. It is recommended that you contact Symantec for
the most current version of this program.
Norton Desktop for Windows (EP.EXE)
-----------------------------------
If the data-recovery program Erase Protect (EP.EXE) is loaded
from the AUTOEXEC.BAT file, you need to disable it when setting
up Windows 3.1, especially if you are upgrading over a previous
version of Windows. Erase Protect tries to save copies of all
deleted files, which can cause you to run out of disk space
while running Setup.
It is recommended that you run Erase Protect with a permanent
swap file, not a temporary swap file. If you are using a
temporary swap file, you need to exclude files with a .TMP
or .SWP extension from erase protection.
Norton Utilities Version 5.0 (DISKREET, NCACHE)
-----------------------------------------------
This program is incompatible with Windows 3.1 and may cause
your system to fail. It is recommended that you upgrade to
the most recent version of Norton Utilities to correct problems.
Norton Utilities Version. 6.01 (NCACHE)
---------------------------------------
Some versions of NCACHE may prevent you from setting up or
starting Windows 3.1. When Windows is running in standard
mode, your system may fail, especially if NCACHE is set up
as an EMS cache. Setting up NCACHE as an EMS cache is not
recommended. Setting up NCACHE as an XMS cache may solve
the problem.
You may also encounter additional problems using NCACHE.
New versions may correct these problems. For an updated version
of NCACHE, contact Symantec Corporation. In the meantime, you
can use SMARTDrive, which is provided with Windows 3.1.
Norton Utilities Version 6.01 (DISKMON)
--------------------------------------
It is recommended that you do not use DISKMON version 6.01
with Windows 3.1.
PCED Version 2.00
-----------------
Do not load the PCED command-line editor HIGH. Loading it
HIGH may cause unexpected results, such as system failures,
when Windows is running in 386 enhanced mode. If you load
this program before starting Windows, it may be unavailable
when Windows is running in standard mode.
PCKEY.EXE (MultiSoft Keyboard Enhancer and Command-Line Stack)
--------------------------------------------------------------
PCKEY.EXE may not work properly with Windows 3.1 when you are
running more than one non-Windows application at a time. It
is recommended that you unload PCKEY.EXE before starting Windows.
PC-Kwik Disk Accelerator
------------------------
If you use PC-Kwik when Windows is running in 386 enhanced
mode, make sure that you are using version 3.55 or later and
that PC-Kwik is in extended memory, not expanded memory. To
get an upgraded version of PC-Kwik, contact MultiSoft.
PC-Kwik Disk-Cache Utility (PC-KWIK.EXE)
----------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, provided with Windows
3.1, instead.
PC-Kwik Version. 1.59 (PCK.EXE, PSKSCRN.EXE, PCKEY.COM)
-------------------------------------------------------
If version 1.59 of PC-KWIK is loaded before setting up Windows,
Setup may fail. PC-KWIK Version 2.0 may correct this problem.
PCSXMAEM.SYS Utility
--------------------
This utility is incompatible with Windows. You should remove
all references to it from your CONFIG.SYS and AUTOEXEC.BAT
files before setting up or starting Windows 3.1. PCSXMAEM.SYS
is similar to XMAEM.SYS. It has been renamed and slightly
modified. It is provided with current versions of the IBM PC/3270
emulator.
PCSX2EMS.SYS
-------------
Windows will run correctly with PCSX2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this
program is incompatible with Windows. PCSX2EMS.SYS is
provided with the IBM PC/3270 emulator.
PC Tools Deluxe Version 7.1 (DATAMON)
------------------------------------
If you load PC Tools DATAMON using the \SENTRY+ option,
Setup may fail if you are low on disk space. Do not use the
\SENTRY+ option when loading DATAMON.
Do not load DATAMON after loading SMARTDrive. If DATAMON
is loaded after SMARTDrive, your system may fail. See the
PC Tools documentation for information about how to unload
DATAMON.
PC Tools Deluxe Version 6.0 (DESKTOP)
------------------------------------
If you try to start PC Tools from an MS-DOS Prompt within
Windows in standard mode, your system may fail. In enhanced
mode, your system may restart itself. These problems also occur
if you use MS-DOS commands from an MS-DOS Prompt within
Windows.
Version 7.0 of PC Tools may correct these problems. However,
do not load DESKTOP from an MS-DOS Prompt if it was loaded
before starting Windows 3.1. If you do, your system may fail
when you quit Windows. It is recommended that you run DESKTOP
from its PIF, provided with Windows 3.1.
PC Tools Deluxe Version 7.1 (VDEFEND)
-------------------------------------
Setup may not work properly if VDEFEND is loaded before running
Setup. You may load VDEFEND after setting up Windows 3.1.
PC Tools Disk-Cache Utility (PC-CACHE.COM)
-----------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
PRINT (MS-DOS)
--------------
If you are printing several large documents on a network printer
and run Windows Setup from the network, your system may
fail while Setup is creating Program Manager groups.
Printer Assist Version 4.20
---------------------------
Printer Assist is a TSR that you can use to share a
workstation printer with other workstations on Netware 286
and 386 systems. Some Windows applications (such as Microsoft
Word for Windows) print extended characters, mixed with correct
output when this program is loaded.
PYRO! Version 1.0
-----------------
If this screen saver is loaded before starting Windows 3.1, you may
not be able to restore the Windows 3.1 screen after this screen saver
appears.
QMAPS Memory Manager Version 5.16
---------------------------------
If you are using the QMAPS memory manager, you may not be able
to set up or start Windows. New versions may correct these problems.
For an updated version of QMAPS, contact Quadtel. In the meantime, you
may use HIMEM.SYS and EMM386.EXE, provided with Windows 3.1, to manage
memory instead.
RAMTYPE.SYS - AST RAMpage! Boards
---------------------------------
The RAMTYPE.SYS driver is incompatible with Windows. It is
recommended that you remove this driver before setting up
Windows 3.1. If you load the driver from your CONFIG.SYS
file, comment out the command line for the driver as follows:
rem RAMTYPE.SYS
Windows 3.1 will run correctly without RAMTYPE.SYS. However,
other drivers that rely on RAMTYPE.SYS will not load and
applications will not be able to use the expanded memory on
your system.
After setting up Windows, you can use version 1.2 and later of
RAMTYPE.SYS with Windows. If you are using an earlier version
on an IBM PS/2 or micro-channel architecture computer and
your RAMpage! board is configured for expanded and extended
memory, you need to upgrade your AST RAMTYPE.SYS driver after
setting up Windows. You will also need to remove the "rem"
command from your CONFIG.SYS file so that RAMTYPE.SYS will
load properly.
Secretdisk II Disk-Cache Utility (FAST512.SYS)
----------------------------------------------
This disk-cache utility will not work properly with SMARTDrive.
It is recommended that you use SMARTDrive, provided with Windows
3.1, and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If this utility is detected,
Setup removes it from the CONFIG.SYS file for you).
SideKick Versions 1.0 and 2.0 and SideKick Plus
-----------------------------------------------
Miscellaneous problems may occur when running SideKick as a TSR
with Windows 3.1. It is recommended that you use a PIF to run
SideKick as a non-Windows application, instead of loading it
as a TSR.
SoftIce Debugger
----------------
If SoftIce is loaded, Setup will fail when starting the Windows
portion of the program. It is recommended that you unload SoftIce
before setting up Windows 3.1.
SpeedFXR
--------
This program is incompatible with Windows 3.1 when running as a
TSR. It tries to increase the speed of the floppy disk drives,
but slows them down instead. To get the best results, use the
-X option when loading SpeedFXR. This will prevent SpeedFXR from
remaining in memory and affecting the speed of the floppy disk
drives.
SUBST (MS-DOS)
--------------
Do not add or remove "substituted" drives while running Windows 3.1.
If you use the SUBST command before starting Windows and do not
change the state of the substituted drives from an MS-DOS Prompt within
Windows, Windows 3.1 will work properly.
Super PC-Kwik Disk-Cache Utility (SUPERPCK.EXE)
-----------------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
Trantor T100 Host Adapter Driver (TSCSI.SYS)
--------------------------------------------
(For SCSI hard disk drives) - If you use the Trantor T100
driver (TSCSI.SYS), you must use version 4.33d or higher.
Earlier versions identify the SCSI hard disk drive as a
removable drive. This may cause problems when using File
Manager, such as a system failure while formatting the drive
and unexpected results when deleting files. To get an updated
driver, contact Trantor Systems, Ltd.
UMB PRO Version 1.07
--------------------
If you are running UMB PRO, you may experience problems
running Windows in standard mode. In some cases, your system
may fail. Make sure that you are using only one memory manager
with Windows 3.1. It is recommended that you use HIMEM.SYS
and EMM386.EXE, which are installed with Windows 3.1, to
manage memory instead.
Vaccine
-------
If Vaccine is loaded, Setup fails when trying to modify the
CONFIG.SYS and AUTOEXEC.BAT files. You should unload Vaccine
before setting up Windows 3.1. You may also encounter problems,
such as beeping, while running Windows when Vaccine is loaded.
VIREX-PC Version 1.11
---------------------
If VIREXPC.COM is loaded, Windows Setup and Windows 3.1
will fail when KRNL386.EXE performs a write operation. Also,
the first time Windows 3.1 is loaded, you may be returned
to the MS-DOS prompt.
Virus Prevention Plus Version 5.0
---------------------------------
If Virus Prevention Plus is loaded, you may not be able to
successfully set up Windows 3.1. You may also encounter
problems when running Windows 3.1 in 386 enhanced mode.
The Keyboard Lock program may cause Windows to fail.
Virusafe Version 4.0
--------------------
If this program is loaded as a TSR, Setup may fail while setting
up Windows 3.1. It is recommended that you load Virusafe by using
the /C- option. This option turns off the memory-change detection
provided with Virusafe. Version 4.5 may correct this problem.
For more information, see your Virusafe documentation.
XGAAIDOS.SYS
------------
With XGAAIDOS.SYS loaded, Windows 3.1 will fail at the opening
logo if you use the WIN /s option to start Windows in standard mode.
XMAEM.SYS
---------
XMAEM.SYS is a device which causes extended memory to act like
XMA. This utility is incompatible with Windows 3.1. It is recommended
that you remove all references to it from your CONFIG.SYS and
AUTOEXEC.BAT files before setting up or running Windows 3.1.
XMAEM.SYS is provided with IBM DOS version 4.0.
XMA2EMS.SYS
-----------
Windows will run correctly with XMA2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this
program is incompatible with Windows. XMA2EMS.SYS is provided
with IBM DOS version 4.0.
SETUP.TXT
=========
This file contains information about problems that may occur
while running Windows Setup and describes problems that can
occur when using terminate-and-stay-resident (TSR) programs
or drivers with Windows or Windows Setup. If you are using
a TSR or if you encounter problems setting up Windows version
3.1, read this document BEFORE running Setup again.
General Setup Notes
====================
This section includes notes on specific system configurations
that may prevent Setup from installing Windows successfully.
A solution to each problem is provided.
If you are using a hardware or software product listed here,
follow the proposed recommendations before running Setup.
MS-DOS Screen Savers
---------------------
If you are using an MS-DOS screen saver, you should disable
it before running Setup. These screen savers can cause problems
when running Setup.
COMPAQ Computer with MS-DOS Version 5.0 and EGA or VGA
---------------------------------------------------------
If you are using the upgrade version of Microsoft MS-DOS
5.0, check your CONFIG.SYS file to make sure the following
drivers appear in this order:
HIMEM.SYS
EMM386.EXE
ANSI.SYS
Note: If you are using the COMPAQ version of MS-DOS 5.0,
HIMEM.EXE is used in place of HIMEM.SYS and CEMM.EXE
is used in place of EMM386.EXE.
If ANSI.SYS is loaded before HIMEM.SYS or EMM386.EXE (or if
you are using COMPAQ MS-DOS 5.0 before HIMEM.EXE or CEMM.EXE),
Setup may restart your system before Windows is installed.
Also, if you are using the DOS=HIGH,UMB command line to load
MS-DOS into upper memory, loading EMM386.EXE (or CEMM.EXE)
before loading ANSI.SYS will create the maximum amount of
upper memory space on a COMPAQ computer.
AT&T Safari Computer
--------------------
If you have an AT&T Safari computer, you cannot maintain two
versions of Windows (version 3.0 and version 3.1) on your
system. You must upgrade over version 3.0. If you set up
Windows 3.1 in its own directory, Windows will not use the
special drivers required for it to run on the Safari computer.
Using the TIGA Display Driver
-------------------------------
If you are using the TIGA display driver, you must load the
TIGACD.EXE MS-DOS driver manually before running Setup
to upgrade Windows. Otherwise, Windows will not upgrade
your system properly.
After successfully setting up Windows, you can increase the
amount of conventional memory available to non-Windows
applications when Windows is running in 386 enhanced mode
by loading TIGACD.EXE from the WINSTART.BAT file. The
WINSTART.BAT file runs only in 386 enhanced mode. If you
want to run Windows in standard mode, you must load
TIGACD.EXE manually. For more information, see the README.WRI
online document.
Displays That Are Incompatible with Windows Version 3.1
-------------------------------------------------------
Certain display adapters can cause problems with Windows
version 3.1. The most serious problem is a system
failure while running Windows Setup. If you encounter this
problem, run Custom Setup, and then select one of the standard
display types, such as VGA, provided with Windows version 3.1.
With other display drivers, Windows may be set up successfully
but TrueType fonts may not appear correctly on your screen.
An updated driver may be available in the Windows Driver
Library or from your display vendor or manufacturer. For
information about obtaining the Windows Driver Library,
see "Getting Started with Microsoft Windows."
The following display adapters may cause problems:
- ATI Graphics Ultra and Vantage
NOTE: These adapters are 8514/a-compatible and run well
with the 8514/a driver provided with Windows 3.1.
- All DGIS display adapters (Direct Graphics Interface Standard)
from Graphic Software Systems, including the following:
NEC MultiSynch Graphics Engine (MGE)
Zenith Z-649
HP IGC-10, IGC-20
GSS 1000 Series
NOTE: Some DGIS-based adapters are TIGA-compatible and
run well when used with the appropriate TIGACD.EXE
MS-DOS driver and with the TIGA driver provided with
Windows 3.1.
- HP Ultra VGA
- IBM Image Adapter/A
- Matrox MG Series/M-WIN Series
- Palettized VGA 640x480, 16-color (provided with Windows
Multimedia Extensions version 1.0)
- Radius SVGA MultiView
- All RGDI (Renaissance Graphics Device Interface) display
adapters from Appian, Inc., including the following:
Appian Rendition II, IIe, II/XE, and III
Appian GV1024
Decpc 433
- All S3 adapters, including the following:
Orchid Fahrenheit 1280
STB WIND/X
Diamond Stealth VRAM
Using Stacker
-------------
If you are using Stacker to compress your hard disk, there are
certain steps you need to take before setting up Windows.
* If you want to use a swap file with Windows, you must
set up the swap file on the uncompressed drive. When
setting up Stacker, you can leave at least 1 megabyte (MB)
of disk space uncompressed for storing system files. To
leave enough space for the swap file, it is recommended
that the amount of uncompressed disk space equal at least
twice the amount of system memory. For example, if your
system has 4 MB of memory, you should leave at least 8 MB
of disk space uncompressed.
If Stacker is already set up on your system and there is not
enough uncompressed disk space for a swap file, you can run
the STAC utility provided with Stacker to increase the amount
of uncompressed disk space. For more information, see your
Stacker documentation.
* If you are using Stacker version 2.0 or later, Windows Setup
modifies your CONFIG.SYS and AUTOEXEC.BAT files. When Setup
is finished making the modifications, it displays a message
at the end of the Windows portion of Setup notifying you of
the modifications. If you have used Stacker to swap your
startup drive, when you restart your system Stacker will
ask whether you want to update to the new version of the
CONFIG.SYS or AUTOEXEC.BAT file. It is recommended that you
update.
If you are using a version of Stacker earlier than 2.0, you
may need to modify your CONFIG.SYS and AUTOEXEC.BAT files
yourself. For more information, see "Modifying Your CONFIG.SYS
and AUTOEXEC.BAT Files Yourself," following this topic.
* For best performance, do not use SMARTDrive to cache the
compressed drive. You only need to cache the uncompressed
drive. You can include options on the SMARTDRV.EXE line of
the CONFIG.SYS file to specify which drives to cache.
For example, if the Stacker swap utility swaps drives C and
D so that C is compressed and D is uncompressed, you would
include the following line in your CONFIG.SYS file:
device=\windows\smartdrv.exe C- D+
For more information about swap files and using SMARTDrive, see
Chapter 14, "Optimizing Windows," in the "Microsoft Windows User's
Guide."
Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself
---------------------------------------------------------
When you set up Windows, Setup usually places the HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE files in the Windows directory.
If the Windows directory is on a disk that is not available
when you start your computer, such as a removable or nonlocal
disk, or if Setup detects one of the following conditions,
Setup does not modify the CONFIG.SYS or AUTOEXEC.BAT file:
- Your boot drive has been modified by a disk-compression
utility.
- Your CONFIG.SYS file contains references to block device
drivers.
- There is not enough available space on your hard disk to
copy the files.
- The files are already installed on your system and Setup
cannot overwrite them (they are read-only).
Instead, Setup writes proposed changes to the CONFIG.WIN and
AUTOEXEC.WIN or the CONFIG.00x and AUTOEXEC.00x files.
In this case, you must either move the HIMEM.SYS, SMARTDRV.EXE,
and EMM386.EXE files to a drive that is available when you start
your computer, or use a text editor to modify your CONFIG.SYS or
AUTOEXEC.BAT file so that any references to HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE appear after the device=
command line used to load the drivers for your disk drives. Refer
to the CONFIG.WIN and AUTOEXEC.WIN or the CONFIG.00x and
AUTOEXEC.00x files for the proposed changes.
Setting Up XGA on a PS/2 Model 75 or 90
-----------------------------------------------------
If you have a PS/2 model 75 or 90 with an XGA, Windows
Setup will configure the display adapter for 16-color,
640x480 resolution. Do not change this configuration
during Setup. Specifying a different XGA configuration
while setting up Windows may cause Setup to fail.
After you have successfully installed Windows, you can
configure your XGA to use a different resolution or 256 colors,
if your monitor supports it. For more information on how to do
this, see the topic "IBM XGA" in the README.WRI online
document.
If you are using the plasma screen on the PS/2 model 75, use
ONLY the 640x480, 16-color configuration. If you change this
configuration, you will be returned to the MS-DOS prompt when
you try to start Windows.
Correcting the "Out of Environment Space" Error Message
-------------------------------------------------------
If you receive an "out of environment space" message when
starting Windows, you can either:
* Increase the size of your environment by adding the SHELL=
command line to your CONFIG.SYS file. See your MS-DOS
documentation for more information about the SHELL command
and modifying your CONFIG.SYS file.
* Move the SET commands in your AUTOEXEC.BAT file
to the beginning of the file so that they run before the
commands that load terminate-and-stay-resident (TSR)
programs or drivers, such as SMARTDrive.
If Windows Setup Does Not Detect Your Network
---------------------------------------------
If you have a network installed and Setup specifies "No
Network" in the System-Information screen, Setup is not
able to detect your network. For Setup to detect certain
networks, the directory that contains the network program
files must be included in your path.
This is a known problem with these networks: 3Share, 3Open,
LAN Manager, and MSNet. If your path does not include the
directory where the network files are located, you can either:
* Add the directory to the PATH line in your AUTOEXEC.BAT
file.
* Run Custom Setup and specify the full path for your
network in the System-Information screen.
Using Terminate-and-Stay-Resident (TSR) Programs and Drivers
with Windows Version 3.1
=============================================================
The Program Listing section of this document lists several
terminate-and-stay-resident (TSR) programs and drivers that
are known to cause problems when running with Windows version
3.1. Some of the problems you may encounter include system
failures or an incorrect display of information on your screen.
In some cases, special steps are provided to solve the problems.
While setting up Windows version 3.1, Windows Setup searches
the AUTOEXEC.BAT and CONFIG.SYS files for references to TSR
programs and drivers, in addition to scanning memory for TSRs
that are currently running. If Setup detects a TSR that is
known to cause problems when running with Windows version 3.1,
a message appears, asking whether you want to continue or quit
Setup.
If you receive such a message, do the following:
1. Locate your TSR in the Program Listing section of this document
and use the information to determine if the situation encountered
prevents Windows Setup from successfully installing Windows 3.1.
2. If the situation does not affect Windows Setup, you can continue
setting up Windows 3.1 by following the instructions on your
screen.
If the situation does affect Windows Setup and prevents it from
installing Windows on your computer, follow the instructions
on the screen to quit Setup, and then complete the following
steps.
3. Quit the TSR and remove all references to it from your
AUTOEXEC.BAT and CONFIG.SYS files. For more information,
see the documentation for your TSR.
4. Restart your computer.
5. Run Windows Setup again.
After Windows is successfully set up, you may want to restore
your TSRs.
Not all TSRs or drivers included in the Program Listing section
are detected by Setup. The TSRs and drivers that Setup detects
are in the SETUP.INF file, listed under the names "incomptsr1"
and "incomptsr2".
Program Listing
===============
This section describes some problems, discovered during testing,
that you might encounter while using a TSR with Windows version 3.1.
It does not include all possible problems that can occur.
386MAX
------
The documentation for 386MAX recommends against setting the
EXT parameter below 64. If you set this parameter to 0, Windows
Setup and Windows running in standard mode will fail.
See the README.WRI online document for more information
about running 386MAX with Windows 3.1.
386MAX Disk-Cache Utility (QCACHE.EXE)
--------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed
with Windows 3.1, instead.
All Charge 386 Version 3.1
--------------------------
ALLEMM4.SYS is a memory manager that causes problems with
Setup and Windows 3.1. If you encounter problems running
this program with Windows, it is recommended that you use
EMM386.EXE and HIMEM.SYS, provided with Windows 3.1, to
manage memory instead.
Anarkey Version 4.00
--------------------
With some memory configurations, Anarkey version 4.00 running
with Windows 3.1 in 386 enhanced mode may cause unpredictable
system failures. In rare cases, this program can also corrupt
hard-disk data. In addition, Windows 3.1 might not start when
this program is running.
Do not run Windows 3.1 in 386 enhanced mode when Anarkey version
4.00 is running. Version 4.01 may correct these problems. Contact
Moderne Software for a free upgrade of Anarkey 4.01.
Anarkey Version 4.01
--------------------
If Anarkey version 4.01 is loaded before starting Windows in
standard mode, it is not available in any MS-DOS Prompt that
you start from Windows. In this case, it is recommended that
you load Anarkey from each MS-DOS Prompt, as needed.
Do not load Anarkey HIGH before starting Windows in 386
enhanced mode. If you load Anarkey HIGH, your system may
fail when you try to start an application.
APPEND (MS-DOS)
---------------
Do not use the APPEND utility with Windows 3.1. It prevents
Windows and Windows applications from creating valid
Well-Formed-Path (WFP) names for the files they are using.
(A WFP is the complete name of a file, including the drive
letter and full path specification, starting from the root
directory.)
ASP Integrity Toolkit Version 3.7
---------------------------------
This product is a virus-protection program that can cause
problems when running Windows Setup, including system
failure, automatic restarting of the system, and the inability
to use the keyboard. You should turn off protection in the
toolkit before setting up Windows 3.1. For information about
how to do this, see your ASP Integrity documentation.
NOTE: Setting up Windows is considered a system-administration
task. The ASP Integrity Toolkit documentation instructs
you to turn off protection when performing these types
of tasks.
Autocon Version 2.0e
--------------------
Autocon enables you to select up to fifty different configurations
when starting your system. To do this, it modifies the CONFIG.SYS
and AUTOEXEC.BAT files, based on information in its database
(AUTOCON.DAT), when you restart your system from within
AUTOCON.
Windows Setup modifies only the first section in the CONFIG.SYS
and AUTOEXEC.BAT files. If you want to use specific configurations
with Windows, you must run Autocon and then manually edit the
configurations in the database that you want to use. You must do
this after setting up Windows. For your changes to take effect,
you must restart your system from within Autocon. For more
information, see your Autocon documentation.
Bootcon Version 1.60
--------------------
Using Bootcon, you can maintain different system-configuration
information in your CONFIG.SYS and AUTOEXEC.BAT files. You can
then select the configuration you want to use from a menu when
starting your system.
Windows Setup modifies only the first section in the CONFIG.SYS
and AUTOEXEC.BAT files. You must edit the sections of those files
that contain the configurations you want to use after you set up
Windows. For more information, see your Bootcon documentation.
BOOT.SYS
---------
Using BOOT.SYS, you can maintain different system-configuration
information in your CONFIG.SYS and AUTOEXEC.BAT files. You can
then select the configuration you want to use from a menu when
starting your system.
Windows Setup modifies only the first section in the CONFIG.SYS
and AUTOEXEC.BAT files. You must edit the sections of those files
that contain the configurations you want to use after you set
up Windows. For more information, see your BOOT.SYS documentation.
CACHE.EXE Disk-Cache Utility
----------------------------
Do not use two disk-cache utilities with Windows 3.1. It is
recommended that you use SMARTDrive, provided with Windows 3.1,
and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If CACHE.EXE is detected,
Setup removes it from the CONFIG.SYS file for you.)
CACHE.SYS Disk-Cache Utility
----------------------------
This disk-cache utility will not work properly with SMARTDrive.
It is recommended that you use SMARTDrive, provided with
Windows 3.1, and remove all references to other disk-cache
utilities from your CONFIG.SYS and AUTOEXEC.BAT files. (If
CACHE.SYS is detected, Setup removes it from the CONFIG.SYS file
for you.)
CED Version 1.0e
----------------
Using CED with Windows 3.1 may cause problems, including
system failure. It is recommended that you do not use CED
with Windows 3.1.
Central Point Anti-Virus Version 1.1 (VSAFE.COM/VSAFE.SYS)
----------------------------------------------------------
VSAFE.COM/VSAFE.SYS should not be loaded when you set up
Windows 3.1. Otherwise, Setup may not run properly. After
you set up Windows 3.1, you can load VSAFE.
Because Windows uses the disk for memory swapping, you should
turn off the VSAFE write-protection option when running Windows.
For more information, see the Central Point Anti-Virus
documentation.
CMDEDIT.COM Version 2.0 (Date 12-6-91)
--------------------------------------
If this command-line editor is loaded before starting Windows,
it may cause a General Protection Fault when running multiple MS-
DOS Prompts in 386 enhanced mode. Also, it cannot be loaded
from an MS-DOS Prompt within Windows when Windows is
running in standard mode.
Cubit Version 3.01
------------------
When using Cubit with Windows 3.1, do not compress the
Windows SYSTEM directory or any file that is loaded from
the CONFIG.SYS file. Compressing these files could cause
problems.
Before upgrading to Windows 3.1, make sure that the earlier
version of Windows is uncompressed on your hard disk. You
may recompress the files after you have successfully set up
Windows 3.1.
Data Physician Plus Version 2.0 (VirALERT)
------------------------------------------
It is recommended that you do not set up Windows while
VirALERT is running. If you do, VirALERT will display a
warning message every few seconds while Setup is running.
After you have set up Windows, you can run VirALERT. Press
ALT+V to display the VirALERT menu. You can use the commands
on this menu to disable and enable VirALERT.
DOSCUE.COM Command-Line Editor
------------------------------
The DOSCUE command-line editor produces unexpected results
when used with Windows version 3.1. It is recommended that you
do not use this editor with Windows 3.1.
Doubledisk Version 2.5
----------------------
Windows 3.1 may try to access "phantom" disk drives if you use
Doubledisk with Windows 3.1. Phantom drives occur when you
use Doubledisk to create a compressed drive. For example, if you
have drives A, B, and C on your computer and you use Doubledisk
to create drive F, Windows 3.1 (and MS-DOS) recognize drives D
and E as valid drives, even though they do not actually exist. You
can use the DRVOFF utility to prevent Windows from recognizing
phantom drives. Contact Vertisoft to order a copy of the DRVOFF
utility.
FASTOPEN (MS-DOS)
-----------------
FASTOPEN is a RAM resident utility. Problems involving the
file allocation table (FAT) may occur if FASTOPEN is used
together with disk de-fragmenting utilities. In low-memory
situations, you may need to remove FASTOPEN for Windows
3.1 to run properly.
Flash Disk-Cache Utility (FLASH.EXE)
-------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
Graphics (MS-DOS)
-----------------
Loading Graphics from an MS-DOS Prompt within Windows can cause
unexpected results when printing. The active MS-DOS Prompt will
send its output to the printer. Switching between MS-DOS Prompts
may result in mixed printing jobs.
HPEMM386.SYS and HPEMM486.SYS
-----------------------------
These expanded-memory managers are incompatible with Windows
when it is running in 386 enhanced mode. If you plan on running
Windows in 386 enhanced mode, it is recommended that you use
EMM386.EXE to manage memory instead.
HPMM.SYS - HP Memory Manager
----------------------------
When HPMM.SYS is running, you cannot set up Windows 3.1 or
run it in standard mode. You should remove all references to
HPMM.SYS from your CONFIG.SYS and AUTOEXEC.BAT files before
setting up Windows 3.1.
Hyperdisk Disk-Cache Utility
----------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
IBM VDISK.SYS (RAM Disk Utility)
--------------------------------
VDISK.SYS is incompatible with Windows because it occupies
extended memory required to run Windows. This utility prevents
any XMS-compatible memory manager from loading.
IEMM.SYS Memory Manager
-----------------------
The IEMM.SYS memory manager is incompatible with Windows.
It is recommended that you remove all references to IEMM.SYS
from your CONFIG.SYS and AUTOEXEC.BAT files and use
EMM386.EXE, provided with Windows 3.1, to manage memory
instead.
ICACHE.SYS Disk-Cache Utility
-----------------------------
Do not use two disk-cache utilities with Windows version
3.1. It is recommended that you use SMARTDrive, provided with
Windows 3.1, and remove all references to other disk-cache
utilities from your CONFIG.SYS and AUTOEXEC.BAT files. (If
ICACHE.SYS is detected, Setup removes it from the CONFIG.SYS
file for you.)
IBMCACHE.SYS Disk-Cache Utility
-------------------------------
Do not use two disk-cache utilities with Windows version
3.1. It is recommended that you use SMARTDrive, provided with
Windows 3.1, and remove all references to other disk-cache
utilities from your CONFIG.SYS and AUTOEXEC.BAT files. (If
IBMCACHE.SYS is detected, Setup removes it from the CONFIG.SYS
file for you.)
Intel Expanded-Memory Emulator (ILIM386.SYS)
--------------------------------------------
The ILIM386.SYS expanded-memory emulator, provided with the
Intel Inboard/386 product, is incompatible with Windows 3.1.
It is recommended that you remove all references to this emulator
from your CONFIG.SYS and AUTOEXEC.BAT files before setting
up Windows 3.1.
JOIN (MS-DOS)
-------------
Do not add or remove "joined" drives while running Windows 3.1.
If you use the JOIN command before starting Windows 3.1 and
do not change the state of the joined drives from an MS-DOS
Prompt within Windows, Windows 3.1 will work properly.
It is recommended that you do not use joined drives at all if
you plan on running Windows.
KBFLOW TSR by Artisoft
----------------------
If you load the KBFLOW TSR utility provided by Artisoft
before starting Windows 3.1, your system may fail when
starting or using an MS-DOS Prompt from within Windows.
KEYB.COM (MS-DOS)
-----------------
If you use command-line options to load KEYB.COM, it is
recommended that you load it before starting Windows.
After it is loaded, you can change the keyboard configuration
from an MS-DOS Prompt within Windows any time. If you do not
load KEYB.COM before starting windows, you may encounter
problems using a KEYB command that includes an option in an
MS-DOS Prompt. However, you can use the KEYB command without
options at any time to display code-page information.
Lansight Version 2.0
--------------------
Lansight is a utility that you can use to control and monitor
other workstations attached to a Novell network. In some cases,
version 2.0 of Lansight may cause the workstation running
Windows 3.1 to fail.
Lasertool Control Panel Version 2.2
------------------------------------
If you load version 2.2 of the Lasertool Control Panel
program (PCPANEL.EXE) from Windows 3.1, your system may fail.
This program works properly if you load it before starting
Windows.
Le Menu Version 1.0
-------------------
When using Le Menu version 1.0 with Windows 3.1, environment
information such as PATH, PROMPT and WINDIR may be lost
if you start an MS-DOS Prompt from within Windows. If you
want to start Windows 3.1 by using a Le Menu menu command,
it is recommended that you set up Windows 3.1 as a Batch-File
menu command so that COMMAND.COM will load before starting
Windows 3.1. For more information, see your Le Menu documentation.
LOCKIT Version 3.3 (PC Vault, Secure It)
----------------------------------------
Version 3.3 of these programs strip out spaces from the load=
command line in the WIN.INI file. Later versions may correct
this problem.
Logitech Mouse Software Version 5.0/6.0 (CLICK, LOGIMENU)
----------------------------------------------------------
If you want to use CLICK and LOGIMENU from an MS-DOS
Prompt within Windows, you must load the TSRs from that
MS-DOS Prompt, even if you loaded the TSRs before starting
Windows. When you quit Windows, you must reload the TSRs
for them to work properly from the MS-DOS prompt outside of
Windows, even if you loaded them from an MS-DOS Prompt within
Windows.
Mace Disk-Cache Utility (MCACHE.SYS)
------------------------------------
This disk-cache utility will not work properly with SMARTDrive.
It is recommended that you use SMARTDrive, provided with Windows 3.1,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If Mace is detected, Setup
removes it from the CONFIG.SYS file for you.)
Maximizer Memory Manager (MAXIMIZE.COM)
---------------------------------------
If you are using the Maximizer memory manager, you may not be able
to set up or start Windows. Make sure that you are using only one
memory manager with Windows 3.1. It is recommended that you use
HIMEM.SYS and EMM386.EXE, which are installed with Windows 3.1,
to manage memory instead.
MIRROR (MS-DOS)
-----------------
If MIRROR is loaded from Windows 3.1 by using the Run command in
standard mode, you cannot remove it from memory by using the
MIRROR /U command. This will cause an error message to appear.
NDOSEDIT.COM (Date 1-1-84)
--------------------------
You may have problems loading this command-line editor. Also,
it may cause unexpected results when running with Windows 3.1.
NetRoom Memory Manager (RM386.SYS)
-------------------------------------------
With some older versions of NetRoom, you may encounter
problems setting up Windows. In this case, contact Helix
Software for a newer version of NetRoom.
Newspace Version 1.07
---------------------
This disk-compression utility is incompatible with Windows
3.1 and may cause several problems.
Norton Anti-Virus Version 1.0
-----------------------------
If you load version 1.0 of Anti-Virus before setting up Windows,
Setup may fail. It is recommended that you contact Symantec for
the most current version of this program.
Norton Desktop for Windows (EP.EXE)
-----------------------------------
If the data-recovery program Erase Protect (EP.EXE) is loaded
from the AUTOEXEC.BAT file, you need to disable it when setting
up Windows 3.1, especially if you are upgrading over a previous
version of Windows. Erase Protect tries to save copies of all
deleted files, which can cause you to run out of disk space
while running Setup.
It is recommended that you run Erase Protect with a permanent
swap file, not a temporary swap file. If you are using a
temporary swap file, you need to exclude files with a .TMP
or .SWP extension from erase protection.
Norton Utilities Version 5.0 (DISKREET, NCACHE)
-----------------------------------------------
This program is incompatible with Windows 3.1 and may cause
your system to fail. It is recommended that you upgrade to
the most recent version of Norton Utilities to correct problems.
Norton Utilities Version. 6.01 (NCACHE)
---------------------------------------
Some versions of NCACHE may prevent you from setting up or
starting Windows 3.1. When Windows is running in standard
mode, your system may fail, especially if NCACHE is set up
as an EMS cache. Setting up NCACHE as an EMS cache is not
recommended. Setting up NCACHE as an XMS cache may solve
the problem.
You may also encounter additional problems using NCACHE.
New versions may correct these problems. For an updated version
of NCACHE, contact Symantec Corporation. In the meantime, you
can use SMARTDrive, which is provided with Windows 3.1.
Norton Utilities Version 6.01 (DISKMON)
--------------------------------------
It is recommended that you do not use DISKMON version 6.01
with Windows 3.1.
PCED Version 2.00
-----------------
Do not load the PCED command-line editor HIGH. Loading it
HIGH may cause unexpected results, such as system failures,
when Windows is running in 386 enhanced mode. If you load
this program before starting Windows, it may be unavailable
when Windows is running in standard mode.
PCKEY.EXE (MultiSoft Keyboard Enhancer and Command-Line Stack)
--------------------------------------------------------------
PCKEY.EXE may not work properly with Windows 3.1 when you are
running more than one non-Windows application at a time. It
is recommended that you unload PCKEY.EXE before starting Windows.
PC-Kwik Disk Accelerator
------------------------
If you use PC-Kwik when Windows is running in 386 enhanced
mode, make sure that you are using version 3.55 or later and
that PC-Kwik is in extended memory, not expanded memory. To
get an upgraded version of PC-Kwik, contact MultiSoft.
PC-Kwik Disk-Cache Utility (PC-KWIK.EXE)
----------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, provided with Windows
3.1, instead.
PC-Kwik Version. 1.59 (PCK.EXE, PSKSCRN.EXE, PCKEY.COM)
-------------------------------------------------------
If version 1.59 of PC-KWIK is loaded before setting up Windows,
Setup may fail. PC-KWIK Version 2.0 may correct this problem.
PCSXMAEM.SYS Utility
--------------------
This utility is incompatible with Windows. You should remove
all references to it from your CONFIG.SYS and AUTOEXEC.BAT
files before setting up or starting Windows 3.1. PCSXMAEM.SYS
is similar to XMAEM.SYS. It has been renamed and slightly
modified. It is provided with current versions of the IBM PC/3270
emulator.
PCSX2EMS.SYS
-------------
Windows will run correctly with PCSX2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this
program is incompatible with Windows. PCSX2EMS.SYS is
provided with the IBM PC/3270 emulator.
PC Tools Deluxe Version 7.1 (DATAMON)
------------------------------------
If you load PC Tools DATAMON using the \SENTRY+ option,
Setup may fail if you are low on disk space. Do not use the
\SENTRY+ option when loading DATAMON.
Do not load DATAMON after loading SMARTDrive. If DATAMON
is loaded after SMARTDrive, your system may fail. See the
PC Tools documentation for information about how to unload
DATAMON.
PC Tools Deluxe Version 6.0 (DESKTOP)
------------------------------------
If you try to start PC Tools from an MS-DOS Prompt within
Windows in standard mode, your system may fail. In enhanced
mode, your system may restart itself. These problems also occur
if you use MS-DOS commands from an MS-DOS Prompt within
Windows.
Version 7.0 of PC Tools may correct these problems. However,
do not load DESKTOP from an MS-DOS Prompt if it was loaded
before starting Windows 3.1. If you do, your system may fail
when you quit Windows. It is recommended that you run DESKTOP
from its PIF, provided with Windows 3.1.
PC Tools Deluxe Version 7.1 (VDEFEND)
-------------------------------------
Setup may not work properly if VDEFEND is loaded before running
Setup. You may load VDEFEND after setting up Windows 3.1.
PC Tools Disk-Cache Utility (PC-CACHE.COM)
-----------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
PRINT (MS-DOS)
--------------
If you are printing several large documents on a network printer
and run Windows Setup from the network, your system may
fail while Setup is creating Program Manager groups.
Printer Assist Version 4.20
---------------------------
Printer Assist is a TSR that you can use to share a
workstation printer with other workstations on Netware 286
and 386 systems. Some Windows applications (such as Microsoft
Word for Windows) print extended characters, mixed with correct
output when this program is loaded.
PYRO! Version 1.0
-----------------
If this screen saver is loaded before starting Windows 3.1, you may
not be able to restore the Windows 3.1 screen after this screen saver
appears.
QMAPS Memory Manager Version 5.16
---------------------------------
If you are using the QMAPS memory manager, you may not be able
to set up or start Windows. New versions may correct these problems.
For an updated version of QMAPS, contact Quadtel. In the meantime, you
may use HIMEM.SYS and EMM386.EXE, provided with Windows 3.1, to manage
memory instead.
RAMTYPE.SYS - AST RAMpage! Boards
---------------------------------
The RAMTYPE.SYS driver is incompatible with Windows. It is
recommended that you remove this driver before setting up
Windows 3.1. If you load the driver from your CONFIG.SYS
file, comment out the command line for the driver as follows:
rem RAMTYPE.SYS
Windows 3.1 will run correctly without RAMTYPE.SYS. However,
other drivers that rely on RAMTYPE.SYS will not load and
applications will not be able to use the expanded memory on
your system.
After setting up Windows, you can use version 1.2 and later of
RAMTYPE.SYS with Windows. If you are using an earlier version
on an IBM PS/2 or micro-channel architecture computer and
your RAMpage! board is configured for expanded and extended
memory, you need to upgrade your AST RAMTYPE.SYS driver after
setting up Windows. You will also need to remove the "rem"
command from your CONFIG.SYS file so that RAMTYPE.SYS will
load properly.
Secretdisk II Disk-Cache Utility (FAST512.SYS)
----------------------------------------------
This disk-cache utility will not work properly with SMARTDrive.
It is recommended that you use SMARTDrive, provided with Windows
3.1, and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If this utility is detected,
Setup removes it from the CONFIG.SYS file for you).
SideKick Versions 1.0 and 2.0 and SideKick Plus
-----------------------------------------------
Miscellaneous problems may occur when running SideKick as a TSR
with Windows 3.1. It is recommended that you use a PIF to run
SideKick as a non-Windows application, instead of loading it
as a TSR.
SoftIce Debugger
----------------
If SoftIce is loaded, Setup will fail when starting the Windows
portion of the program. It is recommended that you unload SoftIce
before setting up Windows 3.1.
SpeedFXR
--------
This program is incompatible with Windows 3.1 when running as a
TSR. It tries to increase the speed of the floppy disk drives,
but slows them down instead. To get the best results, use the
-X option when loading SpeedFXR. This will prevent SpeedFXR from
remaining in memory and affecting the speed of the floppy disk
drives.
SUBST (MS-DOS)
--------------
Do not add or remove "substituted" drives while running Windows 3.1.
If you use the SUBST command before starting Windows and do not
change the state of the substituted drives from an MS-DOS Prompt within
Windows, Windows 3.1 will work properly.
Super PC-Kwik Disk-Cache Utility (SUPERPCK.EXE)
-----------------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive.
There is no reason to use two disk-cache utilities with Windows.
It is recommended that you use SMARTDrive, which is installed with
Windows 3.1, instead.
Trantor T100 Host Adapter Driver (TSCSI.SYS)
--------------------------------------------
(For SCSI hard disk drives) - If you use the Trantor T100
driver (TSCSI.SYS), you must use version 4.33d or higher.
Earlier versions identify the SCSI hard disk drive as a
removable drive. This may cause problems when using File
Manager, such as a system failure while formatting the drive
and unexpected results when deleting files. To get an updated
driver, contact Trantor Systems, Ltd.
UMB PRO Version 1.07
--------------------
If you are running UMB PRO, you may experience problems
running Windows in standard mode. In some cases, your system
may fail. Make sure that you are using only one memory manager
with Windows 3.1. It is recommended that you use HIMEM.SYS
and EMM386.EXE, which are installed with Windows 3.1, to
manage memory instead.
Vaccine
-------
If Vaccine is loaded, Setup fails when trying to modify the
CONFIG.SYS and AUTOEXEC.BAT files. You should unload Vaccine
before setting up Windows 3.1. You may also encounter problems,
such as beeping, while running Windows when Vaccine is loaded.
VIREX-PC Version 1.11
---------------------
If VIREXPC.COM is loaded, Windows Setup and Windows 3.1
will fail when KRNL386.EXE performs a write operation. Also,
the first time Windows 3.1 is loaded, you may be returned
to the MS-DOS prompt.
Virus Prevention Plus Version 5.0
---------------------------------
If Virus Prevention Plus is loaded, you may not be able to
successfully set up Windows 3.1. You may also encounter
problems when running Windows 3.1 in 386 enhanced mode.
The Keyboard Lock program may cause Windows to fail.
Virusafe Version 4.0
--------------------
If this program is loaded as a TSR, Setup may fail while setting
up Windows 3.1. It is recommended that you load Virusafe by using
the /C- option. This option turns off the memory-change detection
provided with Virusafe. Version 4.5 may correct this problem.
For more information, see your Virusafe documentation.
XGAAIDOS.SYS
------------
With XGAAIDOS.SYS loaded, Windows 3.1 will fail at the opening
logo if you use the WIN /s option to start Windows in standard mode.
XMAEM.SYS
---------
XMAEM.SYS is a device which causes extended memory to act like
XMA. This utility is incompatible with Windows 3.1. It is recommended
that you remove all references to it from your CONFIG.SYS and
AUTOEXEC.BAT files before setting up or running Windows 3.1.
XMAEM.SYS is provided with IBM DOS version 4.0.
XMA2EMS.SYS
-----------
Windows will run correctly with XMA2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this
program is incompatible with Windows. XMA2EMS.SYS is provided
with IBM DOS version 4.0.
Autodesk P386 ADI 4.1
DEV_RC Combined display and rendering display driver
(Rel 4.0 10/91)
Contents
--------
README.TXT -- This file
RCPTVGA.EXP -- P386 ADI 4.1 DEV_RC driver w/ HiColor support
Features
--------
* Support Trident TVGA8800 and TVGA8900 series.
* Support 16-color and 256-color up to 1024x768.
* Support 32K-color rendering display (Sierra HiColor DAC).
* Support 64K-color rendering display (Sierra 485/7/9 DAC).
* Combined display and rendering display driver.
* Support all Autodesk products which support ADI P386 v4.0/4.1
display (e.g. AutoCAD 386 Release 10/11, AutoShade V2.0,
Autodesk 3D Studio V1.0, etc).
* Support Dual-Screen (automatic detect).
* Individual colors selectable for parts of the graphics screen.
* Easy configure, automatic detect 8800/8900, automatic detect
video memory size.
Resolutions Available
---------------------
8900-1M 8900-512K 8900-256K 8800-512K 8800-256K
------------------------------------------------------------------------------
* Display:
640x480-16c X X X X X
800x600-16c X X X X X
1024x768-16c X X X
320x200-256c X X X X X
640x400-256c X X X X
640x480-256c X X X
800x600-256c X X
1024x768-256c X
* Rendering Display:
320x200-256c X X X X X
640x400-256c X X X X
640x480-256c X X X
800x600-256c X X
1024x768-256c X
512x480-32768c X X
640x480-32768c X
800x600-32768c X
512x480-65536c X X
640x480-65536c X
800x600-65536c X
Installation
------------
Installation procedures can vary for Autodesk products. Please
consult your Autodesk reference manual for complete installation
procedures. A general guide for installation follows:
* Copy RCPTVGA.EXP to your Autodesk directory.
* Set DSPADI, RDPADI or RCPADI as required, for example:
SET DSPADI=RCPTVGA
SET RDPADI=RCPTVGA
SET RCPADI=C:\3DS\RCPTVGA.EXP
* Configure the display device and/or rendering display device as
ADI P386 display.
SETUP.TXT
=========
This file contains information about problems that may occur while running
Windows for Workgroups Setup and describes problems that can occur when
using terminate-and-stay-resident (TSR) programs or drivers with Windows for
Workgroups or Setup. If you are using a TSR or if you encounter problems
setting up Windows for Workgroups, read this document BEFORE running Setup
again.
General Setup Notes
====================
This section includes notes on specific system configurations that may
prevent Setup from installing Windows for Workgroups successfully. A
solution to each problem is provided.
If you are using a hardware or software product listed here, follow the
proposed recommendations before running Setup.
Network Cards
--------------
If you are using one of the following network cards, you must run Setup
with the /i option:
Novell/Anthem NE1500
Novell/Anthem NE2100
Advanced Micro Devices (AMD) AM2100
Microdyne EXOS 105
At the MS-DOS prompt, type the following:
setup /i
MS-DOS Screen Savers
---------------------
If you are using an MS-DOS screen saver, you should turn it off before
running Setup. These screen savers can cause problems when running Setup.
COMPAQ Computer with MS-DOS Version 5.0 and EGA or VGA
---------------------------------------------------------
If you are using the upgrade version of Microsoft MS-DOS 5.0, check your
CONFIG.SYS file to make sure the following drivers (if present) appear in
this order:
HIMEM.SYS
EMM386.EXE
ANSI.SYS
Note: If you are using the COMPAQ version of MS-DOS 5.0,
HIMEM.EXE is used in place of HIMEM.SYS and CEMM.EXE
is used in place of EMM386.EXE.
If ANSI.SYS is loaded before HIMEM.SYS or EMM386.EXE (or if you are using
COMPAQ MS-DOS 5.0 before HIMEM.EXE or CEMM.EXE), Setup may restart your
system before Windows for Workgroups is installed. Also, if you are using
the DOS=HIGH,UMB command line to load MS-DOS into upper memory, loading
EMM386.EXE (or CEMM.EXE) before loading ANSI.SYS will create the maximum
amount of upper memory space on a COMPAQ computer.
AT&T Safari Computer
--------------------
If you have an AT&T Safari computer, you cannot maintain two versions of
Windows (version 3.0 and version 3.1) on your system. You must upgrade over
version 3.0. If you set up Windows for Workgroups version 3.1 in its own
directory, it will not use the special drivers required to run on the Safari
computer.
Displays That May Require Driver Updates with Windows for Workgroups
--------------------------------------------------------------------
Certain third-party display drivers designed for Windows version 3.0 can
cause problems with Windows for Workgroups version 3.1. The most serious
problem is a system failure while running Windows for Workgroups Setup. If
you encounter this problem, run Custom Setup, and then select one of the
standard display types, such as VGA, that is provided with Windows for
Workgroups.
With other Windows version 3.0 display drivers, Windows for Workgroups may
be set up successfully but TrueType fonts may not appear correctly on your
screen.
An updated driver may be available in the Windows Driver Library (WDL) or
from your display vendor or manufacturer. For information about obtaining
the WDL, see the "Getting Started" book.
Windows version 3.0 drivers for the following display adapters may cause
problems:
- ATI Graphics Ultra and Vantage
NOTE: These adapters are 8514/a-compatible and run well
with the 8514/a driver provided with Windows for Workgroups.
- DGIS display adapters (Direct Graphics Interface Standard)
from Graphic Software Systems, including the following:
NEC MultiSynch Graphics Engine (MGE)
Zenith Z-649
HP IGC-10, IGC-20
GSS 1000 Series
NOTE: Some DGIS-based adapters are TIGA-compatible and
run well when used with the appropriate TIGACD.EXE
MS-DOS driver and with the TIGA driver provided with
Windows for Workgroups.
- HP Ultra VGA (versions earlier than 1.4 only)
- IBM Image Adapter/A
- Matrox MG Series/M-WIN Series
- Palettized VGA 640x480, 16-color (provided with Windows
Multimedia Extensions version 1.0)
- Radius SVGA MultiView
- RGDI (Renaissance Graphics Device Interface) display
adapters from Appian, Inc., including the following:
Appian Rendition II, IIe, II/XE, and III
Appian GV1024
Decpc 433
- S3 adapters, including the following:
Orchid Fahrenheit 1280
STB WIND/X
Diamond Stealth VRAM
Using Stacker
-------------
If you are using Stacker to compress your hard disk, there are
certain steps you need to take before setting up Windows for Workgroups.
* If you want to use a swap file with Windows for Workgroups, you must
set up the swap file on the uncompressed drive. When setting up Stacker,
you can leave at least 1 megabyte (MB) of disk space uncompressed for
storing system files. To leave enough space for the swap file, it is
recommended that the amount of uncompressed disk space equal at least
twice the amount of system memory. For example, if your system has 4 MB
of memory, you should leave at least 8 MB of disk space uncompressed.
If Stacker is already set up on your system and there is not enough
uncompressed disk space for a swap file, you can run the STAC utility
provided with Stacker to increase the amount of uncompressed disk space.
For more information, see your Stacker documentation.
* If you are using Stacker version 2.0 or later, Windows for Workgroups
Setup modifies your CONFIG.SYS and AUTOEXEC.BAT files. When Setup
finishes making the modifications, it displays a message at the end of
the Windows portion of Setup, notifying you of the modifications. If you
have used Stacker to swap your startup drive, when you restart your
system, Stacker will ask whether you want to update to the new version of
the CONFIG.SYS or AUTOEXEC.BAT file. It is recommended that you update.
If you are using a version of Stacker earlier than 2.0, you may need to
modify your CONFIG.SYS and AUTOEXEC.BAT files yourself. For more
information, see the following topic, "Modifying Your CONFIG.SYS and
AUTOEXEC.BAT Files Yourself."
* For best performance, do not use SMARTDrive to cache the compressed drive.
You only need to cache the uncompressed drive. You can include options on
the SMARTDRV.EXE line of the CONFIG.SYS file to specify which drives to
cache.
For example, if the Stacker swap utility swaps drives C and D so that C
is compressed and D is uncompressed, you would include the following line
in your AUTOEXEC.BAT file:
c:\windows\smartdrv.exe c- d+
For more information about swap files and using SMARTDrive, see Chapter 11,
"Managing Memory and Performance," in the "Microsoft Windows for Workgroups
User's Guide."
Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself
---------------------------------------------------------
When you set up Windows for Workgroups, Setup usually places the HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE files in the Windows directory. If the Windows
directory is on a disk that is not available when you start your computer,
such as a removable or nonlocal disk, or if Setup detects one of the
following conditions, Setup does not modify the CONFIG.SYS or AUTOEXEC.BAT
file:
- Your boot drive has been modified by a disk-compression
utility.
- Your CONFIG.SYS file contains references to block device
drivers.
- There is not enough available space on your hard disk to
copy the files.
- The files are already installed on your system and Setup
cannot overwrite them (they are read-only).
Instead, Setup writes proposed changes to the CONFIG.WIN and AUTOEXEC.WIN or
the CONFIG.00x and AUTOEXEC.00x files. In this case, you must either move
the HIMEM.SYS, SMARTDRV.EXE, and EMM386.EXE files to a drive that is
available when you start your computer, or use a text editor to modify your
CONFIG.SYS or AUTOEXEC.BAT file so that any references to HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE appear after the device= command line used to
load the drivers for your disk drives. Refer to the CONFIG.WIN and
AUTOEXEC.WIN or the CONFIG.00x and AUTOEXEC.00x files for the proposed
changes.
Setting Up XGA on a PS/2 Model 75 or 90
---------------------------------------
If you have a PS/2 model 75 or 90 with an XGA, Windows for Workgroups Setup
will configure the display adapter for 16-color, 640x480 resolution. Do not
change this configuration during Setup. Specifying a different XGA
configuration while setting up Windows for may cause Setup to fail.
After you have successfully installed Windows, you can configure your XGA to
use a different resolution or 256 colors, if your monitor supports it. For
more information on how to do this, see the topic "IBM XGA: Configuring
Color and Resolution" in the README.WRI online document.
If you are using the plasma screen on the PS/2 model 75, use ONLY the
640x480, 16-color configuration. If you change this configuration, you
return to the MS-DOS prompt when you try to start Windows.
Correcting the "Out of Environment Space" Error Message
-------------------------------------------------------
If you receive an "out of environment space" message when starting Windows,
you can either:
* Increase the size of your environment by adding the SHELL= command
line to your CONFIG.SYS file. See your MS-DOS documentation for more
information about the SHELL command and about modifying your CONFIG.SYS
file.
* Move the SET commands in your AUTOEXEC.BAT file to the beginning of
the file so that they run before the commands that load
terminate-and-stay-resident (TSR) programs or drivers, such as
SMARTDrive.
Using Terminate-and-Stay-Resident (TSR) Programs and Drivers
with Windows for Workgroups
=============================================================
The "Program Listing" section of this document lists several
terminate-and-stay-resident (TSR) programs and drivers that are known to
cause problems when running with Windows for Workgroups. Some of the
problems you may encounter include system failures or an incorrect display
of information on your screen. In some cases, special steps are provided to
solve the problems.
While setting up Windows for Workgroups, Setup searches the AUTOEXEC.BAT and
CONFIG.SYS files for references to TSR programs and drivers, in addition to
scanning memory for TSRs that are currently running. If Setup detects a TSR
that is known to cause problems when running with Windows for Workgroups, a
message appears, asking whether you want to continue or quit Setup.
If you receive such a message, do the following:
1. Locate your TSR in the "Program Listing" section of this document
and use the information to determine if the situation encountered
prevents Setup from successfully installing Windows for Workgroups.
2. If the situation does not affect Setup, you can continue setting up
Windows for Workgroups by following the instructions on your
screen.
If the situation does affect Setup and prevents it from installing
Windows for Workgroups on your computer, follow the instructions on the
screen to quit Setup, and then complete the following steps.
3. Quit the TSR and remove all references to it from your
AUTOEXEC.BAT and CONFIG.SYS files. For more information,
see the documentation for your TSR.
4. Restart your computer.
5. Run Windows for Workgroups Setup again.
After Windows for Workgroups is successfully set up, you may want to restore
your TSRs.
Not all TSRs or drivers included in the "Program Listing" section are
detected by Setup. The TSRs and drivers that Setup detects are in the
SETUP.INF file, listed under the names "incomptsr1" and "incomptsr2".
Program Listing
===============
This section describes some problems, discovered during testing, that you
might encounter while using a TSR with Windows for Workgroups. It does not
include all possible problems that can occur.
386MAX
------
The documentation for 386MAX recommends against setting the EXT parameter
below 64. If you set this parameter to 0, Setup and Windows for Workgroups
running in standard mode will fail.
See the README.WRI online document for more information about running 386MAX
with Windows for Workgroups.
386MAX Disk-Cache Utility (QCACHE.EXE)
--------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
instead.
All Charge 386 Version 3.1
--------------------------
ALLEMM4.SYS is a memory manager that causes problems with Setup and Windows
for Workgroups. If you encounter problems running this program with Windows
for Workgroups, it is recommended that you use EMM386.EXE and HIMEM.SYS,
provided with Windows for Workgroups, to manage memory instead.
Anarkey Version 4.00
--------------------
With some memory configurations, Anarkey version 4.00 running with Windows
for Workgroups in 386 enhanced mode may cause unpredictable system failures.
In rare cases, this program can also corrupt hard-disk data. In addition,
Windows for Workgroups might not start when this program is running.
Do not run Windows for Workgroups in 386 enhanced mode when Anarkey version
4.00 is running. Version 4.01 may correct these problems. Contact Moderne
Software for a free upgrade to Anarkey 4.01.
Anarkey Version 4.01
--------------------
If Anarkey version 4.01 is loaded before starting Windows for Workgroups in
standard mode, it is not available in any instance of MS-DOS Prompt that you
start within Windows for Workgroups. In this case, it is recommended that you
load Anarkey from each instance of MS-DOS Prompt, as needed.
Do not load Anarkey HIGH before starting Windows for Workgroups in 386
enhanced mode. If you load Anarkey HIGH, your system may fail when you try
to start an application.
APPEND (MS-DOS)
---------------
Do not use the APPEND utility with Windows for Workgroups. It prevents
Windows and Windows-based applications from creating valid Well-Formed-Path
(WFP) names for the files they are using. (A WFP is the complete name of a
file, including the drive letter and full path specification, starting from
the root directory.)
ASP Integrity Toolkit Version 3.7
---------------------------------
This product is a virus-protection program that can cause problems when
running Setup, including system failure, automatic restarting of the system,
and the inability to use the keyboard. You should turn off protection in
the toolkit before setting up Windows for Workgroups. For information
about how to do this, see your ASP Integrity documentation.
NOTE: Setting up Windows for Workgroups is considered a system-administration
task. The ASP Integrity Toolkit documentation instructs you to turn
off protection when performing these types of tasks.
Autocon Version 2.0e
--------------------
Autocon enables you to select up to fifty different configurations when
starting your system. To do this, it modifies the CONFIG.SYS and
AUTOEXEC.BAT files, based on information in its database (AUTOCON.DAT), when
you restart your system from within AUTOCON.
Windows for Workgroups Setup modifies only the first section in the
CONFIG.SYS and AUTOEXEC.BAT files. If you want to use specific
configurations with Windows, you must run Autocon and then manually edit the
configurations in the database that you want to use. You must do this after
setting up Windows for Workgroups. For your changes to take effect, you must
restart your system from within Autocon. For more information, see your
Autocon documentation.
Bootcon Version 1.60
--------------------
Using Bootcon, you can maintain different system-configuration information
in your CONFIG.SYS and AUTOEXEC.BAT files. You can then select the
configuration you want to use from a menu when starting your system.
Setup modifies the first section in the CONFIG.SYS and AUTOEXEC.BAT
files, and may modify certain other sections that contain network drivers
(for example, LAN Manager drivers and NetWare drivers may be deleted). After
you set up Windows for Workgroups, you must edit the sections of those files
that contain other configurations you want to use. For more information, see
your Bootcon documentation.
BOOT.SYS
--------
Using BOOT.SYS, you can maintain different system-configuration information
in your CONFIG.SYS and AUTOEXEC.BAT files. You can then select the
configuration you want to use from a menu when starting your system.
Setup modifies the first section in the CONFIG.SYS and AUTOEXEC.BAT
files, and may modify certain other sections that contain network drivers
(for example, LAN Manager drivers and NetWare drivers may be deleted). After
you set up Windows for Workgroups, you must edit the sections of those files
that contain other configurations you want to use. For more information, see
your BOOT.SYS documentation.
CACHE.EXE Disk-Cache Utility
----------------------------
Do not use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your CONFIG.SYS
and AUTOEXEC.BAT files. (If CACHE.EXE is detected, Setup removes it from the
CONFIG.SYS file for you.)
CACHE.SYS Disk-Cache Utility
----------------------------
This disk-cache utility will not work properly with SMARTDrive. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If CACHE.SYS is detected, Setup removes
it from the CONFIG.SYS file for you.)
CED Version 1.0e
----------------
Using CED with Windows for Workgroups may cause problems, including
system failure. It is recommended that you do not use CED with Windows for
Workgroups.
Central Point Anti-Virus Version 1.1 (VSAFE.COM/VSAFE.SYS)
----------------------------------------------------------
VSAFE.COM/VSAFE.SYS should not be loaded when you set up Windows for
Workgroups. Otherwise, Setup may not run properly. After you set up
Windows for Workgroups, you can load VSAFE.
Because Windows uses the disk for memory swapping, you should turn off the
VSAFE write-protection option when running Windows for Workgroups.
For more information, see the Central Point Anti-Virus documentation.
CMDEDIT.COM Version 2.0 (Date 12-6-91)
--------------------------------------
If this command-line editor is loaded before starting Windows for
Workgroups, it may cause a General Protection Fault when you run multiple
MS-DOS Prompts in 386 enhanced mode. Also, it cannot be loaded from an
MS-DOS Prompt within Windows when Windows is running in standard mode.
Cubit Version 3.01
------------------
When using Cubit with Windows for Workgroups, do not compress the
Windows SYSTEM directory or any file that is loaded from the CONFIG.SYS
file. Compressing these files could cause problems.
Before upgrading to Windows for Workgroups, make sure that the earlier
version of Windows is uncompressed on your hard disk. You may recompress the
files after you have successfully set up Windows for Workgroups.
Data Physician Plus Version 2.0 (VirALERT)
------------------------------------------
It is recommended that you do not set up Windows for Workgroups while
VirALERT is running. If you do, VirALERT will display a warning message
every few seconds while Setup is running.
After you have set up Windows for Workgroups, you can run VirALERT. Press
ALT+V to display the VirALERT menu. You can use the commands on this menu to
disable and enable VirALERT.
DOSCUE.COM Command-Line Editor
------------------------------
The DOSCUE command-line editor produces unexpected results when used with
Windows for Workgroups. It is recommended that you do not use this editor
with Windows for Workgroups.
Doubledisk Version 2.5
----------------------
Windows for Workgroups may try to access "phantom" disk drives if you use it
with Doubledisk. Phantom drives occur when you use Doubledisk to create a
compressed drive. For example, if you have drives A, B, and C on your
computer and you use Doubledisk to create drive F, Windows for Workgroups
and MS-DOS recognize drives D and E as valid drives, even though they do
not actually exist. You can use the DRVOFF utility to prevent Windows from
recognizing phantom drives. Contact Vertisoft to order a copy of the DRVOFF
utility.
FASTOPEN (MS-DOS)
-----------------
FASTOPEN is a RAM-resident utility. Problems involving the file allocation
table (FAT) may occur if FASTOPEN is used together with disk-defragmenting
utilities. In low-memory situations, you may need to remove FASTOPEN for
Windows for Workgroups to run properly.
Flash Disk-Cache Utility (FLASH.EXE)
-------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for
Workgroups, instead.
Graphics (MS-DOS)
-----------------
Loading Graphics from MS-DOS Prompt within Windows can cause unexpected
results when printing. The active MS-DOS Prompt will send its output to the
printer. Switching between multiple MS-DOS Prompts may result in mixed
printing jobs.
HPEMM386.SYS and HPEMM486.SYS
-----------------------------
These expanded-memory managers are incompatible with Windows for Workgroups
when it is running in 386 enhanced mode. If you plan on running Windows for
Workgroups in 386 enhanced mode, it is recommended that you use EMM386.EXE
to manage memory instead.
HPMM.SYS - HP Memory Manager
----------------------------
When HPMM.SYS is running, you cannot set up Windows for Workgroups or
run it in standard mode. You should remove all references to HPMM.SYS from
your CONFIG.SYS and AUTOEXEC.BAT files before setting up Windows for
Workgroups.
Hyperdisk Disk-Cache Utility
----------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
instead.
IBM VDISK.SYS (RAM Disk Utility)
--------------------------------
VDISK.SYS is incompatible with Windows for Workgroups because it occupies
extended memory required to run Windows for Workgroups. This utility prevents
any XMS-compatible memory manager from loading.
IEMM.SYS Memory Manager
-----------------------
The IEMM.SYS memory manager is incompatible with Windows for Workgroups. It
is recommended that you remove all references to IEMM.SYS from your
CONFIG.SYS and AUTOEXEC.BAT files and use EMM386.EXE, provided with Windows
for Workgroups, to manage memory instead.
ICACHE.SYS Disk-Cache Utility
-----------------------------
Do not use two disk-cache utilities with Windows for Workgroups.
It is recommended that you use SMARTDrive, provided with Windows for
Workgroups, and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If ICACHE.SYS is detected, Setup
removes it from the CONFIG.SYS file for you.)
IBMCACHE.SYS Disk-Cache Utility
-------------------------------
Do not use two disk-cache utilities with Windows for Workgroups.
It is recommended that you use SMARTDrive, provided with Windows for
Workgroups, and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If IBMCACHE.SYS is detected, Setup
removes it from the CONFIG.SYS file for you.)
Intel Expanded-Memory Emulator (ILIM386.SYS)
--------------------------------------------
The ILIM386.SYS expanded-memory emulator, provided with the Intel
Inboard/386 product, is incompatible with Windows for Workgroups. It is
recommended that you remove all references to this emulator from your
CONFIG.SYS and AUTOEXEC.BAT files before setting up Windows for Workgroups.
JOIN (MS-DOS)
-------------
Do not add or remove "joined" drives while running Windows for Workgroups.
If you use the JOIN command before starting Windows for Workgroups and do
not change the state of the joined drives from MS-DOS Prompt within Windows,
Windows for Workgroups will work properly. It is recommended that you do not
use joined drives at all if you plan on running Windows.
KEYB.COM (MS-DOS)
-----------------
If you use command-line options to load KEYB.COM, it is recommended that you
load it before starting Windows for Workgroups. After it is loaded, you can
change the keyboard configuration from MS-DOS Prompt within Windows at any
time. If you do not load KEYB.COM before starting Windows, you may encounter
problems when using a KEYB command that includes an option in an MS-DOS
Prompt. However, you can use the KEYB command without options at any time to
display code-page information.
Lansight Version 2.0
--------------------
Lansight is a utility that you can use to control and monitor other
workstations attached to a Novell network. In some cases, version 2.0 of
Lansight may cause the workstation running Windows for Workgroups to
fail.
Lasertool Control Panel Version 2.2
------------------------------------
If you load version 2.2 of the Lasertool Control Panel program (PCPANEL.EXE)
from Windows for Workgroups, your system may fail. This program works
properly if you load it before starting Windows for Workgroups.
Le Menu Version 1.0
-------------------
When using Le Menu version 1.0 with Windows for Workgroups, environment
information such as PATH, PROMPT and WINDIR may be lost if you start MS-DOS
Prompt from within Windows. If you want to start Windows for Workgroups by
using a Le Menu menu command, it is recommended that you set up Windows for
Workgroups as a Batch-File menu command so that COMMAND.COM will load before
starting Windows for Workgroups. For more information, see your Le Menu
documentation.
LOCKIT Version 3.3 (PC Vault, Secure It)
----------------------------------------
Version 3.3 of these programs strip out spaces from the load= command line
in the WIN.INI file. Later versions may correct this problem.
Logitech Mouse Software Version 5.0/6.0 (CLICK, LOGIMENU)
----------------------------------------------------------
If you want to use CLICK and LOGIMENU from MS-DOS Prompt within Windows, you
must load the TSRs from that MS-DOS Prompt, even if you loaded the TSRs
before starting Windows for Workgroups. When you quit Windows for
Workgroups, you must reload the TSRs for them to work properly from the
command prompt outside of Windows, even if you loaded them from MS-DOS
Prompt within Windows.
Mace Disk-Cache Utility (MCACHE.SYS)
------------------------------------
This disk-cache utility will not work properly with SMARTDrive. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If Mace is detected, Setup removes it
from the CONFIG.SYS file for you.)
Maximizer Memory Manager (MAXIMIZE.COM)
---------------------------------------
If you are using the Maximizer memory manager, you may not be able to set up
or start Windows for Workgroups. Make sure that you are using only one
memory manager with Windows for Workgroups. It is recommended that you use
HIMEM.SYS and EMM386.EXE, which are provided with Windows for Workgroups, to
manage memory instead.
MIRROR (MS-DOS)
-----------------
If MIRROR is loaded from Windows for Workgroups by using the Run command in
standard mode, you cannot remove it from memory by using the MIRROR /U
command. This will cause an error message to appear.
NDOSEDIT.COM (Date 1-1-84)
--------------------------
You may have problems loading this command-line editor. Also, it may cause
unexpected results when running with Windows for Workgroups.
NetRoom Memory Manager (RM386.SYS)
-------------------------------------------
With some older versions of NetRoom, you may encounter problems setting up
Windows for Workgroups. In this case, contact Helix Software for a newer
version of NetRoom.
NetWare NetBIOS
---------------
The NetWare NetBIOS TSR is incompatible with Windows for Workgroups in
many configurations. In most cases, Setup will detect NetWare NetBIOS and
remove the startup command from your system. However, if you have NetWare
NetBIOS set up to start from a location other than your AUTOEXEC.BAT file
(for example, from a batch file), Setup cannot detect it. In this case, you
need to remove NetWare NetBIOS manually. For information about configuring
Windows for Workgroups to work with the NetWare NetBIOS TSR, see the
NETWORKS.WRI online document.
Newspace Version 1.07
---------------------
This disk-compression utility is incompatible with Windows for Workgroups
and may cause several problems.
Norton Anti-Virus Version 1.0
-----------------------------
If you load version 1.0 of Anti-Virus before setting up Windows for
Workgroups, Setup may fail. It is recommended that you contact Symantec for
the most current version of this program.
Norton Desktop for Windows (EP.EXE)
-----------------------------------
If the data-recovery program Erase Protect (EP.EXE) is loaded from the
AUTOEXEC.BAT file, you need to disable it when setting up Windows for
Workgroups, especially if you are upgrading over a previous version of
Windows. Erase Protect tries to save copies of all deleted files, which can
cause you to run out of disk space while running Setup.
It is recommended that you run Erase Protect with a permanent swap file, not
a temporary swap file. If you are using a temporary swap file, you need to
exclude files having a .TMP or .SWP extension from erase protection.
Norton Utilities Version 5.0 (DISKREET, NCACHE)
-----------------------------------------------
This program is incompatible with Windows for Workgroups and may cause your
system to fail. It is recommended that you upgrade to the most recent
version of Norton Utilities to correct problems.
Norton Utilities Version. 6.01 (NCACHE)
---------------------------------------
Some versions of NCACHE may prevent you from setting up or starting Windows
for Workgroups. When Windows for Workgroups is running in standard mode,
your system may fail, especially if NCACHE is set up as an EMS cache.
Setting up NCACHE as an EMS cache is not recommended. Setting up NCACHE as
an XMS cache may solve the problem.
You may also encounter additional problems using NCACHE. New versions may
correct these problems. For an updated version of NCACHE, contact Symantec
Corporation. In the meantime, you can use SMARTDrive, which is provided with
Windows for Workgroups.
Norton Utilities Version 6.01 (DISKMON)
--------------------------------------
It is recommended that you do not use DISKMON version 6.01 with Windows for
Workgroups.
PCED Version 2.00
-----------------
Do not load the PCED command-line editor HIGH. Loading it HIGH may cause
unexpected results, such as system failures, when Windows for Workgroups is
running in 386 enhanced mode. If you load this program before starting
Windows for Workgroups, it may be unavailable when Windows for Workgroups is
running in standard mode.
PCKEY.EXE (MultiSoft Keyboard Enhancer and Command-Line Stack)
--------------------------------------------------------------
PCKEY.EXE may not work properly with Windows for Workgroups when you are
running more than one MS-DOS--based application at a time. It is recommended
that you unload PCKEY.EXE before starting Windows for Workgroups.
PC-Kwik Disk Accelerator
------------------------
If you use PC-Kwik when Windows for Workgroups is running in 386 enhanced
mode, make sure that you are using version 3.55 or later and that PC-Kwik is
in extended memory, not expanded memory. To get an upgraded version of
PC-Kwik, contact MultiSoft.
PC-Kwik Disk-Cache Utility (PC-KWIK.EXE)
----------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
instead.
PC-Kwik Version. 1.59 (PCK.EXE, PSKSCRN.EXE, PCKEY.COM)
-------------------------------------------------------
If version 1.59 of PC-KWIK is loaded before setting up Windows for
Workgroups, Setup may fail. PC-KWIK Version 2.0 may correct this problem.
PCSXMAEM.SYS Utility
--------------------
This utility is incompatible with Windows for Workgroups. You should remove
all references to it from your CONFIG.SYS and AUTOEXEC.BAT files before
setting up or starting Windows for Workgroups. PCSXMAEM.SYS is similar
to XMAEM.SYS. It has been renamed and slightly modified. It is provided with
current versions of the IBM PC/3270 emulator.
PCSX2EMS.SYS
-------------
Windows for Workgroups will run correctly with PCSX2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this program is
incompatible with Windows for Workgroups. PCSX2EMS.SYS is provided with the
IBM PC/3270 emulator.
PC Tools Deluxe Version 7.1 (DATAMON)
------------------------------------
If you load PC Tools DATAMON using the \SENTRY+ option, Setup may fail if
you are low on disk space. Do not use the \SENTRY+ option when loading
DATAMON.
Do not load DATAMON after loading SMARTDrive. If DATAMON is loaded after
SMARTDrive, your system may fail. See the PC Tools documentation for
information about how to unload DATAMON.
PC Tools Deluxe Version 6.0 (DESKTOP)
------------------------------------
If you try to start PC Tools from MS-DOS Prompt within Windows for
Workgroups in standard mode, your system may fail. In enhanced mode, your
system may restart itself. These problems also occur if you use MS-DOS
commands from MS-DOS Prompt within Windows.
Version 7.0 of PC Tools may correct these problems. However, do not load
DESKTOP from MS-DOS Prompt if it was loaded before starting Windows for
Workgroups. If you do, your system may fail when you quit Windows for
Workgroups. It is recommended that you run DESKTOP from its PIF, provided
with Windows for Workgroups.
PC Tools Deluxe Version 7.1 (VDEFEND)
-------------------------------------
Setup may not work properly if VDEFEND is loaded before running Setup. You
may load VDEFEND after setting up Windows for Workgroups.
PC Tools Disk-Cache Utility (PC-CACHE.COM)
-----------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows. It is recommended
that you use SMARTDrive, provided with Windows for Workgroups, instead.
PRINT (MS-DOS)
--------------
If you are printing several large documents on a network printer and run
Setup from the network, your system may fail while Setup is creating Program
Manager groups.
PYRO! Version 1.0
-----------------
If this screen saver is loaded before starting Windows for Workgroups,
you may not be able to restore the Windows for Workgroups screen after
this screen saver appears.
QMAPS Memory Manager Version 5.16
---------------------------------
If you are using the QMAPS memory manager, you may not be able to set up or
start Windows for Workgroups. New versions may correct these problems. For
an updated version of QMAPS, contact Quadtel. In the meantime, you may use
HIMEM.SYS and EMM386.EXE, provided with Windows for Workgroups, to manage
memory instead.
RAMTYPE.SYS - AST RAMpage! Boards
---------------------------------
The RAMTYPE.SYS driver is incompatible with Windows for Workgroups. It is
recommended that you remove this driver before setting up Windows for
Workgroups. If you load the driver from your CONFIG.SYS file, comment
out the command line for the driver as follows:
rem RAMTYPE.SYS
Windows for Workgroups will run correctly without RAMTYPE.SYS. However,
other drivers that rely on RAMTYPE.SYS will not load and applications will
not be able to use the expanded memory on your system.
After setting up Windows for Workgroups, you can use version 1.2 and later
of RAMTYPE.SYS with Windows for Workgroups. If you are using an earlier
version on an IBM PS/2 or Micro Channel Architecture computer and your
RAMpage! board is configured for expanded and extended memory, you need to
upgrade your AST RAMTYPE.SYS driver after setting up Windows for Workgroups.
You will also need to remove the "rem" command from your CONFIG.SYS file so
that RAMTYPE.SYS will load properly.
Secretdisk II Disk-Cache Utility (FAST512.SYS)
----------------------------------------------
This disk-cache utility will not work properly with SMARTDrive. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If this utility is detected, Setup
removes it from the CONFIG.SYS file for you).
SideKick Versions 1.0 and 2.0 and SideKick Plus
-----------------------------------------------
Miscellaneous problems may occur when running SideKick as a TSR with Windows
for Workgroups. It is recommended that you use a PIF to run SideKick as
a MS-DOS--based application, instead of loading it as a TSR.
SoftIce Debugger
----------------
If SoftIce is loaded, Setup will fail when starting the Windows portion of
the program. It is recommended that you unload SoftIce before setting up
Windows for Workgroups.
SpeedFXR
--------
This program is incompatible with Windows for Workgroups when running as
a TSR. It tries to increase the speed of the floppy disk drives, but slows
them down instead. To get the best results, use the -X option when loading
SpeedFXR. This will prevent SpeedFXR from remaining in memory and affecting
the speed of the floppy disk drives.
SUBST (MS-DOS)
--------------
Do not add or remove "substituted" drives while running Windows for
Workgroups. If you use the SUBST command before starting Windows for
Workgroups and do not change the state of the substituted drives from MS-DOS
Prompt within Windows, Windows for Workgroups will work properly.
Super PC-Kwik Disk-Cache Utility (SUPERPCK.EXE)
-----------------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows. It is recommended
that you use SMARTDrive, provided with Windows for Workgroups, instead.
Trantor T100 Host Adapter Driver (TSCSI.SYS)
--------------------------------------------
(For SCSI hard disk drives) - If you use the Trantor T100 driver
(TSCSI.SYS), you must use version 4.33d or higher. Earlier versions identify
the SCSI hard disk drive as a removable drive. This may cause problems when
using File Manager, such as a system failure while formatting the drive and
unexpected results when deleting files. To get an updated driver, contact
Trantor Systems, Ltd.
UMB PRO Version 1.07
--------------------
If you are running UMB PRO, you may experience problems running Windows for
Workgroups in standard mode. In some cases, your system may fail. Make sure
that you are using only one memory manager with Windows for Workgroups.
It is recommended that you use HIMEM.SYS and EMM386.EXE, which are provided
with Windows for Workgroups, to manage memory instead.
Vaccine
-------
If Vaccine is loaded, Setup fails when trying to modify the CONFIG.SYS and
AUTOEXEC.BAT files. You should unload Vaccine before setting up Windows for
Workgroups. You may also encounter problems, such as beeping, while
running Windows for Workgroups when Vaccine is loaded.
VIREX-PC Version 1.11
---------------------
If VIREXPC.COM is loaded, Setup and Windows for Workgroups will fail
when KRNL386.EXE performs a write operation. Also, the first time Windows
for Workgroups is loaded, you may be returned to the MS-DOS prompt.
Virus Prevention Plus Version 5.0
---------------------------------
If Virus Prevention Plus is loaded, you may not be able to successfully set
up Windows for Workgroups. You may also encounter problems when running
Windows for Workgroups in 386 enhanced mode. The Keyboard Lock program
may cause Windows for Workgroups to fail.
Virusafe Version 4.0
--------------------
If this program is loaded as a TSR, Setup may fail while setting up Windows
for Workgroups. It is recommended that you load Virusafe by using the
/C- option. This option turns off the memory-change detection provided with
Virusafe. Version 4.5 may correct this problem. For more information, see
your Virusafe documentation.
XGAAIDOS.SYS
------------
With XGAAIDOS.SYS loaded, Windows for Workgroups will fail at the
opening logo if you use the WIN /S option to start Windows for Workgroups in
standard mode.
XMAEM.SYS
---------
XMAEM.SYS is a device which causes extended memory to act like XMA. This
utility is incompatible with Windows for Workgroups. It is recommended
that you remove all references to it from your CONFIG.SYS and AUTOEXEC.BAT
files before setting up or running Windows for Workgroups. XMAEM.SYS is
provided with IBM DOS version 4.0.
XMA2EMS.SYS
-----------
Windows for Workgroups will run correctly with XMA2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this program is
incompatible with Windows for Workgroups. XMA2EMS.SYS is provided with IBM
DOS version 4.0.
MS-DOS is a registered trademark and Windows is a trademark of
Microsoft Corporation.
AT&T is a registered trademark of American Telephone and Telegraph Company.
RAMpage! is a registered trademark of AST Research, Inc.
SideKick is a registered trademark of Borland International, Inc.
PC Tools and PC Tools Deluxe are trademarks of Central Point Software, Inc.
COMPAQ is a registered trademark of Compaq Computer Corporation.
HP is a registered trademark of Hewlett-Packard Company.
IBM and PS/2 are registered trademarks of International Business Machines
Corporation.
Intel is a registered trademark, and Inboard and LANSight are trademarks,
of Intel Corporation.
Logitech is a trademark of Logitech, Inc.
NEC is a registered trademark of NEC Corporation.
Exos, NetWare, and Novell are registered trademarks of Novell, Inc.
Norton Utilities is a registered trademark of Peter Norton Computing,
Incorporated.
386MAX is a registered trademark of Qualitas, Inc.
Radius is a trademark of Radius, Inc.
Stacker is a registered trademark of STAC Electronics.
Norton Anti-Virus is a registered trademark of Symantec Corporation.
Zenith is a registered trademark of Zenith Electronics Corporation.
--------------------------------------------------------------------------
SETUP.TXT
=========
This file contains information about problems that may occur while you are
running Windows for Workgroups Setup or when you are using terminate-and-
stay-resident (TSR) programs or drivers with Windows for Workgroups or Setup.
If you are using a TSR or if you encounter problems setting up Windows for
Workgroups, read this document BEFORE you run Setup again.
GENERAL SETUP NOTES
====================
This section includes notes on specific system configurations that may
prevent Setup from installing Windows for Workgroups successfully. A
possible solution to each problem is provided.
If you are using a hardware or software product listed here, follow the
proposed recommendations before you run Setup.
Network Cards
-------------
If you are using one of the following network cards, you must run Setup
with the /i option:
Novell(R)/Anthem NE1500
Novell/Anthem NE2100
Advanced Micro Devices (AMD) AM2100
Microdyne Exos(R) 105
To do this, type the following at the MS-DOS prompt:
setup /i
MS-DOS(R) Screen Savers
-----------------------
If you are using an MS-DOS screen saver, you should turn it off before
running Setup. These screen savers can cause problems when running Setup.
COMPAQ(R) Computer with MS-DOS Version 5.0 or later and EGA or VGA Display
-----------------------------------------------------------------
If you are using the upgrade version of Microsoft MS-DOS 5.0 or later, check your
CONFIG.SYS file to make sure the following drivers (if present) appear in
this order:
HIMEM.SYS
EMM386.EXE
ANSI.SYS
Note: If you are using the COMPAQ version of MS-DOS 5.0, HIMEM.EXE is used
in place of HIMEM.SYS and CEMM.EXE is used in place of EMM386.EXE.
If ANSI.SYS is loaded before HIMEM.SYS or EMM386.EXE (or if you are using
COMPAQ MS-DOS 5.0 before HIMEM.EXE or CEMM.EXE), Setup may restart your
system before Windows for Workgroups is installed. Also, if you are using
the DOS=HIGH,UMB command line to load MS-DOS into upper memory, loading
EMM386.EXE (or CEMM.EXE) before loading ANSI.SYS will create the maximum
amount of upper memory space on a COMPAQ computer.
AT&T(R) Safari Computer
-----------------------
If you have an AT&T Safari computer, you cannot maintain two versions of
Windows on your system. You must upgrade over your previous version of
Windows, if you have one. If you set up Windows for Workgroups version 3.11
in its own directory, it will not use the special drivers required to run on the Safari
computer.
Displays That May Require Driver Updates with Windows for Workgroups
--------------------------------------------------------------------
Certain third-party display drivers designed for Windows version 3.0 can
cause problems with Windows for Workgroups version 3.11. The most serious
problem is a system failure while you are running Windows for Workgroups
Setup. If you encounter this problem, run Custom Setup, and then select
one of the standard display types, such as VGA, that is provided with
Windows for Workgroups.
With other Windows version 3.0 display drivers, Windows for Workgroups may
be set up successfully, but TrueType fonts may not appear correctly on your
screen.
An updated driver may be available in the Windows Driver Library (WDL) or
from your display vendor or manufacturer. For information on obtaining drivers
from the WDL, see the "Getting Drivers from the Windows Driver Library
(WDL)" section later in this document.
Windows version 3.0 drivers for the following display adapters may cause
problems:
* ATI Graphics Ultra, Vantage, and Mach32
NOTE: These adapters are 8514/a-compatible and run well
with the 8514/a driver provided with Windows for Workgroups.
* DGIS display adapters (Direct Graphics Interface Standard)
from Graphic Software Systems, including the following:
NEC(R) MultiSynch Graphics Engine (MGE)
Zenith(R) Z-649
HP(R) IGC-10, IGC-20
GSS 1000 Series
NOTE: Some DGIS-based adapters are TIGA-compatible and
run well when used with the appropriate TIGACD.EXE
MS-DOS driver and with the TIGA driver provided with
Windows for Workgroups.
* HP Ultra VGA (versions earlier than 1.4 only)
* IBM(R) Image Adapter/A
* Matrox MG Series/M-WIN Series
* Palettized VGA 640x480, 16-color (provided with Windows
Multimedia Extensions version 1.0)
* Radius(R) SVGA MultiView
* RGDI (Renaissance Graphics Device Interface) display
adapters from Appian, Inc., including the following:
Appian Rendition II, IIe, II/XE, and III
Appian GV1024
Decpc 433
- S3 adapters, including the following:
Orchid Fahrenheit 1280
STB WIND/X
Diamond Stealth VRAM
Using the ATI Mach 32 Video Adapter
-----------------------------------
Before you run Windows Setup, make sure the Mach 32 adapter is set up
correctly. In the Mach 32 Install program, choose the Set Power-Up
Configuration option. Set the VGA Memory Size to half the RAM
available on the Mach 32 adapter. Since most Mach 32 adapters come with
1 MB of RAM, the appropriate setting is usually 512K.
Using Stacker(R)
----------------
If you are using Stacker to compress your hard disk, you need to take the
following steps before setting up Windows for Workgroups.
* If you want to use a swap file with Windows for Workgroups, you must
set up the swap file on the uncompressed drive. When you set up Stacker,
you can leave at least 1 MB of disk space uncompressed for storing system
files. To leave enough space for the swap file, it is recommended that the
amount of uncompressed disk space equal at least twice the amount of
system memory. For example, if your system has 4 MB of memory, you should
leave at least 8 MB of disk space uncompressed.
If Stacker is already set up on your system and there is not enough
uncompressed disk space for a swap file, you can run the STAC utility
provided with Stacker to increase the amount of uncompressed disk space.
For more information, see your Stacker documentation.
* If you are using Stacker version 2.0 or later, Windows for Workgroups
Setup modifies your CONFIG.SYS and AUTOEXEC.BAT files. When Setup
finishes making the modifications, it displays a message notifying you
of the modifications. If you have used Stacker to swap your startup drive,
when you restart your system Stacker will ask whether you want to update
to the new version of the CONFIG.SYS or AUTOEXEC.BAT file. It is
recommended that you update.
If you are using a version of Stacker earlier than 2.0, you may need to
modify your CONFIG.SYS and AUTOEXEC.BAT files yourself. For more
information, see the following topic, "Modifying Your CONFIG.SYS and
AUTOEXEC.BAT Files Yourself."
* For best performance, do not use SMARTDrive to cache the compressed drive.
You only need to cache the uncompressed drive. You can include options on
the SMARTDRV.EXE line of your CONFIG.SYS file to specify which drives to
cache.
For example, if the Stacker swap utility swaps drives C and D, so that C
is compressed and D is uncompressed, you would include the following line
in your AUTOEXEC.BAT file:
c:\windows\smartdrv.exe c- d+
For more information about swap files and using SMARTDrive, see Chapter 11,
"Managing Memory and Performance," in the "Microsoft Windows for Workgroups
User's Guide."
Solving Memory Conflicts by Using MONOUMB.386 or MONOUMB2.386
-------------------------------------------------------------
If you encounter the following message when you start Windows for
Workgroups, your display driver may be accessing the monochrome
address range (B000-B7FF), which prevents the memory manager from
using this range for upper memory blocks:
"Windows cannot set up an upper memory block at segment B000.
Exclude this address space by using the syntax of your memory
manager. For more information, use an MS-DOS editor to read
the SETUP.TXT file."
To solve this problem, try installing MONOUMB2.386 on your system.
MONOUMB2.386 is a device driver that allows certain memory managers to use
the monochrome address range for upper memory blocks even if your display
driver is accessing this range.
You can get MONOUMB2.386 from Windows for Workgroups 3.1 or from Microsoft.
It is not included on the Windows for Workgroups 3.11 disks. To install
MONOUMB2.386, carry out the following procedure:
1. Copy and expand the MONOUMB2.38_ file to your Windows SYSTEM directory
by typing the following at the MS-DOS prompt:
expand a:\monoumb2.38_ c:\windows\system\monoumb2.386
2. Add the following setting to the [386Enh] section of your SYSTEM.INI
file:
device=monoumb2.386
3. Start Windows for Workgroups.
Note: MONOUMB2.386 may not work with some memory managers, such as
EMM386.EXE. In this case, you can try using MONOUMB.386, provided
with the Windows Driver Library (WDL). For information on obtaining
drivers from the WDL, see the "Getting Drivers from the Windows Driver
Library (WDL)" section later in this document.
You can also exclude the address region B000-B7FF. This specifies that the
memory manager should not try to use this address range for upper memory
blocks. For information about excluding specific address ranges, see the
following topic.
Solving Memory Conflicts by Excluding an Address Range
------------------------------------------------------
If you encounter the following message when you start Windows for
Workgroups, and the address specified in the message is not B000,
you must exclude the address range:
"Windows cannot set up an upper memory block at segment xxxx.
Exclude this address space by using the syntax of your memory
manager. For more information, use an MS-DOS editor to read
the SETUP.TXT file."
If the address specified in the message is B000, you can try installing
MONOUMB2.386 or MONOUMB.386, as described in the preceding topic.
The method you use to exclude an address range depends on the memory manager
you are using. For example, if you are using EMM386.EXE, you need to remove
the I=xxxx option from the device=emm386.exe command line in your CONFIG.SYS
file, where xxxx is the address range starting at the address specified in
the error message.
If you are using QEMM, you need to include the X= option on the
device=qemm386.sys command line in your CONFIG.SYS file. For example, to
exclude the address range C000-C7FF, you would specify the following:
device=qemm386.sys X=C000-C7FF
For more information about modifying your CONFIG.SYS file, see your MS-DOS
documentation. For more information about installing and configuring
EMM386.EXE, see "Managing Memory and Performance" in your Windows or Windows
for Workgroups user's guide. For information about installing and configuring
other memory managers, see the documentation provided with your memory
manager.
Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself
---------------------------------------------------------
When you set up Windows for Workgroups, Setup usually places the HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE files in the Windows directory. If the Windows
directory is on a disk that is not available when you start your computer,
such as a removable or nonlocal disk, or if Setup detects one of the
following conditions, Setup does not modify your CONFIG.SYS or AUTOEXEC.BAT
file:
* Your boot drive has been modified by a disk-compression utility.
* Your CONFIG.SYS file contains references to block device drivers.
* Your CONFIG.SYS file is set up for multiple configurations.
* There is not enough available space on your hard disk to copy the files.
* The files are already installed on your system, and Setup cannot overwrite
them (they are read-only).
Instead, Setup writes proposed changes to the CONFIG.WIN and AUTOEXEC.WIN or
the CONFIG.00x and AUTOEXEC.00x files. In this case, you must either move
the HIMEM.SYS, SMARTDRV.EXE, and EMM386.EXE files to a drive that is
available when you start your computer, or use a text editor to modify your
CONFIG.SYS or AUTOEXEC.BAT file so that any references to HIMEM.SYS,
SMARTDRV.EXE, and EMM386.EXE appear after the device= command line used to
load the drivers for your disk drives. Refer to the CONFIG.WIN and
AUTOEXEC.WIN or the CONFIG.00x and AUTOEXEC.00x files for the proposed
changes.
Using Multiple System Configurations with Windows for Workgroups
----------------------------------------------------------------
MS-DOS version 6.0 or higher lets you define multiple system
configurations in a single CONFIG.SYS file. When you install Windows for
Workgroups 3.11, If you are running MS-DOS version 6.0 or higher, Setup
checks the CONFIG.SYS file for the [menu] keyword section to determine
whether the CONFIG.SYS file contains multiple configurations. If so,
Windows for Workgroups 3.11 Setup creates a file called CONFIG.WIN in
the Windows directory which contains the entries that need to be present in
the CONFIG.SYS file.
Setup will not automatically change the CONFIG.SYS file in order to
preserve the user's configuration in case it has difficulty interpreting the
user's environment. Once Setup has finished, you can open the
CONFIG.SYS file and the new CONFIG.WIN file that Setup created, and
merge the two together.
NOTE: [Windows for Workgroups] is used in this section to refer to the
configuration block in your CONFIG.SYS file that you use for your
Windows for Workgroups configuration. The exact name of this block may
be different that that used here depending on the name you used for your
configuration.
When using the multiple-configuration capability in MS-DOS 6 (or any other
third-party product that provides similar capabilities), it is important
to note the following information:
The following lines should be in either the [Common] configuration block
or the [Windows for Workgroups] configuration block of the
CONFIG.SYS file so that the Windows for Workgroups 3.11 networking
components will load properly:
device=C:\WINDOWS\HIMEM.SYS
device=C:\WINDOWS\IFSHLP.SYS
Note: If you also have a configuration block in your CONFIG.SYS file for
running Microsoft LAN Manager or Windows for Workgroups 3.1 that you
wish to continue to use after installing Windows for Workgroups 3.11,
place the IFSHLP.SYS device driver line in your Windows for
Workgroups 3.11 configuration block instead of in the [common]
configuration block. If you place IFSHLP.SYS in your [common]
configuration block, it will prevent the network drivers for LAN Manager
or Windows for Workgroups 3.1 from loading properly.
Other device driver lines that can be in either the [Common] configuration
block or the [Windows for Workgroups] configuration block include:
device=C:\WINDOWS\EMM386.EXE
device=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER
If you were previously using Windows for Workgroups 3.1, you can
remove the following device driver lines from the [Windows for
Workgroups] block in your CONFIG.SYS file if they are still present once
Windows for Workgroups 3.11 has been installed.
c:\windows\protman.dos /i:c:\windows
c:\windows\<network card driver>.DOS { for example, EXP16.DOS }
c:\windows\workgrp.sys
If these device driver lines appear in your CONFIG.SYS file more than
once, Windows for Workgroups Setup only removes their first occurrence.
If your [Windows for Workgroups] block is not the first one in your
CONFIG.SYS file, you may need to move them by hand from the
[Windows for Workgroups] block by hand.
Third-party network transports should be moved to the transports= line in
the [network drivers] section of the SYSTEM.INI file.
The CONFIG.SYS and AUTOEXEC.BAT files are no longer used to load
the NDIS network adapter card drivers and network protocol drivers.
Windows for Workgroups 3.11 specifies the network configuration in the
SYSTEM.INI and PROTOCOL.INI files.
If you are using different network adapter card drivers or network
protocols and want to switch between these different configurations, the
SYSTEM.INI and PROTOCOL.INI files must be changed to reflect the
configuration settings. The simplest way to enable a quick change of
configurations is to maintain separate copies of SYSTEM.INI and
PROTOCOL.INI files that reflect the adapters or protocols you need to
support.
Setting Up an XGA Video Adapter on a PS/2(R) Model 75 or 90
-----------------------------------------------------------
If you have a PS/2 model 75 or 90 with an XGA video adapter, Windows for
Workgroups Setup will configure the display adapter for 16-color, 640x480
resolution. Do not change this configuration during Setup. Specifying a
different XGA configuration while setting up Windows for Workgroups may
cause Setup to fail.
After you have successfully installed Windows, you can configure your XGA to
use a different resolution or 256 colors, if your monitor supports it. For
more information on how to do this, see the topic "IBM XGA: Configuring
Color and Resolution" in the README.WRI online document.
If you are using the plasma screen on the PS/2 model 75, use ONLY the
640x480, 16-color configuration. If you change this configuration, you
return to the MS-DOS prompt when you try to start Windows.
Setting up an IBM Token Ring 4/16Mbs Network Card on a Microchannel (MCA) Computer
---------------------------------------------------------------------------
If you have a Microchannel computer, and you are installing Windows for Workgroups
support for the IBM Token Ring 4/16Mbs network card, you must make sure the
Maximum Transmits parameter is set no higher than 1024. If you try to use a higher
value, the network card will not work with your computer.
Correcting the "Out of Environment Space" Error Message
-------------------------------------------------------
If you receive an "out of environment space" message when starting Windows,
you can solve the problem in either of two ways:
* Increase the size of your environment by adding the SHELL= command
line to your CONFIG.SYS file. See your MS-DOS documentation for more
information about the SHELL command and about modifying your CONFIG.SYS
file.
* Move the SET commands in your AUTOEXEC.BAT file to the beginning of
the file so that they run before the commands that load
terminate-and-stay-resident (TSR) programs or drivers, such as
SMARTDrive.
Using Multimedia Extensions Version 1.0 with Windows for Workgroups
-------------------------------------------------------------------
To use the Multimedia Extensions with Windows for Workgroups, first
set up Windows with Multimedia Extensions version 1.0. Then upgrade to
Windows for Workgroups by installing it into the same directory. If
you set up Windows for Workgroups before setting up Multimedia
Extensions, not all the files will be properly installed.
See the README.WRI online document for more information about running
Multimedia Extensions with Windows for Workgroups.
Getting Drivers from the Windows Driver Library (WDL)
============================================================
If you have a modem, you can download Windows Driver Library files from network services, including CompuServe«, GEnieÖ, Microsoft OnLine, or various user-group bulletin boards (such as the bulletin-board services on the Association of PC User Groups network). If you have a modem, you can download Windows Driver Library components from network services, including CompuServe«, GEnieÖ, Microsoft OnLine, or various user-group bulletin boards (such as the bulletin-board services on the Association of PC User Groups network). Files from the Windows Driver Library is also available from Microsoft Download Service (MSDL), which you can reach by calling (206) 936-MSDL (936-6735) any time except between 1:00 A.M. and 2:30 A.M. Pacific time. To use MSDL, use the following communications settings:
Baud rate
1200, 2400, or 9600
Data bits
8
Parity
None
Stop bits
1
People within the United States who do not have a modem can order individual files on disks from the Windows Driver Library by calling Microsoft Product Support Services at (206) 637-7098 or (206) 635-4948 (text telephone).
USING TERMINATE-AND-STAY-RESIDENT (TSR) PROGRAMS AND DRIVERS
WITH WINDOWS FOR WORKGROUPS
============================================================
The "Program Listing" section of this document lists a number of terminate-
and-stay-resident (TSR) programs and drivers that are known to cause
problems when running with Windows for Workgroups. Some of the problems
you may encounter include system failures or incorrect screen displays.
In some cases, we have included solutions or workarounds for the problems.
When you install Windows for Workgroups, Setup searches your AUTOEXEC.BAT
and CONFIG.SYS files for references to TSR programs and drivers and scans
memory for TSRs that are currently running. If Setup detects a TSR that is
known to cause problems when running with Windows for Workgroups, a message
appears asking whether you want to continue or quit Setup.
If you receive such a message, carry out the following procedure:
1. Locate your TSR in the "Program Listing" section of this document.
Determine whether the situation prevents Setup from successfully
installing Windows for Workgroups.
2. If the situation does not affect Setup, continue setting up Windows for
Workgroups by following the instructions on your screen.
If the situation does affect Setup and prevents it from installing
Windows for Workgroups, quit Setup, and then carry out the following
steps.
3. Quit the TSR and remove all references to it from your AUTOEXEC.BAT and
CONFIG.SYS files. For more information, see the documentation for your
TSR.
4. Restart your computer.
5. Run Windows for Workgroups Setup again.
After Windows for Workgroups is successfully set up, you may want to
restore your TSRs.
Setup cannot detect all the TSRs or drivers included in the "Program
Listing" section. The TSRs and drivers that Setup can detect are listed
in the in the [incomptsr1] and [incomptsr2] sections of the SETUP.INF
file.
PROGRAM LISTING
===============
This section describes some problems that you might encounter while using a
TSR with Windows for Workgroups. It does not include all possible problems
that can occur.
386MAX(R)
---------
The documentation for 386MAX recommends against setting the EXT parameter
below 64. If you set this parameter to 0, Setup will fail.
See the README.WRI online document for more information about running 386MAX
with Windows for Workgroups.
386MAX Disk-Cache Utility (QCACHE.EXE)
--------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
instead.
All Charge 386 Version 3.1
--------------------------
ALLEMM4.SYS is a memory manager that causes problems with Setup and Windows
for Workgroups. If you encounter problems running this program with Windows
for Workgroups, it is recommended that you use EMM386.EXE and HIMEM.SYS,
provided with Windows for Workgroups, to manage memory instead.
Anarkey Version 4.00
--------------------
Do not run Windows for Workgroups when Anarkey version 4.00 is running. With
some memory configurations, running Anarkey version 4.00 with Windows for
Workgroups may cause unpredictable system failures. In rare cases, this
program can also corrupt hard-disk data. Also, Windows for Workgroups might
not start when this program is running.
Version 4.01 may correct these problems. Contact Moderne Software for a free
upgrade to Anarkey 4.01.
Anarkey Version 4.01
--------------------
Do not load Anarkey HIGH before starting Windows for Workgroups. If you load
Anarkey HIGH, your system may fail when you try to start an application.
APPEND (MS-DOS)
---------------
Do not use the APPEND utility with Windows for Workgroups. It prevents
Windows and Windows-based applications from creating valid Well-Formed-Path
(WFP) names for the files they are using. (A WFP is the complete name of a
file, including the drive letter and full path specification, starting from
the root directory.)
ASP Integrity Toolkit Version 3.7
---------------------------------
This virus-protection program can cause problems when you are running Windows
for Workgroups Setup, including system failure, automatic restarting of the
system, and keyboard failure. You should turn off protection in the Toolkit
before you set up Windows for Workgroups. For information about how to do
this, see your ASP Integrity documentation.
Autocon Version 2.0e
--------------------
Autocon enables you to select up to 50 different configurations when you
start your system. To do this, it modifies your CONFIG.SYS and AUTOEXEC.BAT
files, based on information in its database (AUTOCON.DAT), when you restart
your system from within Autocon.
Windows for Workgroups Setup modifies only the first section in your
CONFIG.SYS and AUTOEXEC.BAT files. If you want to use specific
configurations with Windows, you must run Autocon and then manually
edit the configurations in the database that you want to use. You
must do this after setting up Windows for Workgroups. For your changes
to take effect, you must restart your system from within Autocon. For
more information, see your Autocon documentation.
Bootcon Version 1.60
--------------------
Bootcon enables you to maintain different system-configuration information
in your CONFIG.SYS and AUTOEXEC.BAT files. You can then select the
configuration you want to use from a menu when you start your system.
Setup modifies the first section in your CONFIG.SYS and AUTOEXEC.BAT
files and may modify certain other sections that contain network drivers
(for example, LAN Manager drivers and NetWare drivers may be deleted). After
you set up Windows for Workgroups, you must edit the sections of those files
that contain other configurations you want to use. For more information, see
your Bootcon documentation.
BOOT.SYS
--------
BOOT.SYS enables you to maintain different system-configuration information
in your CONFIG.SYS and AUTOEXEC.BAT files. You can then select the
configuration you want to use from a menu when you start your system.
Setup modifies the first section in your CONFIG.SYS and AUTOEXEC.BAT
files and may modify certain other sections that contain network drivers
(for example, LAN Manager drivers and NetWare drivers may be deleted). After
you set up Windows for Workgroups, you must edit the sections of those files
that contain other configurations you want to use. For more information, see
your BOOT.SYS documentation.
CACHE.EXE Disk-Cache Utility
----------------------------
Do not use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your CONFIG.SYS
and AUTOEXEC.BAT files. (If CACHE.EXE is detected, Setup removes it from your
CONFIG.SYS file for you.)
CACHE.SYS Disk-Cache Utility
----------------------------
This disk-cache utility will not work properly with SMARTDrive. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If CACHE.SYS is detected, Setup removes
it from your CONFIG.SYS file for you.)
CED Version 1.0e
----------------
Using CED with Windows for Workgroups may cause problems, including
system failure. It is recommended that you do not use CED with Windows for
Workgroups.
Central Point Anti-Virus Version 1.1 (VSAFE.COM/VSAFE.SYS)
----------------------------------------------------------
VSAFE.COM/VSAFE.SYS should not be loaded when you set up Windows for
Workgroups. Otherwise, Setup may not run properly. After you set up
Windows for Workgroups, you can load VSAFE.
If you are upgrading to Windows for Workgroups 3.11, you must also
delete all the CHKLIST.MS files that VSAFE has created before you run Setup.
Because Windows uses the disk for memory swapping, you should turn off the
VSAFE write-protection option when you run Windows for Workgroups.
For more information, see the Central Point Anti-Virus documentation.
CMDEDIT.COM Version 2.0
-----------------------
If this command-line editor is loaded before Windows for Workgroups is
started, it may cause a General Protection Fault when you run multiple
MS-DOS Prompts.
Cubit Version 3.01
------------------
When you are using Cubit with Windows for Workgroups, do not compress the
Windows SYSTEM directory or any file that is loaded from your CONFIG.SYS
file. Compressing these files could cause problems.
Before you upgrade to Windows for Workgroups, make sure that the earlier
version of Windows is uncompressed on your hard disk. You may recompress the
files after you have successfully set up Windows for Workgroups.
Data Physician Plus Version 2.0 (VirALERT)
------------------------------------------
It is recommended that you do not set up Windows for Workgroups while
VirALERT is running. If you do, VirALERT will display a warning message
every few seconds while Setup is running.
After you have set up Windows for Workgroups, you can run VirALERT. Press
ALT+V to display the VirALERT menu. You can use the commands on this menu to
disable and enable VirALERT.
DOSCUE.COM Command-Line Editor
------------------------------
The DOSCUE command-line editor produces unexpected results when used with
Windows for Workgroups. It is recommended that you do not use this editor
with Windows for Workgroups.
Doubledisk Version 2.5
----------------------
Windows for Workgroups may try to access "phantom" disk drives if you use it
with Doubledisk. Phantom drives occur when you use Doubledisk to create a
compressed drive. For example, if you have drives A, B, and C on your
computer and you use Doubledisk to create drive F, Windows for Workgroups
and MS-DOS recognize drives D and E as valid drives, even though they do
not actually exist. You can use the DRVOFF utility to prevent Windows from
recognizing phantom drives. Contact Vertisoft to order a copy of the DRVOFF
utility.
Fastopen (MS-DOS)
-----------------
Fastopen is a RAM-resident utility. Problems involving the file allocation
table (FAT) may occur if Fastopen is used with disk-defragmenting utilities.
In low-memory situations, you may need to remove Fastopen for Windows for
Workgroups to run properly.
Flash Disk-Cache Utility (FLASH.EXE)
------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for
Workgroups, instead.
Graphics (MS-DOS)
-----------------
Loading Graphics from MS-DOS Prompt within Windows can cause unexpected
results when you are printing. The active MS-DOS Prompt will send its
output to the printer. Switching between multiple MS-DOS Prompts may
result in mixed printing jobs.
HPEMM386.SYS and HPEMM486.SYS
-----------------------------
These expanded-memory managers are incompatible with Windows for Workgroups.
It is recommended that you use EMM386.EXE to manage memory instead.
HPMM.SYS - HP Memory Manager
----------------------------
When HPMM.SYS is running, you cannot set up Windows for Workgroups.
You should remove all references to HPMM.SYS from your CONFIG.SYS
and AUTOEXEC.BAT files before setting up Windows for Workgroups.
Hyperdisk Disk-Cache Utility
----------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
instead.
IBM VDISK.SYS (RAM Disk Utility)
--------------------------------
VDISK.SYS is incompatible with Windows for Workgroups because it occupies
extended memory required to run Windows for Workgroups. This utility prevents
any XMS-compatible memory manager from loading.
IEMM.SYS Memory Manager
-----------------------
The IEMM.SYS memory manager is incompatible with Windows for Workgroups. It
is recommended that you remove all references to IEMM.SYS from your
CONFIG.SYS and AUTOEXEC.BAT files and use EMM386.EXE, provided with Windows
for Workgroups, to manage memory instead.
ICACHE.SYS Disk-Cache Utility
-----------------------------
Do not use two disk-cache utilities with Windows for Workgroups.
It is recommended that you use SMARTDrive, provided with Windows for
Workgroups, and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If ICACHE.SYS is detected, Setup
removes it from your CONFIG.SYS file for you.)
IBMCACHE.SYS Disk-Cache Utility
-------------------------------
Do not use two disk-cache utilities with Windows for Workgroups.
It is recommended that you use SMARTDrive, provided with Windows for
Workgroups, and remove all references to other disk-cache utilities from
your CONFIG.SYS and AUTOEXEC.BAT files. (If IBMCACHE.SYS is detected, Setup
removes it from your CONFIG.SYS file for you.)
Intel(R) Expanded-Memory Emulator (ILIM386.SYS)
-----------------------------------------------
The ILIM386.SYS expanded-memory emulator, provided with the Intel
Inboard(TM)/386 product, is incompatible with Windows for Workgroups. It is
recommended that you remove all references to this emulator from your
CONFIG.SYS and AUTOEXEC.BAT files before setting up Windows for Workgroups.
JOIN (MS-DOS)
-------------
Do not add or remove "joined" drives while you are running Windows for
Workgroups. If you use the JOIN command before starting Windows for
Workgroups and do not change the state of the joined drives from MS-DOS
Prompt within Windows, Windows for Workgroups will work properly. It is
recommended that you do not use joined drives at all if you plan to run
Windows.
KEYB.COM (MS-DOS)
-----------------
If you use command-line options to load KEYB.COM, it is recommended that you
load it before starting Windows for Workgroups. After it is loaded, you can
change the keyboard configuration from MS-DOS Prompt within Windows at any
time. If you do not load KEYB.COM before starting Windows, you may encounter
problems when using a KEYB command that includes an option in an MS-DOS
Prompt. However, you can use the KEYB command without options at any time to
display code-page information.
LANSight(TM) Version 2.0
------------------------
LANSight is a utility that you can use to control and monitor other
workstations attached to a Novell network. In some cases, version 2.0 of
LANSight may cause the workstation running Windows for Workgroups to
fail.
Lasertool Control Panel Version 2.2
-----------------------------------
If you load version 2.2 of the Lasertool Control Panel program (PCPANEL.EXE)
from Windows for Workgroups, your system may fail. This program works
properly if you load it before you start Windows for Workgroups.
Le Menu Version 1.0
-------------------
When you are using Le Menu version 1.0 with Windows for Workgroups,
environment information such as PATH, PROMPT, and WINDIR may be lost if you
start MS-DOS Prompt from within Windows. If you want to start Windows for
Workgroups by using a Le Menu menu command, it is recommended that you set
up Windows for Workgroups as a Batch-File menu command so that COMMAND.COM
will load before starting Windows for Workgroups. For more information, see
your Le Menu documentation.
LOCKIT Version 3.3 (PC Vault, Secure It)
----------------------------------------
Version 3.3 of these programs strips out spaces from the load= command line
in the WIN.INI file. Later versions may correct this problem.
Logitech(TM) Mouse Software Version 5.0/6.0 (CLICK, LOGIMENU)
-------------------------------------------------------------
If you want to use CLICK and LOGIMENU from MS-DOS Prompt within Windows, you
must load the TSRs from that MS-DOS Prompt, even if you loaded the TSRs
before starting Windows for Workgroups. When you quit Windows for
Workgroups, you must reload the TSRs for them to work properly from the
command prompt outside of Windows, even if you loaded them from MS-DOS
Prompt within Windows.
Mace Disk-Cache Utility (MCACHE.SYS)
------------------------------------
This disk-cache utility will not work properly with SMARTDrive. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If Mace is detected, Setup removes it
from your CONFIG.SYS file for you.)
Maximizer Memory Manager (MAXIMIZE.COM)
---------------------------------------
If you are using the Maximizer memory manager, you may not be able to set up
or start Windows for Workgroups. Make sure that you are using only one
memory manager with Windows for Workgroups. It is recommended that you use
HIMEM.SYS and EMM386.EXE, which are provided with Windows for Workgroups, to
manage memory instead.
Mirror (MS-DOS)
---------------
If you run Mirror from Windows for Workgroups by using the Run command
or from a command line within an MS-DOS box, it creates an inaccurate
MIRROR.FIL file. You should run Mirror only before you run Windows.
If you run Mirror with the /t option and then start Windows, you cannot
remove it from memory by using the MIRROR /u command until you exit Windows.
This will cause an error message to appear.
NDOSEDIT.COM
------------
You may have problems loading this command-line editor. Also, it may cause
unexpected results when running with Windows for Workgroups.
NetRoom Memory Manager (RM386.SYS)
----------------------------------
With some older versions of NetRoom, you may encounter problems setting up
Windows for Workgroups. In this case, contact Helix Software for the most
current version of NetRoom.
NetWare(R) NetBIOS
------------------
The NetWare NetBIOS TSR is incompatible with Windows for Workgroups in
many configurations. In most cases, Setup will detect NetWare NetBIOS and
remove the startup command from your system. However, if you have NetWare
NetBIOS set up to start from a location other than your AUTOEXEC.BAT file
(for example, from a batch file), Setup cannot detect it. In this case, you
need to remove NetWare NetBIOS manually. Windows for Workgroups 3.11
includes an IPX/SPX compatible protocol that you can use instead of NetBIOS.
For information about configuring Windows for Workgroups to work with it, see the
NETWORKS.WRI online document.
Newspace Version 1.07
---------------------
This disk-compression utility is incompatible with Windows for Workgroups
and may cause several problems.
Norton Anti-Virus(R) Version 1.0
--------------------------------
If you load version 1.0 of Anti-Virus before you set up Windows for
Workgroups, Setup may fail. It is recommended that you contact Symantec for
the most current version of this program.
Norton Desktop for Windows (EP.EXE)
-----------------------------------
If the data-recovery program Erase Protect (EP.EXE) is loaded from your
AUTOEXEC.BAT file, you need to disable it when you are setting up Windows
for Workgroups, especially if you are upgrading over a previous version of
Windows. Erase Protect tries to save copies of all deleted files, which can
cause you to run out of disk space while running Setup.
It is recommended that you run Erase Protect with a permanent swap file.
If you are using a temporary swap file, you need to exclude files that have
a .TMP or .SWP extension from erase protection.
Norton Utilities(R) Version 5.0 (DISKREET, NCACHE)
--------------------------------------------------
This program is incompatible with Windows for Workgroups and may cause your
system to fail. It is recommended that you upgrade to the most recent
version of Norton Utilities to correct problems.
Norton Utilities Version. 6.01 (NCACHE)
---------------------------------------
Some versions of NCACHE may prevent you from setting up or starting Windows
for Workgroups. This is more likely to happen if NCACHE is set up as an EMS
cache. Setting up NCACHE as an XMS cache instead may solve the problem.
You may also encounter additional problems using NCACHE. New versions may
correct these problems. For an updated version of NCACHE, contact Symantec
Corporation. In the meantime, you can use SMARTDrive, which is provided with
Windows for Workgroups.
Norton Utilities Version 6.01 (DISKMON)
---------------------------------------
It is recommended that you do not use DISKMON version 6.01 with Windows for
Workgroups.
PCED Version 2.00
-----------------
Do not load the PCED command-line editor HIGH. Loading it HIGH may cause
unexpected results, such as system failures, when Windows for Workgroups is
running.
PCKEY.EXE (MultiSoft Keyboard Enhancer and Command-Line Stack)
--------------------------------------------------------------
PCKEY.EXE may not work properly with Windows for Workgroups when you are
running more than one MS-DOS--based application at a time. It is recommended
that you unload PCKEY.EXE before starting Windows for Workgroups.
PC-Kwik Disk Accelerator
------------------------
If you use PC-Kwik with Windows for Workgroups, make sure that you are
using version 3.55 or later and that PC-Kwik is in extended memory, not
expanded memory. To get an upgraded version of PC-Kwik, contact MultiSoft.
PC-Kwik Disk-Cache Utility (PC-KWIK.EXE)
----------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows for Workgroups. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
instead.
PC-Kwik Version. 1.59 (PCK.EXE, PSKSCRN.EXE, PCKEY.COM)
-------------------------------------------------------
If version 1.59 of PC-KWIK is loaded before setting up Windows for
Workgroups, Setup may fail. PC-KWIK Version 2.0 may correct this problem.
PCSXMAEM.SYS Utility
--------------------
This utility is incompatible with Windows for Workgroups. You should remove
all references to it from your CONFIG.SYS and AUTOEXEC.BAT files before
setting up or starting Windows for Workgroups. PCSXMAEM.SYS is similar
to XMAEM.SYS. It has been renamed and slightly modified. It is provided with
current versions of the IBM PC/3270 emulator.
PCSX2EMS.SYS
------------
Windows for Workgroups will run correctly with PCSX2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this program is
incompatible with Windows for Workgroups. PCSX2EMS.SYS is provided with the
IBM PC/3270 emulator.
PC Tools Deluxe(TM) Version 7.1 (DATAMON)
-----------------------------------------
If you load PC Tools DATAMON using the \SENTRY+ option, Setup may fail if
you are low on disk space. Do not use the \SENTRY+ option when loading
DATAMON.
Do not load DATAMON after loading SMARTDrive. If DATAMON is loaded after
SMARTDrive, your system may fail. See the PC Tools documentation for
information about how to unload DATAMON.
PC Tools Deluxe Version 6.0 (DESKTOP)
-------------------------------------
If you try to start PC Tools from a MS-DOS Prompt within Windows for
Workgroups, your system may fail or restart itself. These problems also
occur if you use MS-DOS commands from a MS-DOS Prompt within Windows.
Version 7.0 of PC Tools may correct these problems. However, do not load
DESKTOP from a MS-DOS Prompt if it was loaded before starting Windows for
Workgroups. If you do, your system may fail when you quit Windows for
Workgroups. It is recommended that you run DESKTOP from its PIF, provided
with Windows for Workgroups.
PC Tools Deluxe Version 7.1 (VDEFEND)
-------------------------------------
Setup may not work properly if VDEFEND is loaded before running Setup. You
may load VDEFEND after setting up Windows for Workgroups.
PC Tools(TM) Disk-Cache Utility (PC-CACHE.COM)
----------------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows. It is recommended
that you use SMARTDrive, provided with Windows for Workgroups, instead.
PRINT (MS-DOS)
--------------
If you are printing several large documents on a network printer and run
Setup from the network, your system may fail while Setup is creating Program
Manager groups.
PYRO! Version 1.0
-----------------
If this screen saver is loaded before starting Windows for Workgroups,
you may not be able to restore the Windows for Workgroups screen after
this screen saver appears.
QMAPS Memory Manager Version 5.16
---------------------------------
If you are using the QMAPS memory manager, you may not be able to set up or
start Windows for Workgroups. New versions may correct these problems. For
an updated version of QMAPS, contact Quadtel. In the meantime, you can use
HIMEM.SYS and EMM386.EXE, provided with Windows for Workgroups, to manage
memory instead.
RAMTYPE.SYS - AST RAMpage!(R) Boards
------------------------------------
The RAMTYPE.SYS driver is incompatible with Windows for Workgroups. It is
recommended that you remove this driver before setting up Windows for
Workgroups. If you load the driver from your CONFIG.SYS file, comment
out the command line for the driver as follows:
rem RAMTYPE.SYS
Windows for Workgroups will run correctly without RAMTYPE.SYS. However,
other drivers that rely on RAMTYPE.SYS will not load and applications will
not be able to use the expanded memory on your system.
After you set up Windows for Workgroups, you can use version 1.2 and later
of RAMTYPE.SYS with Windows for Workgroups. If you are using an earlier
version on an IBM PS/2 or Micro Channel Architecture computer and your
RAMpage! board is configured for expanded and extended memory, you need to
upgrade your AST RAMTYPE.SYS driver after you set up Windows for Workgroups.
You will also need to remove the "rem" command from your CONFIG.SYS file so
that RAMTYPE.SYS will load properly.
Secretdisk II Disk-Cache Utility (FAST512.SYS)
----------------------------------------------
This disk-cache utility will not work properly with SMARTDrive. It is
recommended that you use SMARTDrive, provided with Windows for Workgroups,
and remove all references to other disk-cache utilities from your
CONFIG.SYS and AUTOEXEC.BAT files. (If this utility is detected, Setup
removes it from your CONFIG.SYS file for you).
SideKick(R) Versions 1.0 and 2.0 and SideKick Plus
--------------------------------------------------
Miscellaneous problems may occur when you run SideKick as a TSR with Windows
for Workgroups. It is recommended that you use a PIF to run SideKick as
an MS-DOS--based application instead of loading it as a TSR.
SoftIce Debugger
----------------
If SoftIce is loaded, Setup will fail when starting the Windows portion of
the program. It is recommended that you unload SoftIce before you set up
Windows for Workgroups.
SpeedFXR
--------
This program is incompatible with Windows for Workgroups when running as
a TSR. It tries to increase the speed of the floppy disk drives, but slows
them instead. To get the best results, use the -X option when loading
SpeedFXR. This will prevent SpeedFXR from remaining in memory and affecting
the speed of the floppy disk drives.
SUBST (MS-DOS)
--------------
Do not add or remove "substituted" drives while you are running Windows for
Workgroups. If you use the SUBST command before starting Windows for
Workgroups and do not change the state of the substituted drives from an
MS-DOS Prompt within Windows, Windows for Workgroups will work properly.
Super PC-Kwik Disk-Cache Utility (SUPERPCK.EXE)
-----------------------------------------------
Do not use this disk-cache utility simultaneously with SMARTDrive. There is
no reason to use two disk-cache utilities with Windows. It is recommended
that you use SMARTDrive, provided with Windows for Workgroups, instead.
Trantor T100 Host Adapter Driver (TSCSI.SYS)
--------------------------------------------
(For SCSI hard disk drives) - If you use the Trantor T100 driver
(TSCSI.SYS), you must use version 4.33d or higher. Earlier versions identify
the SCSI hard disk drive as a removable drive. This may cause problems when
you are using File Manager--for example, your system could fail while you
format a drive, or you could get unexpected results when you delete files.
To get an updated driver, contact Trantor Systems, Ltd.
UMB PRO Version 1.07
--------------------
If you are running UMB PRO, you may experience problems running Windows for
Workgroups. In some cases, your system may fail. Make sure that you are
using only one memory manager with Windows for Workgroups. It is recommended
that you use HIMEM.SYS and EMM386.EXE, which are provided with Windows for
Workgroups, to manage memory instead.
Vaccine
-------
If Vaccine is loaded, Setup fails when trying to modify your CONFIG.SYS and
AUTOEXEC.BAT files. You should unload Vaccine before you set up Windows for
Workgroups. You may also encounter problems, such as beeping, while
running Windows for Workgroups when Vaccine is loaded.
VIREX-PC Version 1.11
---------------------
If VIREXPC.COM is loaded, Setup and Windows for Workgroups will fail
when KRNL386.EXE performs a write operation. Also, the first time Windows
for Workgroups is loaded, you may be returned to the MS-DOS prompt.
Virus Prevention Plus Version 5.0
---------------------------------
If Virus Prevention Plus is loaded, you may not be able to set up Windows
for Workgroups successfully. You may also encounter problems when you run
Windows for Workgroups. The Keyboard Lock program may cause Windows for
Workgroups to fail.
Virusafe Version 4.0
--------------------
If this program is loaded as a TSR, Setup may fail while you are setting
up Windows for Workgroups. It is recommended that you load Virusafe by using
the /C- option. This option turns off the memory-change detection provided
with Virusafe. Version 4.5 may correct this problem. For more information,
see your Virusafe documentation.
XMAEM.SYS
---------
XMAEM.SYS is a device that causes extended memory to act like XMA. This
utility is incompatible with Windows for Workgroups. It is recommended
that you remove all references to it from your CONFIG.SYS and AUTOEXEC.BAT
files before you set up or run Windows for Workgroups. XMAEM.SYS is
provided with IBM DOS version 4.0.
XMA2EMS.SYS
-----------
Windows for Workgroups will run correctly with XMA2EMS.SYS if it is loaded
on a computer that has an XMA board installed. Otherwise, this program is
incompatible with Windows for Workgroups. XMA2EMS.SYS is provided with IBM
DOS version 4.0.
************ SETUP.TXT ************
Thank you for purchasing Microsoft Windows NT. To
give you the greatest possible benefit from this product,
we've included this detailed set of notes on Windows NT.
We hope you enjoy using this operating system.
Feedback from the thousands of Windows NT beta sites
has shown that Windows NT Setup proceeds smoothly in
the vast majority of cases. However, there are cases where
you may experience difficulties with hardware incompatibilities
or conflicts. SETUP.TXT contains information that you
may need in order to install Windows NT or Windows NT
Advanced Server on some hardware configurations.
Information applies to both Windows NT and Windows
NT Advanced Server.
For more information on installation, see the chapters "Installing
Windows NT" and "Troubleshooting" in the Windows NT System Guide or
Windows NT Advanced Server System Guide.
1.0 Removing Previous Versions
If you have installed a pre-release version of Windows NT, you should
delete it before installing this version. Depending on the release, the
Windows NT Boot Loader may not support booting both this release of the
operating system and a previous release.
2.0 General Hardware Notes
Windows NT has a very wide range of hardware support -- including
support for over 1600 x86 uniprocessor systems, over 25 x86
multiprocessor systems, as well as supporting RISC systems (for
details please see the Hardware Compatibility List). To cover a
few outlying cases, we've included these notes.
2.1 Interrupt Conflicts
A common problem in a computer with several supported devices is
conflicting interrupts, I/O ports, or memory usage. Where possible, we
have identified such cases in this document. However, if one of the
supported devices does not seem to work, it may be due to the
particular hardware configuration. For more specific information,
see your hardware manual or contact your system manufacturer.
2.2 ROM Shadowing
If you encounter persistent installation problems on multiprocessor
systems, try installing with ROM shadowing disabled.
2.3 Intel EtherExpress 16 LAN Adapter
In some cases, selecting "early" in the I/O Channel Ready box
can stop the network adapter card from functioning correctly and
may require reconfiguring with the Intel SoftSet utility. If you are
unsure whether your system can take advantage of this network
setting, consult your hardware vendor.
3.0 Specific Computer Systems
3.1 ACER AcerFrame 3000 MP
Before installing Windows NT, disable shadow RAM Video BIOS.
3.2 IBM Personal System/2
On some IBM PS/2 systems only planar memory is recognized when
booting from the Windows NT CD-ROM boot disk or Disk #1 of the
floppy disk installation set. This is a memory card problem. You may
encounter this problem if your system contains a card with the
following part numbers:
FRU-88F0075
Option 87F9856 or 87F9860
Newer model cards are available that correct this problem. Part numbers
for the newer cards are:
FRU-87F9916 or 34F2825
Option 34F3077 or 34F3011
Using Kingston expansion memory can also correct this problem.
It is recommended that before you install Windows NT, you update your
system configuration using the PS/2 Reference Diskette version 1.21 or
later
3.3 Installation on the IBM ThinkPad
The IBM ThinkPad 700c and 720c portables require an ABIOS patch to
install and run Windows NT. Copy the following files from the ThinkPad
Reference Diskette onto C:\
ABIOS.SYS
SF*.BIO
3.4 Olivetti LSX5030
For the Olivetti LSX5030, disable all ROM shadowing.
3.5 Toshiba T4400SX Monochrome
The Toshiba T4400SX display is not supported when an
external monitor is connected.
3.6 Gateway Nomad and TI Travelmate Notebooks
To successfully install Windows NT on these machines, you
must choose "Custom Setup". If you encounter problems
running setup while scanning for SCSI Adapters, you can
delete the SCSI drivers from the setup diskette to solve
the problem.
To properly use the floppy drive with Windows NT, configure
the system using its setup utility. Set the Advanced Operating
System option to Auto. When power management drivers for
these machines are available from Texas Instruments, using
the Auto option will not be necessary.
The built in InPort/QuickPort mouse adapter requires a mouse
driver from Texas Instruments to work properly under Windows NT.
You can use a serial mouse until this driver is available from
Texas Instruments.
In order to use the internal modem for these computers, you will
need a power management driver and software from Texas Instruments.
The best configuration for the NE2000 Network Adapter under
Windows NT is at IRQ5 and I/O Port 340H.
3.7 Gateway 2000 and Micronics Gemini 486 VESA Local Bus
Motherboards
Windows NT may stop running on systems that use Ultrastor's U34F Local
Bus controller with the Micronics Gemini 486 VESA Local Bus motherboard.
Some older Gateway systems include this combination of hardware.
The problem is a timing issue that only appears with Windows NT, the
Ultrastor U34F, and the Micronics Gemini 486 VESA Local Bus
motherboard. Disabling the motherboard's external cache should allow
Windows NT to run. The problem does not occur with ISA bus controllers
from Ultrastor. This problem does not occur on Gateway 2000 or Micronics
VESA Local Bus motherboards with a blue OverDrive socket.
If you encounter this problem, you can resolve it by an upgrade offered by
Micronics for the Gemini 486 VESA Local Bus motherboard. The
motherboard will need to be returned to Micronics for an upgrade. The
Micronics reference number for this is VLBA03. Micronics can be reached at
510-651-2300 for additional information. If you have a Gateway computer,
contact Gateway 2000 at 800-846-2301 for upgrade information.
3.8 Zeos Freestyle/SL Notebook Computer
When performing a Windows NT installation on this computer, you
must power off the computer after the text-based portion of Setup is
complete and you have been prompted to press CTRL+ALT+DEL to
restart the computer. Otherwise a keyboard controller failure may occur.
4.0 General Disk Drive Information
4.1 Volume Sets Created Via the BIOS
On controllers other than the UltraStor 124f, Windows NT does not
support disk controllers that create volume sets via the BIOS
(i.e. two different drives merged into a single drive letter).
4.2 Caching Disk Controllers and Drives
Windows NT supports caching disk controllers and drives only if one of
the following is true:
- The controller has a driver that specifically supports caching
(several of these exist: DPT and IBM SCSI Caching Adapter).
- Write-through is active (i.e. write caching is disabled) either by
setting it manually or by default when the computer starts.
- The entire cache option is off, either by setting it manually or by
default when the computer starts.
Using a caching controller or drive in other situations risks loss of
data if the computer is rebooted or a power failure occurs before the
cache has flushed itself. You can minimize risk by waiting at least 1
minute (less if you know the maximum time the cache waits before
flushing itself) after all system activity stops before rebooting.
The disk activity light is a good indicator of how write caching is
being done on your system. This applies to the initial Windows NT
installation as well as shutdown. Note that unexpected power failure
at any time can potentially corrupt data on the disk, possibly to the
extent that the disk becomes unreadable. Making the delay time that
write data is cached before being flushed to disk as small as
possible reduces this risk.
4.3 IDE/ESDI Drive Support
The Windows NT IDE/ESDI drive support is limited to two
disk drives per controller. A second IDE/ESDI controller from
Compaq (on Compaq machines only) or built in like the
Gateway 2000 VESA local bus machines is supported by the
standard Windows NT product. If you have a need to
configure from 2 to 6 IDE or ESDI controllers in one
system, contact MS Product Support Services for details on
how to do so.
4.4 Installing onto Systems with an ESDI Drive Containing More
Than 1024 Cylinders
In some cases, Windows NT installation proceeds normally until the
first boot from the hard drive where Windows NT is installed. The
Windows NT Boot loader will load various files and then produce a
Fatal System Error: 0x0000006b with the message that Phase 1 Process
Initialization failed. Following this message will be some type of
hex dump and the system will be locked up. If you experience this
difficulty the following information can help.
Testing has been done on the following ESDI controllers using a hard
drive with a capacity exceeding 516 MB (MB=1,048,576 bytes) formatted.
The MS-DOS limit of 1024 cylinders creates a situation where special
BIOS mapping on the controller is used to change the geometry of the
drive. ESDI drives are capable of being prepared with various values
of "sectors per track" (spt) such as 53 or 63 spt geometry during a
low-level format. Here is a brief example of a drive capacity using a
different spt format.
1024 cylinders X 15 heads X 53 spt X 512 bytes per sector =
398MB formatted capacity
or
1024 cylinders X 15 heads X 63 spt X 512 bytes per sector =
472MB formatted capacity
Thus using 63 spt will yield 74MB more space. Windows NT is perfectly
compatible with either geometry, and depending on the drive/controller
can access the remaining cylinders beyond 1024. This space can be
partitioned and formatted but not accessed by MS-DOS as the boot OS.
However, some controllers can successfully remap the remaining
cylinders beyond 1024 so that either MS-DOS or Windows NT can use the
entire capacity. An example would be:
1632 cylinders X 15 heads X 53 spt X 512 bytes per sector =
634MB formatted capacity
Testing has been done on the following ESDI controllers with their
Windows NT compatibility results:
DTC (Data Technology Corp)
Model 6282-24:
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. Windows NT will be able to access
the cylinders beyond 1024. Do not low-level the drive using Head
Mapping Mode.
Model 6290-24:
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. Since this card does not have an
onboard BIOS, Windows NT cannot access the remaining cylinders
beyond 1024.
Model 6290 SEZ (Dual SCSI/ESDI Controller):
Maximum Windows NT compatible geometry is using BIOS translation
in the EISA configuration using 63 spt and limit of 1024
cylinders under MS-DOS. Windows NT can access the remaining
cylinders beyond 1024.
Model 6295-24:
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. This model does have an onboard BIOS
so Windows NT can access the remaining cylinders beyond 1024. Do
not low-level the drive using Head Mapping Mode.
Adaptec
Model 2322D:
Several methods that can achieve maximum drive capacity are as
follows:
1. Disable drive translation and the on-board controller bios.
Then use a user defined drive type with the actual drive
parameters. For example:
Drive Type in CMOS=48 Cylinders=1632 Heads=15 SPT=53
This will give 634MB capacity. MS-DOS will still be limited to
the first 1024 cylinders which makes 398MB available. Windows
NT will be able to access the cylinders beyond 1024 yielding
another 236MB.
2. This option allows both MS-DOS & Windows NT to access the entire
drive. Jumper the controller for Drive Splitting. Disable
drive translation and the on-board controller BIOS. Set up
the first physical drive in the CMOS as:
Cylinders=1024 Heads=15 SPT=53
which will give a drive capacity of 398MB. Set up the second
drive (it appears as a physical drive) in the CMOS as:
Cylinders=606 Heads=15 SPT=53
This will yield another 236MB. Windows NT will actually see
the drive as two physical drives.
UltraStor
All models with PROM versions less than #####-009
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. Windows NT will be able to access
the cylinders beyond 1024.
All models with PROM versions equal to or greater than #####-009
Maximum Windows NT compatible geometry is to use "Track mapping"
during Low-Level formatting. Both MS-DOS and Windows NT will have
access to entire drive capacity.
5.0 SCSI Devices
Windows NT supports over 60 SCSI host adapters, over 30 SCSI CD-ROM
drives, over 40 SCSI tape drives, over 10 SCSI removable media systems,
and SCSI scanners. Here are some detailed notes on Windows NT's SCSI
support.
This section provides information on configuring SCSI devices when
running Windows NT.
5.1 SCSI CD-ROM Devices
The SCSI and CD-ROM support built into Windows NT 3.1 requires that
CD-ROMs provide SCSI parity to function properly. For many drives
this is a configurable option or is active by default. Check the
documentation for your CD-ROM to find specifics on how this is
configured for your drive. Examples of drives which do not provide
or support SCSI parity are the NEC CDR-36 and CDR-37 drives.
5.2 Installing from a SCSI CD-ROM Device
When you are installing Windows NT from a SCSI CD-ROM device, make
sure that the device does not have an ID of 0 or 1. Some SCSI BIOS
programs reserve 0 and 1 for hard disks. If you set your CD-ROM with
an ID of 0 or 1, you will likely see an extra partition in Setup that
does not exist.
If you have 2 CD-ROM devices connected to the same SCSI Host Adapter,
then Windows NT Setup does not necessarily install using the CD-ROM that
contains the higher SCSI ID. If using one CD-ROM results in Setup
displaying a message "Please insert the CD-ROM into the CD-ROM drive,"
then remove the CD and try the other CD-ROM. Setup chooses one CD-
ROM drive and refers to it as 'the' CD-ROM drive.
5.3 Installing Windows NT with a Proprietary Adapter Driver
Some SCSI and proprietary CD-ROM adapter drivers are provided in the
Driver Library on the Windows NT CD. These drivers are contained in
a directory tree below the \DRVLIB directory. Some of the drivers will
have a readme.txt containing additional configuration information.
Please read this information before installing.
To install using one of these drivers:
1. Using your current operating system, access the Windows NT CD-ROM,
and change to the directory containing the driver that you want to use.
2. Copy all files in that directory to a blank, formatted floppy
placed in drive A: (Windows NT Setup requires the driver to be on
a disk in drive A). Label the disk "Driver Disk"
3. Shut down your current operating system (if necessary), and reboot
with the Windows NT CD-ROM Boot disk in drive A.
4. When Setup asks for Custom or Express setup, choose Custom.
5. When choosing an adapter press 'S' for additional SCSI adapters.
6. Choose "Other (requires disk provided by hardware manufacturer)."
7. Setup prompts for the driver disk. Insert the "Driver Disk" in
drive A.
5.4 Installing with Unsupported CD-ROM Drives
Please refer to the chapter "Installing Windows NT" in the Windows NT
System Guide or Windows NT Advanced Server System Guide for
information on installing Windows NT from MS-DOS when your system
has an unsupported CD-ROM drive.
5.5 Adding a CD-ROM After Installing Windows NT
If you add a CD-ROM drive after you have installed Windows NT, use the
Devices option in Control Panel to configure device startup. For all
CD-ROM drives, set the Startup value of Scsicdrm to System. If your
drive does not support SCSI-2 Audio, also set the Startup value of
Cdaudio to System. Cdaudio should also be set to System for some SCSI-1
CD-ROM drives, including the Denon DRD-253; Pioneer-DRM-600; NEC
Intersect 73, 73m, 74, 84; and Hitachi 1750s, 1650s, 3650.
For more information on starting devices, choose the Help button in the
Devices dialog box.
5.6 NEC Intersect CD-ROM
NEC Intersect CD-ROM readers have a switch that enables 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. To avoid this problem, set
switch number 5 ON. The switch is located with switches labeled SW1.
5.7 SCSI Termination
The SCSI bus must be properly terminated on both ends. If you are
using both an external and an internal SCSI device, it is best to
terminate the devices and remove the terminators on the SCSI adapter.
For the SCSI adapter to operate effectively, termination power must be
provided on the SCSI bus either by the adapter or by a SCSI device
connected to the bus. Some adapters provide termination power with
no configuration options. Others do not provide termination power
(for example, Future Domain 1660 and Trantor 128 and 130B). Still
others provide termination power only if a jumper is set on the
adapter (for example, Future Domain 850M).
Please consult the documentation for your SCSI adapter and SCSI
device to make sure that termination power is present on the SCSI bus.
5.8 Adaptec
An Adaptec adapter might use conflicting memory addresses with other
cards such as network adapters. This requires reconfiguring the
hardware by changing jumpers.
DMA speed cannot be set on an Adaptec 154x SCSI controller. Currently
the AHA154X.SYS driver supports a DMA transfer rate of 5.0 MB.
The Adaptec AHA154xC card is extremely sensitive to termination and
cabling. Systems with this card should use SCSI-II cables and/or
SCSI-II active terminators. SCSI-II cables are available from
Amphenol Quintec and Icontec. If these recommendations are not
followed, unreliable operation, including data corruption, is possible.
The Adaptec AHA-1542C and Denon DRD-253 are incompatible under Windows
NT. The AHA-1542C requires active termination and the Denon DRD-253
CD-ROM has built in passive termination.
The Adaptec 1640 Micro Channel adapter does not support the Maynard
2000 or 1300 DAT drives in this release. The 1640 adapter is not
supported on IBM PS/2 Model 70 computers.
There is a known problem using Micronics VL bus motherboards with
Adaptec 1542x adapters.
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
Technical Support at (408) 945-2550 for information on the most recent
version, 3.20, of the BIOS. BIOS versions after 3.08 do not have this
problem. The latest 154x BIOS also supports drives that are larger
than 1 GB under both BIOS/MS-DOS and Windows NT. Windows NT will be
able to access drives larger than 1 GB even without this upgrade
provided and extended partition is used.
The Adaptec AHA164x driver logs unnecessary errors. These occur while
NTBACKUP is in use with a tape connected to the AHA164x. The entries
look like:
7/10/93 2:41:40 AM AHA154x Error None 11 N/A
[MachineName] The driver detected a controller error on \Device\ScsiPort1.
These entries may be ignored. Also when too many of these entries are
generated a pop-up is created indicating the error log is full. This
can be avoided by setting the system event log settings to overwrite
the events as needed.
5.9 Buslogic
When using a Buslogic 747 SCSI Adapter with an AST Manhattan SMP
computer, you must disable the adapter's BIOS. For more information
on disabling the BIOS, refer to the adapter's documentation.
5.10 Compaq Smart SCSI Array
The Compaq Smart SCSI Array must be configured to use any possible
interrupt other than IRQ 2 to function properly under Windows NT.
5.11 Dell Drive Array
The Adaptec emulation mode on the Dell Drive Array (DDA) must
be disabled for compatibility with the hardware's Windows NT driver.
5.12 Future Domain
The Windows NT driver that supports the Future Domain 845, 850, and
885 adapters assumes operation on IRQ 5. If the adapter is set for
another interrupt, the Future Domain driver will continue to work,
but in a polling fashion that may slow down operation of the system.
Further, the Future Domain driver will register to the system claiming
the use of IRQ 5 and this may disrupt operation of another device
that is actually configured for IRQ 5. If you are using one of the
above mentioned Future Domain adapters, please complete the Windows
NT installation normally, then change the IRQ information for the
driver in the registry. If the IRQ is incorrect, the driver will
log an event viewable in the Event Viewer Administrative Tool.
If you have a 16-bit Future Domain card or an 8-bit M series card
configured with an external SCSI device, make sure that SCSI
termination is correct. You must set a jumper on the card for this
setting. Check the cards documentation for details.
A Future Domain SCSI adapter might use conflicting memory addresses.
This requires reconfiguring the hardware by changing jumpers.
5.13 IBM PS/2 SCSI Adapter
To configure an IBM SCSI adapter with a BIOS dated before 1991 for use
with Windows NT, use a PS/2 Reference Diskette version 1.21 or later.
5.14 Maynard SCSI Adapter
You cannot use Express Setup to install Windows NT onto a hard disk
attached to a WD33C9C SCSI host adapter (Maynard SCSI adapter) because
Setup cannot identify this adapter. However, you can use Custom Setup
to install this adapter card. Or, after Setup, you can use the Setup
icon to install the adapter card.
5.15 Mylex DCE376 and Tangent 48933 USA
The Tangent and Zeos 433 EISA system comes standard with a Mylex 376
controller which operates in WD1003 emulation mode by default. This
will be no longer be necessary when a SCSI driver for this card becomes
available for Windows NT.
5.16 UltraStor SCSI Controllers
If you experience a problem in tape functionally with a supported 4mm
DAT Tape Device and an UltraStor 14F or 24F controller, contact
UltraStor for an upgrade to resolve this.
If you have an UltraStor 34F controller installed into a Micronics VLB
motherboard, it is recommended that you turn the motherboard external
cache off.
The UltraStor 124 adapter is compatible with removable media drives,
but does not allow the user to remove and replace media. For this reason,
Windows NT does not support removable media drives when used with this
controller.
The combination of the UltraStor 14F and DEC Talk Speech Synthesizer
Card can cause Windows NT Setup to fail due to an I/O port conflict.
To avoid this problem, either set the DEC I/O to 350, or delete the
file ULTRA14F.SYS from the boot floppy while leaving the DEC card at
default settings.
5.17 Trantor
These adapters are SCSI-termination sensitive. If Windows
NT hangs upon booting, or if Windows NT Setup cannot find devices
attached to a Trantor adapter, verify that the SCSI termination
occurred and that one of the SCSI devices attached to the Trantor
adapter is providing termination power.
The Trantor T228 MCA SCSI adapter is not supported on the IBM PS/2
Model 95.
5.18 Texel DM-5024 CD-ROM
A firmware level of 1.10C is required to make the DM-5024 CD-ROM
compatible with Windows NT. Contact Texel at 1-800-886-3935 for
information on this upgrade.
6.0 Error Messages
6.1 Couldn't Find NTLDR
This message is displayed if the file NTLDR is missing from the root
of the C: drive. You can copy the file to C:\ from either the CD ROM
or floppy disks.
To copy NTLDR from the CD ROM, make the CD ROM your current drive and
enter the command:
copy \i386\ntldr C:\
To copy NTLDR from floppy disk, insert Disk 2 in your disk drive and
make that drive the current drive. Then enter the command:
expand ntldr.$ c:\ntldr
6.2 Error 0000001E
Generally, this error implies a problem in the file system. Run CHKDSK
or another similar utility on the drive. Make sure your hardware is on
the hardware compatibility list.
6.3 Error 0x00000069 or 0x00000067
This initialization error indicates that Windows NT is unable to
communicate with the hard drive controller. Try the following:
- 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.
- Make sure there are no missing Windows NT system files.
6.4 NMI Hardware Error
This error is caused by a hardware problem. In some cases, the
computer's memory can be at fault, leading to an error that does
not appear when running MS-DOS or Windows 3.x, but does appear when
running Windows NT. Memory errors can occur when the access rate does
not match the requirements of the system board or when the access
rate varies between SIMM modules or chips on a module. Cache memory
access rates that are too slow can also cause this problem. In general,
the first steps toward troubleshooting are to make sure that contacts
for all boards and memory modules are clean, that boards and memory
modules are properly seated, and that the computer is free of dust.
6.5 System Error F002
If you receive a System Error F002, this probably means that your
hardware is faulty; for example, you may be experiencing a memory
failure. If this occurs, run the manufacturer's diagnostics procedure
and check to see if your memory is the proper speed for your CPU.
7.0 Video Display Drivers and Adapters (x86 Computers)
Windows NT has excellent video support, supporting over 45 video
display adapters, including excellent high-end support. Here are
some detailed notes on Windows NT's video support.
The information in this section is applicable for x86 computers only.
To select a video adapter other than VGA, you must run Custom Setup
or run Windows NT Setup from the Main program group after you have
completed installation.
This release supports the VGA standard video cards plus some newer
video cards. If the video card you use is not listed in this section,
select VGA as the display device in Windows NT Setup. If you choose a
display mode in Setup that your hardware does not support, you will
need to reinstall Windows NT. You should be careful when installing
some of the higher resolution modes to be sure that your monitor
supports the resolution and vertical refresh rates.
If the display mode selected by the user is not valid -- because the
video card was not present or because the card had insufficient video
memory -- an alternate driver will be selected by Setup automatically
so that the computer is able to boot.
If you encounter problems read your video manual again for proper settings.
You may have overlooked something in the manual that pertains to Windows
NT if you previously installed the card under Windows 3.1.
In general, Windows NT video drivers do not use interrupts. Many VGA
cards use jumpers to enable IRQ 2 interrupt for EGA compatibility. When
possible, you should disable the IRQ 2 interrupt.
During setup Windows NT may allow you to set the vertical refresh rate for
your card. Read your monitor manual to see what settings you can use. If you
are unsure, set up at the lower resolution, and then later try higher resolutions.
If after changing these settings and rebooting, you find that your display is not
operating correctly, reboot again and use the "last known good" feature to
restore your previous video settings. Be aware of the fact that some monitors
may be physically damaged by wrong video settings.
Minimum video memory requirements for Windows NT:
640x480x16 colors 512K
640x480x256 colors 512K
800x600x16 colors 512K
800x600x256 colors 1M
1024x768x16 colors 512K
1024x768x256 colors 1M
1280x1024x256 colors See individual driver requirements
7.1 VGA
If you experience a problem with the standard VGA driver, try the
alternative VGA driver that programs the VGA directly. The standard
VGA driver uses the VGA display adapter's BIOS to initialize the card.
To use the alternate driver, rename the standard driver VGA.SYS to
VGA.SAV. Then copy VGA_ALT.SYS to VGA.SYS and reboot.
7.2 8514/A and Compatible Cards
When installing Windows NT on a computer that has an 8514/A or
compatible graphic card (for example, IBM's 8514/A or ATI's 8514Ultra),
and the computer has an older version of BIOS, Custom Setup may display
your video card as "Unknown."
You can change the video driver from "Unknown" to the Standard VGA
(640x480, 16 colors) driver during Windows NT Setup. If you have an ATI
8514 Ultra graphic card, after Windows NT Setup is completed, you can run
Windows NT Setup located in the Main group in Program Manager to select
the appropriate ATI video driver. Express Setup will default the video
driver to the Standard VGA (640x480, 16 colors) when an unknown video
card is detected.
There is no other video driver for 8514/A or compatible graphic cards
included in this release of Windows NT.
7.3 Cirrus-based Cards
For boards based on the Cirrus Logic chip set, select Cirrus with the
appropriate resolution during Setup.
7.4 VESA VGA
The VESA VGA driver uses the newer standard for detecting if a card
can handle the 800x600 Super VGA mode. VESA VGA is not supported, if
you have a card that uses the old standard, or a card that required an MS-
DOS-based TSR to implement Super VGA functionality. Standard VGA
mode is supported instead.
7.5 Diamond SpeedSTAR (and any ET4000 SVGA)
For the Diamond SpeedSTAR cards, select ET4000 with the appropriate
display mode during Setup.
Some ET4000 adapters do not support the setting of refresh rates
through software.
If you have a card with only 512K bytes of video memory, the
800x600x256 and 1024x768x256 color modes will not work correctly.
7.6 ProDesigner II Display
For the Orchid Technologies ProDesigner II and ProDesigner IIs cards,
select ET4000 with the appropriate display mode during Setup.
7.7 S3 VGA
To run the S3 video driver, your graphics adapter must have at least 1 MB of
video memory.
The vertical refresh rate for most S3 based video is set by dip switches on the
card, or by running an MS-DOS program that programs the adapter's ROM.
For these systems, select the default setting in Windows NT Setup. The MS-
DOS setup program for these cards, must be run under MS-DOS. If you have
a DELL machine or Number Nine card, you may use the other settings when
listed.
If you experience difficulties using the S3-based video card on your Hewlett-
Packard Vectra computer, call Hewlett-Packard technical support to upgrade
your BIOS EEPROMS.
7.8 Trident
For Trident cards, select Trident with the appropriate display mode during
Setup. Trident 8900c based boards do not show 256 color MS-DOS-based
applications in frozen windows well.
7.9 Video Seven, Headland Technologies VRAM II, and VRAM II Ergo
For these devices, select Video Seven VRAM with the appropriate resolution
during Setup.
When using the VRAM II with BIOS version 8.05, you may see random
characters or vertical lines when rebooting. Contact Headland Technologies
for a ROM upgrade.
The VRAM II Ergo display card also causes problems if its DIP switches are
not set correctly. All the switches should be off (set to the right) except for
switch #3. If this fails to correct your problem, please contact Headland
Technologies technical support.
VRAM I BIOS rev. 1.18 does not support any 256-color modes under
Windows NT.
The IRQ jumper settings should always be set OFF. Note that on
BIOS rev. 8.57 and 8.59, the settings are the reverse of that shown
in the documentation.
7.10 Western Digital/Paradise
For Western Digital cards, select WD with the appropriate display mode
during Setup. We have performed testing on WD90C30 and WD90C31 chip sets.
7.11 XGA
For these devices, select XGA or XGA2 with the appropriate resolution
during Setup. The XGA cards require 1 MB of video memory, and only
support 256 color modes. Make sure that your monitor supports the
modes you select.
Only install the XGA driver on portables with plasma displays if an
external monitor is attached.
7.12 ATI
The ATI drivers support the following boards:
GRAPHICS ULTRA
GRAPHICS VANTAGE
8514/ULTRA
GRAPHICS ULTRA PRO
GRAPHICS ULTRA+
The GRAPHICS ULTRA, GRAPHICS VANTAGE, and 8514/ULTRA
with 1 MB of graphics memory support resolutions of 640x480, 800x600,
1024x768 at 256 colors.
The GRAPHICS ULTRA PRO and GRAPHICS ULTRA+ with 2 MB of
graphics memory and the aperture enabled support the following resolutions:
640x480, 800x600, 1024x768, 1280x1024 at 8 bpp with 256 colors
640x480, 800x600, 1024x768 at 16 bpp with 65,536 colors
640x480, 800x600 at 24 bpp with 16,777,216 colors
640x480 at 32 bpp with 16,777,216 colors
The GRAPHICS ULTRA PRO and GRAPHICS ULTRA+ with 1 MB of
graphics memory and the aperture enabled support the following resolutions:
640x480, 800x600, 1024x768 at 8 bpp with 256 colors
640x480 at 16 bpp with 65,536 colors
The GRAPHICS ULTRA PRO and GRAPHICS ULTRA+ in an ISA bus
computer and the aperture disabled support the following resolutions:
640x480, 800x600, 1024x768, 1280x1024 at 8 bpp with256 colors
640x480, 800x600, 1024x768 at 16 bpp with 65,536 colors
The supported resolutions and pixel depths are conditional on there being
enough memory on the card. All cards require a minimum of 1 MB of
graphics memory. The pixel depth is conditional on the DAC type on the
display adapter. If you choose a resolution that is not supported or your card
has not been installed for, the driver substitutes a supported resolution.
The following configurations are not supported:
The GRAPHICS ULTRA, GRAPHICS VANTAGE, and 8514/ULTRA at
1280x1024 and 16 colors.
The GRAPHICS ULTRA PRO, and GRAPHICS ULTRA+ if you have an
ISA bus and NO aperture (ie more than 12 megs RAM) at the following
resolutions:
640x480, 800x600 at 24 bpp with 16,777,216 colors
640x480 32 at bpp with 16,777,216 colors]
8.0 Removable Media
Removable media drives (such as Bernoulli and Syquest) are supported
for use with the FAT and NTFS file systems only.
Optical drives that support media with sector sizes larger than 512
bytes must have the 512-byte sector size media mounted while
installing Windows NT, even if Windows NT is not being installed onto
the optical drive.
If you install Windows NT or any portion of Windows NT onto removable
media, be sure to shut down Windows NT before removing the media.
(That is, choose Shutdown from the File menu of Program Manager.)
Do not remove the media until after Windows NT has completed its
shutdown process. Media must be installed to run Windows NT Setup.
9.0 Supported Keyboard Layouts
During setup, the following keyboard layouts cannot be used:
Czech
Greek
Hungarian
Polish Programmer
Russian
These keyboards are for use only with Unicode applications and
require installing the Unicode font, Lucida Sans Unicode.
10.0 Installing Windows NT over NextStep
NextStep makes nonconventional changes to partition tables that can
distort measurement of the amount of space remaining on a drive. If
more space is reported than is actually available, installation can
fail due to lack of space on the drive.
11.0 Converting File Systems During Installation
If your disk is too fragmented, there may not be enough room for
Setup to create the system files. If this occurs, Setup will not be
able to convert a volume at the conclusion of installation. Before
trying to convert the volume again, either delete some files, or
backup and reformat the drive.
12.0 Reporting Problems
If you encounter a system problem, please report it to Microsoft
using BUGREP.TXT. This file is located in the \SUPPORT\SUPTOOLS
directory on the CD-ROM as well as floppy Disk #4 of the floppy
install disk set. Additionally, SAMPBUG.TXT is an example of a
completed bug report.
************ SETUP.TXT ************
Thank you for purchasing Microsoft Windows NT. To
give you the greatest possible benefit from this product,
we've included this detailed set of notes on Windows NT.
We hope you enjoy using this operating system.
Feedback from the thousands of Windows NT beta sites
has shown that Windows NT Setup proceeds smoothly in
the vast majority of cases. However, there are cases where
you may experience difficulties with hardware incompatibilities
or conflicts. SETUP.TXT contains information that you
may need in order to install Windows NT or Windows NT
Advanced Server on some hardware configurations.
Information applies to both Windows NT and Windows
NT Advanced Server.
For more information on installation, see the chapters "Installing
Windows NT" and "Troubleshooting" in the Windows NT System Guide or
Windows NT Advanced Server System Guide.
1.0 Removing Previous Versions
If you have installed a pre-release version of Windows NT, you should
delete it before installing this version. Depending on the release, the
Windows NT Boot Loader may not support booting both this release of the
operating system and a previous release.
2.0 General Hardware Notes
Windows NT has a very wide range of hardware support -- including
support for over 1600 x86 uniprocessor systems, over 25 x86
multiprocessor systems, as well as supporting RISC systems (for
details please see the Hardware Compatibility List). To cover a
few outlying cases, we've included these notes.
2.1 Interrupt Conflicts
A common problem in a computer with several supported devices is
conflicting interrupts, I/O ports, or memory usage. Where possible, we
have identified such cases in this document. However, if one of the
supported devices does not seem to work, it may be due to the
particular hardware configuration. For more specific information,
see your hardware manual or contact your system manufacturer.
2.2 ROM Shadowing
If you encounter persistent installation problems on multiprocessor
systems, try installing with ROM shadowing disabled.
2.3 Intel EtherExpress 16 LAN Adapter
In some cases, selecting "early" in the I/O Channel Ready box
can stop the network adapter card from functioning correctly and
may require reconfiguring with the Intel SoftSet utility. If you are
unsure whether your system can take advantage of this network
setting, consult your hardware vendor.
3.0 Specific Computer Systems
3.1 ACER AcerFrame 3000 MP
Before installing Windows NT, disable shadow RAM Video BIOS.
3.2 IBM Personal System/2
On some IBM PS/2 systems only planar memory is recognized when
booting from the Windows NT CD-ROM boot disk or Disk #1 of the
floppy disk installation set. This is a memory card problem. You may
encounter this problem if your system contains a card with the
following part numbers:
FRU-88F0075
Option 87F9856 or 87F9860
Newer model cards are available that correct this problem. Part numbers
for the newer cards are:
FRU-87F9916 or 34F2825
Option 34F3077 or 34F3011
Using Kingston expansion memory can also correct this problem.
It is recommended that before you install Windows NT, you update your
system configuration using the PS/2 Reference Diskette version 1.21 or
later
3.3 Installation on the IBM ThinkPad
The IBM ThinkPad 700c and 720c portables require an ABIOS patch to
install and run Windows NT. Copy the following files from the ThinkPad
Reference Diskette onto C:\
ABIOS.SYS
SF*.BIO
3.4 Olivetti LSX5030
For the Olivetti LSX5030, disable all ROM shadowing.
3.5 Toshiba T4400SX Monochrome
The Toshiba T4400SX display is not supported when an
external monitor is connected.
3.6 Gateway Nomad and TI Travelmate Notebooks
To successfully install Windows NT on these machines, you
must choose "Custom Setup". If you encounter problems
running setup while scanning for SCSI Adapters, you can
delete the SCSI drivers from the setup diskette to solve
the problem.
To properly use the floppy drive with Windows NT, configure
the system using its setup utility. Set the Advanced Operating
System option to Auto. When power management drivers for
these machines are available from Texas Instruments, using
the Auto option will not be necessary.
The built in InPort/QuickPort mouse adapter requires a mouse
driver from Texas Instruments to work properly under Windows NT.
You can use a serial mouse until this driver is available from
Texas Instruments.
In order to use the internal modem for these computers, you will
need a power management driver and software from Texas Instruments.
The best configuration for the NE2000 Network Adapter under
Windows NT is at IRQ5 and I/O Port 340H.
3.7 Gateway 2000 and Micronics Gemini 486 VESA Local Bus
Motherboards
Windows NT may stop running on systems that use Ultrastor's U34F Local
Bus controller with the Micronics Gemini 486 VESA Local Bus motherboard.
Some older Gateway systems include this combination of hardware.
The problem is a timing issue that only appears with Windows NT, the
Ultrastor U34F, and the Micronics Gemini 486 VESA Local Bus
motherboard. Disabling the motherboard's external cache should allow
Windows NT to run. The problem does not occur with ISA bus controllers
from Ultrastor. This problem does not occur on Gateway 2000 or Micronics
VESA Local Bus motherboards with a blue OverDrive socket.
If you encounter this problem, you can resolve it by an upgrade offered by
Micronics for the Gemini 486 VESA Local Bus motherboard. The
motherboard will need to be returned to Micronics for an upgrade. The
Micronics reference number for this is VLBA03. Micronics can be reached at
510-651-2300 for additional information. If you have a Gateway computer,
contact Gateway 2000 at 800-846-2301 for upgrade information.
3.8 Zeos Freestyle/SL Notebook Computer
When performing a Windows NT installation on this computer, you
must power off the computer after the text-based portion of Setup is
complete and you have been prompted to press CTRL+ALT+DEL to
restart the computer. Otherwise a keyboard controller failure may occur.
4.0 General Disk Drive Information
4.1 Volume Sets Created Via the BIOS
On controllers other than the UltraStor 124f, Windows NT does not
support disk controllers that create volume sets via the BIOS
(i.e. two different drives merged into a single drive letter).
4.2 Caching Disk Controllers and Drives
Windows NT supports caching disk controllers and drives only if one of
the following is true:
- The controller has a driver that specifically supports caching
(several of these exist: DPT and IBM SCSI Caching Adapter).
- Write-through is active (i.e. write caching is disabled) either by
setting it manually or by default when the computer starts.
- The entire cache option is off, either by setting it manually or by
default when the computer starts.
Using a caching controller or drive in other situations risks loss of
data if the computer is rebooted or a power failure occurs before the
cache has flushed itself. You can minimize risk by waiting at least 1
minute (less if you know the maximum time the cache waits before
flushing itself) after all system activity stops before rebooting.
The disk activity light is a good indicator of how write caching is
being done on your system. This applies to the initial Windows NT
installation as well as shutdown. Note that unexpected power failure
at any time can potentially corrupt data on the disk, possibly to the
extent that the disk becomes unreadable. Making the delay time that
write data is cached before being flushed to disk as small as
possible reduces this risk.
4.3 IDE/ESDI Drive Support
The Windows NT IDE/ESDI drive support is limited to two
disk drives per controller. A second IDE/ESDI controller from
Compaq (on Compaq machines only) or built in like the
Gateway 2000 VESA local bus machines is supported by the
standard Windows NT product. If you have a need to
configure from 2 to 6 IDE or ESDI controllers in one
system, contact MS Product Support Services for details on
how to do so.
4.4 Installing onto Systems with an ESDI Drive Containing More
Than 1024 Cylinders
In some cases, Windows NT installation proceeds normally until the
first boot from the hard drive where Windows NT is installed. The
Windows NT Boot loader will load various files and then produce a
Fatal System Error: 0x0000006b with the message that Phase 1 Process
Initialization failed. Following this message will be some type of
hex dump and the system will be locked up. If you experience this
difficulty the following information can help.
Testing has been done on the following ESDI controllers using a hard
drive with a capacity exceeding 516 MB (MB=1,048,576 bytes) formatted.
The MS-DOS limit of 1024 cylinders creates a situation where special
BIOS mapping on the controller is used to change the geometry of the
drive. ESDI drives are capable of being prepared with various values
of "sectors per track" (spt) such as 53 or 63 spt geometry during a
low-level format. Here is a brief example of a drive capacity using a
different spt format.
1024 cylinders X 15 heads X 53 spt X 512 bytes per sector =
398MB formatted capacity
or
1024 cylinders X 15 heads X 63 spt X 512 bytes per sector =
472MB formatted capacity
Thus using 63 spt will yield 74MB more space. Windows NT is perfectly
compatible with either geometry, and depending on the drive/controller
can access the remaining cylinders beyond 1024. This space can be
partitioned and formatted but not accessed by MS-DOS as the boot OS.
However, some controllers can successfully remap the remaining
cylinders beyond 1024 so that either MS-DOS or Windows NT can use the
entire capacity. An example would be:
1632 cylinders X 15 heads X 53 spt X 512 bytes per sector =
634MB formatted capacity
Testing has been done on the following ESDI controllers with their
Windows NT compatibility results:
DTC (Data Technology Corp)
Model 6282-24:
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. Windows NT will be able to access
the cylinders beyond 1024. Do not low-level the drive using Head
Mapping Mode.
Model 6290-24:
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. Since this card does not have an
onboard BIOS, Windows NT cannot access the remaining cylinders
beyond 1024.
Model 6290 SEZ (Dual SCSI/ESDI Controller):
Maximum Windows NT compatible geometry is using BIOS translation
in the EISA configuration using 63 spt and limit of 1024
cylinders under MS-DOS. Windows NT can access the remaining
cylinders beyond 1024.
Model 6295-24:
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. This model does have an onboard BIOS
so Windows NT can access the remaining cylinders beyond 1024. Do
not low-level the drive using Head Mapping Mode.
Adaptec
Model 2322D:
Several methods that can achieve maximum drive capacity are as
follows:
1. Disable drive translation and the on-board controller bios.
Then use a user defined drive type with the actual drive
parameters. For example:
Drive Type in CMOS=48 Cylinders=1632 Heads=15 SPT=53
This will give 634MB capacity. MS-DOS will still be limited to
the first 1024 cylinders which makes 398MB available. Windows
NT will be able to access the cylinders beyond 1024 yielding
another 236MB.
2. This option allows both MS-DOS & Windows NT to access the entire
drive. Jumper the controller for Drive Splitting. Disable
drive translation and the on-board controller BIOS. Set up
the first physical drive in the CMOS as:
Cylinders=1024 Heads=15 SPT=53
which will give a drive capacity of 398MB. Set up the second
drive (it appears as a physical drive) in the CMOS as:
Cylinders=606 Heads=15 SPT=53
This will yield another 236MB. Windows NT will actually see
the drive as two physical drives.
UltraStor
All models with PROM versions less than #####-009
Maximum Windows NT compatible geometry is to use 63 spt and limit
of 1024 cylinders under MS-DOS. Windows NT will be able to access
the cylinders beyond 1024.
All models with PROM versions equal to or greater than #####-009
Maximum Windows NT compatible geometry is to use "Track mapping"
during Low-Level formatting. Both MS-DOS and Windows NT will have
access to entire drive capacity.
5.0 SCSI Devices
Windows NT supports over 60 SCSI host adapters, over 30 SCSI CD-ROM
drives, over 40 SCSI tape drives, over 10 SCSI removable media systems,
and SCSI scanners. Here are some detailed notes on Windows NT's SCSI
support.
This section provides information on configuring SCSI devices when
running Windows NT.
5.1 SCSI CD-ROM Devices
The SCSI and CD-ROM support built into Windows NT 3.1 requires that
CD-ROMs provide SCSI parity to function properly. For many drives
this is a configurable option or is active by default. Check the
documentation for your CD-ROM to find specifics on how this is
configured for your drive. Examples of drives which do not provide
or support SCSI parity are the NEC CDR-36 and CDR-37 drives.
5.2 Installing from a SCSI CD-ROM Device
When you are installing Windows NT from a SCSI CD-ROM device, make
sure that the device does not have an ID of 0 or 1. Some SCSI BIOS
programs reserve 0 and 1 for hard disks. If you set your CD-ROM with
an ID of 0 or 1, you will likely see an extra partition in Setup that
does not exist.
If you have 2 CD-ROM devices connected to the same SCSI Host Adapter,
then Windows NT Setup does not necessarily install using the CD-ROM that
contains the higher SCSI ID. If using one CD-ROM results in Setup
displaying a message "Please insert the CD-ROM into the CD-ROM drive,"
then remove the CD and try the other CD-ROM. Setup chooses one CD-
ROM drive and refers to it as 'the' CD-ROM drive.
5.3 Installing Windows NT with a Proprietary Adapter Driver
Some SCSI and proprietary CD-ROM adapter drivers are provided in the
Driver Library on the Windows NT CD. These drivers are contained in
a directory tree below the \DRVLIB directory. Some of the drivers will
have a readme.txt containing additional configuration information.
Please read this information before installing.
To install using one of these drivers:
1. Using your current operating system, access the Windows NT CD-ROM,
and change to the directory containing the driver that you want to use.
2. Copy all files in that directory to a blank, formatted floppy
placed in drive A: (Windows NT Setup requires the driver to be on
a disk in drive A). Label the disk "Driver Disk"
3. Shut down your current operating system (if necessary), and reboot
with the Windows NT CD-ROM Boot disk in drive A.
4. When Setup asks for Custom or Express setup, choose Custom.
5. When choosing an adapter press 'S' for additional SCSI adapters.
6. Choose "Other (requires disk provided by hardware manufacturer)."
7. Setup prompts for the driver disk. Insert the "Driver Disk" in
drive A.
5.4 Installing with Unsupported CD-ROM Drives
Please refer to the chapter "Installing Windows NT" in the Windows NT
System Guide or Windows NT Advanced Server System Guide for
information on installing Windows NT from MS-DOS when your system
has an unsupported CD-ROM drive.
5.5 Adding a CD-ROM After Installing Windows NT
If you add a CD-ROM drive after you have installed Windows NT, use the
Devices option in Control Panel to configure device startup. For all
CD-ROM drives, set the Startup value of Scsicdrm to System. If your
drive does not support SCSI-2 Audio, also set the Startup value of
Cdaudio to System. Cdaudio should also be set to System for some SCSI-1
CD-ROM drives, including the Denon DRD-253; Pioneer-DRM-600; NEC
Intersect 73, 73m, 74, 84; and Hitachi 1750s, 1650s, 3650.
For more information on starting devices, choose the Help button in the
Devices dialog box.
5.6 NEC Intersect CD-ROM
NEC Intersect CD-ROM readers have a switch that enables 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. To avoid this problem, set
switch number 5 ON. The switch is located with switches labeled SW1.
5.7 SCSI Termination
The SCSI bus must be properly terminated on both ends. If you are
using both an external and an internal SCSI device, it is best to
terminate the devices and remove the terminators on the SCSI adapter.
For the SCSI adapter to operate effectively, termination power must be
provided on the SCSI bus either by the adapter or by a SCSI device
connected to the bus. Some adapters provide termination power with
no configuration options. Others do not provide termination power
(for example, Future Domain 1660 and Trantor 128 and 130B). Still
others provide termination power only if a jumper is set on the
adapter (for example, Future Domain 850M).
Please consult the documentation for your SCSI adapter and SCSI
device to make sure that termination power is present on the SCSI bus.
5.8 Adaptec
An Adaptec adapter might use conflicting memory addresses with other
cards such as network adapters. This requires reconfiguring the
hardware by changing jumpers.
DMA speed cannot be set on an Adaptec 154x SCSI controller. Currently
the AHA154X.SYS driver supports a DMA transfer rate of 5.0 MB.
The Adaptec AHA154xC card is extremely sensitive to termination and
cabling. Systems with this card should use SCSI-II cables and/or
SCSI-II active terminators. SCSI-II cables are available from
Amphenol Quintec and Icontec. If these recommendations are not
followed, unreliable operation, including data corruption, is possible.
The Adaptec AHA-1542C and Denon DRD-253 are incompatible under Windows
NT. The AHA-1542C requires active termination and the Denon DRD-253
CD-ROM has built in passive termination.
The Adaptec 1640 Micro Channel adapter does not support the Maynard
2000 or 1300 DAT drives in this release. The 1640 adapter is not
supported on IBM PS/2 Model 70 computers.
There is a known problem using Micronics VL bus motherboards with
Adaptec 1542x adapters.
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
Technical Support at (408) 945-2550 for information on the most recent
version, 3.20, of the BIOS. BIOS versions after 3.08 do not have this
problem. The latest 154x BIOS also supports drives that are larger
than 1 GB under both BIOS/MS-DOS and Windows NT. Windows NT will be
able to access drives larger than 1 GB even without this upgrade
provided and extended partition is used.
The Adaptec AHA164x driver logs unnecessary errors. These occur while
NTBACKUP is in use with a tape connected to the AHA164x. The entries
look like:
7/10/93 2:41:40 AM AHA154x Error None 11 N/A
[MachineName] The driver detected a controller error on \Device\ScsiPort1.
These entries may be ignored. Also when too many of these entries are
generated a pop-up is created indicating the error log is full. This
can be avoided by setting the system event log settings to overwrite
the events as needed.
5.9 Buslogic
When using a Buslogic 747 SCSI Adapter with an AST Manhattan SMP
computer, you must disable the adapter's BIOS. For more information
on disabling the BIOS, refer to the adapter's documentation.
5.10 Compaq Smart SCSI Array
The Compaq Smart SCSI Array must be configured to use any possible
interrupt other than IRQ 2 to function properly under Windows NT.
5.11 Dell Drive Array
The Adaptec emulation mode on the Dell Drive Array (DDA) must
be disabled for compatibility with the hardware's Windows NT driver.
5.12 Future Domain
The Windows NT driver that supports the Future Domain 845, 850, and
885 adapters assumes operation on IRQ 5. If the adapter is set for
another interrupt, the Future Domain driver will continue to work,
but in a polling fashion that may slow down operation of the system.
Further, the Future Domain driver will register to the system claiming
the use of IRQ 5 and this may disrupt operation of another device
that is actually configured for IRQ 5. If you are using one of the
above mentioned Future Domain adapters, please complete the Windows
NT installation normally, then change the IRQ information for the
driver in the registry. If the IRQ is incorrect, the driver will
log an event viewable in the Event Viewer Administrative Tool.
If you have a 16-bit Future Domain card or an 8-bit M series card
configured with an external SCSI device, make sure that SCSI
termination is correct. You must set a jumper on the card for this
setting. Check the cards documentation for details.
A Future Domain SCSI adapter might use conflicting memory addresses.
This requires reconfiguring the hardware by changing jumpers.
5.13 IBM PS/2 SCSI Adapter
To configure an IBM SCSI adapter with a BIOS dated before 1991 for use
with Windows NT, use a PS/2 Reference Diskette version 1.21 or later.
5.14 Maynard SCSI Adapter
You cannot use Express Setup to install Windows NT onto a hard disk
attached to a WD33C9C SCSI host adapter (Maynard SCSI adapter) because
Setup cannot identify this adapter. However, you can use Custom Setup
to install this adapter card. Or, after Setup, you can use the Setup
icon to install the adapter card.
5.15 Mylex DCE376 and Tangent 48933 USA
The Tangent and Zeos 433 EISA system comes standard with a Mylex 376
controller which operates in WD1003 emulation mode by default. This
will be no longer be necessary when a SCSI driver for this card becomes
available for Windows NT.
5.16 UltraStor SCSI Controllers
If you experience a problem in tape functionally with a supported 4mm
DAT Tape Device and an UltraStor 14F or 24F controller, contact
UltraStor for an upgrade to resolve this.
If you have an UltraStor 34F controller installed into a Micronics VLB
motherboard, it is recommended that you turn the motherboard external
cache off.
The UltraStor 124 adapter is compatible with removable media drives,
but does not allow the user to remove and replace media. For this reason,
Windows NT does not support removable media drives when used with this
controller.
The combination of the UltraStor 14F and DEC Talk Speech Synthesizer
Card can cause Windows NT Setup to fail due to an I/O port conflict.
To avoid this problem, either set the DEC I/O to 350, or delete the
file ULTRA14F.SYS from the boot floppy while leaving the DEC card at
default settings.
5.17 Trantor
These adapters are SCSI-termination sensitive. If Windows
NT hangs upon booting, or if Windows NT Setup cannot find devices
attached to a Trantor adapter, verify that the SCSI termination
occurred and that one of the SCSI devices attached to the Trantor
adapter is providing termination power.
The Trantor T228 MCA SCSI adapter is not supported on the IBM PS/2
Model 95.
5.18 Texel DM-5024 CD-ROM
A firmware level of 1.10C is required to make the DM-5024 CD-ROM
compatible with Windows NT. Contact Texel at 1-800-886-3935 for
information on this upgrade.
6.0 Error Messages
6.1 Couldn't Find NTLDR
This message is displayed if the file NTLDR is missing from the root
of the C: drive. You can copy the file to C:\ from either the CD ROM
or floppy disks.
To copy NTLDR from the CD ROM, make the CD ROM your current drive and
enter the command:
copy \i386\ntldr C:\
To copy NTLDR from floppy disk, insert Disk 2 in your disk drive and
make that drive the current drive. Then enter the command:
expand ntldr.$ c:\ntldr
6.2 Error 0000001E
Generally, this error implies a problem in the file system. Run CHKDSK
or another similar utility on the drive. Make sure your hardware is on
the hardware compatibility list.
6.3 Error 0x00000069 or 0x00000067
This initialization error indicates that Windows NT is unable to
communicate with the hard drive controller. Try the following:
- 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.
- Make sure there are no missing Windows NT system files.
6.4 NMI Hardware Error
This error is caused by a hardware problem. In some cases, the
computer's memory can be at fault, leading to an error that does
not appear when running MS-DOS or Windows 3.x, but does appear when
running Windows NT. Memory errors can occur when the access rate does
not match the requirements of the system board or when the access
rate varies between SIMM modules or chips on a module. Cache memory
access rates that are too slow can also cause this problem. In general,
the first steps toward troubleshooting are to make sure that contacts
for all boards and memory modules are clean, that boards and memory
modules are properly seated, and that the computer is free of dust.
6.5 System Error F002
If you receive a System Error F002, this probably means that your
hardware is faulty; for example, you may be experiencing a memory
failure. If this occurs, run the manufacturer's diagnostics procedure
and check to see if your memory is the proper speed for your CPU.
7.0 Video Display Drivers and Adapters (x86 Computers)
Windows NT has excellent video support, supporting over 45 video
display adapters, including excellent high-end support. Here are
some detailed notes on Windows NT's video support.
The information in this section is applicable for x86 computers only.
To select a video adapter other than VGA, you must run Custom Setup
or run Windows NT Setup from the Main program group after you have
completed installation.
This release supports the VGA standard video cards plus some newer
video cards. If the video card you use is not listed in this section,
select VGA as the display device in Windows NT Setup. If you choose a
display mode in Setup that your hardware does not support, you will
need to reinstall Windows NT. You should be careful when installing
some of the higher resolution modes to be sure that your monitor
supports the resolution and vertical refresh rates.
If the display mode selected by the user is not valid -- because the
video card was not present or because the card had insufficient video
memory -- an alternate driver will be selected by Setup automatically
so that the computer is able to boot.
If you encounter problems read your video manual again for proper settings.
You may have overlooked something in the manual that pertains to Windows
NT if you previously installed the card under Windows 3.1.
In general, Windows NT video drivers do not use interrupts. Many VGA
cards use jumpers to enable IRQ 2 interrupt for EGA compatibility. When
possible, you should disable the IRQ 2 interrupt.
During setup Windows NT may allow you to set the vertical refresh rate for
your card. Read your monitor manual to see what settings you can use. If you
are unsure, set up at the lower resolution, and then later try higher resolutions.
If after changing these settings and rebooting, you find that your display is not
operating correctly, reboot again and use the "last known good" feature to
restore your previous video settings. Be aware of the fact that some monitors
may be physically damaged by wrong video settings.
Minimum video memory requirements for Windows NT:
640x480x16 colors 512K
640x480x256 colors 512K
800x600x16 colors 512K
800x600x256 colors 1M
1024x768x16 colors 512K
1024x768x256 colors 1M
1280x1024x256 colors See individual driver requirements
7.1 VGA
If you experience a problem with the standard VGA driver, try the
alternative VGA driver that programs the VGA directly. The standard
VGA driver uses the VGA display adapter's BIOS to initialize the card.
To use the alternate driver, rename the standard driver VGA.SYS to
VGA.SAV. Then copy VGA_ALT.SYS to VGA.SYS and reboot.
7.2 8514/A and Compatible Cards
When installing Windows NT on a computer that has an 8514/A or
compatible graphic card (for example, IBM's 8514/A or ATI's 8514Ultra),
and the computer has an older version of BIOS, Custom Setup may display
your video card as "Unknown."
You can change the video driver from "Unknown" to the Standard VGA
(640x480, 16 colors) driver during Windows NT Setup. If you have an ATI
8514 Ultra graphic card, after Windows NT Setup is completed, you can run
Windows NT Setup located in the Main group in Program Manager to select
the appropriate ATI video driver. Express Setup will default the video
driver to the Standard VGA (640x480, 16 colors) when an unknown video
card is detected.
There is no other video driver for 8514/A or compatible graphic cards
included in this release of Windows NT.
7.3 Cirrus-based Cards
For boards based on the Cirrus Logic chip set, select Cirrus with the
appropriate resolution during Setup.
7.4 VESA VGA
The VESA VGA driver uses the newer standard for detecting if a card
can handle the 800x600 Super VGA mode. VESA VGA is not supported, if
you have a card that uses the old standard, or a card that required an MS-
DOS-based TSR to implement Super VGA functionality. Standard VGA
mode is supported instead.
7.5 Diamond SpeedSTAR (and any ET4000 SVGA)
For the Diamond SpeedSTAR cards, select ET4000 with the appropriate
display mode during Setup.
Some ET4000 adapters do not support the setting of refresh rates
through software.
If you have a card with only 512K bytes of video memory, the
800x600x256 and 1024x768x256 color modes will not work correctly.
7.6 ProDesigner II Display
For the Orchid Technologies ProDesigner II and ProDesigner IIs cards,
select ET4000 with the appropriate display mode during Setup.
7.7 S3 VGA
To run the S3 video driver, your graphics adapter must have at least 1 MB of
video memory.
The vertical refresh rate for most S3 based video is set by dip switches on the
card, or by running an MS-DOS program that programs the adapter's ROM.
For these systems, select the default setting in Windows NT Setup. The MS-
DOS setup program for these cards, must be run under MS-DOS. If you have
a DELL machine or Number Nine card, you may use the other settings when
listed.
If you experience difficulties using the S3-based video card on your Hewlett-
Packard Vectra computer, call Hewlett-Packard technical support to upgrade
your BIOS EEPROMS.
7.8 Trident
For Trident cards, select Trident with the appropriate display mode during
Setup. Trident 8900c based boards do not show 256 color MS-DOS-based
applications in frozen windows well.
7.9 Video Seven, Headland Technologies VRAM II, and VRAM II Ergo
For these devices, select Video Seven VRAM with the appropriate resolution
during Setup.
When using the VRAM II with BIOS version 8.05, you may see random
characters or vertical lines when rebooting. Contact Headland Technologies
for a ROM upgrade.
The VRAM II Ergo display card also causes problems if its DIP switches are
not set correctly. All the switches should be off (set to the right) except for
switch #3. If this fails to correct your problem, please contact Headland
Technologies technical support.
VRAM I BIOS rev. 1.18 does not support any 256-color modes under
Windows NT.
The IRQ jumper settings should always be set OFF. Note that on
BIOS rev. 8.57 and 8.59, the settings are the reverse of that shown
in the documentation.
7.10 Western Digital/Paradise
For Western Digital cards, select WD with the appropriate display mode
during Setup. We have performed testing on WD90C30 and WD90C31 chip sets.
7.11 XGA
For these devices, select XGA or XGA2 with the appropriate resolution
during Setup. The XGA cards require 1 MB of video memory, and only
support 256 color modes. Make sure that your monitor supports the
modes you select.
Only install the XGA driver on portables with plasma displays if an
external monitor is attached.
7.12 ATI
The ATI drivers support the following boards:
GRAPHICS ULTRA
GRAPHICS VANTAGE
8514/ULTRA
GRAPHICS ULTRA PRO
GRAPHICS ULTRA+
The GRAPHICS ULTRA, GRAPHICS VANTAGE, and 8514/ULTRA
with 1 MB of graphics memory support resolutions of 640x480, 800x600,
1024x768 at 256 colors.
The GRAPHICS ULTRA PRO and GRAPHICS ULTRA+ with 2 MB of
graphics memory and the aperture enabled support the following resolutions:
640x480, 800x600, 1024x768, 1280x1024 at 8 bpp with 256 colors
640x480, 800x600, 1024x768 at 16 bpp with 65,536 colors
640x480, 800x600 at 24 bpp with 16,777,216 colors
640x480 at 32 bpp with 16,777,216 colors
The GRAPHICS ULTRA PRO and GRAPHICS ULTRA+ with 1 MB of
graphics memory and the aperture enabled support the following resolutions:
640x480, 800x600, 1024x768 at 8 bpp with 256 colors
640x480 at 16 bpp with 65,536 colors
The GRAPHICS ULTRA PRO and GRAPHICS ULTRA+ in an ISA bus
computer and the aperture disabled support the following resolutions:
640x480, 800x600, 1024x768, 1280x1024 at 8 bpp with256 colors
640x480, 800x600, 1024x768 at 16 bpp with 65,536 colors
The supported resolutions and pixel depths are conditional on there being
enough memory on the card. All cards require a minimum of 1 MB of
graphics memory. The pixel depth is conditional on the DAC type on the
display adapter. If you choose a resolution that is not supported or your card
has not been installed for, the driver substitutes a supported resolution.
The following configurations are not supported:
The GRAPHICS ULTRA, GRAPHICS VANTAGE, and 8514/ULTRA at
1280x1024 and 16 colors.
The GRAPHICS ULTRA PRO, and GRAPHICS ULTRA+ if you have an
ISA bus and NO aperture (ie more than 12 megs RAM) at the following
resolutions:
640x480, 800x600 at 24 bpp with 16,777,216 colors
640x480 32 at bpp with 16,777,216 colors]
8.0 Removable Media
Removable media drives (such as Bernoulli and Syquest) are supported
for use with the FAT and NTFS file systems only.
Optical drives that support media with sector sizes larger than 512
bytes must have the 512-byte sector size media mounted while
installing Windows NT, even if Windows NT is not being installed onto
the optical drive.
If you install Windows NT or any portion of Windows NT onto removable
media, be sure to shut down Windows NT before removing the media.
(That is, choose Shutdown from the File menu of Program Manager.)
Do not remove the media until after Windows NT has completed its
shutdown process. Media must be installed to run Windows NT Setup.
9.0 Supported Keyboard Layouts
During setup, the following keyboard layouts cannot be used:
Czech
Greek
Hungarian
Polish Programmer
Russian
These keyboards are for use only with Unicode applications and
require installing the Unicode font, Lucida Sans Unicode.
10.0 Installing Windows NT over NextStep
NextStep makes nonconventional changes to partition tables that can
distort measurement of the amount of space remaining on a drive. If
more space is reported than is actually available, installation can
fail due to lack of space on the drive.
11.0 Converting File Systems During Installation
If your disk is too fragmented, there may not be enough room for
Setup to create the system files. If this occurs, Setup will not be
able to convert a volume at the conclusion of installation. Before
trying to convert the volume again, either delete some files, or
backup and reformat the drive.
12.0 Reporting Problems
If you encounter a system problem, please report it to Microsoft
using BUGREP.TXT. This file is located in the \SUPPORT\SUPTOOLS
directory on the CD-ROM as well as floppy Disk #4 of the floppy
install disk set. Additionally, SAMPBUG.TXT is an example of a
completed bug report.
===========================================================================
README.SDK
===========================================================================
This document covers the following topics:
* A guide to sources of information that complement the
Windows 3.1 Software Development Kit (SDK) manuals.
* Instructions for setting your PATH, INCLUDE, and LIB
environment variables, and other instructions for
configuring your Windows development environment. (The SDK
Install program appends this information to this
README.SDK file.)
OTHER SOURCES OF INFORMATION
The following list describes online documents that contain
important information about the Windows 3.1 SDK that is not
included in the on-line Windows Help or QuickHelp documentation.
Document Contents
_____________________________________________________________________
README.WRI Additional information about the Windows
3.1 SDK. This file is in Microsoft Write
format.
WINDOWS.TXT Information about changes to WINDOWS.H,
including STRICT.
ROBUST.TXT Information on how to build robust applications.
WINDOWSX.TXT Information on using the message crackers and
control functions in WINDOWSX.H.
Additional information is available on the following topics:
* Microsoft C Runtime Libraries
* Message Crackers and Control APIs
* Audio Documentation and Software
* New Directories
* Dialog Editor (DLGEDIT.EXE)
* Windows clipboard formats
* DOS Protected Mode Interface (DPMI) Specification
These sources are described in this section.
Microsoft C Runtime Libraries
-----------------------------
C runtime libraries for Windows are no longer included with the SDK.
These files are now included with the C product you use for
Windows Development.
Message Crackers and Control APIs
---------------------------------
The Message Crackers and Control APIs were moved from WINDOWS.H
to WINDOWSX.H. Most known bugs and problems reported from
pre-release 2 are fixed in this release of WINDOWSX.H. You can
build generic Windows applications that use Message Crackers and
Control APIs and which are STRICT compliant by using WINDOWSX.H
with the generic sample MAKEAPP located in the SAMPLES
subdirectory.
Audio Documentation and Software
--------------------------------
This release also includes MMSYSTEM.H and on-line documentation
on how to use the new audio services in Windows 3.1. The on-line
documentation is located in WIN31MWH.HLP, MMPWKBK.HLP,
and MCISTRWH.HLP (WinHelp format) or WIN31QH.HLP, MCISTRQH.HLP
(QuickHelp format).
New Directories
---------------
BIN contains the files previously installed in the
root WINDEV directory
GUIDE contains the Guide to Programming Samples
SAMPLES contains the new sample source code applications
REDIST contains the redistributable file for the SDK
HELP contains the SDK Quickhelp files
Windows Clipboard Formats
-------------------------
Specifications for various clipboard formats supported by
Microsoft and other vendors' applications are available from
sources described below.
* Rich Text Format (RTF) -- similar to the standard text
format, except that formatting attributes such as font,
style, and size are embedded. The RTF specification is
included in the "Microsoft Word Technical Reference for
Windows and OS/2 Presentation Manager,", which may be
ordered through bookstores or directly from Microsoft
Press at (800)888-3303.
* Binary Interchange File Format (BIFF) -- the native
Microsoft Excel format. The BIFF specification is
available from Microsoft Excel Telephone Sales at
(800)227-6444; ask for department "ET".
* Tag Image File Format (TIFF) -- a format that assists in
incorporating line art, photographs, and other raster
images into documents via desktop publishing application
programs. The TIFF specification is available from Aldus
Corporation at (206)628-2320; select the Production
Information phone extension. It is also available in the
CompuServe "Aldus" Forum, Library 10.
* Data Interchange Format (DIF), WKS, and WK1 -- formats
maintained by Lotus Development Corporation,
(617)253-9150.
DOS Protected Mode Interface (DPMI) Specification
-------------------------------------------------
This specification defines how DOS programs can access the
extended memory of PC architecture computers while
maintaining system protection. Windows provides
applications access to extended memory through Windows'
implementation of DPMI. Most Windows applications do not
need to directly use DPMI services, since these services are
provided by the Windows application programming interface
(API). Special Windows applications and device drivers may
need to access DMPI services directly.
The DPMI specification is available from Intel Corporation
at (800)548-4725. (Request part number JP-26.) This DPMI
specification should be read in conjunction with the
"Windows Support for DPMI" note included in the Windows
Developer's Notes, described above.
=========================================================
Setting Your PATH, INCLUDE, and LIB Environment Variables
=========================================================
Based on the directories that you specified during the SDK
installation procedure, you should add the following
directories in your environment variables:
----------------------------------------------
Companion Diskette for "Programming Windows"
(c) Charles Petzold, 1992
----------------------------------------------
This diskette contains source code and executable (.EXE) files for all the
sample programs described in the third edition of "Programming Windows" by
Charles Petzold (Microsoft Press, 1992). The programs are stored in
subdirectories corresponding to the book chapters.
In the root directory of the companion diskette, you'll find four batch files
named MSC.BAT, BCP.BAT, MSCDLL.BAT, and BCPDLL.BAT. Before compiling the
programs, you must execute MSC.BAT and MSCDLL.BAT if you are using Microsoft
C/C++ 7.0, or BCP.BAT and BCPDLL.BAT if you're using Borland C++ 3.1.
If you want to recreate all the .EXE files, you can run the MAKEMSC.BAT batch
file (for the Microsoft compiler) or MAKEBCP.BAT for the Borland compiler.
********README.TXT for the Windows 3.1 Device Development Kit************ This file contains two sections: Section A: Specific Information/workarounds to help build the drivers provided with the Windows 3.1 DDK. Section B: A Description of the Device Driver Sources Provided. ****SECTION A: Specific Information/Workarounds To Build Drivers********* If WINDEV Directory Already Exists ********************************** If you already have a WINDEV directory installed on your disk prior to installing the DDK, we strongly recommend you use a different directory to install the TOOLS, LIB and INCLUDE files provided with the DDK. Running Out Of Memory ********************* Because it can be very easy to run out of conventional memory when building device drivers and virtual devices when using the NMAKE utility, we are also providing the XMSMAKE utility which will additionally use extended memory. If you are encountering strange errors, you may be running out of memory and we recommend trying XMSMAKE which is located in the \TOOLS directory of the Device Drivers Samples & Tools Disks. Building 386 Grabbers ********************* You MUST use the LINK.EXE in the \TOOLS directory of the Device Driver Samples and Tools Disk Set when building the 386 Grabbers. Binary Compare of the PSCRIPT.DRV, SNDBLST2.DRV, and MCIPIONR.DRV Files *********************************************************************** If you build either the PSCRIPT.DRV, SNDBLST2.DRV or MCIPIONR.DRV drivers, your built driver may not exactly binary compare with the corresponding drivers provided in the Windows 3.1 retail product. The few differences noted are due to different build environments used, machine and memory configurations, etc. The driver you build will function identically to that provided in the retail product. Building VDDVGA.386,VDD8514.386 Virtual Devices ************************************************ When executing the Makefiles MAKEVGA and MAKE8514, please note that the created object files for both share the same object filename. So if you first create the VDDVGA.386 virtual device and then proceed to create the VDD8514.386 device you must be sure to first delete all filenames with the *.obj file extension. Nmake Version ************* If you want to build a driver that binary compares to the driver in the retail version, you need to be sure to use the NMAKE.EXE tool provided in the \TOOLS directory on the Device Driver Samples & Tools disk set. If you use the one provided with the C 6 Compiler, the driver may not binary compare but should function identically. ****SECTION B: Description of Device Driver Sources********************** Below are descriptions of device driver sources contained in the DDK. The information includes where you can find the code on the diskettes, the procedure for building the driver and the features the code demonstrates. NOTE: We recommend that you print out the text file "LAYOUTS.TXT" located in the root directory of the Device Driver Samples and Tools Disk#1 for a listing of the source directories and disk locations for the Samples and Tools Disk Sets. The sources are setup in sub-directories on the enclosed diskettes. You should use the DOS COPY or XCOPY command to copy all files and related sub-directories to your hard disk. It is important that you maintain the structure as provided on the diskettes for the accompanying MAKE and batch files to work properly. Also be sure to expand the compressed files to their normal size after copying them to your hard disk. Display Driver Sources ********************** We are providing 1, 4 and 8 plane display driver sources in the DDK. You will find all the 1 plane driver sources on the Device Driver Samples and Tools Disk Sets under \DISPLAY\1PLANE. The 4 plane sources are under \DISPLAY\4PLANE. The 8 plane sources are under \DISPLAY\8PLANE. 1 Plane Drivers - CGA, EGA mono, EGA high res B&W, Hercules, Plasma, and MCGA ***************************************************************************** All of these drivers are 1 plane drivers. These drivers run Bi-Modal (in Real and Protected memory modes), support Device Independent Bitmaps (DIB), and greater than 64K fonts. They are located on the Device Driver Samples and Tools Disk Sets under \DISPLAY\1PLANE. These drivers share common code in many areas. Thus, the directory structures should be copied in their entirety to your hard disk. We suggest you use the MS-DOS XCOPY command to do this. You need to change directory to the appropriate sub-directory for the driver you wish to build. Each driver directory has a Makefile to build the driver. You will find the Makefile for each driver under: \DISPLAY\1PLANE\BW\CGAHERC\CGA\ for CGA \DISPLAY\1PLANE\BW\CGAHERC\PLASMA\ for Compaq Plasma \DISPLAY\1PLANE\BW\CGAHERC\HERCULES\ for Hercules monochrome \DISPLAY\1PLANE\BW\EGA\EGAHIBW\ for EGA hi res black/white \DISPLAY\1PLANE\BW\EGA\EGAMONO\ for EGA monochrome \DISPLAY\1PLANE\BW\EGA\VGAMONO\ for MCGA To build the driver, use the NMAKE utility provided with Microsoft C 6. If your display device is based on the 1 plane CGA, EGA, or Hercules standard, you should base your driver code on one of these drivers. Otherwise, these sources should provide you with the sample code necessary for you to design and plan for a new driver. 4 Plane Drivers - EGA, VGA, and Super VGA ****************************************** The EGA, VGA, and Super VGA driver sources utilize all 4 planes to support 16 colors. The Super VGA display driver is new for Windows 3.1. It is nearly identical to the VGA sources, but determines an appropriate extended resolution mode number from the WIN.INI file. These drivers run Bi-Modal (in Real and Protected memory modes), support Device Independent Bitmaps (DIB), and greater than 64K fonts. The EGA, VGA, and Super VGA driver sources utilize all 4 planes to support 16 colors. All three drivers demonstrate a new feature of Windows 3.1, "Mouse Blur" that leaves "mouse trails" on the screen to improve cursor visibility on LCD screens. These drivers share common code in many areas. Thus, all the files in the \DISPLAY\4PLANE directory structure found on the Device Driver Samples and Tools should be copied in their entirety to your hard disk. We suggest you use the MS-DOS XCOPY command to do this. Be sure to expand the compressed files to their original size before using them. You need to change directory to the appropriate sub-directory for either the EGA, VGA, or Super VGA driver and execute the MakeFile using the NMAKE utility. You will find a makefile file for each driver under: \DISPLAY\4PLANE\EGA\ for EGA hi res color \DISPLAY\4PLANE\SVGA\ for Super VGA \DISPLAY\4PLANE\VGA\ for VGA If your display device is based on the 4 plane EGA or VGA standard, you should base your driver code on either of these drivers. Otherwise, these sources should provide you with the sample code necessary for you to design and plan for a new driver. 4 Plane Drivers - Pen-Capable VGA ********************************* To build Pen-Capable VGA display drivers, set the MS-DOS environment variable PENWIN=1, delete all object files, and rebuild. Note that this procedure is documented in the VGA driver makefile. 8 Plane Driver - Video Seven VRAM, VGA, 8514/a ********************************************** We have provided you sources to the Video Seven VRAM/FastWrite VGA and 8514/a drivers. These drivers use all 8 planes available on the card for 256 color support. The code provides a good example of the use of the Palette Manager and Device Independent Bitmaps (DIB). This driver is adapted to run Bi-Modal and supports >64K fonts. This driver source can also be used as an example of how a packed pixel driver is implemented under Windows. The 8514/s driver provides a sample of how to support the TrueType font technology with a display adapter that does its own font caching. In addition, this driver provides an example of Windows 3.1's multiple-resolution driver feature, which allows a single driver executable to support more than one screen resolution, or supply a variety of resolution-dependent resources (e.g.. small or large fonts). To demonstrate the use of DIBs and the Palette Manager in these drivers, you can run the sample application, SHOWDIB, provided in the SDK. You will find these sources on the Device Driver Samples and Tools Disk Set under the directory \8PLANE. You need to copy the entire directory structure to your hard disk. Use the MS-DOS XCOPY command to do this. Be sure to expand the compressed files to their original size before using them. Note, the 8PLANE directory contains an empty sub-directory called DEBUG. You must have this directory available when you build the driver, otherwise the MAKE files will fail. To build the drivers, you need to run the batch file: \DISPLAY\8PLANE\V7VGA\ for Video 7 VRAM VGA (NOTE: This builds the driver file V731VGA.DRV. This driver is renamed to V7VGA.DRV in Windows 3.1) \DISPLAY\8PLANE\8514\SOURCE for 8514/a NOTE: Be sure to use the /E parameter when XCOPYING the 8514 sources to your disk. The makefile is expecting to have the empty subdirectory \DISPLAY\8PLANE\8514\SOURCE\OBJ and will generate an error if this subdirectory is not present. Windows Real and Standard Mode Grabbers *************************************** The Windows real and standard mode grabbers are on the Device Driver Samples and Tools under \GRABBERS. Since much of the grabber code for different displays are common, you should copy the GRABBERS sub-directory in its entirety to your hard disk. Be sure to expand the compressed files to their original size before using them. The individual grabbers are in the following directories: \DISPLAY\GRABBERS\CGAHERC\CGA \DISPLAY\GRABBERS\CGAHERC\HERCULES \DISPLAY\GRABBERS\EGA\EGACOLOR \DISPLAY\GRABBERS\EGA\EGAMONO \DISPLAY\GRABBERS\VGA\VGACOLOR \DISPLAY\GRABBERS\VGA\VGAMONO You should run the NMAKE utility with the Makefiles provided in each of these directories to build the appropriate grabber. System Font Sources ******************* We have provided the Windows 3.1 proportional system font and the Windows 2.0 fixed pitch system font. If your display driver supports resolutions other than the display resolutions provided in Windows, you may need to modify the system fonts for your display. You will need to copy the \FONTS directory to your hard disk in its entirety. Use the MS-DOS XCOPY command to do this. You will find this directory on the Device Driver Samples and Tools. The 3.x proportional system fonts are hand tuned for the screen and match the Adobe font widths for their Helvetica font. If you need to adapt the system font for a display with a different horizontal resolution than the ones supported by these fonts, you need to adjust the font widths accordingly. This will ensure the character will best "copy fit" the printed character with those on the screen. You can modify these files with the Font Editor tool provided with the SDK. Before you will be able to build any fonts, you must make the FONTS.OBJ file. You do this by running: MASM FONTS; from the \FONTS directory. You only need to do this once. To build the proportional system font files, execute the Makefile by using NMAKE from the \FONTS\SYSTEM directory: The font file names for the new proportional system fonts are: CGASYS.FON for (640 x 200) CGA resolution EGASYS.FON for (640 x 350) EGA high resolution VGASYS.FON for (640 x 480) VGA resolution 8514SYS.FON for (1024 x 768) 8514/a resolution In addition to the 3.x system font, the Windows 2.0 fixed pitch system font is necessary for older Windows applications running under Windows 3.0 and 3.1. All Windows applications which are not "marked" to run with the new proportional font, or which were not developed as a Windows 3.x application, will be given the fixed pitch font for displaying text in dialog and message boxes, and the client area. Windows 3.x supports both of these files, so it may be necessary for you to also modify the appropriate fixed pitch font. You will find these fonts in the \FONTS\FIXED directory. The Makefile is executed from this directory by running NMAKE. The font file names for the 2.0 fixed pitch system fonts are: CGAFIX.FON for (640 x 200) CGA resolution EGAFIX.FON for (640 x 350) EGA high resolution VGAFIX.FON for (640 x 480) VGA resolution (square pixels) 8514FIX.FON for (1024 x 768) 8514/a resolution (square pixels) 8514OEM.FON Uses the OEM Character Set CGAOEM.FON Uses the OEM Character Set EGAOEM.FON Uses the OEM Character Set VGAOEM.FON Uses the OEM Character Set VGA850.FON Uses Code Page 850 VGA860.FON Uses Code Page 860 VGA861.FON Uses Code Page 861 VGA863.FON Uses Code Page 863 VGA865.FON Uses Code Page 865 Printer Driver Sources ********************** We are providing driver sources for our PCL5/HP LaserJet III and Postscript printer drivers. In additional, sample sources for dot-matrix black/white and color raster printers are also included. Building "Minidriver" Printer Drivers ************************************* In order to build the printer drivers created by UNITOOL.EXE from the Minidriver disk, make sure to install the include & library files into the first directory on your LIB and INCLUDE MS-DOS environment variables. PCL5/HP LaserJet III Printer driver *********************************** The PCL5/HP LaserJet III driver sources are being provided as an example of how to support the dynamic downloading of TrueType fonts as well as the new ResetDC API on PCL-type laser device. It now does printer memory tracking as well. The PCL5/HP LaserJet III core driver sources are on the Device Driver Samples and Tools Disk Set under \PRINTERS\HPPCL5A. The HPPCL5A directory contains subdirectories necessary for building the driver. You can build the driver by running the MAKEIT.BAT batch file from the ..\HPPCL5A directory. NOTE: Be sure to maximize the amount of conventional memory available when building this driver. We recommend using MS-DOS Version 5.0 to provide as much conventional memory as possible. The PFM Editor (PFMEDIT.EXE) for PCL fonts is documented in the Printer and Fonts Kit and is provided on the Device Driver Samples and Tools Disk Set under \TOOLS. The PFM Editor is for editing PCL fonts files that use the 3.0 PFM font file format. Please note that the PFM font files that are used with the Universal driver for PCL devices uses a new updated 3.1 file format and they are modified via the UniTool tool. If you want to use these 3.1 format PFM files with the PFM editor, you must first run them through a file converter we provide, CVTHPPFM.EXE which is provided under the \TOOLS directory. This is a simple DOS utility that takes as its first parameter the 3.1 PFM Font file and creates a new 3.0 PFM font file with the name specified in the second parameter. The Printer Font Installer source is on the Device Driver Samples and Tools Disk Set under \PRINTERS\FINSTALL. You can build the font installer by running the MAKEIT.BAT file from the ..\FINSTALL directory. This module is called by selecting the "Fonts..." button in the HPPCL5A driver dialog box. The HPPCL5A driver and the Printer Font Installer are being provided to serve as a base for your Windows 3.1 printer driver development. PostScript Printer driver version 3.5 ************************************* The PostScript driver is also a good example of how to support the downloading of TrueType fonts on a PostScript printer. It also provides the ability to map TrueType fonts to Type 1 fonts in your PostScript printer. In addition, several other new features have been added: the ability to specify the resolution, per page downloading of fonts, setting the half-tone frequency, setting the halftone angle, printing a negative image, printing a mirror image, generating output that conforms to the Adobe Structured Document conventions and others. The driver dialogs have also been updated to better conform to the suggested design conventions for printer dialog boxes, according to the Microsoft Style Guide. The driver sources are on the Device Driver Samples and Tools Disk Sets under \PRINTERS\PS35. To build the driver execute the Makefile by running NMAKE. It is likely that you may run out of memory in building the driver. To prevent this, run NMAKE in the RES and UTILS subdirectories prior to running NMAKE in the PS35 directory. To build this driver, you will need to be sure to install the Alternate Math Small libraries during the SDK Install. The name of the needed library is SDLLCAW.LIB NOTE: Be sure to maximize the amount of conventional memory available when building this driver. We recommend using MS-DOS Version 5.0 to provide as much conventional memory as possible. The PostScript driver is designed to make it easy to add new device support, without modifying the source files. Provided in the DDK is a tool called MKPRN.EXE. You use this tool to compile PostScript Printer Description (PPD) files into Windows Printer Description (WPD) files. You can then install .WPD files for the PostScript driver by creating a driver distribution disk just as for any other printer driver. There is no longer an "Add Printer" option in the driver's Print Setup dialog box. Refer to the file CONTROL.INF in the Windows SYSTEM subdirectory to see an example of how to create the WPD entry for an OEMSETUP.INF file for installing unlisted PostScript models. The MKPRN.EXE tool is on Device Driver Samples and Tools under \TOOLS. Generic / Text Only Driver (TTY) Sample Sources *********************************************** Sample sources for the Generic / Text Only driver are included in this kit. You can use the Generic / Text Only printer driver with any printer for printing text with no graphics. Since this driver uses the printer's internal character set (or sets), it is a convenient driver for printing quick drafts of large documents or spreadsheets. The files are on the Device Driver Samples and Tools Disk Set under \PRINTERS\TTY. To build the TTY driver execute the Makefile under \PRINTERS\TTY using the NMAKE utility. Keyboard Driver Sources *********************** The keyboard sources are on the Device Driver Samples and Tools Disk Set under \KEYBOARD. There is a batch file provided to build the IBM style keyboard driver and all the international tables for foreign keyboards. They keyboard driver structure has not been changed since Windows 3.0. To build the drivers, execute the Makefile by running NMAKE in the \KEYBOARD directory. Please note that this makefile builds the driver file KBD.DRV. This driver is renamed to KEYBOARD.DRV in Windows 3.1. Mouse Driver Sources ******************** The Microsoft Mouse drive sources are on the Device Driver Samples and Tools Disk Set . Copy all the files from the \MOUSE directory to your hard disk with the MS-DOS XCOPY or COPY command. Be sure to expand the compressed files to their original size before using them. To build the driver, run: NMAKE in the \MOUSE directory. The mouse driver has few changes from the version shipped with the Windows 3.0 DDK. No changes are expected, except bug fixes. Note that this driver will not binary compare with the Mouse driver provided with Windows 3.1 since this driver contains proprietary source code. COMM Driver Sources ******************* The COMM driver sources are on the Device Driver Samples and Tools Disk Set. Copy all the files from the \COMM directory to your hard disk with the MS-DOS XCOPY command. Be sure to expand the compressed files to their original size before using them. To build the driver, execute the Makefile by running the Nmake utility. This driver requires the include file INT31.INC. You will need to copy this file from the Virtual Devices and Tools Disk Set from the \INCLUDE directory. Make sure this file is in your include path. Sound Driver Sources ******************** The sound driver sources are on the Device Driver Samples and Tools Disk Set. Copy all the files from the \SOUND directory to your hard disk with the MS-DOS XCOPY or COPY command. Be sure to expand the compressed files to their original size before using them. To build the driver, execute the Makefile by running the Nmake utility. The sound driver has few changes from the version shipped with the Windows 3.0 DDK. The driver was only modified for bug fixes. Network Driver Sources ********************** The MS-Net network driver sources are on the Device Driver Samples and Tools Disk Set. Copy all the files from the \NET directory to your hard disk with the MS-DOS XCOPY or COPY command. Be sure to expand the compressed files to their original size before using them. To build the driver, execute the Makefile by running the Nmake utility. Appendix B: Description of Virtual Device Sources ************************************************** Each source directory contains one or more .ASM source files, a .DEF file, and a Makefile. The Makefile is for use with Microsoft NMAKE or with other Unix-style MAKE utilities. Note, NMAKE is not provided in the DDK, but is included with some of the Microsoft language products (for example,C 6.00A). These MAKE files offer examples of the proper uses of the tools, options, and general build procedures that should be followed in developing virtual devices. As mentioned previously, these sources are provided for you to begin development for Windows 3.1 386 enhanced mode virtual device support. The Display Devices (CGA, EGA, VGA, 8514, HERC, V7VGA) ****************************************************** This device virtualizes the video display and is the most complex of the devices supplied in the DDK. The various VDD sources are on the Virtual Device Samples and Tools Disk Sets under the directories \VDDCGA, \VDDEGA ,\VDDVGA, \VDDHERC, and \VDDV7VGA. The \VDDCGA source tree contains files to only build the CGA VDD. This VDD also provides support for the Compaq Plasma display (also called IDC). The \VDDEGA source tree contains files to only build the VDDEGA. The \VDDVGA source tree provided uses conditional assembly to build two separate virtual devices to handle standard VGA and 8514/a video adapters. The \VDDHERC source tree contains files to only build the Hercules VDD. The \VDDV7VGA source tree contains files to only build the Video 7 VDD. You will find different Makefiles for each of the VDDs in the appropriate directories mentioned above. Listed below are the Makefile names for each VDD: * Adapter NMAKE * CGA MAKEFILE EGA MAKEFILE VGA MAKEVGA 8514 MAKE8514 Hercules MAKEFILE Video 7 MAKEVGA NMAKE by default will use the "Makefile" file to process. You can also specify the Makefile to use by using the /F parameter. The VGA and 8514 Makefiles are located in the same directory and so they have different names for the Makefile. The Display/Windows Interface (GRABBER) *************************************** The grabbers for 386 enhanced mode are different than the grabbers run in real or standard modes. They are responsible for rendering a virtual machine's display context within a window; therefore, they are closely bound with the virtual display device (VDD). Each VDD needs to be accompanied by its own grabber as a linked pair. The sources are on the Virtual Device Samples and Tools Disk Sets under the \GRABBERS directory structure. The DDK contains source for CGA, EGA, VGA, 8514/a, Compaq Plasma, Hercules, and Video 7 grabbers. Since they are all built in the same directory, different Makefiles are provided for each of them. Below are the Makefile names for each grabber: * Adapter NMAKE * CGA MAKECGA. EGA MAKEFILE. VGA MAKEVGA. 8514 MAKEDIB. Hercules MAKEHERC. AT&T/Compaq MAKEPLSM. Video 7 MKV7. NMAKE by default will use the "Makefile" file to process. You can also specify the Makefile to use by using the /F parameter. These Makefiles require that the CMACROS.INC include file be located in the \GRABBERS directory. This file is provided in the \OEMFONTS directory. The font files used by the grabbers when running in a window are provided in this kit. You will find them on disk 2 under \OEMFONTS. Run the Nmake utility to execute the Makefile here. The DMA Device (VDMAD) ********************** This device handles direct memory access devices. Virtual devices can support hardware cards which use DMA by calling the DMA Services provided by the VDMAD. These services are documented in the DDK documentation. See the section on the Floppy Drive Device, for an example of a device which uses the DMA Services. The VDMAD itself should not normally need to be customized; it would only need to be altered to support DMA on machines with non-standard architectures. The sources are on the Virtual Device Samples and Tools Disk Set under the \VDMAD directory structure. The EBIOS Device (EBIOS) ************************ This device detects the EBIOS page on machines (such as the PS/2) where it is used, identifies it, and ensures that it is reserved as global memory. It will probably not need to be modified, but is provided here as an example of a relatively simple device which passively accommodates something in the environment. The sources are on the Virtual Device Samples and Tools Disk Set under the \EBIOS directory structure. The Keyboard Device (VKD) ************************* This is one of the more complicated devices, as it not only virtualizes the keyboard but also interacts with the Windows shell to handle hotkeys and other special functions. It should be modified to support other, nonstandard keyboards. The sources are on the Virtual Device Samples and Tools Disk Set under the \VKD directory structure. The Mouse Device (VMD) ********************** This device virtualizes the mouse and maps the INT 33H API between protect and virtual modes. The sources are on the Virtual Device Samples and Tools Disk Set under the \VMD directory structure. The Netbios Device (VNETBIOS) ***************************** This device maps the Netbios API between protect and virtual modes, allowing Windows applications to access the network. It also handles asynchronous network transactions by mapping the application's buffer into global memory, so the network software can access it when the asynchronous event occurs (even if another virtual machine is running at the time). This should be modified by network vendors who extend the standard NetBIOS interface and also serve as a guide to writing virtual devices for other types of network software. The sources are on the Virtual Device Samples and Tools Disk Set under the \VNETBIOS directory structure. The Network Device (LDOSNET) **************************** In general, this device manages network connections and assures network integrity across all virtual machines. This device is not part of the Windows 3.1 retail package. It is provided as a sample source to demonstrate some mechanisms used in supporting network functionality. The device should be modified when your software does not use standard MS-DOS redirector calls for handling network connections. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \LDOSNET directory. The BIOS Device (BIOSXLAT) ************************** This device maps the ROM BIOS API between protected mode and virtual 8086 mode, allowing Windows applications and device drivers access to ROM BIOS services. This should be modified when there are non-standard ROM BIOS calls that pass pointers to memory and which are used by Windows applications or device drives. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \BIOSXLAT directory, The Paging Device (PAGESWAP) **************************** This device is used by 386 enhanced mode for demand paging at either the INT 21H or INT 13H level. The sources are on the Virtual Device Samples and Tools Disk Set under the \PAGESWAP directory structure. The Printer Device (VPD) ************************ The Printer Device virtualizes access to the parallel ports. If a second virtual machine tries to access one of the ports while it is being used by another application, a contention dialog is presented to the user allowing them to resolve the dispute of ownership. This virtual device was installed by default in Windows 3.0 but is no longer used with Windows 3.1. It is a simple VxD and is used as an example in the Virtual Device Adaptation Guide. The sources are on the Virtual Device Samples and Tools Disk Set under the \VPD directory structure. The COMM Device (VCD) ********************* This device virtualizes the standard serial ports on ISA architecture machines. It supports COM1 through COM4. It should be modified to add support for different chip sets or for additional COM ports. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \VCD directory. The Virtual COMM Device (COMBUFF) ********************************* This device works with the Vitual COMM Device (VCD) to buffer com input for MS-DOS Virtual Machines. It supports COM1 through COM4. It can be modified to provide other handshaking protocols, or just used as sample source for virtualizing COM ports by cooperating with VCD. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \COMBUFF directory. The Floppy Drive Device (VFD) ***************************** This device is responsible for two things: -- It removes special timer port trappings to ensure copy protection schemes work properly. -- It communicates with the VDMAD to synchronize DMA channel usage. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \VFD directory. The 386 Enhanced Mode Block Device (WDCTRL) ******************************************* This virtual device is used to talk directly to hard-drive controllers that are Western Digital 1003 compatible. This allows us to do disk i/o entirely in ring 0 protected mode, bypassing the real mode BIOS. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \WDCTRL directory. The PageFile Device (PAGEFILE) ****************************** This virtual device handles our virtual memory paging file, and will always call through BlockDev if any FastDisk devices are available. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \PAGEFILE directory. The INT13 Virtual Device (INT13) ******************************** The Int13 device is used in conjunction with the 386 Enhanced Mode Block Device. It traps and emulates Int 13h BIOS calls. You will find the sources on the Virtual Device Samples and Tools Disk Set under the \INT13 directory.
Welcome to Microsoft Windows DDK Chinese Edition 3.1, the DDKE 3.1. This file gives some issues you should know to use the DDKE 3.1. 1.Environment: To use DDKE 3.1, you should have already installed the C compiler, SDK 3.1, DDK 3.1, and SDKE 3.1. You should set the PATH variable to use the correct version of tools. If a tool is provided both by DDKE 3.1 and other packages, set PATH appropriately to use the one provided by DDKE 3.1. This is also true for LIB and INCLUDE environment variables 2.Compression: Files in DDKE are not compressed. 3.To build a sample: Just go to its directroy, enter NMAKE. 4.Conventional memory consideration: The size of available conventional memory is a critical factor while building large project, such as driver program. You should configure your system to reserve as many conventional memory as possible. For example, load COMMAND.COM in high memory, remove TSR programs, etc. See the MS-DOS reference for this consideration. Also, different version of tools may require different amount of memory to work. The NMAME.EXE in the directory of TOOLS of diskette 1 is an apparent example for this. If you encounter momory problem in making a sample, try to copy this NAMEK.EXE into your disk and set path to use this tool. *note: The Setup program will update the NMAKE.EXE in your SDK/DDK directories automatically. So if you set PATH to access tools in your SDK/DDK first, this will not cause problem. 5.Contents of DDKE ----------------- This is the DDKE Sample Source tree: +-- README.TXT This file | +-- SETUP.EXE The batch file to help setup DDKE | +-- FONTS\ | | | +--FIXED\ VGA, EGA & 8514 fixed fonts | | | +--SYSTEM\ VGA, EGA & 8514 system fonts | +-- GRABBERS\ Grabber sample codes for VGA & HERC | +--MINIDRIV\ The mini-drive sample code | +--PSCRIPT\ The PostScript printer driver sample code | +-- VXD\ Virtual Device Sample codes | +-- WIFE-FD\ WIFE font driver sample source code | +-- TOOLS | +-- INCLUDE | +-- LIB After installing DDKE into the DDK tree, say, WINDEV\ This is the DDKE Sample Source tree: +-- README.TXT This file | +-- SETUP.EXE The batch file to help setup DDKE | +-- CFONTS\ | | | +--FIXED\ VGA, EGA & 8514 fixed fonts | | | +--SYSTEM\ VGA, EGA & 8514 system fonts | +-- CGRABBRS\ Grabber sample codes for VGA & HERC | +-- MINIDRIV\ The mini-drive sample code | +-- CPSCRIPT\ The PostScript printer driver sample code | +-- CVXD\ Virtual Device Sample codes | +-- WIFE-FD\ WIFE font driver sample source code | +-- INCLUDE | +-- LIB
MICROSOFT WINDOWS SOUND SYSTEM (Version 1.0)
Copyright (C) 1991-1992 Microsoft Corporation
This document contains information that supplements the "Microsoft
Windows Sound System User's Guide" and accompanying software.
CONTENTS
I. Before you run the Microsoft Windows Sound System (WSS) Setup
1. Other sound boards
2. Switching to Windows Program Manager
II. Troubleshooting
III. Voice Pilot
IV. ProofReader
1. Multiple instances
2. Installation sequence
3. Removing or reinstalling ProofReader
V. Compatibility issues
1. WSS and other boards
2. WSS and MIDI sequencing software
VI. Modifications to the WSS User's Guide information
VII. Removing WSS from your system
_____________________________________________________________________
I. Before you run the Microsoft Windows Sound System Setup
1. Other sound boards
Before installing the Microsoft Windows Sound System, open the
Windows Control Panel icon and double-click the Drivers icon.
If the list of installed drivers includes the Ad Lib,
Sound Blaster, or Pro Audio Spectrum drivers, we suggest
that you remove them by selecting the driver and clicking the Remove
button.
2. Switching to Windows Program Manager:
If you run out of disk space during Setup and need to delete some
files, you can switch to Windows Program Manager without exiting
Setup in two ways:
a.) Press Alt+Tab and choose the Windows Program Manager icon;
b.) Press Ctrl+Esc, select Program Manager from the task list and
click the Switch To button.
Follow step a or b again to switch from Program Manager back to
WSS Setup.
__________________________________________________________________________
II. Troubleshooting
1. If you get a continuous sound repeated over and over again when you
choose the Check option and click the Sound Check button in
Setup, one of two things could be wrong:
a.) You did not remove the Ad Lib driver as described in section I.1.
above.
b.) You have one or more conflicting interrupts (IRQ). From WSS
Setup, choose the Board option and change the interrupt (IRQ) value
for your board.
2. If you do not hear any sound in Sound Finder or in the Guided Tour,
or if Music Box does not find your CD-ROM drive, make sure you have
the following entries:
a.) In your WIN.INI file in your Windows 3.1 directory:
[MCI extensions]
wav=waveaudio
mid=sequencer
rmi=sequencer
b.) In your SYSTEM.INI file in your Windows 3.1 directory:
[MCI]
CDAudio=mcicda.drv
WaveAudio=mciwave.drv
Sequencer=mciseq.drv
c.) Make sure that you have the following files in your Windows 3.1
system directory:
MCICDA.DRV
MCIWAVE.DRV
MCISEQ.DRV
3. If you're running a shared installation of Windows over a network,
you won't be able to play MIDI files.
__________________________________________________________________________
III. Voice Pilot
You can improve recognition results by changing the
recording level in the Windows Sound System Recording Control
application. If the level is too high, recognition will be poor.
You can access Recording Control through the Input Level
button in the Options dialog box.
As a keyboard alternative to clicking the Microphone button, press
Ctrl+Alt.
If stray noises are frequently recognized as words, you can increase
the recognition threshold by using the Sounds Must Match Words
slider control in the Options dialog box.
As a shortcut for training, editing, or deleting an item, click
the item in the Active Words list, and then choose a command from the
pop-up menu.
To move quickly to a word in the list in the Vocabulary dialog box, first
click the list, and then type the first letter of the word.
Continue typing the same letter until the highlight reaches the
desired word.
Voice Pilot can have difficulty recognizing shorter words, even after
training. If this happens, you can add longer words or phrases to the
vocabulary which perform the same actions.
__________________________________________________________________________
IV. ProofReader
1. Multiple instances:
If you run more than one instance of Microsoft Excel or Lotus 1-2-3
for Windows, only the first instance of it will contain the ProofReader.
2. Installation sequence:
You must install your Windows spreadsheet package before you run the
WSS Setup program to install the ProofReader.
3. Removing or reinstalling ProofReader:
To remove or reinstall ProofReader from Microsoft Excel, please
follow your Microsoft Excel documentation on how to remove or install
the "ProofReader For Excel" add-in.
To remove or reinstall ProofReader for Lotus 1-2-3 for Windows,
please follow your Lotus 1-2-3 for Windows documentation on how to
remove or install the "123RDR" add-in.
__________________________________________________________________________
V. Compatibility issues
1. The Microsoft Windows Sound System board may not work with other
sound boards. We recommend that you remove all other sound drivers
from the Windows Control Panel Drivers application and remove other
sound boards from your machine.
The synthesis chip on the WSS board can conflict with those on other
sound boards.
If you use multiple sound boards and drivers, you can encounter
interrupt (IRQ), I/O address, and/or DMA channel conflicts which
can cause your system to hang or repeat sounds.
2. Using MIDI Sequencing Software with your WSS Board:
There are some known incompatibilities with certain Musical
Instrument Digital Interface (MIDI) sequencing software packages.
The WSS Sound Finder cannot play a file with an extension of
.MID or .RMI while a sequencing program is open, regardless of
whether a file is actually loaded into the sequencer. In this
situation, you can play the file through the Windows Sound
System board using either your sequencing program or Sound
Finder. If you would like to use Sound Finder to browse MIDI
files and additional file types as well, close your sequencer before
using Sound Finder. You should find that Sound Finder now plays MIDI
files without a problem.
If you experience difficulties using your MIDI sequencer with
your WSS board:
i.) Consult the WSS documentation to ensure you have properly
installed and configured both the board and the software.
ii.) Consult your sequencer's documentation for additional assistance.
iii.) If you are still experiencing problems, contact Microsoft
Product Support Services.
________________________________________________________________________
VI. Modifications to the WSS User's Guide information
1. When you double-click on a file in Windows File Manager, the
file is not loaded into Sound Finder. Instead, the file is loaded into
Quick Recorder.
2. After performing a Paste Mix command in Quick Recorder, the Undo command
works correctly.
__________________________________________________________________________
VII. Removing WSS from your system
If you ever want to remove everything associated with the Windows
Sound System from your machine, there is a file called DEINSTAL.TXT
in your WSS directory (c:\sndsys by default) which documents every
file installed, its location, and how to remove it from
your system.
Icon Hear-It Icon Hear-It
Version 1.0
July 25, 1992
Welcome to version 1.0 of Icon Hear-It.
Please read through this Readme.txt file. It contains important information
not available when the manual was printed.
Icon Do-It Users
Icon Hear-It replaces Icon Do-It during installation. Since Icon
Hear-It contains all the functions of Icon Do-It plus more, you can simply
erase Icon Do-It from your hard drive.
Sound
If you do not hear any sound please try assigning the sound again.
If that doesn't work, check and make sure the HEARITFX
directory exists beneath Windows and that the TASOUNDS directory exists
beneath ICONHEAR. The TASOUNDS directory CANNOT be moved, nor can the
files beneath it be deleted. You will lose your talking applications
if Icon Hear-It cannot find these sound files.
You can erase all or some of the files in HEARITFX without damaging
Icon Hear-It. But, you will lose any of the preattached sounds whose
file you have deleted or moved. However, after relocating this directory
you can reattach these sounds.
Icon Hear-It supports all .wav files. You can use your own sounds
with Icon Hear-It by clicking through the directory list boxes to the
directory that contains your .wav files and following the instructions
outlined in the User's Guide for attaching sounds.
Sound Board Not Being Used
If you have a sound board installed (i.e. Sound Blaster, Ad Lib,
Thunder Board, etc) and the sounds are still being played through
the PC Speaker:
1. Go into Control Panel, then Drivers.
2. Check to make sure your sound driver is installed.
3. Remove the Sound Driver for PC-Speaker.
You will be prompted that this sound driver is required by your system,
do you really want to remove it. Click Yes. You will then be asked
if you want to restart Windows, also Click Yes.
If you are still not getting sound through your sound card you will
need to edit your SYSTEM.INI file located in your Windows directory.
You can use NOTEPAD or DOS EDIT to do this.
Towards the bottom of this file, you will see a section similar to the
following:
[drivers]
Wave=mvspeakr.drv
Replace the words mvspeaker.drv with the name of your speaker driver.
Then, save the file and restart Windows.
Adding Push Buttons
If you add a push button and give it a sound, you will see it in the
Track All Icon Hear-It Sounds window. But, if you unattach the sound,
the push button will be removed from this list. The preattached push buttons will
always remain in the list whether you unassign their sounds or not.
Speaker Driver Setup
The Speaker Driver Setup push button in the Options Window works ONLY with
the speaker driver installed with Icon Hear-It. When loading, if
Icon Hear-It detects a sound board or speaker driver already on your
system, it will not allow you to use it Speaker Setup.
If you do not have a sound board or other speaker driver installed
and you still can't access the Speaker Driver Setup, you need to edit your
system.ini file and remove the line :
Wave= speakerdrivername
from underneath the [Drivers] section. The next time Icon Hear-It loads,
it will write a new "Wave = " with its own speaker driver.
DOS Applications that Use Sound
If you have attached a sound to an icon for a DOS based application
that uses sound, you may get an error messager saying your sound card
is in use by another program. This is happening because the DOS
application accesses the sound board directly and if it is in use
by Windows, (which it would be if it was playing the sound attached
to the icon) it cannot be accessed again by DOS.
==========================================================
Companion Disk for
MICROSOFT WINDOWS 3.1 DEVELOPER'S WORKSHOP
(C) 1993 Microsoft Press
==========================================================
This companion disk contains all source code, include files,
executable files, and other files for the examples presented
in Microsoft Windows 3.1 Developer's Workshop. For your
convenience, the files are organized into six directories whose
names correspond to the authors of the book's articles:
\hall Internationalizing Windows Software by Bill Hall
\chivertn Zooming, Coordinate Spaces, and Transformations:
from Win16 to Win32 by Bob Chiverton
\butler Programming Windows for Pen Computing by John Butler
\sinha NetBIOS Programming by Alok Sinha
\patch Developing Virtual Device Drivers by Ray Patch
\craig Visual Basic as a Professional Tool by John Clark Craig
NOTE: If you haven't done so already, please make a backup
copy of this disk before proceeding any further! We also
recommend that you slide the write-enable tab on the disk to
the open position and store the disk in a safe place.
To install this disk, create a directory on your hard disk
and copy the disk to the directory. For example:
c:
mkdir windev
xcopy a:\*.* windev /s
To compile these examples, you must have installed the
Microsoft C/C++ 7.0 compiler (or Microsoft C 6.0) and
libraries and the Microsoft Windows 3.1 SDK. The Visual Basic
programs offered in John Clark Craig's article were compiled
with Visual Basic 2.0. However, they are all compatible with
Visual Basic 1.0.
Every effort was made to ensure the accuracy of the book and
this disk. Should you encounter a problem, please contact
us at the following address:
Microsoft Press
Attn: Microsoft Windows 3.1 Developer's Workshop Editor
One Microsoft Way
Redmond, WA 98052-6399
No telephone calls, please.