SETUP.TXT
=========

This file contains information about problems that may occur while you are
running Windows 95 Setup.

Note: It is recommended that you check your hard disk for viruses before
setting up Windows 95. If you have MS-DOS 6.x, you should run MSAV before
running Setup.

Finding and fixing hard disk problems during Setup (Using ScanDisk)
===================================================================

Windows 95 Setup automatically runs ScanDisk to check for problems on your
hard disk(s). If there are problems, Setup cannot continue until they
are fixed.

NOTE:  The MS-DOS based version of ScanDisk that Setup runs may detect long
file name errors, but it cannot correct them.  These errors will not prevent
Setup from proceeding, but once it completes, you should run the new Windows
version of ScanDisk from within Windows 95 to correct these errors.

Fixing hard disk problems
-------------------------
If you see a message during Setup that says you must run ScanDisk to fix
problems on your hard disk, follow these steps to fix the problems.

If you are setting up Windows 95 over MS-DOS or a previous version of Windows
such as Windows 3.1:

1. Quit Windows.
2. Insert Setup Disk 1 or the Windows CD-ROM into the drive.
3. Type the following line at the command prompt:

        a:scandisk.exe /all

   where "a" is the drive that contains the Windows disk.
4. Follow the instructions on your screen and fix any problems that ScanDisk
   finds.
5. Start Windows, and then run Setup again.

If you are setting up Windows 95 over a previous version of Windows 95:

1. Quit Setup.
2. On the Start menu, point to Programs, point to Accessories, point to 
   System Tools, and then click ScanDisk.
3. Check your hard disk(s) for errors and repair any problems found.

NOTE: If you are running Setup from MS-DOS, ScanDisk will run and you'll be
able to fix most problems from within Setup.


Problems running ScanDisk
-------------------------
If you get a message during Setup saying that there is not enough memory
to run ScanDisk, free some conventional and/or upper memory, and then run
Setup again. If you have MS-DOS 6.x, try running MEMMAKER to free memory.

If you still don't have enough memory, or if you have other problems while
Setup is running ScanDisk, then you can bypass ScanDisk in Setup by running
Setup with the /IS option. Type the following command:

        setup /is

NOTE: It is recommended that you not bypass ScanDisk during Setup. If you do,
there may be problems with your hard disk that could cause Windows 95 to not
install or run correctly.

If you still have problems after running Setup with the /IS option, try 
running Setup with the /IQ option. Type the following command:

        setup /iq


If you have a compressed drive
===============================

If you have used compression software to compress your hard disk you may get
a message saying that there is not enough space on the host partition of the
compressed drive. Setup may have to copy some files to your startup drive,
the host for your startup drive, or the host for your Windows drive. If you
get this message, you should free up some space on the specified drive, and
then run Setup again. Try one of the following:

- If you are setting up Windows on a compressed drive, try setting it up on
  a non-compressed drive if you can.

- If there are files on your host partition that you no longer need, try
  deleting them.

- If you are running Windows 3.1 and have a permanent swapfile, try making
  it smaller. In Control Panel, double-click the 386 Enhanced icon and then
  choose Virtual Memory. Then modify the size of your swapfile.

- Use your disk compression software to free up some space on the host
  drive for the compressed drive. If you compressed your drive with DriveSpace
  or DoubleSpace, follow these steps:

  1. Quit Windows.
  2. Run DRIVESPACE.EXE or DOUBLESPACE.EXE.
  3. Select the compressed drive on whose host you want to free space.
  4. On the Drive menu, choose Change Size.

  If you used other compression software, such as Stacker, consult the
  documentation that came with the compression software.

Note: If you notice a discrepancy in the amount of free space reported by
Setup and the amount of space you think is available on your host drive, it
may be because Windows uses some space for creating a swapfile. This may not
appear to take up any space when Windows is not running. 

Note: If you create a startup disk during Setup, make sure you do not use a
compressed disk for the startup disk.

If you have SuperStor compression
----------------------------------
If you have compressed your hard disk with SuperStor, Setup may not be able
to find your startup drive and install Windows 95. If you get a message about
this during Setup, you should uncompress your disk and remove SuperStor.
Then run Setup again.


If you have XtraDrive compression
----------------------------------
If you have comressed your hard disk with XtraDrive and you are upgrading a
previous version of Windows, Setup will not be able to install Windows 95
unless you turn off XtraDrive's write-cache. To turn this off, follow these
steps:

1. Quit Windows.
2. Run VMU.EXE (XtraDrive's Volume Maintenance Utility).
3. Choose Advanced Options, and then press ENTER.
4. Set the EMS cache size to 0.
5. Set the Conventional cache size to 1 (the minimum).
6. Set Allow Write Caching to NO.
7. At the confirmation prompt, choose Yes. You will see a message saying that
   you must restart your computer for the changes to take effect.
8. Quit Volume Maintenance Utility and restart your computer.
9. Start Windows and then run Setup again.


Installing Windows 95 over Windows NT 
======================================
If you are multi-booting MS-DOS and Windows NT, boot to MS-DOS, and
run Setup from either MS-DOS or Win 3.x.  You will not be able to
install Windows 95 to a directory with a shared Win 3.x/Windows NT
configuration, you will need to install Windows 95 to a different
directory.

If you are not multi-booting MS-DOS and Windows NT, you should
configure your machine to multi-boot MS-DOS and Windows NT first, and
then follow the instructions above.

If you boot MS-DOS from a floppy and run Setup, you will no longer be
able to boot Windows NT (however, you can restore Windows NT by
booting from the Windows NT boot/repair disk, and selecting the
"Repair" option).


Installing Windows 95 over OS/2
==================================
Setup will not run on OS/2.  You will need to boot to MS-DOS and run
Setup from the MS-DOS prompt.

If you are using OS/2 Boot Manager to choose operating systems at
startup, Setup will disable Boot Manager to insure that Windows 95 can
reboot the system and complete its installation. Boot Manager can be
reactivated by booting with an OS/2 boot disk and using the OS/2
FDISK utility (see procedure at the end of this section).

If you are not using Boot Manager, you should configure your machine
to use Boot Manager, and then follow the instructions above.

If you boot MS-DOS from a floppy and run Setup, you will no longer be
able to boot OS/2 after Windows 95 has been installed. You will need to
delete the AUTOEXEC.BAT and CONFIG.SYS files that OS/2 uses before
running Windows 95 Setup.

If you want to remove OS/2 from your computer after you have installed
Windows 95, follow these steps:

1. Back up the data files you want to keep onto a floppy disk or network
   drive.

2. Delete the files in each of your OS/2 directories and subdirectories,
   and then delete the OS/2 directories.

3. In the root directory, the following files are marked as hidden system
   files and need to be deleted:

   EA DATA.SF
   OS2LDR.MSG
   OS2KRNL
   OS2BOOT
   WP DATA.SF

   In My Computer or Windows Explorer, make sure hidden files are visible. To
   do this, click the View menu and then click Options. Then click
   "Show All Files".

   Then delete the OS/2 files listed above.

   Note: If you have a version of OS/2 other than version 2.0, the names of
   the OS/2 files on your hard disk may differ from those that appear in this
   procedure. Also, depending on which version of OS/2 you have, you may see
   the following files in your root directory which you can delete:

        OS2DUMP
        OS2LDR
        OS2LOGO
        OS2VER

4. Remember to empty the Recyle Bin to permanently remove the files from your
   computer.     

5. If you had Boot Manager installed and want to remove it, restart your
   computer and then complete the following steps. (It is recommended that
   you print this file before restarting your computer.)

6. When you see the Boot Manager menu, choose to boot to MS-DOS and run FDisk.

7. Choose to make the MS-DOS partition (C) your "active" partition.

8. Quit FDisk and then restart your computer.


If you want to reinstate Boot Manager after you install Windows 95, follow
these steps.

To reinstate Boot Manager:
1. Start your computer with the OS/2 Installation Diskette.
2. Choose #2 Advanced Installation.
3. Choose "Specify a different drive or partition".
   When you see the warning about modifying partitions press ENTER.
4. Make sure the the Boot Manager partition is set to "Startable".
5. If you see a message warning that one of the partitions must be
   "Installable", set the OS/2 partition to "Installable".
6. Quit FDisk and then restart your computer.


Installing Windows 95 on computers with LANtastic
=================================================

If you are running the LANtastic server, you must disable it before setting
up Windows 95. To disable the LANtastic server, either remove the "server.exe"
line from your AUTOEXEC.BAT file, or type the following command:

        server /remove


If you are running LANtastic, and have either mapped or shared your startup
drive (usually the C drive), Setup will not be able to determine which
drive is your startup drive and will not be able to continue.

Before running Setup, you must disable the mapping or stop sharing your
startup drive.


SETUP ERROR MESSAGES
=====================

This section lists specific messages that you may encounter during Setup and
gives details about the problem and what you should do to fix it.

SU0167
------
If you have a directory called "desktop" in your Windows current Windows
directory, Setup will not be able install Windows 95 into that directory.
Windows 95 creates a directory called "desktop" and uses it for system files.
If you get this message during Setup, you should rename or move your
current "desktop" directory. Then run Setup again.


Standard Mode messages
----------------------
If you get any of the following error messages, you should remove any memory
managers (such as EMM386.exe, QEMM, 386Max) from your CONFIG.SYS file, and
then run Setup again.

Standard Mode: Invalid DPMI return.
Standard Mode: Fault in MS-DOS Extender.
Standard Mode: Bad Fault in MS-DOS Extender.
Standard Mode: Unknown stack in fault dispatcher.
Standard Mode: Stack Overflow.


GENERAL SETUP NOTES
====================

This section includes notes on specific system configurations that may
prevent Setup from installing Windows 95 successfully. A
possible solution to each problem is provided.


Plug And Play Network Cards and 16-bit Real Mode Drivers
--------------------------------------------------------
When you need to run the 16-bit real mode driver for
your NIC (which is common if you use DLC or another real mode
protocol), sometimes your PnP card may appear not to function.
The reason for this is that on most computers, your PnP card remains
inactive until Windows 95 turns on the card.  16-bit NIC drivers, load 
before Windows 95 has a chance to turn on PnP cards.  Some 16-bit 
NIC drivers know nothing about PnP cards (most NE2000 PnP clones fall 
into this category), and this is where you would see a problem.

In order to use your PnP card with a 16-bit NIC driver:
1) Run the softset utility that comes with your PnP card, and set the
card to non-PnP mode.  
2) Remove the net card from the network control panel
3) Readd the card using the Add New Hardware Control Panel applet.

When you move to a 32-bit protect mode NIC driver in the future, you
may rerun softset to turn on PnP mode for your card.

Parallel Port Network Adapters
------------------------------
Any Network adapter that uses a Real Mode network driver and runs off
your Parallel Port might have problems with this release of Windows 95.
These problems will be fixed for final release.  To use your
parallel port adapter, disable the printer port within Device
Manager.  Run the System Control Panel Applet, select the Device Manager
tab.  Look for Ports, Printer Port.  Find the printer port that
corresponds to the port you are using for your adapter, and look at it's
properties.  At the bottom of the page,
uncheck any boxes (this disables the printer port).  If you later want
to print using this port, repeat these steps and check all these boxes.  

Adapters that we know are affected include Xircom PE, PE2, and PE3
Pocket Ethernet Adapters.  Your Xircom PE3 will continue to run properly
with our Protect Mode 32-bit driver.

Intel EtherExpress 16 NICs and PCI machines
-------------------------------------------
You may experience system hangs or initialization problems if you are
using an Intel EtherExpress 16 NIC in a PCI machine with some Diamond
Speed Star PCI video cards.  The following are excerpts from Intel's
Customer Support Database.  These problems are not related to Windows
95, and happen on a variety of operating system platforms.  In
general, if you experience other problems with your EtherExpress 16
in a PCI machine, please attempt to replace the card before reporting
the problem to Microsoft.

If you have one of these video cards, contact your vendor about 
getting a new video BIOS update.

* Diamond Speed Star PCI video card with BIOS version 1.01
* Diamond Viper PCI VGA Video Adapter
* Diamond Stealth video card, Bios v1.03


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 95 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 95
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 95
--------------------------------------------------------------------
Certain third-party display drivers designed for Windows version 3.0 can
cause problems with Windows 95. The most serious
problem is a system failure while you are running Windows 95 
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 95.

With other Windows version 3.0 display drivers, Windows 95 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 95 (??).

* 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 95 (???).

* 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 TERMINATE-AND-STAY-RESIDENT (TSR) PROGRAMS AND DRIVERS
WITH WINDOWS 95
============================================================

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 95. 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 95, 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 95, 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 95.

2. If the situation does not affect Setup, continue setting up Windows 95 
   by following the instructions on your screen.
   
   If the situation does affect Setup and prevents it from installing
   Windows 95, 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 95 Setup again.

After Windows 95 is successfully set up, you may want to restore your 
TSRs. 


PROGRAM LISTING
===============

This section describes some problems that you might encounter while using a 
TSR with Windows 95. 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.


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 95. It is
recommended that you use SMARTDrive, provided with Windows 95,
instead.


All Charge 386 Version 3.1 
-------------------------- 
ALLEMM4.SYS is a memory manager that causes problems with Setup and Windows
95. If you encounter problems running this program with Windows
95, it is recommended that you use EMM386.EXE and HIMEM.SYS,
provided with Windows 95, to manage memory instead.


Anarkey Version 4.00
--------------------
Do not run Windows 95 when Anarkey version 4.00 is running. With 
some memory configurations, running Anarkey version 4.00 with Windows may
cause unpredictable system failures. In rare cases, this
program can also corrupt hard-disk data. Also, Windows 95 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 95. 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 95. 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
95 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 95. 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 95 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 95. 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 95, 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 95, 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 95. It is
recommended that you use SMARTDrive, provided with Windows 95,
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 95,
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 95 may cause problems, including
system failure. It is recommended that you do not use CED with Windows 95.


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

It is recommended that you remove VSAFE.COM/VSAFE.SYS before
you set up Windows 95. 

To remove VSAFE, remove any lines containing VSAFE.COM or VSAFE.SYS from
your AUTOEXEC.BAT file. Also, remove any references to VSAFE.COM or VSAFE.SYS
from the RUN= line in your WIN.INI file.

If you are upgrading to Windows 95, 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 95.

If you don't remove VSAFE before you set up Windows, you will see warnings
about COMMAND.COM, WIN.COM, and KRNL.386 when Windows starts. If you see
these warnings, ignore them and choose the update option.

For more information, see the Central Point Anti-Virus documentation.


CMDEDIT.COM Version 2.0
-----------------------
If this command-line editor is loaded before Windows 95 is
started, it may cause a General Protection Fault when you run multiple
MS-DOS Prompts inside Windows 95.


Cubit Version 3.01
------------------
When you are using Cubit with Windows 95, 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 95, 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 95.


Data Physician Plus Version 2.0 (VirALERT)
------------------------------------------
It is recommended that you do not set up Windows 95 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 95, 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 95. It is recommended that you do not use this editor
with Windows 95.


Doubledisk Version 2.5
----------------------
Windows 95 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 95
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  
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 95. It is
recommended that you use SMARTDrive, provided with Windows, instead.


F-PROT Professional
--------------------

Setup cannot run if F-PROT Professional is running. You should remove this
program from your AUTOEXEC.BAT and CONFIG.SYS files, and then check your
WIN.INI file for the following line:

        load=wvirstop.exe

If you see this line, remove it from your WIN.INI file.

When you are done, restart your computer, and then run Setup again.


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 95.
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 95. 
You should remove all references to HPMM.SYS from your CONFIG.SYS 
and AUTOEXEC.BAT files before setting up Windows 95.


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 95. It is
recommended that you use SMARTDrive, provided with Windows 95,
instead.


IBM VDISK.SYS (RAM Disk Utility)
--------------------------------
VDISK.SYS is incompatible with Windows 95 because it occupies
extended memory required to run Windows 95. This utility prevents
any XMS-compatible memory manager from loading.


IEMM.SYS Memory Manager
-----------------------
The IEMM.SYS memory manager is incompatible with Windows 95. 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,
to manage memory instead.


ICACHE.SYS Disk-Cache Utility
-----------------------------
Do not use two disk-cache utilities with Windows 95.
It is recommended that you use SMARTDrive, provided with Windows, 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 95.
It is recommended that you use SMARTDrive, provided with Windows 
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 95. It is
recommended that you remove all references to this emulator from your
CONFIG.SYS and AUTOEXEC.BAT files before setting up Windows 95.


Infinite Disk version 2.1
------------------------
Inifinite Disk version 2.1 does not work properly with Windows 95.
Either remove Infinite Disk software from your computer before you run
Setup, or contact your software dealer for a version of Infinite Disk
software that is compatible with Windows 95.

To remove Infinite Disk software from your system, first restore any
compressed files back to their original state. Then remove the following lines
from your CONFIG.SYS and AUTOEXEC.BAT files:

IDDRV.SYS
IDRES.EXE
PROTECT /C

Then restart your computer and run Setup again.


JOIN (MS-DOS)
-------------
Do not add or remove "joined" drives while you are running Windows 95. 
If you use the JOIN command before starting Windows and do not change the
state of the joined drives from MS-DOS Prompt within Windows, Windows 95
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 95. 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 95 to
fail.


Lasertool Control Panel Version 2.2
-----------------------------------
If you load version 2.2 of the Lasertool Control Panel program (PCPANEL.EXE)
from Windows 95, your system may fail. This program works
properly if you load it before you start Windows 95.
 

Le Menu Version 1.0
-------------------
When you are using Le Menu version 1.0 with Windows 95, 
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 95 as a Batch-File menu command so that COMMAND.COM 
will load before starting Windows 95. 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 95. When you quit Windows, 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 95,
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 95. Make sure that you are using only one
memory manager with Windows 95. It is recommended that you use
HIMEM.SYS and EMM386.EXE, which are provided with Windows 95, to
manage memory instead.


Mirror (MS-DOS)
---------------
If you run Mirror from Windows 95 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 95.


NetRoom Memory Manager (RM386.SYS)
----------------------------------
With some older versions of NetRoom, you may encounter problems setting up
Windows 95. In this case, contact Helix Software for the most
current version of NetRoom.

If you remove the line containing RM386.SYS from your CONFIG.SYS file, you 
may need to install HIMEM.SYS, which comes with Windows or MS-DOS. You can 
do this by adding the following line to your CONFIG.SYS file:

        DEVICE=<path>\HIMEM.SYS

The <path> is the location of your Windows or MS-DOS files (for example,
C:\WINDOWS).


NetWare(R) NetBIOS
------------------
The NetWare NetBIOS TSR is incompatible with Windows 95 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 95  
includes an IPX/SPX compatible protocol that you can use instead of NetBIOS.
For information about configuring Windows 95 to work with it, see the
NETWORKS.WRI online document.


Newspace Version 1.07
---------------------
This disk-compression utility is incompatible with Windows 95
and may cause several problems.


Norton Anti-Virus(R) (all versions)
--------------------------------

If you have any version of Norton Anti-Virus, you should remove it before
running Setup. It is recommended that you do not run Norton Anti-Virus with
Windows 95.

To remove Norton Anti-Virus version 1.5:

1. In your CONFIG.SYS file, remove the following line:

        DEVICE=C:\NAV\NAV_.SYS

2. In your AUTOEXEC.BAT file, remove C:\NAV from the PATH statement.


To remove the anti-virus features of Norton Desktop for Windows version 3.0:

1. In your CONFIG.SYS file, remove the following line:

        DEVICE=C:\NDW\NAVTSR.EXE

2. In your AUTOEXEC.BAT file, remove the following lines:

        C:\NDW\IMAGE.EXE
        C:\NDW from the PATH statement

3. In your SYSTEM.INI file, remove the following lines:

        shell=c:\ndw\ndw.exe (in the [boot] section)
        device=symevent (in the [386enh] section)

4. In your WIN.INI file, remove the following lines:

        load=c:\ndw\navtsrw.exe


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 
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 Speed Drive Disk Utility (SPEEDRV)
-----------------------------------------
If you are running this utility, there may be problems setting up Windows 95.
You should remove any lines in your CONFIG.SYS or AUTOEXEC.BAT files that
contain "speedrv.exe" or "speeddrv.exe".


Norton Utilities(R) Version 5.0 (DISKREET, NCACHE)
--------------------------------------------------
This program is incompatible with Windows 95 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.
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 95.


Norton Utilities Version 6.01 (DISKMON)
---------------------------------------
It is recommended that you do not use DISKMON version 6.01 with Windows 95.


PC-Cache (PC Tools disk cache program)
--------------------------------------
You must remove PC-Cache before you can set up Windows 95. To remove PC-Cache,
you remove any lines in your AUTOEXEC.BAT file that contain "pc-cache.com"
or "pc-cache."


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 95 is
running. 


PCKEY.EXE (MultiSoft Keyboard Enhancer and Command-Line Stack)
--------------------------------------------------------------
PCKEY.EXE may not work properly with Windows 95 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 95.


PC-Kwik Disk Accelerator
------------------------
If you use PC-Kwik with Windows 95, 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 95. It is
recommended that you use SMARTDrive, provided with Windows 95,
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 95,
Setup may fail. PC-KWIK Version 2.0 may correct this problem.


PCSXMAEM.SYS Utility
--------------------
This utility is incompatible with Windows 95. You should remove
all references to it from your CONFIG.SYS and AUTOEXEC.BAT files before
setting up or starting Windows 95. 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 95 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 95. 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,
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. 
If you do, your system may fail when you quit Windows. It is recommended
that you run DESKTOP from its PIF, provided with Windows 95.


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


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 95, instead.

POWER.EXE  Windows Power Management
------------------------------------
If you are running POWER.EXE, you may encounter problems while running Setup
from MS-DOS. You should remove POWER.EXE from your CONFIG.SYS or AUTOEXEC.BAT
file before you run Setup.

It is safe to add this line back to your CONFIG.SYS or AUTOEXEC.BAT file
after Windows has been installed.

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 95,
you may not be able to restore the Windows 95 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 95. 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 95, to manage
memory instead.


RAMTYPE.SYS - AST RAMpage!(R) Boards
------------------------------------
The RAMTYPE.SYS driver is incompatible with Windows 95. It is
recommended that you remove this driver before setting up Windows 95.
If you load the driver from your CONFIG.SYS file, comment
out the command line for the driver as follows:

   rem RAMTYPE.SYS 

Windows 95 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 95, you can use version 1.2 and later
of RAMTYPE.SYS with Windows 95. 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 95.
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 95,
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
95. 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 95.


SpeedFXR
--------
This program is incompatible with Windows 95 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)
--------------
You may encounter problems with SUBST during Setup, but you can safely add
it back after Windows 95 has been installed.


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 95, 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 95.
In some cases, your system may fail. Make sure that you are
using only one memory manager with Windows 95. It is recommended
that you use HIMEM.SYS and EMM386.EXE, which are provided with Windows 95, 
to manage memory instead.

UNDELETE
--------
If you are running UNDELETE with the SENTRY option, Setup may have problems
and there may be cases when you run out of disk space during Setup. It is
recommended that you remove UNDELETE from your CONFIG.SYS and AUTOEXEC.BAT
before running Setup.

(Note: the SENTRY option creates a hidden directory named SENTRY. When you 
delete a file, UNDELETE moves the file from its current location to 
the SENTRY directory.  Before removing UNDELETE from your CONFIG.SYS or
AUTOEXEC.BAT, you should free up disk space by using the UNDELETE /PURGE
command on all drives.)

If you do not remove it, Setup will disable this command for you.


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 95.
You may also encounter problems, such as beeping, while
running Windows 95 when Vaccine is loaded.


VIREX-PC Version 1.11
---------------------
If VIREXPC.COM is loaded, Setup and Windows 95 will fail
when KRNL386.EXE performs a write operation. Also, the first time Windows
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 95
successfully. You may also encounter problems when you run
Windows 95. 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 you are setting 
up Windows 95. 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 95. 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 95. XMAEM.SYS is
provided with IBM DOS version 4.0.


XMA2EMS.SYS
-----------
Windows 95 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 95. 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.

