PLEASE DO NOT Distribute this file.

=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
       M I C R O S O F T     C O N F I D E N T I A L
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*

	       !!  CHICAGO PRE-RELEASE  !!

**  These are the final release notes that did not make it into the 
Installation, Test and Release Notes document.  **

If you have to shut down Chicago, use the shutdown command off of the bottom
left icon in the GUI shell.  IMPORTANT: wait until all hard disk activity has
completely stoppped (ie, usually 10-15 seconds) before cycling power.

DOUBLESPACE:  If you are running DoubleSpace on the machine that you are 
installing Chicago on be sure that you have at least 6 MB of free disk space 
on your uncompressed drive for swapping BEFORE you instal Chicago.  To increase
the free disk space run DBLSPACE at the MS-DOS prompt and follow the screens.

Do NOT setup up Chicago on a machine with any type of disk compression product
except for MS-DOS 6.0 Doublespace.  Support for other products is still being
worked on.  

Do NOT install ANY disk compression utility after Chicago has been installed.

CD ROM:  DO not install Chicago if you have 2 or more CD ROMs on your machine.

DISK UTILITIES/DRIVERS:  Do not use Symantec/Norton or Central Point disk 
utilities, including Backup, on a Chicago machine.

IF you have a PS2 which uses an IAD file, Chicago setup will not work.  We are still working
on the support for this hard disk configuration.

IF you have a Plus Hard card, Chicago will not work correctly with this card so you
should disable these cards before installing Chicago.  We are still working on the
support for this hard disk configuration.  

Do not install Chicago on machines which use a single SCSI adapter for a CD ROM and
one or more other components (ie, hard disks) as support for this configuration
has not been added yet. 

Do not install Chicago on machines that have the following disk utilities or drivers:
		VFeature Delux
		SpeedStor Bootall Option
		Priam Drive
		Everex MBR
		Micro House MBR

MS-DOS 6 DISK UTILITIES:  Do not run MS-DOS 6 Backup or Defrag on your Chicago machine.

If you have a Compaq docking station with hard disk and are using the EXTDISK.DRV driver
in config.sys, this driver will not load under Chicago.  You will still be able to access
your hard disk in the GUI shell or in an MS-DOS VM, however.

Do not install Chicago on a machine with MS-DOS 6 Multi-Config.

The printer drivers provided by HP for the HP LaserJet 4 and the HP Color
DeskJet printers (500C & 550C) do not work under this release of Chicago.
Support for these will be provided in a future release.

The driver for IBM 4019 printer is set by default to download soft fonts.
This does not work. Error codes meaning 'font not found' appear on the printer panel.
Switching to 'Print TT as graphics' works fine.

If you have a display with resolution above 1024 by 768, do not try to run Win 3.1
in a MS-DOS VM, per instructions in the release notes, or your screen may blank 
and freeze when you return to the Chicago shell.

If you have a display adapter with an S3 chip, do not use the generic SVGA 600x800 16 color
or 256 color drivers.

16BIT APPLICATION DEVELOPMENT:
==============================
 * The VC++ version 1.00 workbench has Windows 3.1 specific code 
   and will not run on Chicago.

32BIT APPLICATION DEVELOPMENT:
==============================
Since this is an alpha release of the 32bit application support for Chicago we 
have limitations that you should be aware of:

 * Floating point emulation for 32bit apps is not supported in this release.  
   This also has build implications, you should build and test all of your 
   32bit apps on a 486 DX or a 386 with a coprocessor.

 * Pipes are not supported in this release

 * The debug version of the system is very slow.  You should build and test 
   on retail, only switch to Debug when you are tracking down a specific 
   problem.

 * Command line limitation.  Console applications have a 126 characters 
   limitation.  This will be fixed in future releases.  This may break 
   existing Make files that expect a longer command line.

 * You may have to set your files=50 in your config.sys to use the 32bit 
   tools.

 * The SDK and DDK setup do not check for available disk space in this 
   release. You should have 40 MB free for the SDK minimal installation 
   (80 for the max) and 10 MB for the DDK minimal installation.

 * Do not run Dr. Watson with Visual C++ or Code View for Windows or WinDbg

Known problems with 32bit tools:
 * If you use the C runtime functions tolower or toupper (and possibly other
   string functions) you can not link with the static runtime library. The 
   workaround for some apps that do not use __argc and --argv to parse the 
   command line is to link with crtdll.lib.

 * If you run into the following warning in building a 32bit DLL that makes
   floating point calls:

	 libc.lib(crt0.obj) : warning LNK4016: undefined symbol "_main"

   The workaround is to force the DLL startup to be linked by adding the 
   linker option:
	-include:__CRT_INIT@12

