SETUP.TXT: Microsoft Windows & MS-DOS 5 Upgrade

• Microsoft Windows & MS-DOS 5 Upgrade

SUMMARY

The following information was taken from the Windows & MS-DOS 5 Upgrade SETUP.TXT file.

MORE INFORMATION

MICROSOFT WINDOWS 3.1 & MS-DOS 5 UPGRADE

SETUP.TXT

This file provides important information not included in the "Microsoft Getting Started" manual, the "Microsoft MS-DOS User's Guide and Reference," the "Windows User's Guide" or in online Help.

Specifically, this file contains information about problems that might occur while running the Windows and MS-DOS Setup program and describes problems that can occur when using terminate-and-stay-resident (TSR) programs or drivers with Windows or the Windows and MS-DOS Setup program. If you are using a TSR or if you encounter problems setting up Windows version 3.1, read this document BEFORE running Setup again.

For information about other files and documentation, see the "Welcome" section of "Getting Started."

Note: Within this document, "Windows Setup" refers to the Windows part of the Windows and MS-DOS Setup program. You can execute the Windows only part of this program by following the instructions below:

When this file instructs you to run Windows Setup, do the following:

--If this file instructs you to run Setup from the Main Group within

  the Windows Program Manager, carry out the procedure as stated.

  carry out the procedure described in "Getting Started."

  file does not instruct you to run Setup from the Main Group,
  carry out the following procedure to run Setup for Windows only:

  1. Make drive C your current drive.
  2. Insert Setup Disk #1 into drive A.
  3. Type the following at the command prompt:
        a:setup /w

  This procedure for running a "Windows only" setup after MS-DOS has
  been installed is also described in Appendix A of "Getting Started."

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.

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 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 the Windows and MS-DOS Setup program. 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 "You have special hardware to set up with Windows" in Chapter 3, "Troubleshooting During Setup," in "Getting Started."

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.

  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.

  Multimedia Extensions version 1.0)

- 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

      Orchid Fahrenheit 1280
      STB WIND/X
      Diamond Stealth VRAM

Using Stacker

   instructions, see section 2.21 of the README.TXT file.

   Windows only on a computer with an older version of Stacker,
   your computer might halt on Setup disk 3 while it is analyzing
   your system software. If this happens, remove the Setup disk,
   restart your computer by pressing CTRL+ALT+DEL, and run
   Setup again by typing the following at the command prompt:

   a:setup /w /c

   Note: Before you run Setup again, make sure all the commands
         that load memory-resident programs have been disabled
         in your AUTOEXEC.BAT and CONFIG.SYS files. To disable
         a command, type "rem" and a space in front of the command
         in your CONFIG.SYS and AUTOEXEC.BAT file. Then save the file,
         and restart your computer.

   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. For more information about
   swap files, see "Working with Windows Swap Files" in Chapter 14,
   "Optimizing Windows," in the "Microsoft Windows User's Guide."

   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.

   Stacker 2.0 or later, choose the Custom Setup option
   when you run Setup. When Setup prompts you, don't choose to let
   Setup modify your CONFIG.SYS and AUTOEXEC.BAT files. Modify
   these files yourself after Setup is complete by carrying out
   the following steps:

   * In your AUTOEXEC.BAT, add Windows to your path.

   * Copy the HIMEM.SYS and EMM386.EXE files to your
     uncompressed drive, unless you use a different memory
     manager, such as QEMM-386.

   * Add DEVICE commands for HIMEM.SYS and EMM386.EXE to
     your CONFIG.SYS file, unless you use a different memory
     manager such as QEMM-386. The command lines that load
     these drivers should appear before the command that loads
     STACKER.COM.

   * Make sure a copy of SMARTDRV.EXE is on the
     uncompressed drive. In your CONFIG.SYS file, the
     SMARTDRV.EXE command line should include the
     "/double_buffer" switch and should be the path
     of the file at boot time. For example, if SMARTDRV.EXE
     is in the root directory at boot time, you would include
     the following command in your CONFIG.SYS:

     DEVICE=C:\SMARTDRV.EXE /DOUBLE_BUFFER

     SMARTDRV.EXE should be loaded before STACKER.COM in the
     CONFIG.SYS file.

   * In the AUTOEXEC.BAT file, the SMARTDRV.EXE command
     line should be the path of the file after disk drives
     are swapped. Also, add the /L switch to the SMARTDRV.EXE
     command in your AUTOEXEC.BAT file.

   upgrade from Stacker version 1.1, choose the Express Setup
   option when you are prompted. Setup will modify your CONFIG.SYS
   and AUTOEXEC.BAT files for you. When Setup is finished making
   the modifications, it displays a message at the end
   of the Windows portion of Setup that notifies you of the
   modifications that have been made. 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. Choose Yes.

   need to modify your CONFIG.SYS and AUTOEXEC.BAT files
   yourself, using the CONFIG.WIN and AUTOEXEC.WIN files that
   Setup generates. For information about using these files,
   see "Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself,"
   following this topic.

   the command prompt to set up Windows:

   a:setup /w

Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself

- Your boot drive has been modified by a disk-compression

  utility.

  drivers.

  copy the files.

  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, the Windows and MS-DOS Setup program 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

* 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.

   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.

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.

   network in the System-Information screen.

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, the Windows portion of 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.

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

386MAX

See the README.WRI online document for more information about running 386MAX with Windows 3.1.

386MAX Disk-Cache Utility (QCACHE.EXE)

All Charge 386 Version 3.1

Anarkey Version 4.00

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

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)

ASP Integrity Toolkit Version 3.7

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.

ASSIGN.COM

assign

Autocon Version 2.0e

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

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.

Bootsafe

1 Open your AUTOEXEC.BAT with any text editor. 2 Type "REM" and a space in front of the line that loads

     Bootsafe. For example, the line might look something like this:

     rem c:\cpav\bootsafe

     CTRL+ALT+DEL.

CACHE.EXE Disk-Cache Utility

CACHE.SYS Disk-Cache Utility

CED Version 1.0e

Central Point Anti-Virus Version 1.1 (VSAFE.COM/VSAFE.SYS)

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)

Cubit Version 3.01

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)

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

Doubledisk Version 2.5

FASTOPEN (MS-DOS)

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)

HIMEMSLS.SYS (Software Carousel)

If you use the HIMEMSLS.SYS driver with Software Carousel, open your CONFIG.SYS with any text editor, and delete the command that loads the driver. Then save the file, restart your system, and run Setup.

Setup will install the HIMEM.SYS driver when it installs Windows. Use the HIMEM.SYS driver; do not reinstall the HIMEMSLS.SYS driver.

HPEMM386.SYS and HPEMM486.SYS

HPMM.SYS - HP Memory Manager

Hyperdisk Disk-Cache Utility

IBM VDISK.SYS (RAM Disk Utility)

IEMM.SYS Memory Manager

ICACHE.SYS Disk-Cache Utility

IBMCACHE.SYS Disk-Cache Utility

Intel Expanded-Memory Emulator (ILIM386.SYS)

JOIN (MS-DOS)

KBFLOW TSR by Artisoft

KEYB.COM (MS-DOS)

Lansight Version 2.0

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

LOCKIT Version 3.3 (PC Vault, Secure It)

Logitech Mouse Software Version 5.0/6.0 (CLICK, LOGIMENU)

Mace Disk-Cache Utility (MCACHE.SYS)

Maximizer Memory Manager (MAXIMIZE.COM)

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)

NetRoom Memory Manager (RM386.SYS)

Newspace Version 1.07

Norton Anti-Virus Version 1.0

Norton Desktop for Windows (EP.EXE)

Norton Utilities Version 5.0 (DISKREET, NCACHE)

Norton Utilities Version. 6.01 (NCACHE)

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

PCKEY.EXE (MultiSoft Keyboard Enhancer and Command-Line Stack)

PC-Kwik Disk Accelerator

PC-Kwik Disk-Cache Utility (PC-KWIK.EXE)

PC-Kwik Version. 1.59 (PCK.EXE, PSKSCRN.EXE, PCKEY.COM)

PCSXMAEM.SYS Utility

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)

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)

Printer Assist Version 4.20

PYRO! Version 1.0

QMAPS Memory Manager Version 5.16

RAMTYPE.SYS - AST RAMpage! Boards

   rem RAMTYPE.SYS

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)

SideKick Versions 1.0 and 2.0 and SideKick Plus

SoftIce Debugger

SpeedFXR

SUBST (MS-DOS)

Super PC-Kwik Disk-Cache Utility (SUPERPCK.EXE)

Trantor T100 Host Adapter Driver (TSCSI.SYS)

UMB PRO Version 1.07

Vaccine

VIREX-PC Version 1.11

Virus Prevention Plus Version 5.0

Virusafe Version 4.0

XGAAIDOS.SYS

XMAEM.SYS

XMA2EMS.SYS