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.

You should also turn off any screen savers you have running, and disable any
anti-virus software that is running before you start 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.  From the Windows 95 Start menu, click Run and then type FDISK.
2.  Choose Option #2 "Set Active Partion".
3.  Enter number of Boot Manager Partition. This partition will be the 1MB Non-DOS partition
    usually placed at the top or bottom.
4.  Quit FDISK, and restart your computer as instructed.
    You can now boot OS/2 at any time and change labels of partitions in Boot Manager through
    the OS/2 FDISK program.


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

Memory Managers
================

The following memory managers are incompatible or may cause problems
with Windows 95. It is recommended that you remove all references to
them from your CONFIG.SYS and AUTOEXEC.BAT files and use EMM386.EXE and
HIMEM.SYS, which are provided with Windows, to manage memory instead.

        386Max(R)
        ALLEMM4.SYS - All Charge 386 Version 3.1
        HPEMM386.SYS and HPEMM486.SYS
        HPMM.SYS - HP Memory Manager (must remove before Setup)
        IEMM.SYS Memory Manager
        Intel(R) Expanded-Memory Emulator (ILIM386.SYS)
        Maximizer Memory Manager (MAXIMIZE.COM)
        NetRoom Memory Manager (RM386.SYS)
        QMAPS Memory Manager Version 5.16
        UMB PRO Version 1.07


Note: The documentation for 386MAX recommends against setting the EXT
parameter below 64. If you set this parameter to 0, Setup will fail.

Note: 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).


Disk-cache programs
======================================

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 you are running one of the following disk-cache utilities, you should
remove it. In some cases, Setup will remove it for you.

  386MAX Disk-Cache Utility (QCACHE.EXE) (do not use w/Smartdrive)
  CACHE.EXE Disk-Cache Utility 
  CACHE.SYS Disk-Cache Utility
  Flash Disk-Cache Utility (FLASH.EXE) (do not use w/Smartdrive)
  Hyperdisk Disk-Cache Utility (do not use w/Smartdrive)
  ICACHE.SYS Disk-Cache Utility 
  IBMCACHE.SYS Disk-Cache Utility 
  Mace Disk-Cache Utility (MCACHE.SYS)
  Norton Speed Drive Disk Utility (SPEEDRV)
  Norton Utilities Version 5.0 and 6.1 (DISKREET, NCACHE)
  PC-Cache (PC Tools disk cache program) (must remove before setup)
  PC-Kwik Disk-Cache Utility (PC-KWIK.EXE)
  PC_Kwik Disk Accelorator
  PC-Kwik Version 1.59 (PCK.EXE, PSKSCRN.EXE, PCKEY.COM)
  PC Tools(TM) Disk-Cache Utility (PC-CACHE.COM)
  Secretdisk II Disk-Cache Utility (FAST512.SYS) (do not use with Smartdrive)
  Super PC-Kwik Disk-Cache Utility (SUPERPCK.EXE)


Anti-Virus Software
===================

Some anti-virus programs can cause problems when you run Setup. You should
make sure that no anti-virus programs are running while you are setting up
Windows 95. If the program is a terminate-and-stay-resident program, you
should remove any references to it in your AUTOEXEC.BAT, CONFIG.SYS, or
WIN.INI files.

See the notes for specific anti-virus programs below.

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

  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.

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.

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


USING TERMINATE-AND-STAY-RESIDENT (TSR) PROGRAMS AND DRIVERS
WITH WINDOWS 95
============================================================

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


Autocon Version 2.0e, Bootcon Version 1.60, and BOOT.SYS
---------------------------------------------------------
These programs allow you to select from different configurations when you
start your system. Windows 95 Setup modifies only the first section in your 
CONFIG.SYS and AUTOEXEC.BAT files, so you may have to modify these files
manually after Setup if you want to use these programs. For more information,
see the documentation that came with your program.

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.

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.

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.
 
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 NETWORKS.TXT.

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

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.

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.

SUBST (MS-DOS)
--------------
You may encounter problems with SUBST during Setup, but you can safely add
it back after Windows 95 has been installed.

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.


