Suwin

• "SU" Error Message List for Windows 95, Windows 98, and Windows Me Setup
  This article contains a list of the error messages that you may receive when you run the Setup procedure in Windows 95, Windows 98, Windows 98 Second Edition, or Windows Millennium Edition (Me). This article also describes how to resolve some of the error message behaviors.
  http://support.microsoft.com/?kbid=129971 (W95/98/se/ME 8/6/2002)

• SUWIN Caused a GPF in 256_1280.drv at 0002:0D7B.
  GP Fault After End User License Agreement During Setup
  http://support.microsoft.com/?kbid=135162 (W95/98 7/24/2001)

• SUWIN Caused an Illegal Instruction
  Application Error "SUWIN caused an illegal instruction in module GDI.EXE at 0001:16EF.
  http://support.microsoft.com/?kbid=124177 (W95 12/17/2000)

• "SUWIN General Protection Fault" Error Messages During Windows 95 or Windows 98 Setup
  SUWIN An error has occurred in your application. If you choose ignore you should save your work in a new file. If you choose close, your application will terminate. -or-
  SUWIN caused a general protection fault in moduleKRNL386.EXE
  http://support.microsoft.com/?kbid=224836 (W95/98/se 2/18/2002)

• Suwin Error in Setupx.dll During Windows 95/98 Setup
  SUWIN caused a general protection fault in module setupx.dll @ 0012:1346
  http://support.microsoft.com/?kbid=188107 (W95/98 2/18/2002)
  
  
• "SUWIN General Protection Fault" Error Messages During Windows 95 or Windows 98 Setup
  SUWIN An error has occurred in your application. If you choose ignore you should save your work in a new file. If you choose close, your application will terminate. -or-
  SUWIN caused a general protection fault in module SETUPX.DLL
  http://support.microsoft.com/?kbid=224836 (W95/98/se 2/18/2002)
  
  
• Suwin.exe Caused an Invalid Page Fault in Setupx.dll
  SUWIN.EXE caused an invalid page fault in SETUPX.DLL
  http://support.microsoft.com/?kbid=232963 (W98se 2/18/2002)
  
  
• Mismatched Setupx.dll Is Loaded - Setup Cannot Continue
  SUWIN caused a General Protection Fault in module SUWIN.EXE -or- A mismatched Setupx.dll is loaded. Setup cannot continue. Quit all Windows and MS-DOS based programs and try again. Or quit Windows and run from an MS-DOS command prompt. SU0349
  http://support.microsoft.com/?kbid=299961 (W98/se/ME 8/27/2002)

• SUWIN Caused a General Protection Fault in Module...
  SUWIN caused a General Protection Fault in module SUWIN.EXE at 0006:6EB8
  http://support.microsoft.com/?kbid=136415 (W95 12/17/2000)
  
  
• Mismatched Setupx.dll Is Loaded - Setup Cannot Continue
  SUWIN caused a General Protection Fault in module SUWIN.EXE -or- A mismatched Setupx.dll is loaded. Setup cannot continue. Quit all Windows and MS-DOS based programs and try again. Or quit Windows and run from an MS-DOS command prompt. SU0349
  http://support.microsoft.com/?kbid=299961 (W98/se/ME 8/27/2002)

• Suwin Fault in Unknown When Upgrading to Windows ME
  When you are upgrading to Windows Millennium Edition (Me), SUWIN This program has caused an illegal operation and will be shut down. or SUWIN caused an invalid page fault in module Unknown ataddress.
  http://support.microsoft.com/?kbid=266090 (ME 8/7/2002)

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 95 can
restart the computer and complete its installation. Boot Manager can be
reactivated by running the Fdisk utility that comes with Windows 95
(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 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, 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. (It is recommended 
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 95, 
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.

If you are multi-booting MS-DOS and Windows NT, boot to MS-DOS, and 
then run Setup from either MS-DOS or Windows 3.x. You will not be able 
to install Windows 95 to a directory with a shared Windows 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 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).

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

If you have compressed your hard disk by using SuperStor, Setup may not
be able to find your startup drive and install Windows 95. If you get a
message about this during Setup, un-compress your disk and remove 
SuperStor, then run Setup again.