	    * Chicago Beta-1.3 Release Notes *

INSTALLATION INSTRUCTIONS
=========================

Setup over previous versions of Chicago
---------------------------------------
You can upgrade Chicago versions 122 and higher.  To upgrade Build 122 
(M6/Beta 1) or later, you will have to run Setup from real-mode (it will
not run from Chicago GUI build 122).

If you are running Chicago, you can get to real-mode by placing a 
"Pause" statement at the end of your AUTOEXEC.BAT file, and hitting CTRL-C 
when asked to "Press any key to continue . . ."  Or you can Interactive
Boot by hitting F8 when at the "Starting Windows..." message at boot time and
answer NO to WIN at the end of AUTOEXEC.BAT processing.  You should then be 
able to run Setup from the C:\ prompt.

As of build 170, Chicago no longer preserves your hardware settings on an 
upgrade. Please note your hardware settings prior to install.  This applies  
to your network settings as well, so you may have to manually configure your 
network settings.  A "Custom" install will show all the wizard pages so the 
settings can be verified.

Setup over Windows NT (including Daytona)
-----------------------------------------
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 Chicago to a directory with a shared Win 3.x/Windows NT
configuration, you will need to install Chicago to a different
directory.

If you are not multi-booting MS-DOS and Windows NT, you should
configure you 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).

Setup over OS/2
---------------
If you are using OS/2 Boot Manager to choose operating systems at
startup, Setup will disable Boot Manager to insure that Chicago 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.

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 Chicago has been installed.  You will need to
delete the AUTOEXEC.BAT and CONFIG.SYS files that OS/2 uses before
running Chicago Setup.

Known Setup Problems
--------------------
- When prompted for Setup mode, only "Typical" and "Custom" setup
  modes are available. "Portable" and "Compact" setups are not yet
  implemented and are currently disabled.

- Selecting keyboard layouts International English will not work
  correctly.  You must do this from the control panel keyboard
  language applet.

- Some settings in PIF files will be lost on an upgrade
  over build 122.

- Shortcuts to Control Panel Applets will be lost on an 
  upgrade over build 122.

- The WINBOOT directory that was created in build 122 
  is no longer used, you can delete it.

- WINBOOT.SYS is no longer used (and should be deleted by Setup).  
  It has been replaced with IO.SYS and Setup will create a 
  0-byte MSDOS.SYS file that should not be deleted. 

- COMMAND.PIF will be deleted when upgrading over a previous version
  of Chicago. 

- If you receive the following error message during setup:

    Generic Installer Error
    UpdateInis= processing error
    exiting with error code = 405

  File a bug report, then remove the Device=EMM386.EXE line from 
  CONFIG.SYS and re-run Setup.


WordPad and these Release Notes
-------------------------------
For those of you using MSVC20 and the integrated development 
environment and/or MFC dll's, you will have to re-install MSVC20 
after you have installed this version of Chicago.  This is because the 
WordPad applet uses shared MFC DLL's which are not compatible 
with the integrated development environment.  However, before you 
do this, please use WordPad to review these release notes and possibly 
print them as you need to because once you re-install MSVC20, WordPad 
will no longer work.  This version problem will be addressed in a later 
version.

NOTES FOR SETTING UP NETWORKS
==============================

General
-------
If you are setting up Chicago for a network, ensure that the network client 
software is correctly installed and is running.  Verify network connectivity 
by connecting to a server before you run Setup.  Also be sure that the 
directory that contains your network software is in the PATH= environment 
variable.

As of build 170, Chicago no longer preserves your hardware settings on an 
upgrade. Please note your hardware settings prior to install.  This applies 
to your network settings as well, so you may have to manually configure your 
network settings.  A "Custom" install will show all the wizard pages so the 
settings can be verified.

During the net part of setup, if you double-click on the client you must 
either disable logon validation or enter a value in the domain field 
(it's blank by default).

Frame Type
----------
The Microsoft IPX/SPX compatible protocol now automatically detects
the Frame Type.  The Frame Type should be set to Auto.

Net setup copies files already on my system
-------------------------------------------
In the M6.2 release, if you add a net component, the net control panel will
not only copy the files for the new component, but it will copy all
network files.   This should not cause any problems, but it will make the
copy process a little longer.

Banyan VINES
------------
When you first boot into Chicago, the Banyan drivers will report that
the VINES version is not the latest.   Follow these steps:

1. Check the "Keep files on network" option.  If you do not have this
option, edit your vines.ini and remove the WindowsVersion line.
2. Click Cancel
3. Windows will restart. When it does, click Install.
4. Windows will restart again.   VINES should now be configured properly.

Net adapter hardware resources page does not save settings
----------------------------------------------------------
The net control panel has problems saving changes to hardware resources.
If you type the new settings in on the keyboard, it will not save the
settings.  Instead, you should change settings with the mouse by using
the spin controls next to each setting.

INSTALL NOTES FOR PARTICULAR DEVICES
====================================

Logitech Mouse
--------------
If you have a Logitech mouse and run Setup from MS-DOS, your mouse may
not work during Setup.  This is a known problem and will be fixed in a
future build.

PS/2 Mouse
----------
Anyone installing build 166 over 165 on a machine with a PS/2 mouse should
change the line DOS=LOW,UMB in CONFIG.SYS to DOS=HIGH,UMB before
installing. This will fix the problem of not being able to move the
mouse (and probably use the keyboard) during setup.

Bus Mastering Disk Controller
-----------------------------
"If you have a Bus Mastering disk controller and greater than 16MB of
memory, then you most probably will need a 'SWITCHES=/D' in
CONFIG.SYS.  This will force double buffering to happen and get
around a bug we have in double buffering."

Displays
--------
SYSTEM.INI, [boot] will now always contain "display.drv=display.drv"
if a Chicago version display driver is installed.  The actual driver
(e.g. VGA.DRV, S3.DRV, etc.) is loaded from the registry as of this
release.

Computers with a PCI Bus
------------------------
If you have a computer with a PCI bus, you must remove any memory managers 
(such as EMM386, QEMM, etc) before running setup.

IBM Thinkpad 720
----------------
The PCMCIA socket for the IBM Thinkpad 720 is not supported in this release. 
You will not be able to install 32 bit PCMCIA drivers for this computer.

Intel EtherExpress16
--------------------
If you have an Intel EtherExpress16 network adapter, setup may detect that 
it is using IRQ 3.   This setting will conflict with your mouse or serial 
ports.  While setting up, go through Custom setup and verify the net card 
settings.  On the network screen, bring up the properties for the Intel 
EtherExpress16 and go to the Resources page.  Set the IRQ to 5 (or any value 
other than 3 that does not conflict with other devices on your system).

Xircom PE3 Parallel Port Ethernet Adapter
-----------------------------------------
On some machines, the first boot following setup might say your Xircom PE3
adapter is not functioning.  Do not be alarmed, as all subsequent boots
should work.  Machines that are affected have lpt ports set to something
other than 378.  Laptops that do not use 378 include some IBM Thinkpads and
Compaq Conturas.  Also, if you run your Xircom PE3 on LPT2, following setup
you will need to go to the Network Control Panel, into the Advanced Settings
property for your PE3, and change the Interrupt number from 7 to 5.

NETWORKING
==========

MS Network & Downloading policies
---------------------------------
If you are running a real mode net (i.e. netx or vines) & MS network is 
your primary network with a domain name filled in, we will try to 
download policies from your domain, which involves doing a
RegLoadKey on a network file.  This has the potential to deadlock your 
machine.  One workaround is to remove the registry entry that controls 
policy downloading, which would disable downloading and avoid the 
RegLoadKey.

Mapping a network drive in the GUI for VLM clients
--------------------------------------------------
With certain versions of the VLM client, you will be unable to map a 
network drive using the GUI.  If you go out to a dos box, you will still be 
able to map the drive.

Migrating WfW Persistent Network connections
--------------------------------------------
Persistent net connections including printer redirections that existed under 
Windows 3.1x get lost when you upgrade.  You will need to reestablish them 
under Chicago.

Chicago can't find WSOCK.386
----------------------------
This is a known problem.  Go to the \windows\system directory and rename 
WSOCK.VXD to WSOCK.386.

LOGONOFF.EXE
------------
LOGONOFF.EXE has been removed starting with build 170.  The only way to log 
off in Chicago is from the tray, choose Start, Shut Down..., and the third 
radio button (currently worded as "Close all applications and log on as a 
different user").

Printing with Novell NETX client
--------------------------------
In this release, you cannot print to a CAPTURED printer from Windows 
applications when running the Novell NETX client.  You can install the
printer via the Chicago printer install, and print that way.

Problem with NETX.VLM dated 12-09-93
------------------------------------
There are known problems running Chicago with the Novell VLM component file 
NETX.VLM that is dated 12-09-93.

INFO CENTER
===========

Installing Info Center
----------------------
NOTE: To use the Info Center, you must first have a MS Mail or Workgroup 
Postoffice to connect to.  Please see "Installing a Workgroup Postoffice" 
below.

Info Center is not installed on Chicago by default.  To install the Info 
Center, choose the Custom Setup option in Setup.  When you are prompted with 
a list of components, you must select BOTH  "Info Center" and "WMS" 
components.  Setup will install the Info Center icon on your desktop.  The 
first time you launch the Info Center, you will be prompted for additional 
configuration information.

Installing a Workgroup Postoffice
---------------------------------
The Workgroup postoffice installation and administration component is not 
included with this release. To install a Workgroup postoffice, you need 
Windows for Workgroups version 3.11 or Windows NT version 3.1 or 3.5.

From Windows for Workgroups or Windows NT, run the mail program. It asks you 
if you want to (a) connect to an existing postoffice or (b) create a new 
postoffice. Choose the Create A New Postoffice option. Put this new 
postoffice on a network server that Chicago machines can access. Next, a 
dialog box appears asking you to identify the administrator's account. Type 
Administrator into the user name field and admin into the mailbox field.

When this has been completed, choose Postoffice Manager from the Tools menu; 
doing so starts the Workgroup postoffice administration component, which 
enables you to add users to and remove them from the postoffice. Users 
connecting to the Workgroup postoffice need the following information: the 
location of the postoffice on the network server, their mailbox name, and 
their password.

More information on creating a Workgroup postoffice is contained in the 
Windows for Workgroups Resource Kit and the Windows NT Resource Kit.

New Features:
-------------
1. Drag and drop now works.
2. Attachments now work.
3. Next/Previous buttons now enabled.
4. Grouping messages now works.

Known Problems:
---------------
1. New Personal Information Store format.  Your old store from the M6 release
is not compatible with the new format.  You must create a new store and
start from scratch.
2. New Personal Address Book format.  Your old PAB from the M6 release is
not compatible with the new format.  You must create a new PAB and start
from scratch.
3. Next/Previous Message On Delete is not enabled.
4. Remote client not working.
5. Personal Information Store doesn't compact.
6. There is no interop between M6 and the M6.2 releases.  You cannot
send/receive messages to/from mismatched Chicago releases.  Upgrade all
Info Center users simultaneously.
7. The CompuServe Provider from the M6 release will not work on this version 
of Chicago.  There will not be a Compuserve Provider available for this
release.
8. Simple MAPI for 16 bit applications  is not yet implemented.  You cannot
use Simple MAPI for 16 bit applications running on Chicago (e.g. File.Send
in MS Word running on Chicago.)
9. Start/Find/Infocenter is not working properly.

MAPI SDK
--------
There is no new MAPI SDK included with this release of Chicago.
Updated headers and libraries will be posted on Compuserve so that 
developers can update their code to work on this release of Chicago.

DOUBLESPACE and DRIVESPACE
==========================
The following information applies to you if you are using
DoubleSpace or DriveSpace compressed drives.  This note only applies 
to this release of Chicago.

Do not use DBLSPACE or DRVSPACE from MS-DOS 6.x to compress a drive or
create a new compressed drive.  Chicago will not be able to mount it when
you reboot.  Chicago will work fine with existing compressed drives.

Do not use the Disk Repair Tool or the Check Hard Disk option (in
the Disk Properties dialog) to check a compressed drive that contains
Chicago's swapfile. If you do, your computer might stop responding.

The swapfile will be located on the drive where Chicago is
installed by default, unless you were using a Windows Permanent
Swapfile with Windows 3.1 or 3.11 before upgrading to Chicago.

Each time you run Chicago, a new swapfile will be created. The
old ones will remain as "lost clusters". Lost clusters will not
hurt your data, but they will take up more space on your drive
every time you start Chicago.

Use the following procedure to free disk space:

1. Shutdown Chicago, then reboot.
2. When you see the "Starting Windows" message, press F8.
3. Choose the Interactive Boot option. Choose Y for all prompts,
   until you are prompted for WIN; then press N.
4. Run Scandisk. When you are prompted about data that might
   once have been a file (lost clusters) choose Delete.

DEFRAG and DISK REPAIR
======================
This new build includes Defrag and a graphical disk repair utility.
To run them, bring up the property sheet for a drive and click on the
Tools tab.  Known issues:
 - Defrag does not currently support compressed drives.  That capability 
   will be added in a future beta.
 - In Defrag, do not check the "Defragment Compressed Volume Files" option.

APPLICATION COMPATIBILITY
===============================

Re-installing Applications
--------------------------
If you upgrade your existing Windows 3.1 or Windows for Workgroups 
directory to Chicago then you do not need to re-install your applications.   
If you install Chicago to a new directory then you must re-install all of your 
Windows-based applications.  Hand copying files from your Windows 3.1 
directory to Chicago is not sufficient. 

Pagemaker will cause a General Protection Fault if you access
Help/Learning Pagemaker or Help/Shortcut.  This will be fixed in a later
release.

Wordscan Plus 3.0 is not working with this release of Chicago.

SuperStor compression not fully supported in M6.3  You may not be able to get 
SuperStor compression working with Chicago M6.3. 

F4 function with Stacker Ver2.0 & 3.0 and other compression software may not 
function in this release.  Use the work-around described in the Beta 1 release
notes to use F4 boot option with these utilities.

If you compress your Chicago volume using the Stacker Windows compression
program your desktop shortcuts will need to be manually repaired.  Also,
if you tell the compression program to create Stacker icons it may freeze
your system.

AD-DOS.COM in AUTOEXEC.BAT prevents Windows from loading the After Dark TSR 
because AD-DOS.COM stops Winboot.sys from calling Win.com.  User can 
type Win at the command prompt to continue executing Chicago.

Quick Time for Windows will cause a general protection fault that will hang
the system.  A work-around is to add the below settings to QTW.INI:
	[video]
	Optimize=RAW

Embedded TrueType Fonts Not Displayed - Microsoft PowerPoint can embed 
TrueType fonts in a saved document so that your presentation can use those
fonts even if they are not installed on the another system. 

Disk Utilities - Direct disk writes using Int 26h or Int 13h will fail under
Chicago.  This is necessary in a multi-tasking environment to prevent disk
corruption from multiple utilities running simultaneously.  The LOCK and
UNLOCK commands can be used as work-arounds for DOS utilities.

Title Bar icons covered by Pagemaker, Ami Pro, Freelance, Harvard Graphics,
and Designer.  The icons and buttons placed in the title bar by these
applications may be covered by the system buttons.

Adobe Acrobat 1.0 - Acrobat 1.0 is not functioning correctly on this Chicago
release.  The problems are understood.

CrossTalk 2.0 - Crosstalk 2.0 will not function correctly under Chicago.
You should upgrade to version 2.1.

Word 6.0a Mail Merge Problems Adding Data - There is a known problem where 
Word 6.0a crashes when adding a new data record to a form letter document.
The work-around is to create your data document separately from your mail
merge document.

Microsoft Visual C++ v1.5 - A duplicate VMCPD entry will be placed in your 
SYSTEM.INI file during installation.  You should remove this entry to avoid 
Chicago error messages while booting.

Symantec C++ version 6.1 Profession Will Not Run Under Chicago.  Symantec
Norton Utilities version 8.0 Will Not Run Under Chicago.  These applications
will refuse to run under any version of Windows except for 3.1.

Flight Simulator Unable to Lock XMS Memory with SoundBlaster - Microsoft 
Flight Simulator 5.0 crashes with a message "Unable to lock XMS memory-fatal
error" if you try to run it with a SoundBlaster/SoundBlaster Pro card.  To 
work-around, run the Flight Simulator setup program.  On the sound board
settings screen, choose 'NO' for the 'Use XMS Memory' option.

Flight Simulator Hangs when Changing Speaker Settings.  If you change your PC 
speaker settings after you set up Microsoft Flight Simulator 5.0, you will
hang your system.  Select the PC speaker during Flight Simulator setup.

Minimized Clock in Startup Group Runs Maximized - If you had CLOCK.EXE in 
your Windows 3.1 Startup group set to start minimized, Chicago will start it 
maximized.  This is a known problem.

This release of Chicago does not support the Colorado Backup for Windows when 
using a tape drive for backups.

Aldus PageMaker 5.0 hangs at Chicago Shutdown.  Exit PageMaker before your 
shutdown Chicago.

AmiPro 3.0 tutorial is unusable in high display resolutions.  Run the AmiPro 
tutorial in VGA mode.

Microsoft Publisher - Currently, changes to text in a text frame 
(font, font size, bold, etc) do not occur until the mouse is clicked.  As long
as the mouse click occurs in the 'document design area' (ie. not on a menu or 
button bar), changes will take place.

Cinemania '94 - There are display problems which affects video types such as 
ATI and S3 when using Cinemania '94.  If you experience incorrect colors 
when in 256 color mode,  run in a color mode greater or less than 256 colors.  
Doing so allows Cinemania to run without problems.

Logitech Cordless Mouse - The mouse drivers currently included with 
this beta release do not have support for the Logitech Cordless mouse.  
You will need to down-load the file VMOUSE.VXD from the Chicago 
forum to make it function.  Once you have added this file to 
\windows\system\vmm32, you must restart Chicago for it to load.

If you are installing an application from CDROM and you have MSCDEX 
loaded (a line in AUTOEXEC.BAT) and CD-ROM sharing enabled 
(/S switch) you may have problems.  To work around this, you can remove 
the /S switch from the MSCDEX line in your AUTOEXEC.BAT and reboot.

cc:Mail installation fails from inside a Chicago VM.  cc:Mail should be 
setup using single MS-DOS application mode.

Virus utilities can detect but not clean viruses from Chicago.  This is
because virus utilities use low-level writes to repair the disk.  MS-DOS
based utilities can still be run using the LOCK command.  Windows virus
utilities can only repair viruses if you setup Chicago in Windows 3.1
Compatibility mode (no long file names).

Do not install IronClad on the same machine as Chicago.  The security 
features of Ironclad create numerous problems for Chicago.

Dashboard may cause Chicago to hang or spontaneously shut down.

Norton Desktop for Windows may crash when trying to view network resources.

Hollywood - at the end of Hollywood install it will cause a GPF.  This appears 
to not affect the install and after rebooting the application should work
normally.

Windows help files will fail to run if disk is full.  Work-around is to free
up more space.

If you have problems with non-Chicago Help Files try deleting the file
WHLP16T.DLL in the system subdirectory.

Laplink Pro - Running Laplink Pro 4.0a with a communication rate of >9600 
may not recognize other connected machines.  If you have this problem change 
the communication rate to 9600.

Xtree Gold 2.51 for Dos - Xtree Gold cannot PRUNE directories.  The
work-around is to manually delete the directory structure using another VM.
Also, Xtree Gold may see long filename components while running in real mode.

Timeline 1.0 for Windows- The tutorial for Timeline is not functioning with 
this release.

APPLETS
=======
NOTE: all of these problems will be addressed in a future release.

WordPad
------
Printing.  The problem with truncating characters during printing has been 
partly fixed in this release, but in some cases if the paragraph width is not 
equal to the page width, characters are still lost.  Also, characters will be 
truncated in the print preview view.

OLE drag and drop.  WordPad is a full 32 bit app now.  Drag and drop 
works between two 32 bit apps, but it doesn't yet work between WordPad
and a 16 bit OLE server app.

WordPad will not allow you to open a document which is already open 
by another application.

WinPad
------
WINPAD DATA FILES: WINPAD.DAT and WINPAD.IDX are data files that store 
information entered in any of the WinPad applications as well as WinPad's 
online Help. Deleting these files removes all stored information as well 
as online Help. 

REINSTALLING CHICAGO: If you need to reinstall this release of the Chicago 
beta, follow these steps after running Setup in order to restore the existing 
data from your previous WINPAD.DAT file:
1. Copy WINPAD.BAK to WINPAD.DAT
2. Delete WINPAD.IDX

EXITING WINPAD AND CHICAGO: Exiting Chicago before you exit WinPad can cause 
your system to hang. Therefore, always close WinPad before closing Chicago. 
This problem will be fixed in later versions of the product.

Keyboard Support has been enhanced, but is not fully implemented in this 
release.

MSPaint
-------
Text Selection.  Selecting text in the text box results in incorrect 
painting of the selection.

Rotating an image either 90 or 270 degrees changes the colors

Drag and drop of a selection into an OLE client doesn't work yet.

Menus not available in print preview.

File Viewers
------------
Several new features have been added to file viewers.  Once a file 
viewer window is open, you can drag and drop files from the cabinet 
onto the viewer window.  The View/Reuse Window command 
controls whether a new window is created.  Also, if a file is not 
recognized, it is displayed as a HEX dump, although this feature 
doesn't always work in this release.

Support for viewing PowerPoint 4, Excel 5 charts, and 1-2-3 for 
Windows charts has been added.  Note this version will not work 
when viewing PowerPoint 3 charts. 

Backup
------
This app has been included in order to test hardware compatibility with
new functionality.  Compression is not included, but otherwise, all
features are in.  To do a full system backup, use the automatically
created full system backup file set.  To do a backup of just a few files,
create your own file sets.

Known Problems:
- There are some problems with restore.  There will be updated backup.exe
  and QIC117.VXD files posted on the WINPRE beta forum for you to
  download.  These updates fix the restore problems.  See the
  threads on backup for more information.
- View/Filtering/Folders dialog doesn't paint correctly.
- Trying to backup to a CMS tape unit on the parallel port while using
  a printer on the same parallel port doesn't work correctly.
- Trying to abort a backup or restore operation before it has completed
  will result in a fault.
- The backup app will not load correctly if a VxD from any other backup
  application is already loaded.  Thus, if you have installed Norton/Symantec
  Backup for DOS or Win or Colorado Memory Systems backup for DOS or Win,
  you will be loading a VxD in your System.ini file automatically.  To
  prevent this file from being loaded, comment out the line in your
  System.ini file.

MS-DOS Editor
-------------
NO Known problems.  If you find one, please report it on the CS beta forum.

PRINTING
========

Unable to change printer port setting from property sheet page
--------------------------------------------------------------
There is a known problem with being unable to change the printer
port setting from the property sheet page. This will be corrected
a future release. To workaround this, simply delete the printer
& reinstall the driver with a different port setting.

Problems with MGXPS.DRV and Charisma 2.1
----------------------------------------
There are known problems with the MGXPS.DRV PostScript printer driver
that is automatically installed when using Charisma 2.1, or other
Micrografx products. These problems include GPF errors when trying to
any operation involving the printer folder. This will be corrected
a future release. To workaround, manually edit WIN.INI & remove all
references to this driver & use the PostScript driver that ships with
Chicago instead.

Bidirectional Port monitor for HP-PCL5E printers
------------------------------------------------
The bidirectional port monitor for HP-PCL5E printers (the HP LaserJet 4
family of printers) does not work correctly in this release. This will
be corrected in the next release.

Printing With Image Color Matching
----------------------------------
Printing with image color matching is not functional in this release of
Chicago.

Self Test Page Automatically prints without prompting user first
----------------------------------------------------------------
There is a known problem with the printer self test page always 
printing after installing a new printer. This will be corrected
in the next release.

Win 3.1 Printer Driver settings not being preserved after upgrading
-------------------------------------------------------------------
Win 3.1x printer driver settings are not being preserved after upgrading
to Chicago. This is a known problem which will be corrected in the next
release.

Problems Installing Printer: Files in use
-----------------------------------------
If your default printer is a non-PostScript printer, you can't install
another non-PostScript printer after doing anything printer related.
Similarly, if your default printer is a PostScript printer, you can't
install another PostScript printer after doing anything printer
related. Workaround is to install both PostScript and non-PostScript
based printers, then make the PostScript the default printer when you
want to install a non-PostScript printer, and vise-versa. This is a
known problem which will be corrected in the next release.

DISPLAY
=======

Known Problems
--------------
If Chicago reports a problem with your display settings at startup, 
make sure that "Use device" is set in the System control panel, Device 
Manager page, display adapter Properties, General page, Device Usage 
section.

If your display is corrupted when a windowed MS-DOS Prompt or 
application is opened, change the properties for the program to 
run full screen by default.  This is a known problem on Compaq
AVGA and Qvision, and some Tseng W32 adapters.

Cursor corruption on Orchid Kelvin and other Cirrus Logic 5434
display adapters.

M6 bugs fixed in this release
-----------------------------
It is now possible to change desktop area to 640x480 without 
restarting (provided color palette and font size stay the same).

MODEM COMMUNICATIONS
====================

New features in M6.2
--------------------
All AT command modems are now detected by the Modems control 
panel.  In this release, most are detected as generic modems, e.g. "14400 
Kbps Modem" (incl. some models that were detected by name in M6).  The 
detection scheme is in the process of being revised.  Many more models 
will be detected in future releases.

M6 bugs fixed in M6.2
---------------------
Performance of background comm applications is improved during 
foreground activity.

M6.2 bugs fixed in M6.3
-----------------------
Sporadic failures of Windows comm apps (e.g. WinCIM) caused by COMENUM.VXD
should be fixed.  If you experience these with this build, please submit a
bug report immediately.

MOUSE
=======

M6.2 bugs fixed in M6.3
-----------------------
Speed control is working again in the Mouse control panel.

CORE
====

New core features and bug fixes for this M6.3 release:
------------------------------------------------------
Continued performance enhancements.   This version of Chicago should be 
faster than either M6.2 or M6, but it's not yet up to the final release
goals on a 4MB machine.  If you are installing Chicago on a 4MB machine 
with a network, setup will install several networking protocols as well 
as the file/print server by default.  The server portion is probably 
something you don't want to run on a 4MB machine and removing it should 
decrease the memory requirements for Chicago and make your applications 
run faster.  In future releases, Setup will not (by default) attempt to 
install the server software.  Also, if you have MSCDEX loaded in your
config.sys for a 4MB machine, you should remove that line in order to 
increase performance for this build.

BASE
====

M6 bugs fixed in this release
-----------------------------
1. FLAG_NO_BUFFERING fixed to work as doc-ed in API.
2. IN-2000 adapter related bugs fixed.
3. Sony miniport bug fixes and performance tweaks.
4. Panasonic miniport bug fixes and performance tweaks.
5. Old Future Domain BIOSes (which were buggy) now supported.
6. CD now uses sync data transfer (and async is a user option).

New features in this release
----------------------------
1. PCI IDE supported through protect mode IDE driver.
2. Protect mode driver for Mitsumi miniport.
3. Protect mode driver for Mediavision (with Trantor CD interface).
4. Protect mode driver for DblSpace and DrvSpace drives.
5. UI for manipulating adpater related settings and drive letters.
6. Virtual Memory applet redesigned and bugs fixed.

CONTROL PANEL
============
Regional Settings: Selecting a locale has no effect until you reboot 
the system.

PLUG AND PLAY
=============

M6 Bugs fixed in this release:
------------------------------
- Using PCMCIA modems with Win16 applications.
- "New device found" and/or "Device conflict" messages should not appear
  any longer during setup/first boot on PCI or EISA machines. Please file
  detailed bugs if you still see these messages.
- "Safe detection" has been added to the setup process. If certain classes
  of devices such as network or CD-ROM are not detected via safe methods you
  will be prompted to force hardware detection on these classes.
- Better "crash recovery" during detection. Please file detailed bugs if
  you still have multiple hangs during setup.

New features in this release:
-----------------------------
- PCMCIA install wizard will help you do the right thing when enabling the
  Chicago PCMCIA support.
- PCMCIA support will be enabled automatically unless you have a network 
  or SCSI card. If you have one of these cards you'll need to go to the 
  Device Manager tab in the System control panel and select "use device" 
  in the PCIC or Databook properties. This will take you through the 
  PCMCIA wizard.
- The following portables have been tested with the Chicago PCMCIA 
  drivers:
  AST Bravo, Austin, Compaq Aero, Compaq Elite, Compaq Concerto,  Compudyne,
  DEC 425SL, Gateway Handbook, Gateway Colorbook, IBM Thinkpad 750, 755, 355,
  360, 500, NEC Versa V, Versa E, UltraLite, Toshiba T4600, T4700, T4800,
  T3400, T3300, TI TravelMate, TI M-Series.
- Hot docking works on Plug and Play portables with docking stations.
  Docking support includes automatic switching of screen resolutions when
  docked and undocked.
- Device Manager now includes a hierarchical "tree view" of your system.
- Device Manager allows printing of system and device properties and
  resources.
- Serial port enumerator enables automatic installation of Plug and Play
  modems and mice.
- Video enumerator enables automatic installation of Plug and Play 
  monitors.

Known issues in this release:
-----------------------------
- Hot removal of IDE PCMCIA card may cause a "blue screen". This is  
  harmless, hit enter to recover.
- Installing hardware from the new device control panel may result in an
  installation with no hardware resources. If you install a device in this
  way and you know the resources the device is using you should reserve
  those resources from the device manager under system properties.
- Enabling PCMCIA on some portables may cause the system to reboot. If this 
  happens, remove all PCMCIA cards from your machine, restart and disable 
  PCMCIA via the Device Manager tab in the System control panel. Please 
  file a detailed bug report specifying the type of portable, amount of 
  memory, cards installed, etc.

REGISTRY/REGEDIT:
=================
M6 Bugs fixed in this release:
------------------------------
- Automatic recovery when registry gets corrupted
- Several minor cleanups to the Regedit user interface.
- A bug was fixed which would cause Regedit to GP fault at startup on
  certain machines.  If you still encounter GP faults with the new version 
  of Regedit, please be sure to file a WinBug through Compuserve.

New features in this release:
-----------------------------
- Regedit now remembers screen position and window size settings.
- Regedit now includes a search feature, which will allow you to search 
  for text in Key names, Value names, or Value data.  Searching for binary 
  data is not supported.
- Regedit can now be run in real-mode to import or export registry
  information to/from .REG text files. Run REGEDIT /? for syntax details.
  Note that running regedit from a Chicago MS-DOS box will still invoke
  the GUI editor, however.

POWER MANAGEMENT:
==================

M6 Bugs fixed in this release:
------------------------------
- A bug causing intermittent hangs in suspend or resume operations has 
  been resolved.
- Machines which used to crash at Chicago startup when APM features were
  enabled should work properly now.
- Several fixes to the battery meter to work around buggy status reported
  by various machines have been included.
- Screen saver power management features are no longer visible unless your
  machine has the required hardware and software interfaces.  These
  requirements are: a) An Energy Star (VESA DPMS) monitor, which is settable
  from the Monitor Settings property sheet, and b) a system BIOS supporting
  either APM 1.1 or VESA BIOS Power Management extensions.

Known issues:
-------------
- Some machines may not suspend "automatically" based on inactivity 
  timers. However, user-initiated suspends should still work correctly.
- Resuming from suspend while running in fail-safe mode may cause disk
  access problems on some machines, typically resulting in GP faults which
  require a system reboot.

PEN WINDOWS
===========
1. The pen driver does not work on the Compaq Concerto even though it's
listed as one of the supported hardware configurations.  The Grid 
convertible, however, is now supported.

2. On a system with multiple users, an individual's customized settings
can be saved by turning on "Users can customize desktop settings" in
the Profiles dialog in the Security applet in the Control Panel.  These
settings include options such as ink color, ink width, and other pen
related attributes.  However, there is currently a bug which prevents
an individual's training to be loaded when this setting is turned on.

3. There is currently a bug which prevents the user from writing in the
Edit Text dialog or the Insert Text dialog if they are opened with a
gesture.

4. When running the debug version the Chicago pen extensions, do not
plug your mouse into the Com 1 port. Doing so can cause unpredictable
mouse and pen events.

5. Pressure pens do not work with the WACOM HD-648A.  If you turn off
this option in the registry, your pen should work fine.

ACCESSIBILITY
=============
The following notes describe features designed for users with disabilities.

New features in this release:
-----------------------------
1. Accessibility features can now be adjusted using the Accessibility icon
in Control Panel, which has on-line help.
2. A new accessibility status indicator can be displayed on the task bar or 
as a floating window.
3. The SerialKeys feature now functions to allow alternative input devices
to simulate keyboard and mouse input.
4. The High Contrast feature now allows you to switch between normal and 
high contrast color schemes.

New bugs since M6
-----------------
1. SerialKeys will cause a system errors when turned off, and you can't 
change settings once the feature is turned on.
2. Appearance schemes chosen using the High Contrast feature are not always
reflected in the Display property sheet, the Accessibility Status 
indicator, and the system Start button.

SDK/DDK
======
New Printer Commdlgs
--------------------
Note there are new printer commdlgs in the SDK.  These include an 
updated File/Print and File/Page Setup dialogs.

