Windows 95/4.00.122/RELNOTES.rtf

Release Notes 6/9/94

Contents

Introduction

Note for International Keyboard Users

Installing the SDK

Accessibility

Applets - File Viewers

Applets - HyperTerminal

Applets - International Control Panel (Regional Settings)

Applets - MSPaint

Applets - Miscellaneous

Applets - WinPad

Applets - WordPad

Application Compatibility

Communications - SDK\DDK

Devices, Drivers &amp; Controllers

Disk Defragmenter

Display Adapters &amp; Monitors

Display Drivers - SDK\DDK

Doublespace

Error Messages

General System Issues

Help

Image Color Matching - SDK\DDK

International Character Support

Mail

Mail - Compuserve Connections

Mail - MAPI

Microsoft at Work - FAX

Modems &amp; COM Ports

Mouse

Mouse Drivers - SDK\DDK

Modems - SDK\DDK

Multilingual Content Support

Multimedia - Retail

Multimedia - SDK\DDK

Networks: Setup

Networks: Clients

Networks: General

Networks: Briefcase

Networks: Remote Access and Modems

OLE 2.0 - Object Linking and Embedding

Online Registration

PCMCIA

Pen Services API

Pen Computers

Plug and Play

Power Management

Printing

ScanDisk

Setup

Shell

TAPI - Telephony API

Visual C++

VSERVER Error Messages

Windows Shells

=

= Introduction =

These Release Notes for Chicago Beta 1 documents known problems in the Operating System, the included applications (applets), and system utilites. Please read these notes carefully to help you use and test this Chicago Beta as completely as possible. When submitting bug reports, please check these release notes first. You do not need to submit bug reports on the problems already documented in these release notes, unless specific information is requested.

These notes are organized alphabetically by functional area. If you are looking for a specific peice of information, it may also appear underneath of headings like “NETWORK” or “PLUG and PLAY”, which cover lots of disparate areas also. For instance, printing issues are discussed under both Printing and Network:Printing.

SDK/DDK release notes are displayed in blue. These notes only appear in SDK and DDK versions of the Chicago CD. The retail or end-user notes that appear in black are in the Retail kit as well.

For More Information on Chicago:

For more information on using Chicago, and “What’s New”, use the “START” button on the task bar, and select “HELP”, then choose “WHATSNEW” in the Contents tab. Other general Chicago user information, including how to use new features like the Briefcase, can be found in the HELP guide also.

The document OVERVIEW.RTF in the root directory is extracted from the “Reviewer’s Guide,” described below.

Online sources for Chicago Information

Microsoft has recently put a number of electronic information distribution networks in place to distribute Chicago information. The goal is to achieve near simultaneous distribution of Chicago information worldwide. Here are the various electronic forums which currently contain Chicago information:

(1) Online systems. On Compuserve GO WINNEWS. Other systems currently working with us include PRODIGY, AOL, and GENIE.

(2) The Microsoft FTP server contains all of these files. Connect to ftp.microsoft.com to retrieve them from the \peropsys\win_news\chicago directory.

(3) Bulletin Board Networks -- FIDO*Net, Canada Remote Systems, MSDL, and Windows Online also contain complete sets of these files.

(4) The Microsoft WWW server is expected to be online in early July. It will contain many, but not all, of these files in hypertext form accessible to Mosaic users and other users of the internet WWW server. When it becomes available you will connect to http://www.microsoft.com

Documents available Online

The material we're distributing consists of whitepapers, press releases, guides, speeches, powerpoint slides, and Q&amp;A's.

The “Reviewer’s Guide” (revguid3.zip) is a very comprehensive document describing Chicago features and functionality. It contains lots of good User Interface tips and tricks. This is a Microsoft Word for Windows 6.0 document. It is a 1 meg zip file, and expands to about a 10 meg doc file (with lot’s of graphic images).

The list below is a sample of what is available. The information so far includes:

BILL_EMA DOC 53,760 05-11-94 Bill G's keynote address at the EMA.

CHICOQA2 DOC 47,104 02-07-94 The January Chicago Q&amp;A

GATCMX93 DOC 62,976 05-11-94 Bill's speech at COMDEX 1993

LEHMAN DOC 45,056 05-11-94 Bill's speech to Shearson Lehman

REVGUID3 ZIP 1,042,321 06-01-94 The Chicago Reviewers Guide for M6

INETQ&amp;A DOC 7,168 04-25-94 Q&amp;A on Microsoft and the Internet.

GAMES PPT 49,664 04-22-94 PPT from the WinG launch.

GAMESUM DOC 222,720 04-22-94 Writing HOT Games for Windows guide.

WINGTECH PPT 45,568 04-22-94 Tech presentation from WinG launch.

NETBACK2 DOC 552,960 05-17-94 Chicago Networking Backgrounder

OBJECT7 DOC 609,792 05-11-94 Microsoft's Object Strategy

OLEBG2 DOC 242,688 05-11-94 OLE 2 Backgrounder

OLEQA DOC 49,152 05-11-94 OLE Q&amp;A

P&amp;PTCHBG DOC 81,294 09-21-93 P&amp;P Tech backgrounder

REMOTQ&amp;A DOC 11,776 05-17-94 Chicago remote/mobile computing Q&amp;A

MGMT2 DOC 142,848 03-18-94 Systems Management whitepaper

TAPIBG1 DOC 230,912 03-22-94 TAPI Backgrounder

TAPIQ&amp;A DOC 15,360 03-22-94 TAPI Q &amp; A

TCPIPQ&amp;A DOC 10,240 05-16-94 TCP/IP Q&amp;A

Developer oriented files:

BIGPIC7 DOC 27,136 01-06-94

GREAT11 DOC 33,280 02-21-94

MSDNART DOC 49,931 01-28-94

VCSTRTWP DOC 67,072 05-11-94

= Note for International Keyboard Users =

CHANGING THE DEFAULT KEYBOARD LAYOUT FOR DIFFERENT LANGUAGES

To change the keyboard layout which is used by the shell and by default in applications follow the following steps:

1. Open the Control Panel, Keyboard, Language page

2. Click on Add, select the Language entry which gives the keyboard layout that you want, click Ok

3. Select the English (American) language which should still be at the top of the list, Click Delete.

4. Click Ok to leave this control panel

5. A messagebox will appear stating that you cannot uninstall English keyboard support; ignore this warning and press OK.

6. Click Ok in the dialog which says that the layout will not be unloaded until you reboot.

7. Restart Chicago

Upon return to Chicago, the new default keyboard layout that you selected should be active.

You cannot change keyboard layouts from the Device page of the Keyboard control panel.

This process will be simplified in the final Chicago.

Note also that Chicago's Multilingual Content Support allows multiple keyboard layouts to be loaded and switched among with a hotkey (see separate note below in the Multilingual Content section).

= Installing the SDK =

If you would like to use the MSVC++ tools with the Chicago SDK, please use this installation sequence:

1. Install the Chicago Beta operating system from the Chicago CD

2. Install MSVC++ from the MSVC++ CD, run SETUP from the MSVC20 directory

3. Install the Chicago SDK from the Chicago CD, run SETUP from the SDK directory

If you are not using the MSVC++ tools:

1. Install the Chicago Beta operating system from the Chicago CD

2. Install the Chicago SDK from the Chicago CD, run SETUP from the SDK directory

To install the MAPI SDK:

Follow the instructions below in the MAIL - MAPI notes.

To install Win32s:

Run INSTALL.BAT from the Win32s directory.

Installing the SDK or DDK on Windows NT 3.5.

The SDK and DDK setup programs will not run on Windows NT 3.5. The SDK and DDK files come uncompressed on the CD. If you need to install the SDK or DDK on Windows NT3.5 simply treecopy the files from the CD to your hard disk.

= Accessibility =

High Contrast Mode hotkey not working

The High Contrast Mode Hotkey (left ALT+left SHIFT+PRINTSCREEN) does not adjust all system colors, with the result that some portions of the Chicago user interface will not be legible. Color schemes can be adjusted manually using the Display property sheet.

SerialKeys feature not working

The SerialKeys feature does not work correctly in this release. Please do not use it at this time; updated files will be made available on CompuServe which correct the problem.

Help not yet available

When you press an emergency hotkey to activate an accessibility feature a confirmation dialog is displayed. The Help for these dialogs is not yet available. In future versions the Help button will take you to a help topic which briefly describes the feature and in turn provides a pathway to the property sheet where the feature can be adjusted (including turning off the hotkey).

Features incompatible with third-party mouse and keyboard drivers

The accessibility features are not compatible with some third-party mouse and keyboard drivers. If you install a virtual mouse device designed for Windows 3.1, you will not be able to use the MouseKeys feature. If you install a virtual keyboard device designed for Windows 3.1, you will not be able to use any of the keyboard-related accessibility features. For this reason the features will not be available if you install Microsoft Mouse version 9.01 software.

MouseKeys loses ENTER keys in menus

When MouseKeys is on, you may have to press ENTER twice to activate a highlighted menu item.

FilterKeys does not work with editing keypad

When the SlowKeys, BouceKeys or RepeatKeys features are turned on, pressing any key on the editing keypad will simply beep but not otherwise function. The editing keypad is located between the normal alphabetic keys and the numeric keypad on Enhanced 101- or 102-key keyboards.

Cannot drag sliders in Access Utility

The Access Utility (ACCESS.EXE) supplied as a testing tool with this beta release of Chicago has several dialog boxes with slider controls. These controls cannot be adjusted by dragging the slider with the mouse, but they can be adjusted using the keyboard or by clicking in the scrollbar regions or the scroll areas.

Hotkey combinations support right-side keys

Several emergency hotkey combinations used to activate or deactivate accessibility features currently trigger when you use the modifier keys on the right-hand side of the keyboard. In the final version these will only trigger when the left-hand modifier keys are used. For example, MouseKeys should be activated by left Alt + left Shift + Numlock, but in this release it is also triggered by right Alt + right Shift + Numlock. In addition, the hotkeys will trigger even if the Ctrl key is down, but in the final version they will not.

Incorrect error message strings

Some of the error messages generated by the accessibility features are incomplete or reference incorrect filenames.

= Applets - File Viewers =

Determining if a Format can be Viewed

For this release, the file extension is used to determine if the file can be viewed. If you want to view a particular file, ensure the extension is the default for that file type. The default extensions for the file types supported in this release are listed below:

.ASC=&quot;ASCII file&quot;

.BAT=&quot;MS DOS batch file&quot;

.BMP=&quot;Windows Bitmap Graphics file&quot;

.CDR=&quot;Corel Draw up to v 4.0 files&quot;

.DLL=&quot;Dynamic Link Librarie files&quot;

.DOC=&quot;ANY of a number of document formats, including WinWord x, WordPad&quot;

.DRW=&quot;Micrographix Draw files, all versions&quot;

.EPS=&quot;Encapsulated PostScript files&quot;

.EXE=&quot;Executable files&quot;

.GIF=&quot;Compuserve GIF file&quot;

.INF=&quot;files used by the setup program&quot;

.INI=&quot;configuration files&quot;

.MOD=&quot;Multiplan v 3, 4.0, 4.1 file&quot;

.PRE=&quot;Freelance for Windows v 2.0&quot;

.RLE=&quot;Bitmap files (RunLengthEncoding)&quot;

.RTF=&quot;Rich Text Format file&quot;

.SAM=&quot;AMI and AMI Pro up to 3.0 files&quot;

.TIF=&quot;Tiff file (includes &quot;

.TXT=&quot;Text file&quot;

.WB1=&quot;Quattro Pro for Windows v 5 file&quot;

.WDB=&quot;Works v. 3 Database files&quot;

.WK1=&quot;Lotus 1-2-3 v 1'n'2 files&quot;

.WK3=&quot;Lotus 1-2-3 v 3 file&quot;

.WK4=&quot;Lotus 1-2-3 v 4 file&quot;

.WKS=&quot;Lotus 1-2-3 file or MS Works v 3 Spreadsheet file&quot;

.WMF=&quot;Windows Metafile&quot;

.WPD=&quot;WordPerfect v 5.x for MS-DOS and WordPerfect for Win v 6 Document files&quot;

.WPS=&quot;Works v. 3 Word Processing files&quot;

.WQ1=&quot;Quattro Pro v 1-4 for MS-DOS file&quot;

.WQ2=&quot;Quattro Pro v 5 for MS-DOS file&quot;

.WRI=&quot;Windows 3.x WRITE files&quot;

.XLC=&quot;Excel 4 Chart file&quot;

.XLS=&quot;Excel 4 and 5 Spreadsheet file&quot; Note, If you have a problem viewing a particular file, be sure and include both the file you are trying to view and the version of the application used to create the file.

Graphics and OLE Objects Not Shown

When viewing a word processing or spreadsheet file, graphics and OLE objects in the file are not shown. This is a limitation in the file viewers.

Font Style not Applied

When viewing a word processing or spreadsheet file, the View/Fonts dialog will show font styles in the middle list box, i.e. normal, bold, italic, etc. These styles are NOT applied to the document by design and this middle list box will be removed in a future release.

Excel 5 Charts not Supported

Excel 4.0 Charts can be viewed but support for Excel 5.0 Charts will be added in a future release.

= Applets - HyperTerminal =

Installing a Modem First

If you have not installed a modem using the control panel applet, HyperTerminal will ask you if you would like to and then give an error message, saying that this feature is not yet implemented. HyperTerminal will let you continue, however it will not work correctly. The work around is to install a modem using the control panel applet before running HyperTerminal.

Must Specify a Location

If you have not previously set up a location, HyperTerminal will call Dialer Assistant which will require you to edit your default location. After specifying your area code in the Dialer Assistant you will need to actually close down HyperTerminal. You can save this connection, and refresh the folder, to quickly restart HyperTerminal using the phone number you already specified in this connection.

Your Location

When using the configuration dialogs in HyperTerminal, if you modify your location details or add a new location, you will need to shut down HyperTerminal, and restart it to dial. TAPI will correct this in a future release. If you just created a new connection, save it, and refresh the folder to reopen it.

Incorrect Display on VGA Monitors

Dialogs may have to be repositioned when using HyperTerminal on VGA monitors.

Must Clear Screen Buffer

If the screen buffer is full and then a current connection is terminated and a new connection is established, characters from the new connection will overwrite the screen buffer. To avoid this, clear the screen buffer before establishing a new connection by stopping and then restarting HyperTerminal. These problems will be addressed in a later release.

Some Area Codes in Foreign Countries Do Not Work

Some area codes in foreign countries do not work correctly in this release. This will be addressed in a future release.

Previous HyperTerminal Connections from Build 99

If you received build 99, any connections that you saved using HyperTerminal will not work. You will need to recreate these connections.

= Applets - International Control Panel (Regional Settings) =

Changing the Default Locale

In this beta, changing the default locale is not supported.

Locale Names

The list that will be shown for this beta will be in HEX format. These will be actual names before the final release.

= Applets - MSPaint =

Custom Colors Cause Problems

If you use custom colors, either by creating one or capturing a screen or opening a bitmap which uses one, copy, paste, redraw, and many other operations will not work correctly.

Text Input Issues

-- If the text tool is used to open a text box, text is typed into the box and then some of the text is highlighted, the highlighted text will not be visible or the highlighting will not be drawn correctly.

-- if the toolbar is over the text box when the text is placed, the intersection of the text and the overlapping toolbar image is placed on the picture

-- if text is typed into a text box beyond the right border, the text will wrap, but the last character typed on the previous line is lost. Image Editing Issues

-- Skewing with an angle over 45 degrees does not work correctly

-- Stretching does not work

-- Rotate by 90 degrees doesn't erase previous image (selected area).

-- Rotate by 90 degrees doesn't work for whole image.

-- Rotate by 270 degrees and rotate by 180 degrees (selected or whole image) doesn’t work correctly. Set As Wallpaper

Set As Wallpaper (Center) works as tiled.

No OLE Drag and Drop

OLE drag and drop operations do not work in this release.

F1 for Help Doesn’t Work

F1 for Help doesn’t work correctly now. Work around is to use the Help, Help Contents... command to access help.

= Applets - Miscellaneous =

==

Calculator and Clock

We will be adjusting the user interface of these applets to conform to the Chicago UI style guidelines for our next beta milestone. Please do not submit any bugs against these two applets.

Calendar and Cardfile

These two applets have been replaced by the WinPad applet.

Notepad and Write

These two applets have been replaced by the WordPad applet.

Phone Dialer

There are known crashing bugs using the Dialer utility when hanging up. Please do not submit bug reports about this problem. However, do submit reports for problems unrelated to hanging up.

= Applets - WinPad =

WINPAD CALENDAR APPLICATION

Error When Switching Calendar Orientation

The Calendar application sometimes generates a &quot;subscript out of range&quot; error after numerous switches between portrait mode and landscape mode. This occurs only when the vertical scroll bar in the Day view is at the bottom of the screen. If you continue switching between modes, a GP fault may result. If you see this error, close the Calendar application and then tap or click its application button to reopen the Calendar.

WINPAD TO DO APPLICATION

Delay in Updating After Date Change

In some scenarios, the To Do application does not immediately update the display when a date change is processed by Control Panel's Date/Time applet. Accessing another tab and then returning to the Day view usually causes the date display to be updated correctly. This problem will be fixed in later versions of the product.

Check Boxes in Properties Dialog Not Available

In some cases, choosing Properties from a to-do item's icon menu brings up a dialog box with the check box items not available. The check boxes will be enabled if you enter or change other to-do item options and then return to the Properties dialog box. This problem will be fixed in later versions of the product.

HIDING AND SHOWING PRIVATE ITEMS

Erratic Behavior When Processing Private Items

In some WinPad applications, private items are not processed correctly. This may result in items not being hidden when specified as private, or items being removed from the display even though the item is not marked as private. This problem will be fixed in later versions of the product.

PICK TIME DIALOG

&quot;Type Mismatch&quot; Error Generated

A &quot;Type mismatch&quot; error occasionally results from changing the time in the Pick Time dialog and then choosing the OK button. This only occurs when the text of the hours, minutes, or AM/PM indicator is selected and then deleted. This problem will be fixed in later versions of the product.

FEATURES NOT YET IMPLEMENTED

Keyboard Support

Keyboard support is not fully implemented in this release. Therefore, some buttons (such as the OK button) must be clicked with the mouse or pen.

WINPAD DATA FILES

WINPAD.DAT and WINPAD.IDX

WINDOWS\SYSTEM\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.

Compatibility with Other WinPad Releases

The WINPAD.DAT file provided in future releases of this product may not maintain compatibility with the current release of this file.

Reinstalling Chicago

If you need to reinstall this release of the Chicago beta, follow these steps 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

Order of Operations Important

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.

= Applets - WordPad =

Not Long File Name Aware

This release of WordPad is not long file name aware.

Characters Truncated when Printing

In some situations, when the margins are moved using the handles on the ruler or with Format/Paragraph so that the printed area is different than the File/Page Setup margins, characters will be truncated from the ends of lines and the lines will break in different places on the printout vs. the screen. To avoid this, use the Page Setup margins to set margin widths.

Inserting OLE Objects

Inserting some types of OLE objects into an un-saved WordPad document will fail. Trying to exit WordPad without saving a new document with an OLE object will also fail.

Not OLE Drag and Drop Enabled

This release of WordPad is not OLE drag and drop enabled.

WordPad Faults on Chicago Shutdown

If a document is open in WordPad when Chicago is shut down, WordPad faults.

WinWord 2.0 Documents Not Displayed Correctly

The native file format of WordPad is the WinWord 6.0 file format. Currently, WordPad will try to read in a WinWord 2.0 file but the display is not correct. Future versions will give an error message if a WinWord 2.0 file is used in a File Open operation.

= 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. Please let us know about any application that does not continue to function after the upgrade.

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. Many applications rely on INI and registry settings that are created during setup. Without these settings they may not function correctly. Please take the time to re-install and you will have a much better experience with Chicago. If you decide not to re-install your applications please do not report bugs on the problems you encounter while running them. However, if the application setup fails on Chicago then we definitely want you to report the problem.

SuperStor compression not supported in Beta 1

You may be able to get SuperStor compression working with Beta 1 of Chicago, but we do not believe that we have resolved all of the compatibility issues and therefore do not recommend that you run Chicago with SuperStor for this release. We plan to have SuperStor compression supported in Beta 2.

F4 function with Stacker Ver2.0 &amp; 3.0 and other compression software that are not autoloaded.

When you use F4 to boot into MS-DOS, WINBOOT.SYS loads just far enough to be able to find IO.SYS and MSDOS.SYS on the boot drive, then renames CONFIG, AUTOEXEC, COMMAND and DBLSPACE as appropriate, and then loads and executes IO.SYS. The original CONFIG and AUTOEXEC never get executed during the F4 boot, so the *compressed* boot drive image never gets mounted. This means that we are unable to rename the mirrored files on the *compressed* drive. So when MS-DOS 5 or 6 finally boots and *does* mount the compressed drive, Stacker complains about CONFIG and AUTOEXEC mismatches (since the copies on the *compressed* drive are still Chicago's). COMMAND.COM on the compressed drive is also Chicago's, and that's what MS-DOS will try to load (and fail).

This means that on any system with a compressed boot drive using non-pre-load compression software (eg, not DBLSPACE or Stacker 3.1 or 4.0) would not work with our dual-boot. The only work-around in M6 is to manually rename the files on the *compressed* drive yourself immediately prior to rebooting with F4.

eg, REN C:CONFIG.SYS C:CONFIG.W40

REN C:CONFIG.DOS C:CONFIG.SYS

AD-DOS.COM in AUTOEXEC.BAT prevents Windows from loading

After Dark TSR 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 causes GPF

MYST causes GPF

Quick Time for Windows will cause a general protection fault that will hang the system. A workaround 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.

Applications look for MSDOS.SYS and IO.SYS

Chicago renames your old MS-DOS files MSDOS.DOS and IO.DOS. Because of this, compression utilities such as DBLSPACE, Stacker and SuperStor will not install after Chicago is installed. If any other application installation fails looking for these boot files, please submit a bug report.

The work around it to create zero length IO.SYS and MSDOS.SYS files in the root. Alternatively you can copy WINBOOT.SYS to IO.SYS and WINBOOT.SYS to MSDOS.SYS. The long file names on your system could also pose problems. Please use the LFNBK utility to save your copy of long file names before installing these real mode compression utilities. You can download the LFNBK utility and it’s instructions from CompuServe. (Note: LFNBK must be run from within a Chicago MS-DOS box, not from Single Tasking Application Mode.)

MS-DOS-based application settings

This release of Chicago does not have a complete list of settings for MS-DOS-based application. When running an application you may be presented with a dialog asking if you want to create a PIF. Go ahead and answer yes to the question. In future releases this process will be invisible to the user.

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.

There are a few cases where Int 26h and Int 13h will not be failed.

1) A Chicago-aware application can take an exclusive lock on a particular volume. See the Chicago SDK for more information.

2) If no other application has locked a floppy volume then direct disk writes will be allowed.

3) A user can use the &quot;LOCK&quot; command at the DOS prompt to take an exclusive lock on a particular volume. The LOCK command will only succeed if there are no open files on the volume. After the LOCK command succeeds, any MS-DOS-based application that is run in that VM will be able to perform direct disk writes to the locked volume. The syntax of the LOCK command is &quot;LOCK [Drive Letter]:&quot;. After you are finished with the volume you should UNLOCK it. The UNLOCK syntax is identical to the LOCK command.

NOTE: Existing disk utilities are not aware of the FAT long file name structure in Chicago. Many utilities will truncate long file names down to an 8.3 name. Some utilities may even cause you to lose data. You should be careful in how you use the LOCK command.

Fix System Files

Chicago protects against errant applications which attempt to overwrite system files even though the Chicago files are newer versions than the ones an application will install. Chicago will present the following dialog:

System File Error

The following system files have been replaced with older versions by a

program you recently ran. Windows may not run correctly with these

files installed.

If an application overwrites a system file and you do not get this message, submit a bug report.

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 workaround is to create your data document separately from your mail merge document.

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 &quot;Unable to lock XMS memory-fatal error&quot; if you try to run it with a SoundBlaster/SoundBlaster Pro card. To workaround, 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. Set up Flight Simulator to use the PC speaker during the setup of the application.

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.

Colorado Backup for Windows Not Supported to Tape

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

If you shutdown Chicago with Aldus PageMaker 5.0 still active, your machine will hang. Exit PageMaker before your shutdown Chicago.

AmiPro 3.0 Tutorial Unusable in High Resolutions

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

Microsoft Publisher - Changes to a text frame

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.

WordPerfect 5.2 overwrites Chicago's DDEML.DLL

If you are installing this application over the top of your Chicago installation, and re-start your machine, you will be informed that DDEML.DLL has been overwritten, and asked if you would like to restore the original. However, on this release, the DLL will not be updated. You must do this manually by copying this file from the Chicago &quot;SYSBCKUP&quot; directory (i.e. C:\WINDOWS\SYSBCKUP\DDEML.DLL). After doing so, you need to re-start your system.

Real-Time Mode

When running some MS-DOS games you may presented with a dialog that tells you they require 100% of the CPU time and asks you to run them in &quot;real-time mode&quot;. The text of this dialog is incorrect and there is no real-time mode. The true meaning of this dialog is that the application has programmed the timer to a very short interval. If the game still does not function correctly please mention this dialog in your bug report. This will help us narrow down the problems.

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.

WinFax Pro 4.0

There are two bugs which affect the functionality of WinFax Pro 4.0. To make it work, you must do the following. First copy the Windows 3.1/Windows for Workgroups NOTEPAD.EXE into your Chicago Window's directory, replacing the Chicago NOTEPAD.EXE which calls WORDPAD (this can also be downloaded from the forum).

Secondly, there will be an updated GDI.EXE file which will be posted on CIS (your SYSOP will broadcast it's location when it becomes available). THIS PATCH SHOULD BE USED FOR UTILIZING WIN FAX PRO ONLY! To utilize the fix, you must do the following:

1). Copy the needed file(s) off of the CIS forum.

2). From the Cabinet, locate the file COMMAND.COM (on the root of the &quot;C&quot; drive). Using a right mouse-button click, or using File, Properties from the toolbar, go to the &quot;Program&quot; tab from COMMAND.COM's properties sheet and enable the &quot;Single MS-DOS application mode&quot; check box. After doing this, save the setting by pressing &quot;OK&quot;.

3). After having done step two, active COMMAND.COM either through mouse clicks or through pressing &quot;Enter&quot; in the Cabinet on the file. At this point, if you have any open applications running, the system will shut them down so that you can run in single-application mode.

4). When in single-app mode, rename the GDI.EXE which is in your working Chicago directory (again, to *.TST). Then, copy in the patched GDI.EXE. When you have done this, type &quot;Exit.&quot; This will return you to the Chicago desktop.

5). When you have re-entered Chicago, and have completed using using WinFax, you must go through steps three and four again and replace the patched GDI.EXE with the file which you had renamed (or those on the released CD).

Backup Utilities -

In general, we have found that while using Norton's backup programs for Windows (including Desktop for Windows), there have been incompatibilities with tape units not being recognized/initialized. If you should have this problem, please get the file VFBACKUP.VXD from the CIS forum. This will correct know backup unit issues.

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.

Installing applications from CDROM

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. You can replace this switch after installing your application. An even better solution would be to remove MSCDEX from your autoexec and the CDROM lines in your config.sys, and see if Chicago can use the built-in 32-bit CDROM drivers.

= Communications - SDK\DDK =

Win32 Modem Support

Chicago communications applications should use Win32 Comm API and TAPI to dial, answer, and configure modems. For more information, see the Communications overview in the Win32 documentation, and the TAPI documentation and release notes in the \TAPI directory. At present, the best sample application to refer to is DIALER.EXE, the Chicago Phone Dialer applet. DIALER demonstrates how to use the TAPI functions to make calls and use address translation features, but does not show how to get a Win32 comm handle from TAPI. However, this technique is explained in the TAPI release notes.

New VCOMM Contention Service

The new VCOMM_GetContentionHandler service should be used by VxDs which need direct access to COM and LPT ports, e.g. protected mode drivers for parallel SCSI, disk, dongle, network, sound adapters, etc. This is especially important for support of &quot;passthrough printing&quot; ports on these devices.

Plug and Play COM Enumerator

The \COMPNP directory in the DDK contains a preliminary version of COMENUM.VXD, the Plug and Play COM enumerator. This should be used by manufacturers of serial devices to test new Plug and Play serial devices. The current Plug and Play COM Device specification is also included. See README.TXT in \COMPNP for more details.

= Devices, Drivers &amp; Controllers =

VSERVER Error 6251: the file server cannot be loaded with your disk driver.

If you see this error, your performance will be suboptimal and file and print sharing is not supported. Please see the information under the heading VSERVER at the end of this document..

Sony CDU31A, 33A slow, hangs system, returns corrupted data

The Sony CDU31A and versions of the 33A shipped with Gateway machines are not reliably supported under Chicago. The workaround is to use the real mode drivers and MSCDEX. To remove the protect mode drivers (and use the real mode drivers for the CD-ROM), choose the Device Manager tab in the System Control Panel to remove the device. If this is not possible, remove the file WINDOWS\SYSTEM\IOSUBSYS\SLCD32.MPD directory and reboot your machine.

DPT SCSI controllers with more than one device attached

Systems using DPT PM2XXX SCSI controllers with on board cache may have problems using more than one device on the SCSI chain. DPT is currently working on the problem. The workaround use the real mode drivers for the card.

To remove the protect mode drivers (and use the real mode drivers for the card), choose the Device Manager tab in the System Control Panel to remove the device. If this is not possible, remove the file WINDOWS\SYSTEM\IOSUBSYS\DPTSCSI.MPD directory and reboot your machine.

Future Domain TMC-16xx

A problem has been found with the older BIOS firmware in Future Domain TMC-16XX series SCSI controllers. If the only device connected to the SCSI controller is a internal CDROM, in some cases, the system will hang. To get around this problem, load the Future Domain ASPI drivers in CONFIG.SYS and AUTOEXEC.BAT for the adapter and make sure that DCAM1800.EXE is also loaded in CONFIG.SYS. Do not load any FASTDISK drivers since they do not work with Chicago. As a long range fix, get the latest BIOS from Future Domain for the particular adapter.

NCR MicroChannel SCSI Adapters Not Detected

NCR MCA SCSI adapters are not detected by Chicago. The miniports must be loaded using the New Device icon in the control panel. While in New Device Manager, tell the Wizard that the card is not in the system, so detection will not be attempted.

CD-ROM drives that are handled by a real mode driver and MSCDEX cannot be shared.

Only CD-ROMs with protect mode drivers can be shared at this time. This will be fixed in the next Beta release.

BusLogic Adapters

If you are using Buslogic adapters, You should remove the real mode Buslogic drivers from your config.sys.

Mode Switches can cause DOS VM color problems

Changing screen modes for a DOS VM can cause color distortion problems in Beta 1. We are working on a solution for Beta 2.

ASPI2DOS.SYS causes Chicago to hang during boot on Compaq machines

You should remove the ASPI2DOS.SYS entry from CONFIG.SYS if it is causing your machine to hang under Beta 1.

Incorrect PIF Setting

If a DOS VM is forced to run in exclusive mode because of low memory, the PIF will be permanently modified to run in exclusive mode. For Beta 1 you must bring up the application's properties and turn exclusive mode back off.

Device Manager prevents Windows apps from launching

When the Chicago device manager is active, no Windows-based applications can be launched from an MS-DOS VM command prompt. For Beta 1 you must close the device manager first.

= Disk Defragmenter =

The Disk Defragmenter is not included with this version of Chicago

It will be included in a subsequent release.

= Display Adapters &amp; Monitors =

Setup

If Chicago does not have a new driver for your display adapter when upgrading over a previous version of Windows, it will report it as &quot;Standard Graphics Adapter (VGA)&quot; in the &quot;Change Computer Settings&quot; window, and later display a message that your display driver is invalid. However, you will be able to select your Windows 3.1 driver from a list and continue normally.

Using Windows 3.1 Display Drivers

You can install Windows 3.1 version display drivers from the Display control panel. Go to the Settings page, click &quot;Change Display Type&quot;, click &quot;Change&quot; next to Adapter Type, then click &quot;Have Disk&quot;. Enter the path to the disk or directory containing the Windows 3.1 drivers you wish to use. Select the correct driver to use from the list that appears, and click OK to install. Old drivers will appear in the Select Device dialog under manufacturer type &quot;Windows 3.x Drivers&quot; when &quot;Show All Devices&quot; is selected.

Some Win3.1 drivers require the screen resolution to be specified in the [boot.description] section of SYSTEM.INI, e.g. &quot;display.drv=Acme Inc. 640x480 256 colors&quot;.

General Workaround

If you have problems that might be in a Chicago version display driver, add the line &quot;SafeMode=1&quot; to the [windows] section of WIN.INI, and restart Chicago. This disables all non-essential hardware acceleration, if any. If the problem still occurs, try &quot;SafeMode=2&quot;, which disables all hardware acceleration. Please report all such bugs, noting the effect of either of these switches.

Western Digital

Text may not be displayed properly on some newer Western Digital based display adapters. To work around this, add the line &quot;SafeMode=1&quot; to the [windows] section of WIN.INI.

= Display Drivers - SDK\DDK =

Mini-VDDs

Minivdds are new for this release. These are smaller, easier to write, and more reliable VxDs for save/restore/virtualize of graphics controller states. There are several minivdd source examples, including XGA, Tseng ET4000, and S3.

New Driver Features

The XGA.DRV and FRAMEBUF.DRV minidriver samples demonstrate the following driver features new in this release:

VDD initialization

Software cursor support in the DIB engine

ValidateMode function

800x600 support for 512K adapters

Correct FatalExit behavior

= Doublespace =

DBLSPACE.EXE from MS-DOS 6.x will destroy Long File Names on Chicago

If you are using DoubleSpace on your system, you can install Chicago and still access your compressed drive(s). However, you will not be able to run the DBLSPACE.EXE manager program to perform operations such as resizing or uncompressing your drive(s), or to create additional compressed drives. If you &quot;dual-boot&quot; to MS-DOS 6.x in order to run DBLSPACE, once you have installed Chicago, many compression operations will cause your drive to be defragmented, resulting in the loss of some or all Chicago long file names. One possible work around is to use the LFNBK utility posted on CompuServe to save your long file names before running DBLSPACE.EXE, running DBLSPACE and then using LFNBK to restore your long file names.

DBLSPACE automount not supported

The automounting of compressed floppies and other removable media is not supported by Chicago.

DBLSPACE - Free hard disk space requirements for SWAPFILE

When installing on a machine with 4 meg of ram and dblspace, 10 megs of free space for a swap file on the un-compressed drive is recommennd as a minimum for booting and running Chicago for M6. Anyone installing and using MSVC 2.0 on M6 should leave 15 meg minimum of un-compressed disk space for the swap file as well as ensure that the MaxPagingFileSize in system.ini is commented out or increated to 15 meg.

= Error Messages =

Can not find XXXXXXX.EXE

This error message may also indicate that a .dll or other component associated with an .exe can not be found.

= General System Issues =

Error 6251: File and Print Services cannot load

If you see the message:

Error 6251: In this beta release, file and print sharing services cannot load because

of the disk driver you are using for virtual memory.

this indicates your system is using real mode to access the swapfile. Your performance will be suboptimal and file and print sharing is not supported. If you see this error, please submit a bug report immediately.

If you received floppy disks

The Chicago Floppy Disks 2-14 are in a new Distribution Media Format (DMF). Standard MS-DOS utilities such as COPY, DISKCOPY and DISKCOMP will not work on these disks.

Creating floppy disks from the CD

If you received the CD-ROM, you can create 1.44Mb floppy disk sets by running the TRANSFER.BAT program in the \RETAIL directory. You will need 16 formatted 1.44Mb disks.

Windows 3.1 running in a VM

Chicago can run Windows 3.1 on a separate screen, if you wish. Note that the applications will have to be installed separately for Windows 3.1 and Chicago in this case.

You should only run Windows 3.1 in VGA mode (640 x 480, 16 color). The reason for this is that many Windows 3.1 video drivers require the presence of a separate Windows 3.1 VDD. The VGA driver does not have this requirement and so it functions correctly on the Chicago VDD. The ability to run on other drivers depends on their requirements. It may or may not succeed.

To run Windows 3.1 under Chicago

1. Copy the file WIN31.EXE from your \CHICAGO\SYSTEM directory to your Windows 3.1 directory (usually C:\WINDOWS).

2. Edit the following lines in the file SYSTEM.INI in your Windows 3.1 directory (usually C:\WINDOWS\SYSTEM.INI):

Change To

COMM.DRV=COMM.DRV COMM.DRV=C:\CHICAGO\SYSTEM\DUALCOMM.DRV

MOUSE.DRV=MOUSE.DRV MOUSE.DRV=C:\CHICAGO\SYSTEM\DUALMOUS.DRV

Do this only if the original lines accessed the COMM.DRV and MOUSE.DRV files (the right side of the &quot;=&quot; sign).

3. Set the Command Line and Working Directory in the WIN31.PIF file to reference your Windows 3.1 directory, if it is something other than C:\WINDOWS. To access these properties:

a. Right click on the file C:\CHICAGO\SYSTEM\WIN31.PIF

b. Choose Properties from the context menu

c. Choose the Program Property Sheet

d. Make sure that the Command Line entry starts with your Windows 3.1 directory. Make sure that the Working Directory entry is your Windows 3.1 directory.

4. In your Chicago Main group, create a link to the file \CHICAGO\SYSTEM\WIN31.PIF.

To access Windows 3.1, double-click the icon you just created. Please do not perform Control Panel-related operations from Windows 3.1. However, you can run any application from the Windows 3.1 screen and it will run in a Windows 3.1 environment. To return to Chicago, click on the Chicago icon that will be visible on your Windows 3.1 screen.

Cannot LOCK Drive Where Chicago is installed

Chicago's LOCK command attempts to lock a volume for low-level disk writes. It will fail if any files are open on the drive including the swapfile, loaded .DLLs, running programs, etc. If you are unable to lock a drive while running an MS-DOS prompt under Chicago, try running in single MS-DOS-based application mode.

Fail Safe Boot

Fail Safe boot provides you with access to the Chicago GUI when Chicago fails to boot normally. You should make whatever configuration changes are necessary and then reboot. Fail Safe boot is initiated by pressing F5 right after the &quot;Starting Windows&quot; message appears. There are a few known problems with fail safe boot in this release.

If your registry has been deleted or badly corrupted then fail-safe boot will not start automatically. Since the registry regeneration code runs from inside Windows this is a problem. The work-around for this release is to copy IFSHLP.SYS &amp; HIMEM.SYS from the Chicago directory into the root directory. Use F5 to signal a fail safe boot. The boot sequence will stop because WIN.COM will not be found. Change directories to the \Chicago directory and type &quot;WIN /D:M&quot;. This will cause the fail safe boot to continue. This should only be necessary with a very badly damaged registry.

Fail Safe boot may not finish booting with the debug Windows kernel loaded. This will be fixed in a later release. The problem relates to handling Int 3 without a debugger loaded.

During fail safe boot a dialog will notify you that the network was not loaded. This is by design.

Installing Device Drivers asks for several diskettes

If you add a device driver after Chicago is installed from diskette, you may be prompted to insert several different diskettes. This is a temporary, known problem. It is a consequence of not optimizing the disk layouts the way we will for the final product.

= Help =

MCI commands

The help compiler places an MCI file (AVI, WAV, etc.) into the help file, but WinHelp still reads the file from the disk rather then from the help file. This means the MCI command will only work if the MCI file is in the same location as it was when the help file was compiled.

Context-Sensitive help for labels

Context-sensitive help from the question mark on the title bar does not work on controls with an id value of-1 (typically text labels) or disabled controls. Right-click help does work on these controls.

Drag and Drop

If you select text and drag it from WinHelp to WordPad, first WinHelp will GPF, then WordPad. You can drag text from help to Word 6.

F1 help

If you press F1 in a dialog that has been enabled for context-sensitive help, the popup will display relative to the mouse position rather then to the control that help is being displayed for.

Dismissing context-sensitive help

You must click inside the popup to dismiss it if the popup has been called from a 32-bit application. The focus will not return to the caller's window until you either click on the caller, or 10 seconds elapse with no activity.

= Image Color Matching - SDK\DDK =

Documentation

The Image Color Matching (ICM) APIs are now documented in the Win32 helpfile under &quot;Graphics Device Interface&quot;. A more detailed overview is located in ICMSPEC.DOC in the \DOCS directory. ICM32.DLL and device profiles (*.PF) are built into the retail Chicago release, and installed by Setup into the Chicago \SYSTEM directory. See the ICMTEST.EXE sample application source code in the SDK \SAMPLES\WIN32 directory to see an example of how to use the ICM functions.

Printer Device Profiles

This release includes 5 printer profiles, installed in the WIN.INI [DeviceColorChars] section:

HP PaintJet XL 300 HPX3PC02.PF

HP PaintJet XL300 PostScript HPX3PS02.PF

Tektronix Phaser 200I(4 ) PH200I02.PF

Tektronix Phaser III PXi TPIIIC02.PF

QMS ColorScript 100 Model 30/30i QMS30I02.PF

Although using these profiles in this release will cause incorrect color output when ICM is enabled, they can still be used to test usage of the ICM functions.

Monitor Device Profiles

This release includes eight generic color profiles for monitors, described in the table below. If you don't know which values are correct for your monitor, you can try various profiles to see which works best. To set a monitor profile for ICM to use, copy one of the files below over P22.PF. NOTE: Do not change the &quot;Monitor=&quot; line under [DeviceColorChars] in WIN.INI, it should be &quot;Monitor=P22.PF&quot; in this release (this is a bug that will be fixed in the next release).

Filename Phosphor Type Gamma

B22G1502.PF B-22 1.5

B22G1802.PF B-22 1.8

B22G2102.PF B-22 2.1

EBUG1502.PF EBU 1.5

EBUG1802.PF EBU 1.8

EBUG2102.PF EBU 2.1

P22G1802.PF P-22 1.8

P22G2102.PF P-22 2.1

Scanner Device Profile

Chicago includes a profile for the HP ScanJet IIc. To use this, refer to ICMDOC.DOC.

= International Character Support =

MS-DOS File Names

MS-DOS Box Character Casing Tables are Consistent With Windows NT. This behavior differs slightly from previous versions of MS-DOS in the case of characters which do not have an uppercase equivalent in the OEM codepage. On MS-DOS 6.x and previous, extended characters without uppercase equivalents were converted to unaccented uppercase characters. On Chicago, these characters are stored as accented uppercase characters, but when these cannot be displayed in the OEM code page they are displayed as default characters (underscores.) Chicago's behavior is consistent with the behavior of FAT on Windows NT. The Chicago development team is interested in reports of any compatibility problems that this change may cause.

= Mail =

INFO CENTER

How to Use the Info Center

The Info Center enables you to exchange messages with other users in your group. Using the Info Center requires that you have access to an existing Microsoft Mail version 3.0, version 3.2, or Workgroup postoffice. If you are currently using Microsoft Mail, then you already have a postoffice. If you do not know if you have access to a postoffice, ask your network administrator. If you do not have an existing Microsoft Mail postoffice, you can install a Workgroup postoffice (as outlined in the following section &quot;Installing a Workgroup Postoffice&quot;).

Once you have obtained access to an existing Microsoft Mail version 3.0, version 3.2, or Workgroup postoffice, from the Explorer, map a drive (preferably drive m:) to the postoffice.

Start the Info Center by double-clicking it. Three dialog boxes appear, one after the other.

The first dialog box, titled &quot;MS Mail 3.2 Logon,&quot; is used to access your postoffice. In the server path, type m:\ and in the mailbox field, type your mailbox name (if you don't know what it is, contact your network administrator). In the password field, type your postoffice password. Select the Remember Password check box, and choose the OK button.

The next dialog box, titled &quot;Create/Open Personal Address Book,&quot; asks you to locate your PAB. The PAB (personal address book) is a file that contains mail addresses of people that you commonly send messages to. You won't have a PAB, so you need to create a new one by typing in a filename (we recommend MSMAIL.PAB) and choosing the OK button.

The last dialog box, titled &quot;Create/Open Personal Information Store,&quot; asks you to locate your PST. The PST (personal information store) is a file that contains all the messages that people send you. You won't yet have a PST, so you need to create a new one by typing in a filename (we recommend MSMAIL.PST) and choosing the OK button.

You should now see four folders (Deleted Items, Inbox, Outbox, Sent Mail). To see new messages that other people in your group have sent you, click your Inbox. To send a message to another person in your group, choose New Message from the Compose menu.

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.

Info Center Has Not Implemented the New Window Command on the View Menu

The New Window command on the View menu is not yet implemented.

Cannot Run Simple MAPI 16-Bit Applications on Chicago

You cannot use Simple MAPI from 16-bit applications on this beta release of Chicago. Support for 16-bit applications using Simple MAPI will be available when Chicago ships. You cannot run the 16-bit version of Info Center on Chicago. You cannot run the 16-bit version of the Windows Messaging Subsystem on Chicago.

Info Center Doesn't Save Window State

Info Center doesn't save window positions or layout between sessions.

Remote Usage Is Not Yet Implemented

Shared Folders Are Not Yet Implemented

Users of Microsoft Mail for PC Networks have access to Shared Folders and Private Folders. The current release of Info Center does not provide access to Shared Folders, but does provide access to Personal Folders.

Next and Previous Are Not Yet Implemented in Info Center

The Next and Previous buttons and menu commands are not yet implemented. Furthermore, Info Center does not currently open the next or previous message following a move or delete operation on an open message.

Drag and Drop Is Not Fully Supported in Info Center

The drag and drop functionality is not completely implemented. The workaround is to use the menu buttons or menu commands to move and copy messages.

Can't Insert Objects or Links in Info Center

Embedding objects or links is not yet implemented in the Chicago version of Info Center.

Not All Changes to a User's Profile Are Updated Dynamically

Some changes to the profile (for example, removing a transport provider) are not updated in the current session. For changes to take effect, the user may have to log off and log back onto the same profile.

Compaction Does Not Work on PST in Info Center

The PST (personal information store) has a configuration setting for compaction; this feature is not yet implemented. This means the PST file will never get smaller, even if you delete all your messages from that message store. One workaround is to create a new PST and move messages into the new PST from the old PST.

Cannot Stop a Message from Being Sent Once It Is in the Outbox Folder

When the user sends a message, it is moved into the Outbox folder prior to actually being sent (uploaded). In most cases, the user cannot block the transmission of the message once it has been placed in the Outbox folder.

Cannot Copy Folders Between PSTs in Info Center

Currently, there is no direct way to copy a folder and contents from one PST to another. The workaround is to create a new folder in the target PST and move the messages (using the Move button or the Move command on the File menu). It will be possible to copy a folder between PSTs in the release version.

Address Book Default Settings May Be Incorrect for Mail Version 3.x Users

Address book default settings may be incorrect for Mail version 3.x users. To change the address book default settings: Open the Messaging Profiles Control Panel application. Select the My Profile option, and choose the Edit button. Choose the Profile Settings button in the Edit Profile dialog box. Select the Addressing property sheet page. Mail version 3.x users should set the default address book to Global Address List and add the Global Address List to the Address Book Search Order list.

Can't Reply to Schedule+ Version 1.0 Meeting Requests

Schedule+ version 1.0 meeting requests that are sent can be opened but cannot be replied to.

Temporary Directories in \CHICAGO\MSREMOTE.SFS Directory

Each time a new profile is created, a temporary directory is installed in the \CHICAGO\ MSREMOTE.SFS directory. These temporary directories are not removed when a profile is removed. These temporary directories can be deleted, even if they were created by a profile that has not yet been removed.

Minimum System Requirements

To run the Info Center on the current release of Chicago requires a minimum of a 386/33 processor with 8MB RAM, and 30MB of swap space.

“Password is invalid” Can’t logon with valid password.

When trying to log on to the Work Group Post Office via the dialog box titled “MS Mail 3.2 Logon”, some valid passwords will result in failed logons. The work around is to have the administrator change the password. One password known to work is “password”.

“MS Mail 4.0 Note” menu starts the Briefcase application.

The shortcut menu Start.Programs.Accessories.MS Mail 4.0 Note does not launch a mail application, (the menu command starts the Briefcase application.) This will be fixed in later releases.

= Mail - Compuserve Connections =

INSTALLING, CONFIGURING, AND USING THE COMPUSERVE PROVIDER

Since a full fledged installation utility is not included with this demo release version, it is important that these few steps be followed. (Additional information including support info for the Compuserve provider can be found in the readme.txt file in the \mapi\isv\cis\chi directory)

NOTE: in this release, you must configure the Compuserve provider before using the Info Center. If you have activated the Info Center, you will need to Restart Chicago before continuing.

Installation Steps

Note: you must have a valid Compuserve account number to use the Compuserve Provider to connect to Compuserve.

1. Copy script files: you will need to copy the Compuserve script files into a directory on your

Chicago workstation. The script files are not part of the Chicago release but can be copied

from a workstation that has access to Compuserve. If you currently have a Compuserve

product such as DOSCIM, WINCIM, or CSNAV, the script files can likely be located in a

directory called “scripts”. For easiest configuration, we recommend you create the following

directory structure and copy the script files to your Chicago workstation in the c:\cserve\scripts

directory.

C:\CSERVE


 * - SUPPORT


 * - SCRIPTS

If you do not currently have a CompuServe Product such as DOSCIM, WINCIM,

or CSNAV that has the CompuServe connect scripts, you may obtain the script files by

running the self-extracting pkzip file CSERVE.EXE (located in the mapi\isv\cis\chi directory on

your SDK disk) with the -D parameter, in the directory where you wish to install the script files.

If you choose to run the program in the C:\CSERVE directory, you will obtain a directory tree

structure that looks like the structure above.

2. If you chose a directory other than C:\CSERVE to install script files, add the following line

under the [CompuServe Mail] section in your MSMAIL.INI:

CompuServe-Parent-Dir=X:\MYDIR\

(where X:\MYDIR\ stands for the path to the CompuServe parent directory you are using).

NOTE: Be sure to include the ending backslash.

3. Using the Messaging Profiles option in CHICAGO's control panel, configure the provider such

that you use the CompuServe address book data file called ADDRBOOK.DAT, usually found

in C:\CSERVE\SUPPORT\ADDRBOOK.DAT.

NOTE: To configure the &quot;CompuServe MAPI Services&quot;, use the &quot;Profile Settings&quot; push

button, not the &quot;Edit&quot; push button.

The MAPI Services necessary for the CompuServe MAPI driver are:

CompuServe Address Book

CompuServe Transport

MS Personal Information Store

MS Personal Address Book

By default, when you create a new mail profile (or when you first install Chicago), you will

obtain the MS Personal Information Store and the MS Personal Address Book as a part of that

profile. If you wish to add both the CompuServe transport and address book services, you

may choose the single option called: &quot;CompuServe MAPI Services&quot;. NOTE: If you have not

started the Info Center, start it now. If you have already started prior to this step, you will have

to restart Chicago and then start the Info Center.

4. If you do not have an existing CompuServe settings file (CIS.INI) file present in your

CompuServe parent directory, you will be prompted to enter Communications settings when

you first run the Info Center. The help facility may be used to answer any questions regarding

the proper use of the communications settings dialog, as you complete it.

Driver functions are available by clicking on the CompuServe iconic window. (This will be

found in the toolbar if using Chicago).

5. Also when you first start up the Info Center, you may be asked to supply the locations of

various files, if you have not already done so through the MAPI configuration utility in step #3

above. The CompuServe Address Book file is normally found in

C:\CSERVE\SUPPORT\ADDRBOOK.DAT

When asked to supply the location of the Microsoft Personal Address Book data file and the

Microsoft Personal Information Store file, you may not have these files on your machine if this

is the very first time that you have run Info Center. If that is the case, you may use the dialog

presented to CREATE the files by supplying the file and path name of your choice.

6. When you first run the Info Center with the CompuServe profile, you will be prompted to

choose an active session to use for connecting to CompuServe. In this release, this window

may initially be covered up by the Info Center parent window.

If you wish to always use the active session, you may do so by editing the file MSMAIL.INI,

located in the Windows parent directory. Under the section called [CompuServe Mail], add

the following line:

Use-Active-Session=1

Tips for using this pre-beta release MAPI 1 Driver

- The address type of our MAPI provider is: CompuServe

If you enter new address entries into the private address book, make sure you specify

the address type above.

- The option to connect at &quot;Exit of Mail&quot; should probably not be used since the Info Center

doesn't actually &quot;exit&quot; once started, except when Chicago is shut down.

- By default, the driver is set up to delete retrieved mail from the host computer. If this is not the

desired behavior, you may easily change the behavior by accessing the Settings item

from the CompuServe MAPI driver window.

- If you are unable to dial the modem and/or establish a connection, use the following checklist:

- Connect scripts are present (*.SCR files), and located in the C:\CSERVE\SCRIPTS

directory.

- The communications settings dialog contains the proper information for baud rate,

comm port, phone number, etc.

- The MODEM initialization string matches your modem hardware's requirements.

(Refer to your modem owner's manual for more information.)

- The CompuServe Parent directory points to the proper location so that the above files

are found.

- The phone number supplied supports the baud rate supplied.

- Make sure that the setting for &quot;Show Progress Window&quot; is turned on.

- Currently, the driver will place outgoing messages into the &quot;sent mail&quot; folder prior to the

physical upload process to CompuServe. This is intentional. Note that the mail is not

physically uploaded until the &quot;connect at time&quot; settings dictate, or an immediate send

operation is performed. This mechanism will be modified in a future release to file the

message into &quot;sent mail&quot; after the actual transmission.

- Currently, the MAPI form of Non-Delivery Reports (NDRs) are not generated.

Instead, you may use the copy of the outgoing message filed into the &quot;sent mail&quot; folder if

you wish to modify its contents and resend. MAPI NDRs are also slated for a future

release.

- The current implementation of the CompuServe Address Book services is for accessing a prior

existing ADDRBOOK.DAT file in read-only mode. This is useful for developers who

already have such a file from either DOSCIM, WINCIM, or CSNAV products. If you do

not already have an ADDRBOOK.DAT file, the CSERVE.EXE self-extracting file

contains an example one with a single address. Future versions are planned to allow

both read and write access.

- A typical map of the installed CompuServe Files look like this:

c:\cserve (CIS.INI)


 * - support (ADDRBOOK.DAT)


 * - scripts (*.SCR, MODEM.DB)

c:\chicago (CSERVE.EXE)


 * - system (CSMAP*.DLL, MAPIABM.DLL,CCT200.DLL,CSMAIL.HLP)

Known Limitations of this Release of the CompuServe Provider

-There is a known inconsistency with the handling of attachments within messages. This may cause attachments that you create within a message to not be visible to the CompuServe provider at upload time. This problem will NOT occur if you send the message using the

MS-Binary (TNEF) format.

To alleviate this symptom, we recommend that you send messages with

attachment(s) using the TNEF option. To send a message using TNEF, you must

use the &quot;Send Options&quot; under the File pull down menu in the window used while

composing the message. Checking on the option labeled

&quot;Send as MS-Binary (TNEF)&quot; will cause attachments to be sent properly.

NOTE: The receiver must also be using MS Mail and a service provider that recognizes the

MS-Binary (TNEF) file format for them to be able to view the message's contents.

= Mail - MAPI =

Installing the MAPI SDK

The MAPI SDK (Messaging Application Programming Interface Software Development Kit) is not installed as part of the Chicago SDK. Installing the MAPI SDK on Chicago is a three-step process. First, install the Windows Messaging Subsystem (this must be done from the Chicago Setup program). Second, install the Chicago SDK to get the required development tools. Third, run the MAPI SETUP.EXE program to install the development files. Note that the MAPI SDK supports development on three platforms (Chicago, Windows NT, and 16-bit Windows), so there are three different setup programs; which one you use depends on your preferred development environment. The document you are currently reading concentrates on the Chicago implementation. For more information, and for information on installing to or for other platforms see the README.WRI file in the MAPI directory of the Chicago SDK.

To install the MAPI SDK: From the CD, run \MAPI\CHI\SETUP.EXE. If you have not installed the Windows Messaging Subsystem prior to running the above program, you will be instructed to do so. The MAPI SDK setup program installs all the necessary files, documentation, sample code, libraries, headers, source code, and so on to develop MAPI applications and providers. For information on MAPI, see the online Help file or see the documentation in the MAPI\DOCS directory of the CD.

Cannot Run Simple MAPI 16-Bit Applications on Chicago

You cannot use Simple MAPI from 16-bit applications on this beta release of Chicago. Support for 16-bit applications using Simple MAPI will be available when Chicago ships. You cannot run the 16-bit version of Info Center on Chicago. You cannot run the 16-bit version of the Windows Messaging Subsystem on Chicago.

Additional Information about the MAPI SDK

Additional information about the MAPI and the MAPI SDK can be found in the readme.wri file in the MAPI directory on the CD.

= Microsoft at Work - FAX =

The Microsoft at Work FAX application is not included with this version of Chicago

It will be included in subsequent releases. In addition, the Microsoft At Work FAX group intends to provide this feature for download from CompuServe.

= Modems &amp; COM Ports =

Adding Internal Modems &amp; COM Ports

Chicago displays a &quot;New Device Found: Communications Port&quot; dialog when it detects a new internal modem or COM port adapter in your computer. Click the &quot;Use Default Driver&quot; button when this dialog appears. If the new adapter is a modem, use the Modems icon in the Control Panel to specify its make and model (see additional info, below).

On some PCs, Chicago may not automatically detect a new adapter configured as COM3 or COM4. If this happens, install it manually using the New Device Installation Wizard in the Control Panel. When prompted, select hardware type &quot;Ports&quot;. The wizard will detect the new adapter as a &quot;Communications Port&quot;. You may be instructed to adjust the adapter's interrupt and I/O port address settings in the System control panel.

Using Non-Standard COM Port Interrupt Request Lines (IRQs)

Use the Device Manager in the System control panel to change Chicago's default IRQ setting for a COM port or internal modem. Also, you must add the following line to the SYSTEM.INI [386enh] section, specifying the correct COM port and IRQ for your hardware: COM3Irq=5

The Modems Control Panel

You must specify your modem make and model in the &quot;Modems&quot; control panel in order to use it with the Chicago Remote Access folder, HyperTerminal, and Dialer. If the control panel cannot detect your modem correctly, check for its make and model in the selection list. If the exact model is not listed, then try these tips to find a compatible model:


 * A comparable model name by the same manufacturer will usually work, e.g. a &quot;Practical PM9600FX&quot; modem may work fine specified as a &quot;Practical PM9600HC II&quot;.


 * OEM modems supplied by PC manufacturers are often compatible with Hayes, Microcom, or US Robotics modems. The manual for your modem may indicate compatible models.


 * Try one of the &quot;Hayes Compatible&quot; types listed for manufacturer &quot;Hayes&quot;.


 * Try one of the basic types listed under manufacturer &quot;(Generic)&quot;.

Problems with COM3 or COM4

If you encounter problems accessing a COM3 or COM4 port/modem, try the following tips:


 * Check that the port is installed in the Device Manager in the System control panel. If it is not, install it using the New Device control panel (see more details about how to do this in this section).


 * Check that the port's Input-Output Range and Interrupt Request line is specified correctly in its properties dialog, Resources page.


 * Add the appropriate lines below to your SYSTEM.INI file [386enh] section, specifying COM port, base address, and IRQ settings which are correct for the port:

COM3Base=3E8

COM3Irq=3

= Mouse =

Mouse Trails

This feature is only supported at 640x480 and 800x600, 16 colors. It will be extended to all modes in the next release.

J-Mouse

This Chicago release does not include drivers for the &quot;J&quot; key mouse used on some portable computers. As a workaround, use an external Microsoft or Logitech(R) compatible mouse. Or, edit SYSTEM.INI to install the Windows 3.1 J-Mouse drivers into Chicago. You must change the following SYSTEM.INI lines as they appear in Windows 3.1:

[boot]

mouse.drv=JMMSE.DRV

keyboard.drv=JMKBD.DRV

[386enh]

mouse=JMVMD.386

keyboard=JMVKD.386

Microsoft Mouse 8.x / 9.x

When upgrading, Setup may incorrectly detect when Microsoft Mouse 8.x or 9.x drivers are installed, causing the mouse to freeze. Make sure that your mouse type is set to &quot;Microsoft Mouse or BallPoint&quot; during Setup, or in the Mouse control panel. Also, the &quot;keyboard=&quot; line in the [386enh] section of SYSTEM.INI must be &quot;keyboard=*vkd&quot; (do not use MOUSEVKD.386).

If the Mouse Manager SnapTo feature is turned on, using the right mouse button to drag may cause GP fault errors.

Logitech MouseWare

The current version of the Logitech Mouse driver in Chicago does not support MouseWare utilities.

= Mouse Drivers - SDK\DDK =

VMOUSE driver interfaces have been extended for Plug and Play support. The \SERMOU minidriver sample demonstrates the new interfaces.

= Modems - SDK\DDK =

Modem manufacturers should read MDK.DOC in the DDK \MODEMS directory. This explains how to use the new &quot;Modem Development Kit&quot; to write and test INF files for use with the Chicago Universal Modem Driver.

= Multilingual Content Support =

GetCharacterPlacement, GetTextCharsetInfo and GetFontLanguageInfo are not working

In this beta, these three API's can't be used because the header file wingdi.h is incorrect. The definition for GetCharacterPlacement is missing flags definitions and GetTextCharsetInfo is missing the &quot;WINAPI&quot; name.

The updated WINGDI.H file can be downloaded from the WINDEV CompuServe forum if you need these APIs.

Changing Default Keyboard Layout

Please see the note at the beginning of this document regarding how to change the Defauld Keyboard.

Not Possible to Mix and Match Languages and Layouts

In the Language page of the Keyboard control panel, it is not possible to associate an arbitrary layout with an input language. For this beta, to use the French layout, for example, the user must select the French (Standard) input language. The Latin American layout can be found under the Spanish (Modern Sort) locale. This means that it is not currently possible to use layouts which are not the default for any locale (US-Dvorak and US-International).

Extra Languages Listed in Add Language Dialog

In this beta, selecting some of the languages available in the Keyboard control panel, Language page, Add Language dialog will result in an incorrect error message upon closing the control panel. The affected language will not be added to the loaded list.

The following locales are presently supported directly:

Danish, Dutch (Standard), English (American), English (British), Finnish, French (Belgian), French (Canadian), French (Standard), French (Swiss), German (Standard), German (Swiss), Icelandic, Italian (Standard), Norwegian (Bokmal), Portuguese (Brazilian), Spanish (Modern Sort), Spanish (Traditional Sort), Swedish.

In addition, the following languages and layouts are supported when corresponding fonts are installed as described below:

Russian, Greek, Hebrew.

Existing Applications Enumerate Only Latin-1 Fonts

The fonts in this beta support only the languages of Western Europe. To use multilingual functionality you can install the Cyrillic and Greek fonts which shipped with localized Windows 3.1 in these markets. (Use Settings:Fonts from the Start menu)

Language Switching Hotkey Not Documented

The hotkeys for switching the input language of the active application are Alt+LeftShift and Alt+RightShift. In this beta, this is the only way to switch input language. (Note that you must release the Alt key between consecutive uses of this hotkey.)

= Multimedia - Retail =

Control Panel Property Sheet

The Sound Events property sheet will not play sounds asynchronously for this beta. This means you will not be able to stop them from playing once started.

Saving with Long File Names Not Supported for Multimedia Applications

Media Player and Sound Recorder and other multimedia applications will be unable to save files with the new long file names.

Media Vision Thunder Board

Auto detection of a Media Vision (r) Thunder Board ® may crash the system if you have a second audio card installed. The work around is to remove the 2nd card during the installation and manually change the IRQ address as appropriate.

Media Vision Pro Audio Spectrum

MIDI does not play when using Media Vision's Pro Audio Spectrum audio card.

MusicQuest MQX-32M MIDI Card needs to be manually configured

Users of MusicQuest's MQX-32M cards need to use the device manager to properly configure the card.

MCI ViSCA driver is not working properly

Repeated use of the MCI VIsCA driver will cause the driver to crash. An updated driver will be available on computer shortly.

Panasonic CDROM drives

Panasonic CDROMs may behave inconsistently while playing audio CDs. For example pause or auto-repeat may not work or the driver may hang for long periods of time when accessed.

Reboot Following Media Device Detection

When a new multimedia device has been detected, you must reboot your Windows session. Failing to do so will prevent the new device from working.

Indeo Codec Crashes when compressing files in 32 bit mode

A fixed version of the codec will be available in the Chicago Beta Forum on CompuServe.

Sound Recorder Application

Sound Recorder crashes when run on a system with no sound card.

= Multimedia - SDK\DDK =

32 Bit Capture

32 Bit Capture is not supported in this release of Chicago. Please use 16 Bit Capture.

32 Bit CallBacks Functions are Asynchronous

Therefor when using any 32 Bit multimedia callback functions, you must then issue a yield or sleep.

32 Bit Draw Handlers

32 Bit Draw Handlers are not supported in this release of Chicago.

MCIPuzzl (Sample Application)

32 Bit MCIPuzzl will not run because 32 Bit Draw Handlers are not supported.

timeSetEvent

timeSetEvent always returns failure from 32 Bit.

VxDs

When writing VxDs you must preserve EBX. Previous releases of the Chicago DDK, did not properly save EBX in the Remove_Config handler processing. Please update your code immediately.

In order to compile the multimedia sample VxDs you need to use the C8 compiler and Link386 that came with the PDK2 release.

New multimedia VxD makefiles that are compatible with the C9 compiler in the Beta release will be available in the Chicago Beta Forum on CompuServe.

Building Multimedia Samples

Five of the mulitmedia samples cannot be built using the Microsoft Visual C++ 2.0 tools. They must be built using the tools provided with the M5 PDK. The samples in question are the msmpu401, msopl, mssb16, and mssndsys vxd samples and the vjoyd sample.

= Networks: Setup =

NETWORK SETUP: GENERAL

Closing network control panel incurs long delay

After clicking close or cancel to the network control panel, the computer may not respond for several seconds while your changes are saved. No hourglass is displayed.

Setup incorrectly asks you if you want to overwrite existing files with “older” files from CD

Setup sometimes incorrectly decides that files on the distribution CD are older than the ones on your hard disk. Click “Yes” to All button to overwrite all files.

Cancelling the install of a new component doesn’t remove that component.

If you click the cancel button while setup is copying files for a new net component, the component will still appear in the network control panel, even though it is not fully installed. If you do not want the component, go to the network control panel and remove it.

Changing settings in system.ini will not affect your configuration

The settings in the [network] and [network drivers] sections of system.ini are not used in Chicago. Setup does not delete these settings. Changing these settings will not affect the configuration of Chicago.

No help available in the network control panel or custom network setup work.

This is a known problem and will be fixed in the next beta. For help on network configuration, see the following:

· Release Notes

· Installation Guide

· The network.doc file

· Alpha Resource Kit (available on CompuServe) Error 6251 (Vserver does not load) may appear when booting

Please see the section “VSERVER Errors” near the end of this document.

Error 6251 (NWServer does not load) may appear when booting

Please see the section “VSERVER Errors” near the end of this document.

Fail-safe boot puts up a message saying that network functionality is not available.

Fail-safe boot does not support networking. If you fail safe boot, and see this message, you should click OK. When you boot normally your network should start.

Switching back to Novell NetWare from Microsoft client services for NetWare servers

If you let setup automatically install the Microsoft client services for NetWare and wish to go back to using Novell NetWare, see the installation document for instructions on how to do this.

Cannot see any NetWare servers because setup may have incorrectly detected frame type

When upgrading from Novell NetWare, setup may detect a different frame type than was being used. You can check this in the network control panel by looking at the properties of the IPX/SPX-compatible protocol. The frame type setting is in the Advanced tab.

NETWORK SETUP: NETWORK ADAPTERS

Network Adapter Drivers

Protect mode (NDIS 3.0 format) netcard drivers that worked with Windows for Workgroups 3.11 will not work under Chicago without changes. Additionally, for this release of Chicago, Windows for Workgroups 3.11 and earlier format of setup .inf files will not work correctly. At this point, there are no workarounds. You need to either have a real mode driver (NDIS 2.0 format), an ODI driver or an updated protect mode (NDIS 3.0 format) driver for your netcard, plus a Chicago style .inf file. There are many real mode drivers, updated protect mode drivers and supporting .inf files included in this release.

Setting the I/O address of the IBM 4/16 token ring adapter.

To set the I/O address of this adapter, select either primary or secondary in the Advanced property page for the adapter. The I/O settings in the Resource page will be ignored.

Setup incorrectly detects the IRQ of the Intel EtherExpress 16

Setup may incorrectly detect that this card is running on IRQ 3. To change the IRQ setting while installing Chicago, follow these steps:

1. From the main setup dialog, click the Customize... button to go to custom setup,

2. Click the network button.

3. Go to the properties of the adapter by double click on the Intel EtherExpress 16.

4. Go to the Resources page and select configuration 0.

5. Choose the correct IRQ in the Interrupt (IRQ) field.

6. Click OK for the adapter properties, and again for the network dialog.

7. Click Begin Setup To change the IRQ setting inside Chicago, follow these steps:

1. Open the network icon in the Control Panel.

2. Go to the properties of the adapter by double clicking on the Intel EtherExpress 16.

3. Go to the Resources page and select configuration 0.

4. Choose the correct IRQ in the Interrupt (IRQ) field.

5. Click OK for the adapter properties, and again for the network dialog.

6. Reboot the computer. Changine 3Com Etherlink III (3c509) settings in the network control panel does not change adapter settings

The network control panel does not reprogram the Etherlink III adapter. To change the adapter settings, follow these 3 steps: (1) Use the 3Com configuration disk that came with your adapter to repogram it. (2) Notes the settings just entered. (3) Go to the network control panel and change the settings to the ones you noted. (4) Reboot.

Setup does not configure Chicago for two network adapters properly.

Chicago does not completely support having more than one network adapter in this release. You can add a second adapter in the network control panel. The additional adapters will work in protected mode, but only the first network adapter will work in Single MS-DOS-based application mode.

Your network adapter is not listed in the Select network adapter dialog.

If you know that your net card is compatible with another (i.e. Novell/Anthem NE2000), try choosing the compatible driver. The Chicago beta 1 release supports only a fixed set of network adapters. If your adapter or its compatible driver are not listed, you will not be able to set up the network using that adapter. Chicago beta 1 does not support OEMSETUP.INF files from previous versions of Windows.

Net setup does not detect the tranceiver setting (i.e. whether it is twisted pair, thin net, thick net).

To set the tranceiver setting for those network adapters that support it, follow these steps:

1. Open the network icon in the Control Panel.

2. Open the properites for the net adapter by doubleclicking it.

3. Go to the Advanced property page.

4. In the list box on the left, select the tranceiver setting.

5. On the left, select the proper setting for your tranceiver.

6. Click the “OK” button on this property sheet and then the “OK” button on the net control panel.

7. Reboot the machine. Compaq Concerto Convenicance Base Network Adapter

The network adapter that's installed in the Concerto convenience base is not detected by this beta. You can install the appropriate Chicago drivers by manually selecting the Compaq Ethernet 16E adapter from the Network Properties option in the setup 'Customize' screen

DEC Network Adapters

Users of DEC network adapters are advised to verify the detected configuration via the Advanced Settings\Network during setup. If the detected IRQ or I/O ports are not correct you should set them manually via the Adapter\Properties dialogs.

NETWORK SETUP: UPGRADING WINDOWS FOR WORKGROUPS

Setup does not detect Computer Name and Workgroup

Under some circumstances, setup will not detect the Computer Name and Workgroup for the computer. Setup will prompt you to enter these settings if it does not detect them.

Net0111 error after upgrading from Windows for Workgroups with TCP/IP.

The network will still function, but net setup does not remove the old version of TCP/IP. To remove the old version of TCP/IP, remove the following lines from autoexec.bat:

· tcptsr

· tinyrfc

· nmtsr.exe

· emsbrf.exe

· sockets.exe

· USER=C:\machine

· INIT=C:\machine Setup does not preserve the default protocol.

Chicago setup always sets the IPX/SPX-compatible protocol to be the default protocol. If you want another protocol to be the default protocol, follow these steps:

1. Open the network icon in the Control Panel, or duing Custom setup, click on the Network Options button.

2. Click the “Protocol...” button.

3. Select the protocol you want to be the default protocol.

4. Click the “Set as default” button.

5. Click the Close button and then the OK button on the net control panel to save the settings. Persistent connections are not preserved.

In Windows for Workgroups, users can create network connections that always exist, even when they reboot. Chicago setup does not preserve these network connections. Users will have to create the connections again.

Setup does not migrate the protocols that were running in Windows for Workgroups.

You may have to go to the network control panel and add the protocols again.

NETWORK SETUP: FILE AND PRINT SHARING FOR NETWARE

Configuring Workgroup or SAP browsing

By default, file and print sharing is configured so that computers appear in workgroups as do Windows NT-based servers and computers running Microsoft Network file and print sharing. You can select whether or not a particular machine can maintain the list of machines in a workgroup using the Browse Master setting. If you prefer to use NetWare SAP browsing and have computers appear in the Bindary, change the SAP Browsing parameter to Enabled. When SAP browsing is enabled, the Browse Master setting is not used.

“The pass-through server has not been specified”

If you see the error “The pass-through server has not been specified.” message appears each time the computer boots, then you must take one more step to configure file and print sharing. File and print sharing for NetWare grants access to printers and folders on a per-user basis. It requires the name of the server to retrieve the names of users on a network. To set the name of this server, follow these steps:

1. Open the network icon in the Control Panel.

2. Go to the Security page.

3. In the text field titled, “Obtain list of users and groups from”, enter the name of a Novell NetWare server that maintains user accounts.

4. Click OK.

5. Reboot the computer. NETWORK SETUP: INSTALLING NOVELL NETWARE

When booting, LSL reports that it has already been loaded.

If you configure Chicago to use a Novell NetWare Workstation shell with the Microsoft Network client and manually set the driver type to ODI, setup adds lines to netstart.bat to start the ODI drivers. But, it doesn’t remove the same lines in the startnet.bat that the Novell NetWare installer created. This causes LSL to report that it is already loaded. The network should function completely. You can remove the command lines for LSL.COM and your ODI driver if you wish.

NETBIOS SUPPORT

Running Lotus Notes

Lotus Notes requires users to enter the LANA number that Notes will use. As described below, LANA numbers are assigned dynamically. To configure Chicago to use Lotus Notes, set the protocol you want to run Notes on using the procedure described in the “Assignment of LANA numbers section”, then configure Notes to use LANA 0.

Assignment of LANA numbers

In Chicago, NetBIOS LANA numbers are assigned dynamically starting at 7 and working downward. This was done to accomodate dynamic Plug and Play events like removing a network adapter while the computer is running. If you are running in such a dynamic environment, Chicago does not garuntee that the a given protocol will receive the same LANA number on each boot. If the computer’s network hardware never changes, the LANA numbers may not change at each boot.

As in Windows for Workgroups, you can force a particular protocol to always occupy LANA 0 by selecting it as the default protocol. You will have to do this if you run Lotus Notes. To select a default protocol, follow these steps:

1. Open the network icon in the control panel

2. Click the “Protocol...” button.

3. Select the protocol you wish to be default, and click the “Set as default...” button.

4. Click “Close” and then “OK” to the network control panel.

5. Reboot the computer. NETWORK PROTOCOLS

To use LMHosts, enable DNS

To use an existing LMHosts file, enable DNS by using the DNS Configuration property sheet for TCP/IP, in the network control panel. This will create a registry entry to enable LMHosts name resolution as well. By default, Chicago will look in the Windows directory for the LMHosts file.

Enabling DNS enables name resolution for both Sockets and NetBIOS

Enabling DNS will enable DNS name resolution for both Windows Sockets and the TCP/IP NetBIOS transport (NBT). If you wish to disable DNS name resolution for only NBT, manually change the integer value from 1 to 0 in the registry under

HKLM\System\CurrentControlSet\Services\VxD\MSTCP &quot;EnableDNS&quot;

If you wish to disable DNS name resolution for only Windows Sockets, change the value of the &quot;DNSEnableWINS&quot; entry in the [DNS] section of SYSTEM.INI from 1 to 0.

THIRD-PARTY NETWORKS: GENERAL

See network.doc for more information on setting up third-party networks

TCS 10-Net, Artisoft Lantastic, Beame and Whiteside BW-NFS 3.0: must be only network

In this beta release, you cannot run any of these three networks along with a second network. With other supported third-party networks, you can run any Chicago 32-bit networking components at the same time.

Printing to network printer

Setting up for a printer that is shared via a 3rd party server will fail. The workaround is to redirect lpt1: through an MS-DOS VM to the 3rd party share, then use printer setup for lpt1. For example, if a network printer is connected to lpt: type:

“net use lpt1: \\servername\sharename” at an MS-DOS command prompt (this command depends on the network you are using; please consult the product documentation to find out how to redirect a LPT port). Then use printer setup in the Control Panel.

Setup uses winboot directory for “net” commands

In general, setup may attempt to modify autoexec.bat so that any line containing the command 'net' is directed to the c:\winboot directory. This will create problems if the 'net' line is from a 3rd party network. Check your autoexec.bat file after setup and ensure all commands point to the correct directory.

BANYAN VINES SETUP

To complete setup, you must edit autoexec.bat

After setting up Chicago, you need to use SHIFT-F5 so Windows isn't loaded and edit autoexec.bat to ensure the necessary lines for starting the Banyan network come immediately after the “c:\winboot\net init /dynamic” line. Ensure also that the &quot;net start&quot; line has a full path to the c:\winboot directory and is between the REDIRALL and ARSWAIT lines.

Installing over an existing VINES client

When doing a clean Chicago install over an existing Banyan VINES client, a Banyan dialog will appear when VINES.DRV loads. You need to:

Check the box for keeping files on the network.

Click INSTALL.

Chicago will then exit and restart.

The Banyan dialog will reappear.

Check the box for keeping files on the network.

Click CANCEL.

This will allow the VINES client to run correctly.

PC-NFS SETUP

Setup may not copy files

Ensure the following files are copied to the c:\winboot directory, as setup may not copy them:

sockdrv.sys, pcnfs.sys, nfs-ndis.sys

LANTASTIC SETUP

Lantastic server cannot be running during setup

The Lantastic server cannot be run when Chicago is setting up.

TCS 10-NET SETUP

Invalid Drive Specification error message

If you are running TCS 10Net, and you encounter an error message from MS-DOS &quot;Invalid Drive Specification...&quot;, you need to use MS-DOS's SETVER command on the file 10NET.COM. (Type SETVER /? at an MS-DOS command prompt for help regarding this command).

NETWORK BROWSING (Network Neighborhood &amp; Mapping Drives)

Empty window opens on network resource even if resource is not there

If you try and connect to a network resource and it isn't available or you don't have access privileges on the resource, Windows doesn't put up an error message or give any feedback of the problem. It just opens up an empty window.

= Networks: Clients =

USING THE MICROSOFT NETWORK CLIENT

System appears to hang when attempting to browse a workgroup

When attempting to browse a workgroup in which the browsemaster or backup fail to respond correctly, the system may appear to be hung, when in fact the browse attempt will timeout.

Captured NetWare printers are enumerated twice in the UI

LPT ports captured by the NetWare shell will appear twice. This is only a UI issue and does not affect the captured printer.

Cannot view print queue on down-level server

You may be unable to view the print queue on some older Microsoft-compatible servers with the new 32-bit client.

USING MICROSOFT NETWORK FILE AND PRINT SHARING

File and print sharing (VServer) fails to load (error number 6251)

Please see the section “VSERVER Errors” near the end of this document.

Down level clients can't use shared LFN folders

Older Microsoft or Microsoft-compatible clients (ie., Lan Manager, Workgroup Connection, Windows for Workgroups, etc.) may have problems connecting to and using a shared directory with a long file name as the directory name. Having a short share name does not correct this problem

Auditing does not work

This feature does not currently function.

USING THE MICROSOFT CLIENT FOR NETWARE

Login.exe not supported

Login.exe (command-line login in the login directory of the NetWare server) is not supported by the Microsoft client services for NetWare. You can use the cabinet to log into a server. If the MS Client for NetWare is your default client, you can log into the first NetWare server via the login prompt that appears when you start Chicago.

First Drive behavior is different from NETX or VLM

The Microsoft client for NetWare does not map the first network driver to the preferred server. However, it does make a connection to the preferred server, so that this server shows up in your Network Neighborhood.

Login scripts are not processed

In this beta release, login scripts are not executed when running the Microsoft client for NetWare.

Cannot create long file names on NetWare server through the Cabinet

To create a directory or file with a long name on a NetWare server, you must do this from an MS-DOS command prompt (an MS-DOS window). It will not work if you attempt to do this from the graphical user interface.

Creating a long file name on server returns error if OS/2 namespace is not loaded on server

In order to create files or directories on a NetWare server that have long names, you must have the OS/2 namespace loaded at the server. (Note: this is by design) To load the OS/2 namespace on a NetWare server, consult a NetWare manual.

NetWare Utilities

All utilities that reside on a NetWare server can be executed (except for login); you must run them from an MS-DOS command prompt (an MS-DOS window). You may find that PURGE takes a long time to complete, but does work. VOLINFO Version 2.15 may not work. SETPASS may give an error message, but does work. The NetWare 4.X administrative utilities are not supported in this beta release.

Attaching to a server you're already logged into

If you are logged into a server and you use the command-line to attach to that same server (with a differet username, for example), you may see the error message &quot;CDR 100: Unknown error&quot;. The attachment will not be completed.

NWPopup

The NWPopUp messaging utility is not currently supported by the Microsoft Client for NetWare.

NOVELL NETX AND VLM CLIENTS

NWPopup does not work

NWPopop does not currently work in Chicago with Novell’s NETX or VLM client.

MICROSOFT FILE AND PRINT SHARING FOR NETWARE (see also Setup Notes above)

File and print sharing (NWServer) fails to load (error number 6251)

NWServer can fail to load for several reasons; the system pages through MS-DOS due to an incompatible disk driver, a compressed drive exists for which there is no protect mode driver, or an unknown or incompatible TSR has loaded before IOS.SYS. Certain viruses may also cause it not to load. Check for the existance of the file &quot;IOS.LOG&quot; which may help you to determine why the sever failed to load and remove any unneeded TSR if applicable. If the problem is due to an incompatible disk driver, the only way to run file and print sharing on this computer is to replace the drive with another type of drive (i.e. replace the IBM PS/2 model 70 EDSI controller with a SCSI controller). If you see this message, please file a bug report so that we can track and fix this problem.

Microsoft Client for NetWare required

Setup allows you to install MS file and print sharing for NetWare without installing the Microsoft Client for NetWare. However, you must install the Microsoft Client for NetWare (via the network control panel) in order for MS file and print sharing for NetWare to work.

NetWare server used to provide user list must have an account named Chicago

To run MS file and print sharing for NetWare, you must enter the name of a NetWare server on your network that will provide a user list and user authentication. (This is entered in the Network Control Panel, Security tab - see setup notes above). You must create an account named Chicago on that NetWare server. This account must not have a password, and does not need any permissions.

NetWatcher does not work remotely

In this beta release, you cannot remotely administer (i.e. run NetWatcher against) a Chicago computer with MS file and print sharing for NetWare.

Must be configured for SAP for NETX and VLM clients to access

In order for NETX and VLM clients to see and connect to Chicago computers running MS file and print sharing for NetWare, the Chicago computer must be configured to use SAP (see previous note). Chicago computers running the Microsoft Client for NetWare can connect to computers running either the SAP Browsing or the Workgroup browsing.

NETX and VLM clients cannot capture shared printer on Chicago

NETX and VLM clients cannot connect to a shared printer on a Chicago computer running MS file and print sharing for NetWare.

Only able to give permissions to “The World”

When you enter the name of the NetWare server that provides the userlist for user-level security (in network control panel, security tab), it will not check to see if this is a valid server. If it is not, you will not be informed, but when you go to the Sharing tab on a directory, and attempt to add permissions, you will only be able to give access to “The World”.

= Networks: General =

NETWORK PRINTING

Error message when dragging net printer to local printers folder

When installing a network printer by dragging a shared printer object from a network server to the printers folder on a local machine, you may see the message &quot;Printer Setup - Invalid Network Path&quot;. If you are confident that the printer path is valid, select &quot;Use this Path&quot; and continue on with the installation.

Point and Print and user-level security

To allow point and print on a machine with user level security, it is necessary to add read-only permissions to the printer driver directory (usually \windows\system) as well as adding permissions to the printer itself.

Microsoft Print Services for NetWare in Chicago

When running the Microsoft Print Services for NetWare, you cannot be logged into the same NetWare server as both a user and as print services.

Set your timezone for proper file times on a network

If you are running Chicago as either a peer server, sharing files to other people, or you are using Chicago in an existing Windows NT-based server network, you need to set your timezone properly before file times are displayed properly on networked file systems. Without the timezone information set properly, file times may be off by several hours, depending upon how far away you are from Greenwich Mean Time. To set your timezone, go into the Chicago control panel and choose the &quot;Date/Time&quot; icon, then the &quot;Timezone&quot; tab in that property sheet.

Restart necessary after changing TimeZone

When changing timezone settings it is necessary to restart Chicago before these settings will properly take affect. In beta 1 you will not be prompted to restart after making changes in the Time Zone page under Date/Time in the Control Panel.

System DLLs changed after Time Zone change

If you change your time zone, when you restart, Chicago will warn you in error that a number of system files have changed. Choosing 'Ignore' in the warning dialog will fix the problem. This will be fixed in a later release

NETWORK SECURITY

Permissions not enforced if a directory with a long file name is accessed via MS-DOS name

With user-level security, if you share a folder that has a long file name, the permissions will not be enforced if the folder is accessed via the MS-DOS (8.3) name.

Sharing icon not updated automatically

When a folder is shared or unshared, the icon for the folder does not update until you explicitly refresh.

User level sharing with extended characters

Trying to add user permissions for folders with extended characters causes and error message and fails.

Unsharing a folder gives bogus message

Under user-level security, if a shared folder is un-shared and user permissions deleted, a dialog appears prompting to share the folder.

Bringing up Choose User dialog takes a long time

The user-level security Choose User dialog (when adding permissions to a resource) may take several seconds to come up. This list is populated from server lists so it takes a while to populate.

User-level security for Microsoft network file and print sharing requires Windows NT domain name, NOT Windows NT Advanced Server name

In the previous alpha release of Chicago, user-level security required the name of a Windows NT Advanced Server in order to work. In this beta release, a Windows NT domain is required in order for user-level security to work with Microsoft network file and print sharing.

SECURITY CONTROL PANEL

Master Key only controls system logon password and Windows NT domain password

In this beta release, the only passwords that are controlled by the Master Key are the system logon password and Microsoft network passwords.

APPLETS

Chat &amp; Hearts over remote access

Currently Chat and Hearts do not work over a remote access connection.

WinChat &amp; incoming calls

Winchat will not respond to an incoming call until it has been started once. If you open, then immediately close Winchat, it will answer all incoming calls after that.

WinPopUp - cannot send messages to a workgroup

You cannot send WinPopUp messages to a workgroup.

NETWATCHER

NetWatcher does not run remotely against Chicago file and print sharing for NetWare

NetWatcher can remotely monitor file sharing on a Chicago computer running Microsoft Network File and Print sharing. However, NetWatcher cannot remotely monitor file sharing on a Chicago computer running Microsoft File and Print Sharing for NetWare.

Error message viewing a printer share property sheet

When viewing a printer’s sharing property sheet from withing NetWatcher, you may see an incorrect error message which you should ignore: “Illegal path name. Please choose another path.&quot;

Admin must have same user-level security Windows NT domain as user in order to share a directory on the user’s machine

This applies only under user-level security. If an admin is running NetWatcher on a remote user machine, and the admin wishes to share one of the user’s directories, the admin and the user must use have user-level security configured to use the same Windows NT domain as the user list provider

Establishing persistent shares remotely

Currently, if you create a share on a remote machine, you cannot make that share persistent. Instead, Chicago will attempt to make the share persistent on the local machine.

SYSTEM POLICIES EDITOR

Policies file has system, hidden, and read-only attributes

Upon booting the the System Policies downloader sets the “policy.dat” file to be given system, hidden and read-only attributes. Admins have to change the attributes back to write to chaange policies.

Logon expiration policy does not work

The System Policies Editor includes a policy for logon expiration; this policy does not work in this beta release.

Cannot copy user/workstation policies from one user/machine to another

In the System Policies Editor, you cannot copy the policies of one user or workstation to another user or workstation.

Allows duplicate user or workstation names.

System Policies illegally permits addition of multiple users/workstations with the same name.

Policies that cannot be disabled

The following policies, once set, currently cannot be disabled via the policy editor. To disable, delete the registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Policies.

-minimum password length

-require alphanumeric password

SNMP AGENT

Must add setting to registry for SNMP console to see Chicago SNMP Agent

In order to allow an SNMP management console to contact a Chicago SNMP Agent, you must add a setting to the Chicago registry. Using the “regedit” utility, locate the key HKLM\System\CurrentControlSet\Services\snmp\Parameters\PermittedManagers. Add a value whose name is 1 and value is the IP address of the management console.

NETWORK BACKUP AGENTS

Arcada agent requires updated NLMs from Arcada Software

In order to use the Arcada backup agent, you must (1) have Arcada’s BackupExec for NetWare (single server or enterprise edition), and (2) have two updated Arcada NLMs. Please contact Arcada Software to obtain the NLMs.

Cheyenne agent requires updated NLMs from Cheyenne Software

In order to use the Cheyenne backup agent, you must (1) have Cheyenne’s ARCserve for NetWare product, and (2) have two updated Cheyenne NLMs. Please contact Cheyenne Software to obtain the NLMs.

Cheyenne agent: user interface doesn’t update correctly

The user interface for the Cheyenne ARCserve backup agent is supposed to display status information, but this does not work in this beta release. You do not need to input any information in order for this to work.

Arcada agent publisher: choose “file new” to display all drives

The publisher displays the drives and directories that are to be backed up. It should automatically display all of your hard drives, but in this beta release you must choose “New” from the File menu for this to work.

= Networks: Briefcase =

Updating Files

When updating files, the &quot;thermometer&quot; gauge fills up too rapidly so the Briefcase may still be updating files even when the gauge says the update is done.

Choosing “Update All” when Briefcase is empty corrupts database

If you choose Update All and there are no files in the briefcase, the Briefcase database will be corrupted. You must restart the system to use the Briefcase after this (you will be notified that you must reboot). It is OK to delete the corrupt database when prompted.

Editing Open Briefcases

Do NOT try and rename, delete, or move a Briefcase that has an open Cabinet window. The database is locked and cannot be deleted when the Briefcase is open. Put the focus on another folder and then do whatever you want.

Icons in Update Status

The update status doesn't display the application specific icons like other parts of the cabinet. A file can be identified by its name.

Sorting in Details View

The details view buttons (name, sync copy in, status) don't sort the files like the details buttons in other folders.

All files in the Briefcase become orphans if database is corrupted

The Briefcase database can get damaged. The files will all be intact but their relationship to files outside the Briefcase will be destroyed. As a result, all the files will become orphans. You must re-add all files to the Briefcase.

Update Status doesn't change

When you change a file in the Briefcase, the status column in the Details view doesn't change to reflect the new update status of the file (&quot;Needs Updating&quot;) until you close the Briefcase and reopen it.

“Find Original”

The “Find Original” command does not work across network drives.

= Networks: Remote Access and Modems =

Using Microsoft client services for NetWare and Remote Access

If you are using Microsoft’s Netware Client and Chicago’s Remote Access, you should replace the file “NWREDIR.386” in your \windows\system directory with the an updated version. You can get the updated either from the \Drivers directory of the CD or you can download it from CompuServe if you do not have Chicago on a CD. This version has a fix for large data transfers over slow links.

Must have a network driver loaded in order to open Remote Access folder

You must have at least one network driver loaded in order to open the remote access folder. Otherwise, you will be repeatedly prompted to logon to the network when you open the folder. The problem can be fixed by installing the Microsoft Point to Point Protocol Driver using the

Network Control Panel

Do not install modem using the “New Device” control panel

Do not use the &quot;New Device&quot; Control Panel to install a modem. Use the modem control panel.

Do not install PCMCIA modem in modem control panel

Do not install a PCMCIA modem using the modem control panel if you are using Chicago's 32 bit card services. When you insert a PCMCIA modem you will automatically be prompted to install the modem.

= OLE 2.0 - Object Linking and Embedding =

SDK Sample Apps assume MSVC2.0 Beta Toolkit

The OLE sample apps located in the \sdk\samples\win32\ole2 directory of the Chicago SDK assume the use of the MSVC20 beta toolkit. In order to get these OLE samples to build properly, you must make sure that the MSVC component directories preceed the Chicago SDK component directories for the INCLUDE and LIB paths. For example:

set INCLUDE=c:\msvc20\include;c:\msvc20\mfc\include;c:\sdk\inc32;...

set LIB=c:\msvc20\lib;c:\msvc20\mfc\lib;c:\sdk\lib32;...

If you have and are using the Win32 SDK, please note that the OLE samples provided with that SDK build with the headers and libraries included with that SDK as is; no special handling of the INCLUDE and LIB paths are required.

32-bit OLE Common Dialogs

- 32 bit OLE common dialog for Insert Object, Paste Special, Convert, Links and Object Properties will be in a future release.

- a new 32 bit common dialog for page setup will be in a future release

OLE 2 Documentation

Please refer to the documentation on the SDK CD for more information on OLE 2 and Chicago.

= Online Registration =

Online Registration does not remember computer usage information.

If Online Registration is run more than one time, address and user information is remembered, but the usage information (what software is used and where the computer is used) is not. The information has to be re-entered.

Fatal errors are generated on debug terminals while running Online Registration.

If you are running Chicago with a debugging terminal attached, you will see fatal errors on your debug terminal. You can ignore these for this beta release; they have no effect on the performance of Online Registration or Chicago.

Online Registration does not work outside the United States.

While online components of Chicago will work worldwide in future versions, the beta software will always dial an &quot;800&quot; toll-free number which is not accessible outside the United States.

Dates must be entered in mm/dd/yy format.

Dates entered in any other format are not accepted in this beta release.

= PCMCIA =

Compaq Concerto

This beta does not support the PCMCIA controller that is installed in the Compaq Concerto. You should continue using the PCMCIA drivers provided by Compaq.

I want to use Chicago's 32 Bit PCMCIA support

You can either have Chicago's setup automatically install the PCMCIA support or you can enable it yourself after installing Chicago. If you're currently using real-mode Card and Socket Services drivers or device enablers, you will need to disable the real-mode drivers. The preferred method is to comment out the relevant lines in your CONFIG.SYS file. This will allow you to restore your previous drivers if needed. Example:

rem DEVICE=C:\PCMCIA\SS365.EXE

rem DEVICE=C:\PCMCIA\CS.EXE After disabling your real-mode drivers remove the PCMCIA cards from your system and reboot. If you have not already done so, initiate the Chicago setup process. If you are using a PCMCIA network card, it is recommended that you leave the real-mode Card and Socket Services drivers and do not enable the Chicago protect mode drivers if a Chicago protect mode driver is not available for your card.

Drivers for Intel compatible and Databook PCMCIA controllers are always copied to the Chicago directory if these controllers are detected on your machine. During the first boot, a dialog will be displayed allowing you to enable the drivers. If you choose not to enable the Chicago PCMCIA software, these drivers will be left dormant on your system. You can enable PCMCIA later by accessing the &quot;General&quot; property sheet for the PCMCIA controller in the Device Manager and resetting the &quot;Disable Device&quot; check-box.

The Chicago PCMCIA software can be disabled by accessing the &quot;General&quot; property sheet for the PCMCIA controller in the Device Manager and setting the &quot;Disable Device&quot; check-box.

After enabling the Chicago PCMCIA support, inserting a PCMCIA card for the first time will trigger the automatic device installation process. The current beta includes support for certain fax/modems, hard drives, and network, cards. If your card is supported Chicago will suggest to install a matching driver for it. If the card is not directly supported, Chicago may suggest a default driver. At the end of the installation process the card is initialized and ready to go. When you insert a card that has already been installed you will hear a short beep confirming the card has been recognized and configured by Chicago.

Nativly supported PCMCIA network cards:

Xircom

Socket EA, EA+

Fujitsu

= Pen Services API =

Boxed-Edit (BEdit control)

The new implementation of the Boxed Edit control is not currently backwards compatible with the old one. It now also supports the Chicago look and feel, which may slightly reduce the number of boxes that can be displayed.

HEdit control

All applications that are marked as Chicago applications are automatically made pen aware. All edit controls will be converted into HEdit controls, and a lens button (a button that provides one-tap access to a writing window) appears under certain conditions, reducing some of the available client area.

RichEdit control

There is no pen functionality available in this release for the 32-bit RichEdit control. This version of Writepad, however, uses a 16-bit RichEdit implementation that provides Windows for Pens 1.0 level of functionality.

Gesture Manager

The gesture manager app from Windows for Pens 1.0 has been discontinued.

Trainer

This beta release includes a handwriting trainer application (btrain.exe) for rapidly training the recognizer on your handwriting style

32-Bit support

PENWIN32.DLL and PKPD32.DLL, the 32-bit versions of PENWIN.DLL and PKPD.DLL are not yet available for this release.

On-screen Keyboard

The onscreen keyboard provided in this release will be redesigned and reimplemented.

Registry

This release of pen services does not yet use the Registry. If you need to change a setting, you can do this in PENWIN.INI.

Debug Pen Driver

If you are running the debug version of the pen services and see the mouse pointer moving randomly across the screen, try switching to the retail version of these components: PENWIN.DLL, PKPD.DLL, PENC.DRV, and VPEND.386.

= Pen Computers =

Setup

If you already have Windows for Pens installed in a Windows 3.1 installation and you use Chicago setup to upgrade your Windows installation, you may crash. You should either setup Chicago in a new directory, or remove Pen Windows from your Windows 3.1 setup before upgrading.

You can remove Pen Windows from your Windows 3.1 setup by removing &quot;penwindows&quot; from the &quot;drivers=&quot; line in the &quot;[boot]&quot; section of SYSTEM.INI (be sure to leave the rest of that line intact) and by removing the &quot;penwindows=&lt;path to penwin.dll&gt;&quot; in the [drivers] section.

Upgrading existing pen machines

This release will only run on a desktop with a tablet. Upgrades for existing pen machines, such as the Compaq Concerto, will be provided in the next Beta release.

Only VGA video driver supports Inking

Also, in this release, only the VGA video driver (640 x 480 x 16 color) supports inking. Other video drivers and modes will be supported in the next release.

Pen Tablets

At this time, Chicago setup only offers Wacom tablets as choices for your pen hardware. If you have another tablet, such as a SummaGraphics tablet or a Calcomp tablet, choose one of the Wacom tablets when prompted by Setup. You will not get pen functionality right away. When Chicago is fully installed, you can configure the pen driver for your tablet from the Pen Options button in the General pane of the Pen control panel.

= Plug and Play =

Setup crashes during hardware detection:

If you encounter problems when setting up Chicago from the distribution disk(s), please refer to the following steps:

If your machine stops during the &quot;Analyzing System&quot;/Hardware detection process:

1. Ensure that at least 3 minutes have passed with neither disk nor screen activity (moving magnifying glass). Some detection routines are lengthy and the machine may appear to stop temporarily while they are running.

2. If the machine has truly stopped, try pressing F3 or the exit button. If the system responds to the exit button, choose &quot;No&quot; to continue the setup process.

3. If the machine does not respond to the exit button, reboot your machine, first by pressing Ctrl-Alt-Del, then by using the machine's power button or reset switch if the first method fails.

4. Once the machine has restarted, re-run the SETUP program.

5. SETUP should ask you whether you want to attempt to recover the &quot;failed install.&quot; Choose Yes. A second dialog is shown which only has one choice, OK. After pressing OK, the system detection will run but skip the portion which caused the initial failure. Note that in some systems you might encounter additional failures during the hardware detection process.

6. If the system stops again during the hardware detection process, go back to step 2 and repeat the process until the hardware detection portion of setup completes successfully. It is very important that you NOT delete any system files between installation attempts.

Once setup is complete and Chicago is running, please file a bug report with Microsoft. In addition to the standard files collected by the bug reporting tool you will need to send us the following files:

• C:\SETUPLOG.TXT

• C:\SYSTEM.DAT

• C:\DETLOG.TXT In order to copy SYSTEM.DAT you will need to use the ATTRIB command at an MS-DOS prompt to make the file non-system and non-hidden. Once you have copied the file, use the ATTRIB command again to reset the file attributes to their original state.

If you encounter problems during the &quot;Copying Files&quot; portion of SETUP:

1. Exit the Setup program.

2. Reboot your machine

3. Rerun the setup program

4. Choose &quot;Yes&quot; when asked if you want to recover the failed install.

The file copying process should complete at this point. However, you should file a bug report with Microsoft and send us the files mentioned above so we can determine if one of the detection routines has caused the failure during the copy process.

Removing the registry (System.dat)

If for any reason you need to remove the Chicago registry you should do the following.

1. Reboot your system

2. Press the F8 key when the message “Starting Windows” appears

3. Respond Y to all prompts except the Win prompt to which you should respond N

4. Logon to the network if you need to

5. do the following attrib command on the registry

attrib -r -h -s system.*

6. ren system.* oldreg.*

7. Rerun Chicago setup (Without rebooting)

Installing Chicago on a MicroChannel machine

The Beta release of Chicago may install some MicroChannel devices a second time if you re-install Chicago with a previous registry file intact. This may cause some devices to crash at Chicago startup. The NCR 810 SCSI host adapter is an example of such a device. Follow the instructions above for removing the registry and reinstalling Chicago.

Display resolution does not automatically change when I dock or undock

The beta release of Chicago has not implemented this feature yet. You should run your

machines in VGA mode. This feature will be implemented for the next beta release.

Chicago warns about running setup with Qemm or 386Max

In the Chicago beta, hardware detection may fail to identify all devices in your system if you are using these 386 memory managers. Chicago displays a beta message to warn you of the danger. You may choose to continue however Chicago may not be able to detect all the hardware in your system. If this happens to you, simply install the drivers using the New Device control panel wizard. A second workaround is to remove the 386 memory manager and restart setup.

Microsoft Windows Sound System plays the same sound forever

The Microsoft Windows Sound System is a software configurable device which favors IRQ 7. On some computers which allow the user to disable parallel ports, the Windows Sound System will start play a sound continuously. If you experience this problem, you should check and see if your BIOS setup utility will allow you to enable/disable your parallel ports. If it does ensure your ports are enabled and then register that port with Chicago by running the new device control panel applet.

Intel EtherExpress 16 is disabled after installing Chicago on an NEC Versa

This is an intermittent problem. We are investigating this but at present, there is no way to avoid this problem. If this happens to you, install your network using the Network control panel.

Registry restore does not restore the USER.DAT file.

User.dat is backed up during normal registry maintenance, but it is never restored. If you experience corruption in your user.dat file you will need to manually copy the backup.

PC hangs or net connections are lost when resuming from a suspend.

For the Chicago beta, we recommend you not suspend your machine if you have an active network connection. This problem should be fixed in the next Beta release.

Redetect Dialog appears when no new hardware has been added

There are some software configurable devices like the Intel EtherExpress 16 and the Sound Blaster Pro which can cause Chicago to believe it has seen a new piece of hardware when the driver returns an error. This can happen for a variety of reasons and the only symptom is the dialog which will want to redetect your hardware. Normally, this dialog should only appear when you power on in a docked or undocked state for the first time. If you are certain you have not just docked or undocked, you can choose to detect or not. If you experience problems with the device, you can set a configuration by selecting properties for this device and setting resources manually.

Chicago won't remove a configuration once it has been set.

In the Chicago beta release, the automatic selection is not functional. There will be no way to remove a forced config from the Device Manager. This problem will be resolved in the next beta release.

NCR 810 SCSI Host adapter on a PCI Machine with Phoenix BIOS

We have had reports of some machines where the NCR810 is hardwired to IRQ 15. Attempting to set this device to any other resource will appear to work but in fact will not. This will cause the driver to fail leaving your SCSI bus disabled.

= Power Management =

Suspend/resume features do not work with net cards.

In this release, (and in all prior versions of Windows) network adapters do not prepare correctly when portable computers attempt to enter their suspend mode. Symptoms range from losing net connections upon resume to complete system crash on resume. For M6, we recommend against using suspend/resume features while attached to a network.

SUSPEND Menu on Compaq LTE may cause data loss

If you have a Compaq 386/486 LTE portable with a docking station, do not attempt to suspend your machine with the &quot;Suspend&quot; item on the start menu while the machine is docked. You will not be able to properly resume from this configuration and work (open files) may be lost.

If the machine is not docked, this restriction does not apply.

= Printing =

Problems deleting printers

In this release of Chicago, it is necessary to close the printers folder after deleting a printer for it to be deleted correctly. This problem will be corrected in the next release.

Enhanced Metafile Spooling

How to enable/disable Enhanced Metafile Spooling

Many changes to Chicago affect printing. The most noticeable of these is that all non-PostScript printers spool enhanced metafiles instead of raw printer data as they currently do in Windows 3.1. When you direct an application to print, it will print more quickly (as much as twice as fast) and enable you to resume work much more quickly. If you have problems printing, you might want to disable enhanced metafile spooling to determine if it is causing the problem. Please see the list of known problems with certain applications and enhanced metafile spooling below. Enhanced metafile spooling is enabled by default for all non-PostScript printers. Note that while Enhanced Metafile spooling is displayed as being available for PostScript devices, it is actually not available. This problem with incorrectly displaying EMF spooling being available for PostScript devices will be corrected in the next release. To disable metafile spooling, carry out the following procedure.

To disable metafile spooling:

1. From the tray, choose “Settings...”, and then choose Printers. The Printer folder will be displayed.

2. Right-click the icon for the printer you wish to disable metafile spooling for. A menu appears.

3. Choose Properties. Several Property sheet “tabs” will be shown, choose “Details” by single clicking on the tab.

4. On the Details property sheet page, Click on the button labeled “Spool Settings...”. A dialog box will be displayed.

5. Look for the drop down listbox labeled “Spool Data Format”.

6. Press the down arrow on the right side of the “Spool Data Format” listbox, and select “RAW” instead of “EMF”.

7. Choose OK from this dialog, and OK from the bottom of the property sheet page.

Please use Enhanced Metafile spooling as much as possible, and be sure to report all problems.

Printing from AmiPro 3.0 with Enhanced Metafile Spooling

There are some known problems with printing documents containing bitmaps from AmiPro 3.0 with Enhanced Metafile Spooling enabled. Please disable Enhanced Metafile Spooling when using AmiPro 3.0 under this release.

Printing from WordPerfect for Windows 6.0 with Enhanced Metafile Spooling

There are some known problems with printing documents containing large bitmaps from WordPerfect for Windows 6.0 with Enhanced Metafile Spooling enabled. Please disable Enhanced Metafile Spooling when using WordPerfect for Windows 6.0 under this release if you encounter problems printing documents with large bitmaps.

Printing rotated Truetype fonts on 9 pin dot matrix printers with Enhanced Metafile Spooling

There are some known problems with printing documents containing Truetype fonts rotated at non-orthogonal angles (rotated to any degree other than 0, 90, 180, or 270 degrees) to 9 pin dot matrix printers with Enhanced Metafile Spooling enabled. Please disable Enhanced Metafile Spooling when using such documents with 9 pin dot matrix printers under this release.

Printing from Encarta on non-PostScript printers with Enhanced Metafile Spooling

There are some known problems with printing text from Microsoft Encarta to non-PostScript printers with Enhanced Metafile Spooling enabled. Please disable Enhanced Metafile Spooling when using Encarta with non-PostScript printers under this release.

Printing &amp; Paper Bin selection from AmiPro 3.0

There are some known problems with paper bin selection in this release of Chicago. This will be corrected in the next release.

PostScript Printers

VM tracking

The PostScript printer driver in Chicago will now track PostScript virtual memory availability in the printer, allowing you to print more complex documents than you could with Windows 3.1. However, if you encounter problems where the printer prints a message about being unable to print due to available virtual memory in the printer, please first report the problem, and then you can work around this problem by changing the PostScript options settings from “Optimize for Speed” to “Optimize for Portability” as described under the next section.

Using Lotus 123 R4 with PostScript printers under Chicago

When using Lotus 123 R4 for Windows, you may encounter problems with error messages being printed on PostScript printer instead of the expected output. This is a known problem which will be corrected next release. To work around this problem, you should change the PostScript options settings from “Optimize for Speed” to “Optimize for Portability”. To do this, perform the following:

To change PostScript driver to “Optimize for Portability”

1. From the tray, choose “Settings...”, and then choose Printers. The Printer folder will be displayed.

2. Right-click the icon for the PostScript printer you wish to change settings for. A menu appears.

3. Choose Properties. Several Property sheet “tabs” will be shown, choose “PostScript” by single clicking on the tab.

4. Look for the listbox labeled “PostScript Output Format”.

5. Select “PostScript (Optimize for Portability - ADSC)” instead of “PostScript (Optimize for Speed)” in the listbox.

6. Choose OK from the bottom of the property sheet page.

Using Ventura Publisher 4.1 with PostScript printers under Chicago

Ventura Publisher version 4.1 has some known problems and can not be used under this version of Chicago. This will be fixed in the next release.

Support for WPD files for PostScript printers in Chicago

WPD files (used by the PostScript printer driver in Windows 3.1x) are not supported by the PostScript driver in this release of Chicago. This will be fixed in the next release.

Type 42 printing not supported

Printing of TrueType fonts as “Type 42” fonts in this release of the PostScript printer is not supported.

Plug and Play support for printers

Plug and Play for the HP LaserJet 4L and IBM 4039 LaserPrinter

There are known problems with plug &amp; play detection of the HP LaserJet 4L and IBM 4039 LaserPrinter in this release of Chicago. This will be fixed in the next release. The IBM 4039 LaserPrinter Plus and HP LaserJet 4ML, 4P, 4MP, and 4Si are the plug and play printers supported in this release.

Problems installing printer drivers during first Chicago session after a Plug and Play printer has been installed.

There are known problems with installing additional printer drivers AFTER a plug and play printer has been installed ONLY after the very first time you run Chicago. This will be corrected in the next release. Workaround is to restart Chicago before attempting to add additional printer drivers.

Windows Printing System

Using the Windows Printing System under Chicago

In order to use the Windows Printing System with this release of Chicago, you must have installed the Windows Printing System under Windows 3.1x, and upgrade Chicago over it. Installing the Windows Printing System directly under Chicago is not supported in this release. This will be addressed in the next release of Chicago.

Using Header, Trailer, or test pages from the Windows Printing System under Chicago

There is a known problem with using the header, trailer and test pages from the Windows Printing System driver under Chicago which causes a GP fault. The test page will be fixed, header and trailer will be removed in the next release. Please use the Chicago separator pages instead of the Windows Printing System header and trailer pages.

Using a Texas Instruments microLaser Pro 600 printer

“Out of Paper” error messages when using TI microLaser Pro 600

There are known problems with plug &amp; play detection leaving the TI microLaser Pro 600 in a state where it reports an “Out of Paper” error message back to Chicago. To work around this, you must reset (power cycle) the TI microLaser Pro 600 after starting Chicago each time. This problem will be corrected in the next release.

Serial Printer Communication Settings

Problems using printers/plotters attached to a Serial (COMx) port after upgrading from Windows 3.1x

If you are using a printer or plotter attached to a serial port, and have upgraded from Windows 3.1x, there are known problems with the handshaking protocol not being set correctly. This will be corrected in the next release. To solve this problem, you must re-specify the handshake setting (Hardware, XON/XOFF, etc.). To do this, follow the directions below for setting serial communication values, which also include handshake settings.

Using printer attached to a Serial (COMx) port

If you are using a printer attached to a serial port, you may want to check the serial communications settings. Follow the instructions below to do this.

To change Serial communications settings for a printer:

1. From the tray, choose “Settings...”, and then choose Printers. The Printer folder will be displayed.

2. Right-click the icon for the printer you wish to change settings for. A menu appears.

3. Choose Properties. Several Property sheet “tabs” will be shown, choose “Details” by single clicking on the tab.

4. Choose the “Port Settings” button.

5. A dialog displaying the current serial communications settings will be displayed. Verify &amp; correct the settings as needed.

6. Choose OK to close the dialog box, and then choose OK from the bottom of the property sheet page.

Transmission Retry/Device Not Ready time-out values

Setting “Transmission Retry” &amp; “Device Not Ready” time-out values

Under this release of Chicago, there is not yet a user interface to set Transmission retry or device not ready time-out values. This will be corrected in the next release. To change these settings under this release of Chicago, follow the instructions below.

To change Transmission Retry and/or Device Not Ready time-out values:

1. Start Wordpad, and request to use a “Text File” vs. A “Formatted file”. Load the file name WIN.INI from the directory containing Chicago (which will be named \WINDOWS by default).

2. Move to the bottom of this file &amp; look for the [PrinterPorts] section.

3. You will see several lines below that which look like (one for each installed printer):

HP LaserJet 4P=HPPCL5MS,LPT1:,15,45

4. The value of 15 (seconds) is the default value for “Device Not Ready”, the value of 45 (seconds) is the default value for “Transmission Retry”. Changes these values as desired.

5. Choose “File” and then “Save” from Wordpad to save these changes.

6. You must exit &amp; restart Chicago for these changes to take effect.

Installing support for network printers

General issues

There are several ways in which you can install support for printers not directly attached to your computer. If the printer is being shared from another computer running Chicago, or from a computer running a Novell NetWare print queue that has been configured appropriately (see the Networking section in the M6 release notes for information on how to configure a NetWare print queue), you can take advantage of “Point and Print” for easy printer installation. See the printing section under “What’s New” in the on-line help for more information. If you are installing support for a printer attached directly to the network that is not shared from another computer, please see the section below on “Installing Net Attached Printer Support”.

Using Point and Print with User level security

If you have established user level security, instead of share level security, there are some additional steps you must take to enable Point and Print support. In order to enable point &amp; print support from a computer running Chicago, need to do the following:

To enable Point and Print with User level security:

1. Use the Explorer to locate your SYSTEM directory for Chicago.

2. Right click on the SYSTEM directory icon &amp; choose “Properties”.

3. In the sharing properties for your SYSTEM directory, add all users who are supposed to be able to access your printer(s) with read-only access. It is not necessary to share the directory, just add the permissions.

4. After choosing OK, It will offer to share the directory after you add the permissions. Just say no..

Redirecting Printer ports over a network

The M6 release of Chicago does not provide a user interface for establishing a network redirection for parallel ports. This will be corrected in the next release. In the M6 release, you will need make a physical network redirection via the appropriate command line syntax for your network environment (ex: type “NET USE LPT1”, or “SET PRINT”, or “CAPTURE LPT1:”).

Extended Capabilities Port (ECP) support

Using Extended Capabilities Ports (ECP) under Chicago

Support for Extended Capabilities Ports (as described by IEEE 1284 specification) is NOT installed by default in this release of Chicago. However, you may install support manually if you wish. Please report any problems you experience with the P1284 driver that do not occur with the standard parallel port driver.

To enable ECP support in Chicago M6 release:

1. Consult your computer (or add in card) manual to determine the IRQ and DMA settings selected for each of the ECP ports you wish to use. You must have this information to enable ECP support.

2. Copy the file LPT1284.INF from the \DRIVERS\LPT1284 directory on the M6 CD to your \WINDOWS\INF directory.

3. Copy the files LPT1284.VXD and LPT1284.SYM from the \DRIVERS\LPT1284 directory on the M6 CD to your \WINDOWS\SYSTEM directory.

4. From the tray, choose “Settings...,” and then Choose “Control Panel...”.

5. Double click on the “System” icon in the control panel.

6. Click on the “Device Manager” property sheet tab in the dialog shown.

7. Double click on the “Ports” entry shown in the list, and then select the “Extended Capabilities Port” entry. (Note that you will only see this entry if an Extended Capabilities port has been detected in your computer. If you have multiple ECP ports, will have to repeat steps 7 and 11 to configure each ports DMA and IRQ values.)

8. Select the “Properties” button from the dialog box.

9. Under the “general” property sheet page, select the “Change Driver” button in the “driver Information” groupbox.

10. A dialog will then be displayed that allow you to choose from “Printer Port” and “ECP Parallel Port”. (Note that you will only see this entry if an Extended Capabilities port has been detected in your computer, you must choose “Show All devices” to see both entries otherwise.) Choose “ECP Parallel Port” &amp; then choose OK from the “Select Device” dialog.

11. Choose the “Resources“ property sheet tab. From the “resources” property sheet page, select the “Manual based on” radio button in the “New Settings” groupbox. You will now see control for Interrupt Request (IRQ) and Direct Memory access (DMA) settings. Enter the values you noted during step 1 of these instructions.

12. Choose “OK” to close the dialog, and then choose “Current” when prompted if you wish to use new or Current files.

13. Restart Chicago when prompted. After restarting, you should be able to take advantage of the ECP specific capabilities of the port.

Font Installers

Using the soft font installers for LaserJet compatible or Lexmark printers in M6

There are known problems with installing soft fonts (downloadable fonts) to LaserJet compatible printers and to Lexmark printers in this release of Chicago. These problems will be corrected in the next release.

Using DEC PrintServer printers

Using DEC PrintServer printers with Chicago

For this release of Chicago, you must follow the directions below to install support for net attached DEC PrintServers.

To install net attached DEC PrintServer support in Chicago M6 release:

1. You must have TCP/IP network protocol support installed and working before performing any of the steps listed below.

2. From the tray, choose “Settings...”, and then choose Printers. The Printer folder will be displayed. Double click on the new printer icon. Choose the “Next” button from the first dialog, and choose “Local Printer” and then the “Next” button from the second dialog.

3. In the next dialog box, choose “DEC” from the list of manufacturers. After that, select the specific PrintServer model you wish to install support for &amp; then choose the “Next” button.

4. From the Ports dialog box, choose the “Next” button (Note: The actual port chosen is not important at this point, you will have to change this later).

5. Enter the friendly name you wish to refer to the printer as &amp; then choose the “Next” button.

6. Do not attempt to print the self test page when prompted, choose the “Skip Test” button.

7. From the tray, choose “Run...”, and then type “DECPORTS” into the edit box. A dialog box labeled “Digital PrintServer Printer Ports” will appear. Enter the name you wish to use for the port in the “Name” edit box, and enter the TCP/IP address of the printer in the ‘Address” listbox. Choose OK to close the dialog.

8. You will then need to restart your system for these changes to take effect.

9. After restarting Chicago, From the tray, choose “Settings...”, and then choose Printers. Select the DEC printer you just installed support for and right click on it &amp; choose “Properties”.

10. Choose the “Details” property sheet page. Press the small arrow pointing downward in the dropdown list box labeled “Print To”. You should see the name of the port you created in step #7. Select that port &amp; choose the OK button at the lower left side of the dialog box.

11. You should now be able to print to the PrintServer at the TCP/IP address you provided.

Using network attached HP LaserJet printers

Using network attached HP LaserJets with Chicago

If you have a HP LaserJet printer that is directly attached to the network (usually referred to as using a “JetAdmin” card), you may designate one computer running Chicago as the server which will “share” the printer and maintain the print queue for it. Other Chicago users may use the printer after it has been shared, just like any other shared printer.

To install net attached HP LaserJet support in Chicago M6 release:

1. First, you must have the following Novel Netware files available in order to use the HP JetAdmin utility with Chicago: NWCALLS.DLL, NWIPXSPX.DLL, NWLOCALE.DLL, NWNET.DLL, and NWPSRV.DLL.

2. From the tray, choose “Settings...”, and then choose Control Panel. Double click on the Network icon. Choose the “Service...” button located on the lower right side of the dialog.

3. In the next dialog box, choose “Add”, and then choose “Hewlett Packard” from the “Manufacturers” listbox in the next dialog. You will then see “HP Network Printer service” in the “Models” listbox, select it &amp; then choose OK.

4. Choose “Close” from the “Network Services” dialog.

5. Choose OK from the “Network” dialog box, and provide the Novell Netware files listed in step #1 when prompted. After all of the files have been copied, restart Chicago when prompted.

6. After restarting Chicago, from the tray, choose “Settings...”, and then choose Control Panel. Double click on the “HP JetAdmin” icon.

7. Use the “HP JetAdmin” utility to configure the printer appropriately.

Problems upgrading printer drivers from Windows 3.1x with some HP LaserJet 4 models

If you are installing the Chicago M6 release over a version of Windows 3.1x or Windows for Workgroups 3.1x, and you have a HP LaserJet 4M, 4MP, 4L, 4ML, 4 Plus, or 4M Plus (or any other plug and play printer), you may experience error messages reporting problems having printer drivers upgraded the 1st time you start Chicago. This is a known problem that will be fixed in the next release. The workaround in this release is to leave the printer turned off the first time you start Chicago. After Chicago has started the first time (and upgraded your printers) you may exit &amp; restart Chicago with the printer powered on to use plug and play support to install the correct printer driver.

= ScanDisk =

ScanDisk detects, but cannot repair, damaged Long File Names

The version of ScanDisk which is included in Chicago detects damaged long file names, but it cannot repair them. A forthcoming beta release of Chicago will include a tool which can repair damaged long file names. If you would like to turn off long file name checking, edit your SCANDISK.INI file (in the COMMAND subdirectory of the directory in which Chicago is installed) and in the [ENVIRONMENT] section, change the LfnCheck=On entry to LfnCheck=Off.

= Setup =

CORRECTIONS/UPDATES to &quot;Chicago Installation Notes and Quick Reference&quot;

Version Conflict Warnings when upgrading Windows for Workgroups 3.x

When installing over Windows for Worgroups 3.1 or 3.11, you may get warnings during Setup that the existing files on your system are newer than the files that Chicago is trying to install. This error is incorrect, and you should answer YES or YES TO ALL in this dialog, and install the Chicago files. You may see this errror for the following files:

logonoff.exe

netwatch.exe

ndis.386

ndis2sup.386

netbeui.386

nwlink.386

nwblink.386

vnetsetup.386

vredir.386

vserver.386

Do Not run Setup from inside Windows NT or Daytona

Chicago Setup will not run under Windows NT. You will need to dual-boot to MS-DOS and run setup from Windows 3.x or MS-DOS.

Microsoft At Work FAX is not in Beta 1 (M6)

page 2 - the Microsoft At Work Fax software is not included in this beta release. The Microsoft Information Center (integrated mail client) is included and may be selected for installation using the Customize Option in Setup. Please see the release notes section on the Mail: Information Center for more information. The Microsoft At Work FAX group plans to provide an update for this on CompuServe.

Problems Dual-booting between Windows NT and Chicago

There may be problems if you are using the Window NT multiboot and the Chicago dualboot together. If you are having problems using F4 to start MS-DOS, there may be 0-byte io.sys and msdos.sys hidden files in the root of your boot drive. To work around the problem, delete 0-byte io.sys and msdos.sys files.

Setup may fail when 386MAX is installed (Error: &quot;Incorrect MS-DOS version. MS-DOS 3.1 or greater required&quot;)

Under certain configurations, Setup may not be able to run when 386MAX is installed. If you receive this error, you will need to disable 386MAX and re-run Setup.

Installing New Devices, Printers, etc. from Chicago May Prompt for Multiple Disks

If you installed from floppy disks, when adding a new device such as a printer, network card, etc. from Chicago, you may be prompted for multiple disks. This is a known problem that will be fixed in later releases.

&quot;Standard Mode: Fault in MS-DOS Extender&quot; error when running Setup from MS-DOS

If you receive this error, there may be a conflict in the upper memory region. To work-around this problem, either disable EMM386.EXE from your config.sys file and rerun Setup, or run Setup from Windows 3.x. After Chicago has been installed, you should be able to re-activate EMM386.EXE.

Setting up on notebook computers with Automatic Suspend

Some notebook computers (such as the IBM Thinkpad) will auto suspend after a specified timeout interval, or when the cover is closed. This feature should be disabled during the time Chicago setup is running.

Setting up Chicago over previous versions

You can not setup this version of Chicago over prior versions (build numbers) of Chicago. This includes the M5 build (73), and the pre-M6 “Betas of the Beta”, builds 99, and 108. Although the final M6 may set up over build 116, it is still recommended that you do a clean installation, so you are guaranteed not to generate bogus bugs. You should remove the previous Chicago files, and remove the system.dat file from your root. (To remove system.dat, you must first do “attrib -s -h -r” and then delete it.)

The reason for this is that it is more important that Chicago work on Windows 3.x and Windows for Worgroups 3.x upgrades for the final product. The Chicago team must focus on bugs in these scenarios rather than bugs caused by mix’n’match intermediate build components of Chicago, which would be a one-time bug. Both the testing and the bug fixing to support all the different possible scenarios would delay the Beta release and the ultimate product availability. We appreciate your patience, and the extra time it takes to do a clean install (we have to do this also!), but we believe that this course of action will, in the long run, produce the best possible product in the shortest time. We appologize for the inconveniance.

GPF in Setup right after inserting a floppy for the Emergency Boot Disk and hitting OK

This may be due to a VxD that Norton Utilities installs. The work-around is to either re-start Setup and DO NOT create an emergency boot disk or remove the following line from the [386enh] section of system.ini:

device=symevnt.386

= Shell =

MISSING FUNCTIONALITY

Properties Command

&quot;Properties&quot; command doesn't do anything on My Computer, Network Neighborhood, and Computers &amp; Workgroups inside Net Neighborhood.

OLE 2.0 Drag and Drop

OLE 2.0 drag &amp; drop is not yet supported.

Explorer

The Explorer does not yet support status bar info.

32-bit Common Dialogs

File open is not yet customizable, new Print, Print Setup, and Page Setup dialogs are not available in this beta.

Shortcuts (Links)

Shortcuts do not track movement of the target file in this beta.

UI for File Associations/Types is not yet complete

Please do not open bugs or complaints against the current implementation (including lack of ability to change the extension/type of a file).

KNOWN BUGS

Shortcut Icons do not refresh properly

Desktop: Changing a shortcut icon on the desktop will sometimes not refresh properly. Try clicking on the desktop and hitting F5.

Files &amp; Icons that won’t delete

Desktop: In some circumstances, it is possible to get more than one icon for files, or icons that may not be &quot;deleteable&quot;

Taskbar Right-Click on “depressed” button

Taskbar: Right-clicking a depressed taskbar button will sometimes not produce a context menu correctly because the button is not in a happy state. Click on empty desktop space to un-press the button, or try right-clicking on only the non-depressed buttons..

Dragging Taskbar with AutoHide

Taskbar: doesn't pop-up when you're dragging to it with AutoHide turned on.

Maximized Application goes behind taskbar

Taskbar: some rogue apps still maximize behind the taskbar

Creating New Documents

Folders/Explorer: &quot;New&quot; command sometimes creates documents that cannot be edited with their creator applications.

Changing Drive Label

Folders/Explorer: changing the drive label won't update in My Computer or Explorer

File Open Dialog

New File Open dialog: flashing between folder changes and performance problems have not been fixed. Also, this dialog is not yet customizable.

Locale Control Panel

Control Panel- Locale: not complete

Confirmation dialogs

Confirmation dialogs show file extensions, and sometimes get the order of the source/target switched.

= TAPI - Telephony API =

Telephony API (TAPI) Sample AT Service Provider Problems

When installing the sample AT command set modem service provider using the Telephony Control Panel, you may notice that the service provider does not appear in the list of installed service providers (after configuring the AT modem service provider). To work around this problem, install that AT modem service provider a *second* time, but press 'Cancel' instead of 'OK' at the &quot;ATSP Configuration&quot; dialog. You should then see the AT modem service provider in the list of installed service providers.

The sample AT modem service provider in \SDK\TAPI\SAMPLES\WIN16\ATSP may cause your system to crash or hang if the TAPI client application (such as Dialer) makes more than one telephone call in succession. A fix will be supplied as soon as it is available.

More Info

For more information on how Chicago applications can access the Telephony API, see the TAPI documentation and release notes in the \TAPI directory. At present, the best sample application to refer to is DIALER.EXE, the Chicago Phone Dialer applet. DIALER demonstrates how to use the TAPI functions to make calls and use address translation features.

= Visual C++ =

Enabling new dialog styles in Chicago

Visual C++ 2.0 has added very limited support for a few of the new Chicago controls in the dialog editor. The controls that are available include the Up/Down, Track Bar, Progress, and Hot Key controls. This support is limited to the dialog editor and does not have corresponding ClassWizard and MFC support. Full support will be available in a future release.

To enable the Chicago controls, you need to use the REGEDIT program to add a binary value called &quot;ChicagoControls&quot; set to &quot;01 00 00 00&quot; in the key &quot;HKEY_CURRENT_USER\ Software\ Microsoft\ Visual C++ 2.0\ Dialog Editor&quot;.

Building VxDs using the DDK

As we have mentioned in previous releases of the Chicago DDK, we are phasing out LINK386.EXE. The linker in Visual C ++ 2.0 now has LE' support. So you can compile and link your VxDs with Visual C++ 2.00. This release of the DDK does include LINK386.EXE but it will not be distributed in the final version of the DDK. LINK386 requires an OMF object and Visual C++ 2.00 only emits COFF output, therefore you cannot build an object with the VC compiler and link it with LINK386. If you find that you need to use Link386 you need to go back to the C832 linker that was provided with the last Chicago release or use the retail version of the Visual C++ 1.0 or 1.5 compiler to generate an OMF object.

Using new Chicago features

To make full use of the new features of Chicago applications must be marked 4.0. VC++2.0 does not mark applications with version 4.0

To change the Windows version mark for your application, add the switch

/SUBSYSTEM:Windows,x.y

to the linker command line on the Link tab of the Project Settings dialog box. For example, you might use the following switch for this purpose:

/SUBSYSTEM:Windows,4.0

Applications marked 4.0 will run on Chicago and Windows NT 3.5. To run an application on Windows NT 3.1 the application must be marked 3.10.

DEBUGGING: Using WinDBG with MSVC 2.0 (C9):

To use the WinDBG debugger that comes with the Chicago SDK to debug a Win32 application built with C9, link with the following switch:

-pdb:none

= VSERVER Error Messages =

VSERVER Error 6251: the file server cannot be loaded with your disk driver. If you see this error, Chicago is using real mode to access your swapfile, and therefore, the performance of your system will be suboptimal. Also, file and print sharing is currently not supported if you are using real mode to access your swapfile.

Chicago will use real mode for your swapfile access if:

- you are running hardware not supported by protect-mode drivers. Currently, IBM Microchannel ESDI drives and PCI IDE drives are not supported. Please submit a bug report if you have other disk controllers where we do not have protect-mode drivers.

- a hardware conflict does not allow the protect-mode disk driver to load. The most common conflict is that your hard disk controller and another device (for example, mouse, network, or sound card) are set to the same IRQ. Please submit a bug report indicating that Chicago SETUP did not detect the conflict.

- your system contains unknown device drivers or TSRs in CONFIG.SYS or AUTOEXEC.BAT. Information on offending drivers is located in the file IOS.LOG in your Windows directory. Please submit a bug report about any drivers or TSRs that you are loading.

- your hardware was not detected. If you have a disk drive that is supported by a protect-mode driver that was not deteced, please submit a bug report.

= Windows Shells =

Shell Replacements

Windows shell replacements are closely tied to the version of the operating system they were designed for. Because they are so tightly bound to the OS version, shell replacements will need to be updated for Chicago. Most features will function if the shell replacement is run as an application, but there are problems when they try to replace the 32 bit shell. Please only run shell replacements that were designed for Chicago. All other shell replacements should be run as applications.

Compaq Tab Works(r)

You should either disable the Tab Works(r) File Tracking feature while installing Chicago, or set Program Manager as your default shell.

-- To disable File Tracking, choose Options.File Tracking and uncheck the Track File Creation box. You can also do this whenever prompted to create an icon, using the Options button, if you have already started setup.

-- To set Program Manager as the shell, use Options.Set Shell, and reboot.

Compaq Control Center

The Computer Setup button in the Compaq Control Center may not work on some systems. An alternative way to access these settings is through Compaq BIOS setup by pressing &lt;F10&gt; at boot, when the cursor is in the upper right corner of the screen.

# # # # # # # # # # # # #