       -----------------------------------------------------------
                  Microsoft Windows 98 README for Setup
                             November 1997            
       -----------------------------------------------------------

                (c) Copyright Microsoft Corporation, 1997


This document provides complementary or late-breaking information to
supplement the Microsoft Windows 98 documentation.

------------------------
How to Use This Document
------------------------

To view Setup.txt onscreen in Notepad, maximize the Notepad window.

To print Setup.txt, open it in Notepad or another word processor, 
click the File menu, and then click Print.

--------
CONTENTS
--------
SETUP.TXT

GENERAL SETUP NOTES

FINDING AND FIXING HARD DISK PROBLEMS DURING SETUP (USING SCANDISK)

UNINSTALLING WINDOWS 98

IF YOU HAVE A COMPRESSED DRIVE

INSTALLING WINDOWS 98 OVER WINDOWS NT 

INSTALLING WINDOWS 98 OVER OS/2

INSTALLING WINDOWS 98 ON COMPUTERS WITH LANTASTIC

SETUP ERROR MESSAGES

EDITING THE CONFIG.SYS AND AUTOEXEC.BAT FILES

HARDWARE NOTES

MEMORY MANAGERS

DISK-CACHE PROGRAMS

ANTI-VIRUS SOFTWARE

SETTING UP A DUAL-BOOT CONFIGURATION

CREATING AN MS-DOS BOOT PARTITION

USING TERMINATE-AND-STAY-RESIDENT (TSR) PROGRAMS AND DRIVERS

KNOWN POTENTIAL SETUP PROBLEMS



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

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

NOTE: We recommend that you check your hard disk for viruses
before setting up Windows 98.

You should also turn off any screen savers you have running, and
disable any anti-virus software that is running before you start 
Setup.


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

 - MAKE A NEW STARTUP DISK! Because of changes in the real-mode
   and protect-mode kernels to support FAT32, Windows 98 startup 
   disks are not compatible with earlier versions of Windows. 
   Therefore, when setting up Windows 98 for the first time, be 
   sure to make a new startup disk, EVEN IF YOU ARE NOT PLANNING 
   TO USE FAT32.

 - If you have the Number Nine Imagine 128 Display Adapter, you 
   will probably have to either run Setup from MS-DOS or change 
   your display driver to VGA.


FINDING AND FIXING HARD DISK PROBLEMS DURING SETUP (USING SCANDISK)
===================================================================
Windows 98 Setup automatically runs ScanDisk to check for problems
on your hard disk. 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 98 to
correct these errors.

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

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

1. Quit Windows.
2. If you are setting up from floppy disks, insert Setup Disk 1 into 
   the drive, and then type the following at the command prompt:

	a:scandisk.exe /all

   where "a" is the drive that contains the Windows disk.

   If you are setting up from a CD-ROM, insert the CD-ROM and then 
   type the following:

        f:\win95\scandisk.exe /all

   where "f" is the drive that contains the CD-ROM.

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 98 over a previous version of Windows 
98:

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) and any host drives you have 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. To do this, type the 
following command:

	setup /is

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

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

        setup /is /iq


UNINSTALLING WINDOWS 98
=======================

During Setup, you'll have the option of saving your system files so 
that you can uninstall Windows 98 later. If you want to be able to 
uninstall Windows 98 later, click Yes. Setup will save your system 
files in a hidden, compressed file. If you don't need to be able to 
uninstall Windows 98 later, click No.

You will not see this Setup option if:
- You are upgrading over an earlier version of Windows 98.
- You are installing to a new directory.
- You are running a version of MS-DOS earlier than 5.0.

NOTE: The uninstall files must be saved on a local hard drive. You 
cannot save them to a network drive or a floppy disk. If you have 
multiple local drives, you will be able to select the one you want to 
save the uninstall information on.

NOTE: If you see a message during Setup about not being able to save 
your system files, see the "Setup Error Messages" section later in 
this document.

>>>To uninstall Windows 98 and completely restore your system to its
previous versions of MS-DOS and Windows 3.x, or Windows 95:

1. Click the Start button, point to Settings, and then click Control 
   Panel.
2. Click Add/Remove Programs.
3. On the Install/Uninstall tab, click Windows 98, and then click 
   Remove.

Or, if you are having problems starting Windows 98, use your startup
disk to start your computer, and then run UNINSTAL from the startup
disk.

NOTE: The uninstall program needs to shut down Windows 98. If there 
is a problem with this on your computer, restart your computer and 
press F8 when you see the message "Starting Windows 98." Then click
Command Prompt Only and run UNINSTAL from the command prompt.

If Setup did not complete successfully and you want to restore your
previous versions of MS-DOS and Windows 3.x, or Windows 95, you can 
run UNINSTAL from the \Windows\Command directory on your hard disk, 
or from your startup disk if you created one.

If you saved your files on a drive other than C, you can use the /w 
option to specify the drive where the files are located. For example:

        uninstal /w e:

where e: is the drive containing your previous system files that 
were saved.

If Windows 98 is running and you want to remove the uninstall files 
to free up disk space (6 to 9MB), follow these steps:

1. Click Start, point to Settings, and then click Control 
   Panel.
2. Click Add/Remove Programs.
3. On the Install/Uninstall tab, click Old Windows 3.x/MS-DOS System 
   Files, and then click Remove. Or click Remove Windows 95 system 
   files (Uninstall Info).

You will no longer be able to uninstall Windows 98.


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 an uncompressed drive if possible.
- Delete any unneeded files on your host partition.
- If you are running Windows 3.1 and have a permanent swap file, try
  making it smaller. In Control Panel, click the 386 Enhanced
  icon, and then click Virtual Memory. Then modify the size of your
  swap file.
- Use your disk compression software to free up some space on the host
  drive for the compressed drive. If you compressed your drive by 
  using DriveSpace or DoubleSpace, follow these steps:

  1. Quit Windows.
  2. Run Drvspace.exe or Dblspace.exe.
  3. Select the compressed drive on whose host you want to free space.
  4. On the Drive menu, click Change Size.

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

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 swap
file. 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 by using SuperStor, Setup may 
not be able to find your startup drive and install Windows 98. If 
you get a message about this during Setup, uncompress your disk and 
remove SuperStor, then run Setup again.

If You Have XtraDrive Compression
---------------------------------
If you have compressed your hard disk by using XtraDrive and you are
upgrading a previous version of Windows, Setup will not be able to
install Windows 98 unless you turn off XtraDrive's write-cache. To
turn this off, carry out the following procedure:

1. Quit Windows.
2. Run Vmu.exe (XtraDrive's Volume Maintenance Utility).
3. Click 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, click 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 then restart your computer.
9. Start Windows, and then run Setup again.


INSTALLING WINDOWS 98 OVER WINDOWS NT 
=====================================

If you are multi-booting MS-DOS and Windows NT, boot to MS-DOS, and 
then run Setup from either MS-DOS or Windows 95. You will not be able 
to install Windows 98 to a directory with a shared Windows 95/Windows 
NT configuration; you will need to install Windows 98 to a different
directory.

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

If you boot MS-DOS from a floppy disk and then 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 then selecting 
the Repair option).


INSTALLING WINDOWS 98 OVER OS/2
===============================

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

NOTE: If you are upgrading over OS/2 on an HPFS partition, you will
need to have your OS/2 disk 1 available during Setup.

If you are using OS/2 Boot Manager to choose operating systems at
startup, Setup will disable Boot Manager to ensure that Windows 98 can
restart the computer and complete its installation. Boot Manager can 
be reactivated by running the Fdisk utility that comes with Windows 
98 (see the procedure at the end of this section).

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

If you boot MS-DOS from a floppy disk and then run Setup, you will no
longer be able to boot OS/2 after Windows 98 has been installed. You
will need to delete the Autoexec.bat and Config.sys files that OS/2
uses before running Windows 98 Setup.

If you want to remove OS/2 from your computer after you have installed
Windows 98, carry out the following procedure:

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 sub-
   directories, 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, click Options, and 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 
   listed above. Also, depending on which version of OS/2 you have, 
   in your root directory, you may see the following files, which you 
   can delete:

	OS2dump
	OS2ldr
	OS2logo
	OS2ver

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

If Boot Manager is installed and you want to remove it, restart your 
computer, and then carry out the following procedure. (We recommend
that you print this file before restarting your computer.)

1. When you see the Boot Manager menu, choose to boot to MS-DOS, and 
   then run FDisk.
2. Choose to make the MS-DOS partition (C) your active partition.
3. Quit FDisk, and then restart your computer.

If you want to reinstate Boot Manager after you install Windows 98, 
carry out the following procedure:

1. On the Start menu, click Run, and then type FDISK.
2. Choose Option 2, Set Active Partition.
3. Enter the number of the Boot Manager Partition. This partition 
   will be the 1 MB non-MS-DOS partition usually placed at the top 
   or bottom.
4. Quit FDisk, and then 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 98 ON COMPUTERS WITH LANTASTIC
=================================================

If you are running the LANtastic server, you must disable it before
setting up Windows 98. To disable the LANtastic server, either remove
the Server.exe file 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 drive C), 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 provides information about what to do next.

"Not Enough Memory" Messages
----------------------------
If you encounter an "out of memory" error message, you can increase 
conventional memory by commenting out TSRs and loading device drivers 
into the upper memory area.  For information on how to perform these 
steps, see Microsoft Knowledgebase Article Q134399, "How to Increase 
Conventional Memory for MS-DOS-Based Programs" at the following URL: http://www.microsoft.com/kb/articles/q134/3/99.htm.

"Not Enough Disk Space" Messages
--------------------------------
You can recover disk space by completing any or all of the following 
steps:
* right-click on Recycle Bin, and then click Empty Recycle Bin
* delete contents of your Internet browser cache subdirectory
* delete files with the extensions .bak and .tmp
* delete unused program folders (be sure to back up data first)
* delete old MS-DOS folder, unless dual-boot configuration is 
  desired (Be sure you have a boot disk that supports access to 
  the CD-ROM first)
* delete the hidden file Winundo.dat from a previous installation 
  of Windows 95
* delete old Windows 3.1 folder, unless dual-boot configuration 
  is desired

Setup Cannot Write to the Temporary Directory
---------------------------------------------
This message may be caused by insufficient disk space for the 
temporary directory. If space is available on another drive, use 
the following command line to change the temporary directory 
location:

	Setup /T:<drive letter>:\TEMP

If you do not have space available on another drive, free some disk 
space and run Setup again. See the "Not Enough Disk Space" Messages 
section in this document, for files that can be deleted.

CAB File Error Messages
-----------------------
CAB file errors are most frequently caused by one or more of the 
following: virus, low conventional memory, bad media, or hardware 
problems, especially problems with CD-ROM drives. 

If you have already created a startup disk, quit Setup, shut down 
your computer, insert the startup disk in the floppy drive and 
restart the computer. This creates a controlled environment from 
which to run Setup. Then run Setup from the MS-DOS command prompt.

If you have Multimedia Cloaking and are installing Windows 98 from 
floppy disks, Setup may not run successfully. In this case, if you 
see messages about Setup not being able to read .cab files, then you 
should follow these steps:

1.  Remove the line referencing Cacheclk.exe from your Config.sys 
    and Autoexec.bat files.
2.  Restart your computer.
3.  Run Setup again.

Message SU0010, SU0012, SU0015, or SU0016
-----------------------------------------
If you receive one of these messages during Setup, see the 
sections about OS/2 and Windows NT earlier in this document.

Message SU0011
--------------
If your hard disk is password-protected, Setup will not be able to 
complete successfully. You must first remove the password protection. 
For more information, see the documentation that came with your 
computer.

Message SU0013
--------------
To set up Windows 98, your startup drive must be an MS-DOS boot 
partition. If your startup drive is an HPFS or Windows NT file 
system, you must create an MS-DOS boot partition before running 
Setup. For more information, on creating an MS-DOS boot partition, 
see the documentation that came with your computer.

If you have LANtastic networking or SuperStor compression, see those
sections earlier in this document for more information.

Standard Mode Messages
----------------------
If you get any of the following error messages, you should remove
any memory managers (such as EMM386.exe, QEMM, or 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.

Note: If you still have problems, try adding EMM386.EXE back into 
your Config.sys file and exclude all ranges. For example,

	device=c:\windows\emm386.exe x=A000-FFFF

If you encounter these messages or random hangs during Setup, you 
may need to turn on double-buffering in SmartDrive. Several SCSI 
hard drives and some ESDI drives require double-buffering.

To turn on double buffering, add the following line to the beginning
of your Config.sys file:

	device=c:\windows\smartdrv.exe /double_buffer+

where "c:\windows" is the path to your Windows directory.

"Setup could not back up your system files"
-------------------------------------------
If you see an error message while Setup is saving your system files, 
there may not be enough disk space, particularly on compressed disks. 
You should free up space on the drive you are saving your system 
files on (the default drive is C) by removing unneeded files.

"Cannot continue on this system configuration"
----------------------------------------------
If you get a message saying "Setup cannot continue on this system
configuration," you may have an older, incompatible disk partition.
Before running Setup, you will need to back up your data and then
repartition your disk.

"Some settings have changed since you last started Windows..."
--------------------------------------------------------------
If you receive the following error while attempting to upgrade from 
Windows 95, there is most likely another application loaded that is 
using a file required by Windows 98 Setup. 

   "Some settings have changed since you last started Windows, or 
   a file that Setup needs is being used by another program. Quit 
   Setup, restart Windows, and then run Setup again.  If the problem
   persists, start Setup from MS-DOS. For more information, see 
   Setup.txt on Setup disk 1 or the Windows CD-ROM." 

There are several programs that are known to cause this error:

*  Diamond's "In Control Tools"
*  Ensonics AudioPCI sound card drivers
*  Aztech sound card drivers
*  Some Windows Printing System utilities (Canon BJ series)

There are currently 2 workarounds for this issue:

1.  If you are running one of the above-listed applications, you must 
    ensure that it is disabled before you run Setup.

    *  Ensonic AudioPCI - In Control Panel, System, Device Manager, 
       go to "sound video and game controllers and click on the 
       Properties tab for the sound card. Now check the box to 
       disable this device. Setup should now continue and you can 
       re-enable the sound card after Setup completes.

    *  Diamond's "In Control Tools" - See your Diamond documentation.

    *  Windows Printing System - Click Start, click Run, type 
       Sysedit, and press Enter. Find the Win.ini file and the 
       [Windows] heading. Place a semi-colon ";" in front of the 
       Load= and Run= lines. Save the file. Now find the System.ini 
       file and the [386enh] section and place a semicolon in front 
       of all Device= lines that contain WPS*.*. Save the file and 
       reboot. Setup should now run. You can remove these changes 
       after Setup completes.

2.  If the above procedure fails, or you cannot find the application 
    that is causing the error, you will need to run Windows 98 Setup 
    from MS-DOS mode or a Command prompt-only boot. You will also 
    need to make sure your real-mode CD-ROM drivers are loaded if 
    installing from CD-ROM.

Message SU0167
--------------
A file or directory called Desktop exists on your computer. You 
should rename or move your current Desktop directory, and then run 
Setup again.

Message SU0410
--------------
Setup cannot open a required file, possibly because the file is 
missing or damaged, or possibly because your computer does not have 
enough memory. 

If you have already created a startup disk, quit Setup, shut down 
your computer, insert the startup disk in the floppy drive and 
restart the computer. Then run Setup from the MS-DOS command prompt.

"Cannot Copy File" Messages
---------------------------
Try skipping the file. It may not be essential. If that doesn't work 
(for example, Setup does not complete successfully, or Windows 98 
will not run), quit Setup, shut down your computer, insert the 
startup disk in the floppy drive and restart the computer. Then 
run Setup from the MS-DOS command prompt.

SU99xxxx Messages
-----------------
SU99 is a prefix that is added to all errors that Setup does not 
have a specific error message for. These errors are often caused by 
low conventional memory. If you have already created a startup disk, 
quit Setup, shut down your computer, insert the startup disk in the 
floppy drive and restart the computer. Then run Setup from the 
MS-DOS command prompt.

The following information may be useful for technical support 
personnel. When xxxx is under 1000, the error is from Setupx and 
can be broken down into the following sub-areas:

* SU99101-SU99200 Inf parsing problems (Check the Setuplog.txt file 
  for a more detailed explanation, such as the INF file that is 
  causing the problem.)
	SU99101   Invalid filename
	SU99102   Allocation error
	SU99103   Invalid section name
	SU99104   Out of handles
	SU99105   Inf not found
	SU99106   Invalid Inf file
	SU99107   Invalid HInf
	SU99108   Invalid field
	SU99109   Section not found
	SU99110   End of Section
	SU99111   Profile not found
	SU99112   Line not found
	SU99113   Can't read File
	SU99114   Too Many Inf Files
	SU99115   Invalid Save/Restore
	SU99116   Invalid Inf Type

* SU99201-SU99300 Text processing module (Check the Setuplog.txt file
  for a more detailed explanation, such as the file that is having 
  the problem.)
	SU99201   Very generic "text file not found" message.
	SU99202   Not enough memory (generally terminal)
	SU99203   Could not read the disc (terminal)
	SU99204   Could not write the data (terminal)
	SU99205   Invalid request (very generic)
	SU99206   Invalid line from DELETE_LINE, and so on.

* SU99301-SU99400 Virtual copy module (These deal with the copy 
  engine, so if any of these errors occur while copying files to the 
  hard disk, network drive, and so on, check the Setuplog.txt for 
  more information, such as the file being worked on.)
	SU99301   File I/O failure
	SU99302   String length limit exceeded
	SU99303   Insufficient memory
	SU99304   No String handles available
	SU99305   Reference count would overflow
	SU99306   Invalid argument to function
	SU99307   String library not initialized
	SU99308   String not found in string table
	SU99309   Copy engine busy
	SU99310   User interrupted operation
	SU99311   Invalid destination directory
	SU99312   User skipped operation
	SU99313   Hardware error encountered
	SU99314   List is locked
	SU99315   Wrong disk in the drive
	SU99316   Change mode
	SU99317   Logical Disk ID invalid
	SU99318   Logical Disk ID not found
	SU99319   Logical Disk Descriptor Uninitialized
	SU99320   Logical Disk path is invalid
	SU99321   Failed to load expansion dll
	SU99322   Copy session not open

* SU99401-SU99499 Generic installer (Very generic errors generated 
  when Setup cannot narrow down the problem any further.)
	SU99401   Insufficient memory
	SU99402   Invalid INF file
	SU99403   Can't process LogConfig=
	SU99404   Can't process Config.sys/Autoexec.bat
	SU99405   Can't process UpdateInis= (There was an error 
			updating an .ini file (error during the 
			UpDateInis step in GenInstall. For example, 
			the .ini file may be on a bad sector on the 
			disk or the file may be corrupt in memory. 
			Run ScanDisk to correct disk problems. View 
			the Setuplog.txt file for additional 
			information.
	SU99406   Can't process UpdateIniFields=
	SU99407   Can't process AddReg= (There was a problem adding 
			an entry to the registry. Your registry may 
			be corrupt. If this is a reinstall over a 
			previous installation, try using the 
			System.da0 or System.1st registry files. If 
			this is a first-time setup, try running 
			a Compact installation to minimize the number
			of registry entries. View the Setuplog.txt 
			file for additional information.)
	SU99408   Can't process DelReg=
	SU99409   Can't process Ini2Reg=
	SU99410   Can't process CopyFiles=
	SU99411   Can't process DelFiles=
	SU99412   Can't process RenFiles=
	SU99413   Error returned by a Register API
	SU99414   Can't do copy, del, or renfiles

* SU99500's Device Installer (These deal with the device installer. 
  This means we are having a problem with adding/removing some device 
  from the system. Check the Setuplog.txt file and look for what 
  device is having problems.)
	SU99500   Incorrectly formed device IDF
	SU99501   Invalid compatible device list
	SU99502   Error returned by some registry API
	SU99503   Insufficient memory to complete
	SU99504   Device Info structure invalid
	SU99505   Registry entry/dll invalid
	SU99506   Take default action
	SU99507   User canceled action
	SU99508   No need to copy files during install
	SU99509   Class info structure invalid
	SU99510   Bad inf file encountered
	SU99511   Bad Move Device Params structure
	SU99512   No INF found on OEM disk
	SU99513   Bad property change param structure
	SU99514   Bad Select Device parameters
	SU99515   Bad Remove Device parameters
	SU99516   Bad Enable Class parameters
	SU99517   Fail the Enable Class query
	SU99518   Device Installer API called incorrectly
	SU99519   An OEM path was specified incorrectly
	SU99520   No drivers were updated
	SU99521   No date and time
	SU99522   No Version was specified

The SU99xxxx errors, where xxxx is 1000 or greater, are from Suwin 
calling into Setupx and can be broken down into the following 
sub-areas:

* SU991000-SU991999  file system
	SU991001   Exit by User request.
	SU991002   No hard drives were found
	SU991003   Can't read boot drive
	SU991004   Boot drive is unformatted
	SU991005   Error formatting boot drive
	SU991006   Error setting default values
	SU991007   Error reading reboot data
	SU991008   Not enough memory
	SU991009   Could not find MBR
	SU991010   Error reading hard disk (locked disk)
	SU991011   Error writing to hard disk
	SU991012   Boot drive is write protected
	SU991013   Root dir is full
	SU991014   Specified drive was invalid
	SU991015   System can't be upgraded

* SU992000-SU992999  operating system upgrade module
	SU992001   Exit by user request
	SU992002   No hard drives found
	SU992003   Can't create boot drive
	SU992004   Boot drive is unformatted
	SU992005   Error formatting boot drive
	SU992006   Error setting default values
	SU992007   Error reading reboot data
	SU992008   Not enough memory
	SU992009   Could not find MBR
	SU992010   Error reading hard drive
	SU992011   Error writing to hard drive
	SU992012   Boot drive is write protected
	SU992013   Root dir is full
	SU992014   Specified drive was invalid

* SU993000-SU993999  operating system error codes
	SU993001   Exit by user request
	SU993002   Not enough memory

* SU994000-SU994999  user interface module
	SU994000   Failure to find UI resources 
			(nonfatal for debugging)
	SU994001   Character Windows failed to Init
	SU994002   Char mode screen init failure
	SU994003   Graphics mode screen init failure
	SU994004   Window class or creation failure
	SU994005   Bad HINSTANCE value
	SU994006   UI already initialized

* SU995000-SU995999  These deal with the control module. Basically, 
  this controls what Setup is doing.
	SU995000   Exit by user request
	SU995001   Exit due to error (There was a problem opening the 
			property sheet. Increase the swap file size, 
			conventional memory, and/or extended memory. 
			Problem could be caused by: (1) Error opening/
			validating Setuppp.inf, (2) No "Product Type" 
			in Setuppp.inf, or (3) Error creating the 
			property sheet (Wizard pages).)
	SU995002   Not enough memory
	SU995003   LoadLibrary fail
	SU995004   Resource not found
	SU995005   CPU < 386
	SU995006   Setup can not run in a VM
	SU995007   Inadequate XMS provider
	SU995008   File not found
	SU995009   Cannot create file
	SU995010   Cannot copy file
	SU995011   Cannot delete file
	SU995012   Cannot read file
	SU995013   Cannot write file
	SU995014   Invalid file
	SU995015   No boot drive
	SU995016   MakeProcInstance() failed
	SU995017   Cannot create directory
	SU995018   Cannot find directory
	SU995019   Control data corrupt
	SU995020   Exit windows failed
	SU995021   Spawn of program failed
	SU995022   Pseudo-error: Exit Setup and start Phase 4 Setup
	SU995023   Logical disk ID Invalid
	SU995024   Logical Disk ID not found
	SU995025   Logical Disk descriptor invalid
	SU995026   Logical disk Descriptor uninitialized
	SU995027   Path invalid
	SU995028   Error creating registry keys
	SU995029   Error in System Detection services (There was an 
			error in system detection services. This 
			error may occur if you do not include a space 
			between the /p switch and its detection 
			parameter on the Setup command line. For 
			example, "Setup /pa" will give the error, 
			whereas "Setup /p a" will not. View the 
			Detlog.txt and Setuplog.txt files for more 
			information.)
	SU995030   DOS version below required version
	SU995031   Windows version below req. version
	SU995032   Free Disk space below req. amount
	SU995033   Disk space below full amount but minimal OK
	SU995034   Invalid INF file
	SU995035   Problems merging setver info
	SU995036   Failed to build class list or find matching class
	SU995037   Skip SysCfg item
	SU995038   Error in command line (Invalid command option 
			specified. Check the command line and try 
			again, or type setup /? for help on the Setup 
			command options.)
	SU995039   NETDI's LPDI structure is NULL

* SU995040-SU995044 - The following errors are only found in DBCS 
  versions:
	SU995040   Fail to open IME registry key
	SU995041   Fail to create dispatch IME
	SU995042   Fail to get IME profile data
	SU995043   Fail to create IME sub key
	SU995044   Fail to set IME registry value


EDITING THE CONFIG.SYS AND AUTOEXEC.BAT FILES
=============================================

This section explains how to make changes to your computer's 
Config.sys and Autoexec.bat files. These files tell your computer 
what programs and devices to load on startup (for example, a virus-
scanner program may be loaded automatically in the Autoexec.bat 
file). To remove or disable such a program or device, it may be 
necessary to edit the Config.sys and/or Autoexec.bat files.

To edit the Config.sys and Autoexec.bat files:

1.  In Windows 3.1 or 3.11, click File, click Run, type Sysedit and 
    press Enter. In Windows 95, click Start, click Run, type Sysedit 
    and press Enter.
2.  In the Config.sys or Autoexec.bat dialog box(es), type REM at the 
    beginning of any line(s) that you want to disable.
3.  Save changes and restart your computer.


HARDWARE NOTES
==============

This section includes notes on specific system configurations that 
may prevent Setup from installing Windows 98 successfully.

Sager NP8200 or Wedge Technologies 466/DX2
------------------------------------------
IMPORTANT: If you install Windows 98 on a Sager NP8200 or Wedge 
Technologies 466/DX2 laptop computer, you will not be able to use 
your computer, even if you reinstall a previous version of Windows.

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), your Plug 
and Play card may appear not to function because the 16-bit NIC 
drivers load before Windows 98 has a chance to turn on Plug and Play 
cards. Also, some 16-bit NIC drivers do not recognize Plug and Play 
cards (most NE2000 Plug and Play clones fall into this category).

>>>To use your Plug and Play card with a 16-bit NIC drive:

1. Run the Softset utility that comes with your Plug and Play card,
   and set the card to non-Plug and Play mode.

2. Click the Network icon in Control Panel and then remove the net
   card.

3. In Control Panel, click Add New Hardware and follow the 
   instructions on your screen. Windows 98 will detect your network 
   card.

If you change to a 32-bit protected-mode NIC driver in the future, 
you can rerun Softset to turn on Plug and Play mode for your card.

Diamond Video In-Control Utilities
----------------------------------
You need to remove these utilities before rerunning Windows 98 Setup.

Intel EtherExpress 16 NICs and PCI Computers
--------------------------------------------
Your system may not respond or you may experience initialization 
problems if you are using an Intel EtherExpress 16 NIC in a PCI 
computer 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 98, and happen on a variety of operating 
system platforms. In general, if you experience other problems with 
your EtherExpress 16 in a PCI computer, 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

IBM Thinkpad Model 750x/755x/360x
---------------------------------
If you have one of these models, (including sub-models such as C, 
CE, CX, CS, and CSE), check IBM's bulletin board or the THINKPAD 
forum on CompuServe for updated BIOS and/or Mwave drivers for your 
computer before you install Windows 98.

If you don't upgrade your BIOS, you may have problems if you move the 
mouse while your computer is turning suspend mode on or off.

View Software
-------------
Some utilities for Windows 3.1, such as Long File Names, need to be 
upgraded or used differently with Windows 98. To obtain a version of 
View Software that works with Windows 98, in the United States call 
(800) 536-8439. Outside the United States, call (415) 856-8439.


MEMORY MANAGERS
===============

If you have QEMM installed on your computer, we recommend removing 
it from your Config.sys file before setting up Windows 98. You can 
add it back after Windows 98 is installed.

The following memory managers are incompatible with or may cause
problems with Windows 98. We recommend that you remove all
references to them from your Config.sys and Autoexec.bat files and 
useEmm386.exe and Himem.sys, which are provided with Windows 98, to 
manage memory instead.

        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
===================

Before you run Setup, it is recommended that you remove any third-
party disk-cache programs and replace them with Smartdrv.exe, which 
is provided with Windows 98.

While running Windows 98, you do not need to use a disk-cache utility. 
Setup will remove most disk-cache programs for you.

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 with SmartDrive)
  Cache.exe Disk-Cache Utility
  Cache.sys Disk-Cache Utility
  Flash Disk-Cache Utility (Flash.exe) (do not use with SmartDrive)
  Hyperdisk Disk-Cache Utility (do not use with 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 Accelerator
  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. Make
sure that no anti-virus programs are running while you are setting up
Windows 98. If the program is a terminate-and-stay-resident program,
remove any references to it in your Autoexec.bat, Config.sys, and 
Win.ini files.

If your BIOS has built-in virus protection, you should disable it 
before running Setup. To disable it, you must use the CMOS setup 
program for your BIOS. For more information, see the documentation 
that came with your computer.

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

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 click the update option.
For more information, see the Central Point Anti-Virus documentation.


SETTING UP A DUAL-BOOT CONFIGURATION
==============================================================
To set up a dual-boot configuration on an x86 computer, install the 
operating system in the usual way, and then edit the Boot.ini file 
as described below. All system startup info is stored in the Boot.ini 
file, which is automatically created at the root of your computer's 
hard disk during Setup.

>>>To edit the Boot.ini file:

1.  In Windows Explorer, click View, then click Options, and then 
    click "Show all files."
2.  Make sure "Hide file extensions for known file types" is not 
    checked, and then click OK.
3.  Right-click the Boot.ini file, and then click Properties.
4.  Click to clear the Read-only checkbox, and then click OK.
5.  Right-click the Boot.ini file, click Copy, right-click on a blank 
    area of the Explorer dialog box window, and then click Paste. A 
    backup copy with the file name "Copy of Boot.ini" will be created.
6.  Double-click the Boot.ini file to open it.
7.  Add the name and location of the alternate system in the 
    [operating systems] section of the file, as in the following 
    example:

	[operating systems]
	C:\Winnt="Windows NT 4.0"
	C:\="Microsoft Windows"

8.  Save and close the Boot.ini file.
9.  Right-click the Boot.ini file, and then click Properties.
10. Click the Read-only checkbox, and then click OK.


CREATING AN MS-DOS BOOT PARTITION
==============================================================
To set up Windows 98, your startup drive must be an MS-DOS boot 
partition. If your startup drive is an HPFS or Windows NT file 
system, you must create an MS-DOS boot partition before running 
Setup. For more information, on creating an MS-DOS boot partition, 
see the documentation that came with your computer.


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

APPEND (MS-DOS)
---------------
Do not use the APPEND utility with Windows 98. It prevents Windows
and Windows-based programs 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 enable you to select from different configurations when
you start your computer. Windows 98 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 98, do not compress the Windows
System directory or any file that is loaded from your Config.sys file.

Before you upgrade to Windows 98, 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 98.

Doubledisk Version 2.5
----------------------
Windows 98 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 98 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. To order a copy of
the DRVOFF utility, contact Vertisoft.

Infinite Disk Version 2.1
-------------------------
Infinite Disk version 2.1 does not work properly with Windows 98.
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 98.

>>>To remove Infinite Disk from your computer:

1. Restore any compressed files back to their original state.

2. Remove the following lines from your Config.sys and Autoexec.bat 
   files:

	iddrv.sys
	idres.exe
	protect /c

3. Restart your computer, and then run Setup again.
 
NetWare(R) NetBIOS
------------------
The NetWare NetBIOS TSR is incompatible with Windows 98 in many
configurations. In most cases, Setup will detect NetWare NetBIOS and
remove the startup command from your computer. 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 98 includes an IPX/SPX-compatible protocol that you can use
instead of NetBIOS. For information about configuring Windows 98 to
work with it, see NETWORKS.TXT.

Newspace Version 1.07
---------------------
This disk-compression utility is incompatible with Windows 98.

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 Disklock Versions 3.01 and 3.5
-------------------------------------
Norton Disklock versions 3.01 and 3.5 do not work properly with
Windows 98. Either remove this software from your computer before you
run Setup, or contact Symantec product support for a version of
Disklock that is compatible with Windows 98.

For information about how to remove Disklock from your computer, see
the documentation that came with Norton Disklock.

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 computer 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,
your computer may fail or 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. If you do, your computer may fail when you quit Windows. We 
recommend that you run DESKTOP from its PIF, provided with Windows 98.

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

UNDELETE
--------
If you are running UNDELETE with the SENTRY option, Setup may have
problems, and you may run out of disk space during Setup. We recommend 
that you remove UNDELETE from your Config.sys and Autoexec.bat files 
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 file, 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.


KNOWN POTENTIAL SETUP PROBLEMS
==============================

- If you encounter problems during Setup, such as Setup closing 
  unexpectedly or error messages that do not apply, try increasing the 
  size of your permanent swap file. In general, the size of your 
  permanent swap file plus the amount of RAM in your computer should 
  equal at least 14 MB for Setup to complete successfully. After you 
  change your swap file size, try running Setup again.

  NOTE: If your hard disk is compressed, you may have to increase the 
  size of your host drive before you can increase the size of your
  swap file.

