Copyright: WFW Appnote Help by R. Eugene Baucom


Contents

WFWG 3.11 Appnotes

WG0670 - Using the Softset Utility

WG0788 - WFWG For Individuals with Disabilities

WG0949 - WFWG Setup

WG0971 - NDIS2SUP.386 Corrrects Problems Restarting Windows for Workgroups on Token Ring Machines

WG0973 - RMM.D32 Corrects Five-Second Delay When Starting Windows-Based Applications

WG0974 - VKDA.386 Corrects Keyboard Problems

WG0988 - IBMTOK.386 Corrects Problems with Exiting Windows for Workgroups

WG0990 - ELNK3.386 Corrects Problem with Systems that Hang with Non-802.3 Packets

WG0991 - Updated NE2000.386 Allows WFW to Start Correctly

WG0992 - Updated Files for Microsoft At Work PC Fax Version 1.0

WG1001 - Updated SERIAL.386 for Windows for Workgroups

WG1002 - Microsoft Mail 3.2 SCHEDMSG.DLL Corrects French Headers in WFWG Mail

WG1004 - Updated MSODISUP File Corrects Problems Using 3Com 3c509 and 3c5x9 ODI MLIDs

WG1027 - UPDATED NWLINK.386 Allows Routing Across Cisco Router


This topic is not finished. . .

This Topic is not finished


Disk Locations:


Intel Softset Utility
WG0670

The Intel Softset Utility

Introduction

The enclosed WG0670 disk contains the Intel SOFTSET utility, which is provided by Intel Corporation for use with its EtherExpress(TM) line of network adapter cards. This utility is used to configure the network interface card (NIC) and diagnose potential hardware roblems. Microsoft does not provide this utility with Windows for Workgroups because SOFTSET is not normally required for the proper operation of Windows for Workgroups.

THE INTEL ETHEREXPRESS ETHERNET ADAPTERS

The Intel EtherExpress adapters are software-configurable Ethernet cards. They contain no hardware jumpers, DIP switches, or other means for configuring the NIC. EtherExpress holds its settings in an erasable programmable read-only memory (EPROM) chip. These settings are dynamically adjustable. This means that regardless of the NIC's settings, you can override the adapter settings by using the software.

Windows for Workgroups adjusts the settings of the EtherExpress adapter during the boot of the host machine. For this reason, SOFTSET is not necessary for configuring EtherExpress with Windows for Workgroups and consequently is not included with the released product.

For example, EtherExpress has a default configuration of:

I/O Base	300h

IRQ	3

RAM	None

If you select IRQ 5 during Windows for Workgroups setup, this IRQ setting will override the programmed setting in the EtherExpress EPROM.

NOTE:	 Configuring the EtherExpress adapter with Windows for Workgroups will not change the settings on the NIC EPROM. The reconfiguration will take effect only after the Windows for Workgroups network device drivers have loaded.

ETHEREXPRESS ON AN EISA MACHINE

Extended Industry Standard Architecture (EISA) machines attempt to determine what type of hardware is installed during their boot process. Because the EtherExpress adapter is not configured for Windows for Workgroups until its device drivers load, you can have EtherExpress installed in an EISA machine and have EtherExpress conflict with another NIC. While this does not impede the operation of Windows for Workgroups, the conflict will cause errors during the boot process of the EISA machine.

In this situation, using the Intel SOFTSET utility to change the settings of the EtherExpress adapter will help you bypass boot difficulties. By running SOFTSET, you can change the conflicting settings on EtherExpress to cause it to hold different settings at boot time. Again, this will not interfere with the operation of Windows for Workgroups.

RUNNING SOFTSET

You cannot run SOFTSET if the EtherExpress adapter is in use. Therefore, no network drivers can be loaded when you run SOFTSET. The easiest way to configure EtherExpress with SOFTSET is by booting from a system (bootable) disk. To create a system disk, then boot your machine from it, and then run SOFTSET, do the following:

NOTE: Steps 1 and 2 are not necessary if you already have a system disk. If you have a system disk, place that disk in drive A and skip to step 3.

1. Insert a blank floppy disk in drive A.

2. To create a system disk, type the following at the MS-DOS command prompt and press <Enter: >

format a: /s

3. With the system disk in drive A, reboot your machine.

4. Place the enclosed WG0670 disk in the appropriate drive.

5. Change to the drive that contains the WG0670 disk. Type the  following at the MS-DOS command prompt:

SOFTSET

and press  <Enter: >

SOFTSET will present the following options:

Options	Description
Automatic Setup	When you select this option, SOFTSET will present  two choices: the BNC and DIX connectors. If you are using one of the Microsoft starter kits, or add ons, you should probably choose BNC. Otherwise, you need to know what type of connector your machine is using to connect to the network. BNC connector = Coaxial cable, RG-58, or thinnet DIX connector = 15-pin connector, RG-11, RG-8, or thicknet
Manual setup	This option allows knowledgeable users to configure the EtherExpress adapter to values appropriate for their systems. Alterable settings are: I/O address Interrupt Connector type Force 8-bit operation Boot ROM address Amount of RAM to map RAM start address To change a value, use the arrow keys on the keyboard to highlight your selection and press  < Enter >
Run diagnostics	There are two forms of diagnostics available under this option. Run Diagnostics On Board can be run on any machine containing an EtherExpress adapter. Run  Diagnostics On Network and Set Up As Diagnostics Responder require at least two machines connected with the appropriate cabling. Run Diagnostics On Board allows you to test the Ethernet adapter itself for potential defects. Run Diagnostics On Network and Set Up As Diagnostics Responder allow you to test whether the media connecting the two machines that contain EtherExpress adapters is functional. This is particularly useful in configurations where the cabling or connectors are suspect in networking problems. Running these tests from a machine experiencing problems will help locate these problems. To perform this test, do the following steps: 1. Select Run Diagnostics On Board to ensure that the Ethernet adapter itself is functioning correctly. 2. Install the EtherExpress adapter in two machines. 3. Connect the machines with the appropriate cabling. 4. Start SOFTSET on both machines. 5. On one machine, choose Set Up As Diagnostics Responder. 6. After this machine has been set up with this option, choose Run Diagnostics On Network on the second machine. NOTE: If the SOFTSET diagnostics fail, repeat these steps after troubleshooting general network hardware issues.
View current configuration	This option allows you to view the current settings of the EtherExpress adapter.
Save Configuration to file	This option allows a LAN administrator to save a configuration to a file for use with other EtherExpress adapters.
Load Configuration from file	Choosing this option allows you to load a configuration previously saved to disk. This can also be accomplished from the MS-DOS command line by using the following command: softset /load=<filename> where filename is the name of the configuration file you want to load.
Exit SOFTSET	Choose this option to quit SOFTSET.


Windows for Workgroups and Disabilities
WG0788

Customizing Windows for Workgroups for Individuals with Disabilities

Introduction

This Application Note provides information about the following products and services available for computer users with special needs:

•	Access Pack for Microsoft Windows, a product that makes Windows more accessible for people with movement or hearing disabilities

•	Keyboard layouts designed for people who type with a single hand or wand

•	Support services for people who are deaf or hard-of-hearing

•	Microsoft Mouse driver version 9.0

•	Microsoft documentation on audio cassettes and floppy disks

•	Products available for individuals who are blind or have low vision

•	Help installing Windows for Workgroups

•	Customizing Windows for Workgroups without additional hardware or software

•	More information about products and services for people with disabilities

Note: The information in this Application Note applies to Windows for Workgroups users in the United States only. If you are outside the United States, your Windows for Workgroups package contains a subsidiary information card listing product support telephone numbers and addresses. Contact your subsidiary to find out whether the types of products and services described in this Application Note are available in your area.

 Microsoft Support Services for People Who Are Deaf or Hard-of-Hearing

Through text telephone (TT/TDD) services, Microsoft provides people who are deaf or hard-of-hearing with the same technical product support and customer service as hearing customers.

For sales information and nontechnical customer service, you can contact Microsoft Consumer Sales on a text telephone at (800) 892-5234 between 6:30 A.M. and 5:30 P.M. Pacific time. For technical assistance, you can contact Microsoft Product Support Services (PSS) on a text telephone at (206) 635-4948 between 6:00 A.M. and 6:00 P.M. Pacific time. Microsoft support services are subject to Microsoft prices, terms, and conditions in place at the time the service is used.

Access Pack for Microsoft Windows

Microsoft distributes Access Pack for Microsoft Windows, which provides people who have movement or hearing disabilities with better access to computers running Windows or Windows for Workgroups. With Access Pack for Microsoft Windows, you can configure your Windows system to do the following:

•	Allow easier use of SHIFT, CTRL, and ALT key combinations for people who type with a single finger, a mouthstick, or a wand.

•	Ignore accidental key presses.

•	Adjust or disable the rate at which a character is repeated on the screen when you hold down a key.

•	Prevent extra characters if you unintentionally press a key more than once.

•	Allow you to use the keyboard to control the mouse cursor.

Note: If you use this feature with Microsoft Paintbrush, your system stops responding (hangs). To work around this problem, use Paintbrush keyboard commands. For more information, run Paintbrush and press F1each specific task help topic has information on the keyboard equivalent for the mouse action.

•	Allow you to use an alternate input device to control the computers keyboard and mouse.

•	Provide a visual cue when a computer makes sounds.

•	Enable you to turn off these services for people who do not need them.

Access Pack for Microsoft Windows, which was developed by the Trace R&D Center at the University of Wisconsin at Madison, is available on the Microsoft Windows Driver Library in the file ACCP.EXE.

If you have a modem, you can download Windows Driver Library components from network services, including CompuServe, GEnie, Microsoft Online, various user-group bulletin board services (BBSs) (including BBSs on the Association of PC User Groups [APCUG] network), and the Microsoft Download Service (MSDL). The MSDL is available seven days a week from 2:30 A.M. to 1:00 A.M. at (206) 936-MSDL (936-6735). The modem settings are:

1200,n,8,1

2400,n,8,1

9600,n,8,1 (V.32, V.32bis, V.42, V.42bis)

14,400,n,8,1 (V.32, V.32bis, V.42, V.42bis)

Note: If you cannot connect at 14,400, lower the bits per second to 9600 and try again.

Customers who do not have a modem can obtain disks by calling PSS at (206) 637-7098 (voice telephone) or (206) 635-4948 (text telephone).

Keyboard Layouts for Single-Handed Computer Users

Microsoft distributes software to modify your keyboard layout. These keyboard layouts can be useful for people who have difficulty using the standard QWERTY layout. You can use this software to change your keyboard configuration without adjusting your physical keyboard.

Windows for Workgroups has built-in support for the two-handed Dvorak keyboard layout, which may be useful for preventing or coping with some types of repetitive motion injuries associated with typing. To use this layout, choose the International icon in Control Panel. Two additional layouts are designed for people who type with the left hand only or with the right hand only. These layouts can also be useful for people who type with a single finger or a wand.

The single-handed layouts are included with the PSS Application Note GA0650, "Dvorak Keyboard Layouts." If you have a modem, you can download GA0650 from the network services listed in the previous section. The filename is GA0650.ZIP, except on MSDL, where this Application Note is available in the self-extracting file GA0650.EXE.

Customers who do not have a modem can obtain GA0650 by calling Microsoft Consumer Sales at (800) 426-9400 (voice telephone) or (800) 892-5234 (text telephone).

Microsoft Mouse Driver Version 9.0

If you have trouble seeing the mouse when you are moving it and you are using the Microsoft Mouse or the Microsoft BallPoint Mouse, you can upgrade to version 9.0 of the Microsoft Mouse driver. The optional utilities included with the 9.0 Microsoft Mouse driver offer the following features:

•	Larger pointer sizes     You can choose a small, medium, or large pointer size.

•	Larger I-beam pointer     The I-beam pointer is larger than the regular I-beam.

•	Pointer growth     You can make the pointer increase to the large pointer size when you begin to move the mouse.

•	Cursor color choice     You can choose a white, black, or transparent mouse pointer.

•	Snap-To     You can configure the mouse pointer to jump to the default button when a dialog box opens.

•	Locate     You can make the mouse pointer jump to the middle of the screen when you press a specified control key and mouse button.

•	Sensitivity     You can independently adjust the vertical and horizontal sensitivity. This can be useful for people whose control or range differs for vertical and horizontal movement.

•	Orientation     You can customize the mouse orientation. This can be useful for people who need or want to hold the mouse at a particular angle.

Note: Mouse driver version 9.0 and the optional utilities mentioned above are included with Microsoft Mouse version 2.0.

If you own a Microsoft Mouse, you can order the version 9.0 driver by calling Microsoft Consumer Sales at (800) 426-9400 (voice telephone) or (800) 892-5234 (text telephone). There is a charge for the version 9.0 driver.

Documentation on Audio Cassettes and Floppy Disks

People who cannot use printed documentation can obtain many of Microsofts publications from Recording for the Blind, Inc. (RFB). RFB distributes these documents on audio cassettes and floppy disks to registered members of its distribution service. RFB's collection contains more than 80,000 titles, including Microsoft product documentation and books from Microsoft Press. You can contact Recording for the Blind at the following address and phone and fax numbers:

Recording for the Blind, Inc.

20 Roszel Road

Princeton, NJ  08540

(800) 221-4792	Voice telephone
(609) 987-8116	Fax
Products for Individuals Who Are Blind or Have Low Vision

If you are blind or have low vision, many products are available to help you use Windows. For persons with low vision, there are several screen-enlargement utilities. For blind individuals, there are screen readers that provide alternative output by synthesized voice or refreshable Braille displays.

For more information on the products available, see the "Getting More Information" section on page 1 of this Application Note. For more information about customizing Windows for Workgroups for individuals with low vision, see the "Customizing Windows for Workgroups Without Additional Hardware or Software" section below.

Help Installing Windows for Workgroups

Individuals who rely on some types of accessibility software may have difficulty installing Windows for Workgroups because the accessibility software is not loaded during the graphical portion of Setup. If this presents a problem, you can bypass the graphical portion of Setup by using the /h switch. The /h switch allows you to specify a text file that provides answers to all the questions that you would be prompted for during the graphical portion of Setup. For example, if you create a text file called MYSETUP.SHH, you would then run Setup with the following command:

a:\setup /h:c:\mysetup.shh

For more information on the format of the setup response file, see the SETUP.SHH file provided on your Windows for Workgroups installation disks.

Customizing Windows for Workgroups Without
Additional Hardware or Software

There are many ways you can adjust the appearance and behavior of Windows for Workgroups to suit varying eyesight and motor skills without any additional software or hardware. For example, by changing settings in your WIN.INI and SYSTEM.INI files, you can control screen colors, font sizes, and mouse behavior. You can change these settings in Control Panel or by directly modifying the files. The following sections describe how to identify which settings to modify to achieve the desired results and how to safely modify the WIN.INI, SYSTEM.INI, and other Windows initialization files.

Modifying Initialization Files

Windows initialization files (.INIs) contain information about your system environment. For example, the WIN.INI file contains settings about your Windows environment, and the SYSTEM.INI file contains settings that tell Windows about your system's hardware needs. MSMAIL.INI and SCHEDPLUS.INI contain settings that control the appearance of text and screen colors within the Mail and Schedule+ applications.

You can configure Windows and Windows-based applications to meet your needs and preferences by modifying the information stored in these files. For more information about WIN.INI and SYSTEM.INI, refer to the WININI.WRI and SYSINI.WRI files located in your Windows directory. You can print or view these files from Microsoft Windows Write.

Important: Errors made when editing initialization files can lead to undesirable results when you run Windows. Before changing any entry, make a backup copy of your original file. Also, some text editors can damage characters that have ANSI values greater than 127. To avoid these problems, we recommend that you use Control Panel or Setup whenever possible to make changes. If you must edit the file, use a text editor such as Microsoft Windows Notepad, System Configuration Editor (SYSEDIT.EXE), or MS-DOS Editor.

To change .INI file entries with a text editor:

•	Create a backup copy of the .INI file you want to edit. For example, run File Manager and copy WIN.INI to WIN.BAK.

•	Open the .INI file with a text editor, such as Notepad.

•	Edit the specific entries and save the file.

•	Restart Windows so that the changes take effect.

The next five sections of this Application Note discuss the initialization file entries you can change to achieve the specific results you want. Many of the initialization file entries discussed below are not present in the WIN.INI file by default but you can easily add them with a text editor.

Changing Colors

�	If you have trouble differentiating the system colors, or if they cause eyestrain, you can adjust them in the Colors dialog box of Control Panel.

�	If you have trouble reading full-screen messages displayed by Windows in 386 enhanced mode, you can adjust the colors by using the MessageBackColor and MessageTextColor entries in the [386Enh] section of the SYSTEM.INI file. For example, the following entries generate bright yellow text on a black background in message screens (such as the screen that appears when you press   CTRL+ALT+DEL  ):

MessageTextColor=E

MessageBackColor=0

The following table defines the color values you can use for the MessageBackColor and MessageTextColor entries:

0 - Black	4 - Red	8 - Gray	C - Bright red
1 - Blue	5 - Magenta	9 - Bright blue	D - Bright magenta
2 - Green	6 - Yellow/brown	A - Bright green	E - Bright yellow
3 - Cyan	7 - White	B - Bright cyan	F - Bright white
�	If the desktop pattern or wallpaper causes eyestrain, you can adjust them in the Desktop dialog box of Control Panel.

�	If you have trouble differentiating the colors used by Windows Help, you can adjust them by using the IFJumpColor, IFPopupColor, JumpColor, MacroColor, and PopupColor entries in the [Windows Help] section of the WIN.INI file. The syntax for these entries is

<entry>=red value green value blue value

where the value is a number from 000 to 999, with 999 giving the highest intensity. You must include three digits for each value, and you must include each color value. You can experiment with this setting to create a color that works best for you. The following table lists some colors you can work with:

Setting	Resulting color
000 000 999	Blue
000 999 000	Green
999 000 000	Red
999 999 000	Yellow
999 000 999	Magenta
For more information on these entries, see the WININI.WRI file in your Windows directory.

Changing Fonts

�	If you have trouble reading the Windows for Workgroups system fonts (which are used to display window titles, menus, and dialog boxes), you can increase the font size using the FIXEDFON.FON, FONTS.FON, and OEMFONTS.FON entries in the [boot] section of the SYSTEM.INI file. However, you should replace the default fonts only with other system font files supplied with Windows for Workgroups. These fonts include 8514FIX.FON, 8514SYS.FON, and 8514OEM.FON.

For example, if you are using a VGA video driver, your .FON files are probably set as follows:

fixedfon.fon=vgafix.fon

fonts.fon=vgasys.fon

oemfonts.fon=vgaoem.fon

To increase the size of the system font, expand 8514FIX.FON, 8514SYS.FON, and 8514OEM.FON from the original Windows for Workgroups disks to your Windows program directory (usually C:\WINDOWS). For example, type the following command at the MS-DOS command prompt, and then press ENTER:

expand a:\8514fix.fo_ c:\windows\system\8514fix.fon

Then, edit the [boot] section of your SYSTEM.INI file to read:

fixedfon.fon=8514FIX.FON

fonts.fon=8514SYS.FON

oemfonts.fon=8514OEM.FON

Warning: Do not use font files other than the system .FON fonts supplied with Windows for Workgroups. For example, you cannot use TrueType (.TTF) fonts.

�	If you have trouble reading the titles of icons, you can adjust the appearance of these titles with the IconTitleFaceName and IconTitleSize entries in the [desktop] section of the WIN.INI file. For example:

[desktop]

IconTitleFaceName=Arial

IconTitleSize=12

�	If you have trouble reading small fonts used by some applications and do not want to install a screen enlarger utility, you can restrict the fonts available to Windows-based applications by removing the fonts you do not want in the Fonts dialog box of Control Panel. You do not need to actually delete the font files. If you remove all the fonts, only the system fonts remain available to applications.

Note: You may also need to adjust the icon spacing in the Desktop dialog box of Control Panel and choose Arrange Icons from the Window menu in Program Manager to make all your icon titles visible.

�	If you have trouble reading the file and directory names in File Manager, you can adjust the font settings by choosing Font from the Options menu.

�	If you have trouble locating the text-selection cursor (also known as the caret or insertion bar) in your applications, you can adjust the rate at which it flashes. To do this, choose the Desktop icon in Control Panel.

Changing Schedule+ and Mail Settings

�	If you have trouble reading the text in Schedule+, you can adjust the fonts and colors by choosing Display from the Options menu.

�	If you have trouble reading the text in Microsoft Mail, you can adjust the fonts using the FixedFont, NormalFont, and PrintFont entries in the [Microsoft Mail] section of the MSMAIL.INI file, which is located in your Windows for Workgroups directory. Each entry has four parts separated by commas: the font name, point size, a flag for bold, and a flag for italic. To switch between the normal font and the fixed font, choose Change Font from the View menu. Each entry is described separately in the following paragraphs.

FixedFont=facename, size, 0|1, 0|1

The above entry identifies a fixed-pitch font you can substitute for the one supplied with Microsoft Mail. This font serves as an alternative to the Microsoft Mail default (Helvetica 10 point). This entry affects only the message body text, not the message envelope text or folder lists. In Windows for Workgroups Mail, the default is Courier New, 9, 0, 0 (Courier New, 9-point, not bold, not italic).

NormalFont=facename, size, 0|1, 0|1

The above entry identifies the proportionally spaced default font used to display Mail messages. This entry affects only the message body text, not the message envelope text or folder lists. The default value is Helv, 10, 0, 0.

PrintFont=facename, size, 0|1, 0|1

The above entry identifies the default proportionally spaced font used to print Mail messages. The default value is Helv, 10, 0, 0.

Changing Mouse Behavior

�	If you have difficulty controlling the Microsoft Mouse, you can adjust its speed in the Mouse dialog box of Control Panel.

�	If you have trouble seeing the mouse when you are moving it, you can try using the Mouse Trails feature in the Mouse dialog box of Control Panel. If your third-party video driver does not support the Mouse Trails option, contact your video card vendor for more information.

�	If you have trouble double-clicking the mouse, you can adjust the sensitivity using the Double-Click Speed setting in the Mouse dialog box of Control Panel. You can further adjust the double-click functionality by adding the DoubleClickHeight and DoubleClickWidth entries to the [Windows] section of the WIN.INI file. For example, if you add the following entries to your WIN.INI file and restart your computer, you no longer have to hold the mouse in exactly the same location when you double-click:

DoubleClickHeight=30

DoubleClickWidth=30

�	If you have trouble positioning the mouse on window frames so that you can adjust the size of the windows, you can increase the window border width setting in the Desktop dialog box of Control Panel.

Changing Keyboard Behavior

�	If you have trouble using the keyboard because of the speed at which it repeats or the delay time before it begins repeating, you can adjust these settings in the Keyboard dialog box of Control Panel. (You can adjust keyboard settings even further using Access Pack for Microsoft Windows, which is described on page 1 of this Application Note.)

�	If you cannot use Control Panel to adjust the keyboard, you can adjust the corresponding KeyboardDelay and KeyboardSpeed entries in the [Windows] section of the WIN.INI file. KeyboardDelay establishes how much time elapses after you hold down a key before the key starts to repeat (the default is 2 milliseconds). KeyboardSpeed establishes how much time elapses between repetitions of a character on the display when you hold down a keyboard key (the default is 31 milliseconds).

�	You can use Windows Recorder to automate common tasks. For more information about using Recorder, run Recorder and choose Contents from the Help menu to open Recorder Help.

�	You can use two methods to reduce the number of keystrokes required to switch between applications. You can use Task List to display a list of all applications currently running, or you can assign a shortcut key to each application. Task List can be invoked by pressing CTRL+ESC, or by choosing Switch To from any application's Control menu. Application shortcut keys can be assigned by creating an icon for the application in Program Manager and using the Properties command on the File menu. For more information on Task List and shortcut keys, see the Microsoft Windows for Workgroups User's Guide.

Getting More Information

Information from Microsoft

For more information on Microsoft products and services for people with disabilities, contact Microsoft Consumer Sales at one of the following numbers:

(800) 426-9400	Voice telephone
(800) 892-5234	Text telephone
Third-Party Product Information

The Trace R&D Center at the University of Wisconsin-Madison produces a book and a compact disc (CD) that describe products that help people with disabilities use computers. The book is titled ResourceBook and contains nearly 500 pages of descriptions and photographs of approximately 2,000 aids. The CD provides a database of more than 12,000 products and other information for people with disabilities. It is issued twice a year and is also available in many public libraries. You can contact the Trace R&D Center at the following address and phone and fax numbers:

Trace R&D Center

S-151 Waisman Center

1500 Highland Avenue

Madison, WI  53705-2280

(608) 263-2309	Voice telephone
(608) 263-5408	Text telephone
(608) 262-8848	Fax
Assistive Technology Programs

For general information and recommendations about how computers can help specific individuals, customers should consult a trained evaluator who can best match the individual's needs with the available solutions. An assistive technology program in your area can provide referrals to programs and services available to you. To locate the assistive technology program nearest you, contact the Center for Developmental Disabilities at the following address and phone and fax numbers:

National Information System

Center for Developmental Disabilities

University of South Carolina

Benson Building

Columbia, SC  29208

(800) 922-9234, extension 301	Voice or text telephone, outside South Carolina
(800) 922-1107	Voice or text telephone, in South Carolina
(803) 777-6222	Voice or text telephone, outside the United States
(803) 777-6058	Fax


Setup Information
WG0949

Setup Information

Introduction

This Application Note discusses installation requirements for Microsoft Windows for Workgroups version 3.11, the differences between the Setup programs for Windows for Workgroups 3.11 and Microsoft Windows operating system 3.1, new device drivers and files that ship with Windows for Workgroups, and the Setup options /a, /n, and /h.

Installation Requirements

To install and use Windows for Workgroups 3.11, you must be using MS-DOS version 3.3 or later. To upgrade from a previous installation of Windows, your Windows version must be 3.1 or later, and your Windows files must be included in your PATH statement. (If you have a version of Windows earlier than 3.1, you need to do a complete Windows for Workgroups installation, not an upgrade.) If you want to preserve your Program Manager groups and other existing Windows settings, you need to install Windows for Workgroups in the directory of your current Windows installation.

Disk Space Requirements

Windows for Workgroups 3.11 requires approximately 4.5 megabytes (MB) more disk space than Windows 3.1. The following table illustrates the disk space requirements for the most common installation types.

Type of installation	Windows 3.1	Windows for Workgroups 3.11
Full installation (286)	8.6 MB	Not Available
Upgrade 3.x (286)	5.2 MB	Not Available
Full installation (386)	9.5 MB	18.0 MB
Upgrade 3.x (386)	5.2 MB	9.0 MB
Network administrator (setup /a)	15.3 MB	21.0 MB
Network setup (setup /n)	3 MB	1.2 MB
Supported Networks

The following networks are supported for use with Windows for Workgroups 3.11:

•	Artisoft LANtastic (versions 3.x, 4.x, and 5.x)

•	Banyan VINES (versions 4.11, 5.0, and 5.52)

•	BW-NFS (version 3.0)

•	DEC Pathworks (versions 4.0, 4.1, and later)

•	IBM OS/2 Lan Server (versions 1.2, 1.3, 1.3 CSD, and 2.0 without API)

•	Microsoft LAN Manager (version 2.1)

•	Microsoft Windows Network

•	Microsoft Windows NT (version 3.1)

•	Microsoft Workgroup Client (all versions)

•	Novell NetWare (versions 3.x, 4.0, and later)

•	Sun Microsystems PC-NFS (version 5)

•	TCS 10Net (versions 4.1x, 4.2, and 5.0)

Before you run a shared copy of Windows for Workgroups that is installed over one of these networks, read the following guidelines. For some networks, you need to take some preliminary steps before running a shared copy of Windows for Workgroups.

Novell NetWare Network

If you are running a shared copy of Windows for Workgroups on a Novell workstation, be sure to log on to the Novell server before starting Windows for Workgroups.

Microsoft LAN Manager and Windows for Workgroups

Before you run a shared copy of Windows for Workgroups on a LAN Manager or Windows for Workgroups workstation, be sure to start the network workstation services. You can do this with the net start workstation command.

If you are using the Windows for Workgroups network drivers, you can start the workstation services automatically by placing one of the following entries in the [Network] section of your SYSTEM.INI file:

autostart=full

autostart=basic

Setting AUTOSTART to FULL installs the enhanced network redirector. The enhanced redirector supports named pipes and LAN Manager application programming interface (API) functions.

Setting AUTOSTART to BASIC installs the basic network redirector, which uses less system memory but does not support named pipes.

Neither redirector supports network messaging services or pop-up messages.

LAN Manager automatically installs the redirector based on entries in your AUTOEXEC.BAT and CONFIG.SYS files. These settings are specified in the LAN Manager network documentation.

Notes	With Windows for Workgroups 3.11, you can connect to and use files, directories, and printers that are shared on a Microsoft Windows NT or a Microsoft LAN Manager server. To view the name of a LAN Manager server, at least one computer on the network must have a workgroup name that matches the name of the primary domain of the LAN Manager server.

Unlike in version 3.1, if you are running a shared copy of Windows for Workgroups 3.11, you cannot share your workstation's resources once you have started the real mode redirector.

Using Windows for Workgroups with a Different Network Operating System

In addition to the Windows for Workgroups 3.11 network functionality, you can install Windows support for a third-party network operating system. The network operating systems currently supported are:

•	Banyan VINES (versions 4.11, 5.00, and 5.52)

•	BW-NFS (version 3.0)

•	Novell NetWare Shell (versions 3.x and 4.x)

•	Sun Microsystems PC-NFS (version 5.0)

No third-party files are included with Windows for Workgroups 3.11. You must obtain all third-party network operating system files from your network vendor. You must install the third-party network operating system before you select the Windows support option.

Note: This procedure is not useful unless the drivers you obtain from your vendor are compatible with Windows for Workgroups.

To use Windows for Workgroups with a different network:

1.   In the Network group in Program Manager, choose the Network Setup icon.

2.   In the Network Setup dialog box, choose the Networks button.  The Compatible Networks dialog box appears.

3.   Select the Other option button under the heading "You can install Windows support for an additional network" and then select the network you want to set up. If that network does not appear in the list, select Unlisted Or Updated Network.

4.   You are then prompted to insert the disk containing the network driver supplied by your vendor. After you insert the floppy disk in your drive, Setup installs the network driver. The new network should then appear in the Available Network Types group.

5.   Select your network and choose the Add button.

This adds the network to the Other Networks In Use list.

6.   Choose the OK button twice to exit the Network dialog boxes.

Important: To use the new driver(s), you must reboot your machine.

Installing Windows Support for a Third-Party Network Only

You can install Windows support for a third-party network only; however, you lose Windows for Workgroups peer-to-peer functionality if you do so. You can install support for the following networks:

•	Artisoft LANtastic (versions 3.x, 4.x, and 5.x)

•	Banyan VINES (versions 4.11, 5.0, and 5.52)

•	BW-NFS (version 3.0)

•	DEC Pathworks (versions 4.0, 4.1, or later)

•	IBM OS/2 Lan Server (versions 1.2, 1.3, 1.3 CSD, and 2.0 without API)

•	Microsoft Windows Network (version 3.11 Basic)

•	Novell NetWare (versions 3.x, 4.0, and later)

•	Sun Microsystems PC-NFS (version 5)

•	TCS 10Net (versions 4.1x, 4.2, and 5.0)

Differences in Setup Programs for
Windows 3.1 and Windows for Workgroups 3.11

This section discusses new features in the Windows for Workgroups Setup program, including network detection and dialog box changes.

Network Detection

•	Windows for Workgroups 3.11 Setup performs network card detection. If Setup fails to detect your network card, it prompts you to choose from a list of available network adapters.

•	After a failed installation attempt, you can also force Setup to perform network card detection by using the /f switch (setup /f).

•	You can select No Network as a network type during Setup.

Dialog Boxes

•	Windows for Workgroups Setup 3.11 asks for the computer name and the workgroup in the initial user name dialog box.

•	After Setup completes printer installation, the Install New Network Adapter, Network Adapters, and Compatible Networks dialog boxes may appear, as the following table illustrates.

Dialog box	Express Setup	Custom Setup
Install New Network Adapter	Conditional	Conditional
Network Adapters	No	Yes
Compatible Networks	Conditional	Yes
The Install New Network Adapter dialog box does not appear during either Express or Custom Setup if the Network Card Detection (NCD) utility detects your network card and you confirm the detected network card. Confirming the detected network card places a network adapter entry in the PROTOCOL.INI file. If you don't confirm the detected network card, the Install New Network Adapter dialog box appears. If you are upgrading from a Workgroup Connection or LAN Manager 2.1 installation, there is already a valid network adapter entry in the PROTOCOL.INI file, and this dialog box is skipped.

The Compatible Networks dialog box does not appear during Express Setup if you are upgrading from a LAN Manager 2.1 installation. Selecting a network in this dialog box places a multinet= entry in the [Network] section of the SYSTEM.INI file. If Setup detects the existing LAN Manager 2.1 installation, Setup places the multinet= entry in the SYSTEM.INI file and therefore skips the Compatible Networks dialog box.

•	Once Setup is complete, the option to restart Windows is no longer available. (To load or upgrade network drivers, you must reboot your machine.)

Drivers and Files Shipped with Windows for Workgroups 3.11

Setup does not delete drivers that were installed with Windows 3.1 but were not shipped with Windows for Workgroups. The following table shows the drivers and files that do ship with Windows 3.1 and/or Windows for Workgroups.

Driver or file	Windows 3.1	Windows for Workgroups 3.11
Quad video driver	Yes	No
ATI VIP video driver	Yes	No
82C441 video driver	Yes	No
ET 4000 video driver	No	Yes - however, Windows for Workgroups does not detect this display. You must manually select the driver.
Olivetti/AT&T Keyboard Mouse driver	Yes	No
MSCDEX CD-ROM driver and TBMI2.COM file	Yes	Yes - updated. If there is an existing MSCDEX driver or TBM12.COM file, Setup copies the new driver and file to the Windows directory and modifies the AUTOEXEC.BAT file to point to the new (updated) driver and file.
WFWNET.DRV	No	Yes
VNETBIOS.386	No	Yes
VNETSUP.386	No	Yes
VREDIR.386	No	Yes
VSERVER.386	No	Yes
VBROWSE.386	No	Yes
VWC.386	No	Yes
NETAPI.DLL	No	Yes
PMSPL.DLL	No	Yes
NETDDE.EXE	No	Yes
NDDENB.DLL	No	Yes
WFWSETUP.CPL	No	Yes
NETWORK.INF	No	Yes
LM21DRV.UPD	No	Yes
WFWNET.HLP	No	Yes
CLIPSRV.EXE (ClipBook server)	No	Yes
CLIPBRD.EXE (ClipBook Viewer)	No	Yes
WINCHAT.EXE (Chat)	No	Yes
WINMETER.EXE (WinMeter)	No	Yes
MSMAIL.EXE (Mail)	No	Yes
SCHDPLUS.EXE (Schedule)	No	Yes
NETWATCH.EXE (NetWatcher)	No	Yes
MSHEARTS.EXE (Hearts)	No	Yes
CALENDAR.EXE (Calendar)	Yes	No
SSMYST.SCR (Mystify screen saver)	Yes	No
ARCHES.BMP (Arches wallpaper)	Yes	No
CHITZ.BMP (Chitz wallpaper)	Yes	No
FLOCK.BMP (Flock wallpaper)	Yes	No
MARBLE.BMP (Marble wallpaper)	Yes	No
TARTAN.BMP (Tartan wallpaper)	Yes	No
CHORD.WAV (Chord sound)	Yes	No
TADA.WAV (Trumpet sound)	Yes	No
APPS.HLP (Application Compatibility Help)	Yes	No
COMMCTRL.DLL	No	Yes
FRAMEWRK.DLL	No	Yes
MAILMGR.DLL	No	Yes
MAILSPL.EXE	No	Yes
MAPI.DLL	No	Yes
MSSFS.DLL	No	Yes
PABNSP.DLL	No	Yes
DEMILAYR.DLL	No	Yes
SENDFILE.DLL	No	Yes
STORE.DLL	No	Yes
VFORMS.DLL	No	Yes
AB.DLL	No	Yes
NDDEAPI.DLL	No	Yes
VSHARE.386	No	Yes
VCD.386	Yes	Yes
VDMAD.386	Yes	Yes
VPICD.386	Yes	Yes
VPD.386	Yes	Yes
Setup Options (Setup /A, Setup /N, and Setup /H)

Setup /A and Setup /N

You run Setup with the /a and /n options to configure a workstation to run Windows from a shared directory. Administrative Setup (setup /a) copies all the files from the Windows distribution disks to a single directory and marks them as read-only. This directory can then be used to install and run a shared copy of Windows. Setup /n sets up the shared copy of Windows.

In a stand-alone Windows 3.1 installation, the Windows directory and SYSTEM subdirectory are on your personal hard disk drive. In a shared Windows installation, the Windows directory can be located on the user's hard disk drive or on a network drive, and can be customized for each user. There is no SYSTEM subdirectory, as such, in a network installation; system files are typically located in a shared directory on a network server.

In Windows for Workgroups 3.11, as in Windows 3.1 running on a network, the personal Windows directory contains all files with .INI, .GRP, and .PIF extensions, as well as REG.DAT, WIN.COM, WINVER.EXE, and any MS-DOS device driver files. The personal Windows directory may also contain the MS-DOS network device drivers and the NET.EXE, MSIPX.COM, and NETX.COM files. (These files may also be copied to the root directory of the boot drive, as explained in the following section.) The shared directory contains all other Windows files.

Note: If you are setting up a third-party network operating system under Windows for Workgroups, you must place the necessary files provided by the third-party network operating system manufacturer in the shared Windows directory created by the setup /a command. When you run setup /n, Setup does not prompt you for these files.

Where Setup Places Network Files

The Windows 3.1 Setup program reads the SETUP.INF file to determine where to install files. SETUP.INF uses the file classifications windir and sysdir to refer to files that Setup installs in the Windows directory and SYSTEM subdirectory, respectively.

The Windows for Workgroups 3.11 Setup program reads the NETWORK.INF file to determine where to install files. Setup places files with the windir classification in the personal Windows directory and files with the sysdir classification in a shared server directory. NETWORK.INF also uses two new file classifications, netdir and devdir. Where Setup places these files depends on the type of installation.

Real-mode network device drivers (devdir files) are copied to the personal Windows directory on a local nonremovable, noncompressed drive. These include PROTMAN.DOS, PROTOCOL.INI, and WORKGRP.SYS. If the personal Windows directory is on a remote, removable, or compressed volume, then these files are copied to the root of the boot drive. These device drivers must be correctly referenced in the CONFIG.SYS file.

Real-mode network utilities and terminate-and-stay-resident (TSR) programs (netdir files) are copied to the personal Windows directory on a nonremovable hard disk. These include NET.EXE, MSIPX.COM, NETX.COM, and ROUTE.COM. If the personal Windows directory is on a remote or removable volume, these files are copied to the same directory as the devdir files. These utilities and TSRs must be correctly referenced in the AUTOEXEC.BAT file.

Note: If your personal Windows directory is on a remote volume, you still must have your own hard disk drive to run Windows for Workgroups. Windows for Workgroups does not support diskless workstations or systems without hard disk drives.

The following table illustrates where Setup places the netdir and devdir files for different installations.

Location of Windows installation	Location of netdir files	Location of devdir files
Nonremovable hard disk drive	Windows	Windows
Compressed nonremovable hard disk drive	Windows	Root
Removable drive (for example, SCSI)	Root	Root
Remote drive (setup /n)	Root	Root
Batch Mode Setup (Setup /H)

You can use Setup with the /h option to automate the Setup program. Windows for Workgroups 3.11 and Windows 3.1 come with a system-settings template file called SETUP.SHH, which you can copy or modify to create a custom system-settings file. In addition to the settings specified in the Windows 3.1 template file, the Windows for Workgroups template file includes parameters for the computer name, workgroup, network card, protocol, and compatible network. The SETUP.SHH file is located on Windows for Workgroups 3.11 Disk 1 and is copied to the shared Windows for Workgroups directory when you run setup /a. You can modify the template file with any text editor that can save unformatted text (ASCII) files.

For more information about batch mode setup, refer to Chapter 3 of the Microsoft Windows for Workgroups Resource Kit.


NDIS2SUP.386 Corrects Problems on IBM Token Ring
WG0971

NDIS2SUP.386 CORRECTS PROBLEMS RESTARTING WINDOWS FOR WORKGROUPS ON TOKEN RING MACHINES

Introduction

You may have problems quitting Windows for Workgroups version 3.11 on systems using the NDIS version 2 IBM® token ring driver (IBMTOK.DOS). If you run, quit, and then restart Windows for Workgroups (without restarting the computer), the computer usually stops responding (hangs). With this driver, you may also notice that your video display is reset after you quit Windows for Workgroups. For example, if your video display is set to 50-line mode before you run Windows for Workgroups, it may be reset to 25-line mode after you quit.

The WG0971 disk included with this Application Note contains a new NDIS 2.0/3 support layer file (NDIS2SUP.386) to correct these problems.

To install the new NDIS2SUP.386 file

1.   Insert the enclosed WG0971 disk in the appropriate floppy disk drive.

2.   To copy the file to the Windows SYSTEM directory, type the following at the MS-DOS command prompt and then press  < ENTER >

copy drive:\ndis2sup.386 destination

where drive is the floppy disk drive containing the WG0971 disk and destination is the drive and directory of your Windows SYSTEM directory.

For example, if the WG0971 disk is in drive A and your Windows directory is C:\WINDOWS, type the following at the MS-DOS command prompt and then press ENTER:

copy a:\ndis2sup.386 c:\windows\system


NE2000.COM ODI driver
WG0973

RMM.D32 CORRECTS FIVE-SECOND DELAYWHEN STARTING WINDOWS-BASED APPLICATIONS

Introduction

When you start a Windows-based application under Windows for Workgroups 3.11, you may experience a five-second delay before any disk activity occurs and the application begins to load. This delay occurs if you have 32-bit file access enabled and you are using one of the following network configurations:

•	MSIPX

•	Novell(R) NE2000.COM ODI driver and IPXODI

NOTE: Microsoft has confirmed this problem occurs with version 1.34 of the NE2000 multiple link interface device (MLID) driver (dated 6/3/91) and the versions included in the Novell DOSUP7 and DOSUP8 client files (dated 1/18/93 and 7/30/93, respectively).

This delay is caused by the 32-bit file access real-mode mapper (RMM.D32) timing out. Once the application loads, it runs at normal speed because it is now stored in the 32-bit disk cache (VCACHE.386).

You can work around this delay by disabling 32-bit file access or by installing the updated RMM.D32 file contained on the WG0973 disk included with this Application Note. The updated RMM.D32 file is not hard-coded for a five-second time-out. Instead, it has a one-second default time-out and can be configured using the RMMTimeout= entry in the SYSTEM.INI file.

To install the updated RMM.D32 file

Insert the enclosed WG0973 disk in the appropriate floppy disk drive.

Copy RMM.D32 to your Windows SYSTEM subdirectory using the following

command

copy <drive>:\rmm.d32 <destination>

where <drive> is the floppy disk drive containing the WG0973 disk and  <destination> is the drive and directory of your Windows SYSTEM subdirectory. For example, if your WG0973 disk is in drive A, and your Windows directory is C:\WINDOWS, type the following at the MS-DOS command prompt and then press   < ENTER >:

copy a:\rmm.d32 c:\windows\system

Configuring the RMM.D32 Time-Out Setting

To change the one-second default time-out value for the updated RMM.D32 file, open your SYSTEM.INI file in Microsoft Windows for Workgroups Notepad, locate the [386Enh] section, and add the RMMTimeout= entry setting (which is expressed in milliseconds). For example, to increase the time-out for RMM.D32 to two seconds, add the following entry to the [386Enh] section of your SYSTEM.INI file:

RMMTimeout=2000

To decrease the time-out for RMM.D32 to half a second, change the setting as follows:

RMMTimeout=500


VKDA.386 - Keyboard Problems
WG0974

VKDA.386 CORRECTS KEYBOARD PROBLEMS

Symptoms

When you start Windows for Workgroups version 3.11, your system may stop responding (hang) at the password dialog box or in Program Manager if you set your password to null during Setup. The WG0974 disk included with this Application Note contains a new virtual keyboard driver that corrects this problem for the following computers:

Manufacturer	Model(s)
Ambra Blue Lightning	B466DL, B466TL, D466DL, D466TL, and D466BL
Compaq	All Aero machines
Crystal Data Systems	486 machines
DEC	316 SX
GRiD Systems	320S with Tandy/Phoenix BIOS V 1.10
IBM	Valuepoint PS/2 450TX2/D machine types 6384 and 6382
Tandy	2500 SX/20, 2500 SX/25, 2500 SX/33, and 4020
Twinhead	486/33
Victor	300SX/33 and 400SX
Note: Machines manufactured by Compaq after April 1, 1994, that ship with Windows 3.1 come preinstalled with a virtual keyboard driver (VKD) that corrects this problem. Upgrading to Windows for Workgroups 3.11 leaves this VKD in place and allows the keyboard to work properly. However, if you install Windows for Workgroups 3.11 to a new directory, the keyboard stops functioning. If you perform such an installation, you must manually install the new VKD.

Cause

The keyboard controllers in these machines generate unnecessary interrupts each time a key is pressed and released. The keyboard stops responding because the Windows for Workgroups 3.11 VKD, unlike the Windows 3.1 VKD, does not ignore these extra interrupts.

Resolution

To correct this problem, use one of the following methods:

Install the new VKDA.386 file provided with this Application Note.

----  or  ----

Install the Microsoft Mouse version 9.x driver. The replacement VKD that comes with this software (MOUSEVKD.386) handles the extra interrupts generated by the keyboards.

Note: You may also be able to download a new VKD from the your computer manufacturer's bulletin board service (BBS). For example, SP0738.ZIP, which is available on the COMPAQ BBS, contains a new VKD that corrects this problem. Contact your computer manufacturer to see if an updated driver is available.

To install the new VKDA.386 file

1.  Insert the enclosed WG0974 disk in the appropriate floppy disk drive.

2.  To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press ENTER

copy drive:\vkda.386 destination

where drive is the floppy disk drive containing the WG0974 disk and destination is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG0974 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MSDOS command prompt and then press ENTER:

copy a:\vkda.386 c:\windows\system

3.  Use a text editor to edit the keyboard= entry in the [386Enh] section of the SYSTEM.INI file. Change

keyboard=*vkd

to:

keyboard=c:\windows\system\vkda.386


IBMTOK.386 Exiting WFWG 3.11
WG0988

IBMTOK.386 Corrects Problems with Exiting Windows for Workgroups

Introduction

When you use the Windows for Workgroups version 3.11 IBMTOK.386 driver, you may experience the following problems:

•	A stack overflow error message occurs when you exit Windows for Workgroups.

•	Your system stops responding (hangs) when you exit Windows for Workgroups.

The WG0988 disk included with this Application Note contains a new IBMTOK.386 driver to correct these problems. The new driver allows the MCA IBM token ring card to correctly disengage from the network ring when the network interface card (NIC) is set for IRQ 2.

To install the new IBMTOK.386 file

1    Quit Windows for Workgroups.

2.   Make a backup copy of the currently installed IBMTOK.386 file by typing the following at the MS-DOS command prompt and then pressing  <ENTER >

ren drive:path\ibmtok.386 ibmtok.old

where drive:path is the location of your Windows SYSTEM subdirectory.

For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MSDOS command prompt and then press ENTER:

ren c:\windows\system\ibmtok.386 ibmtok.old

3.   Insert the enclosed WG0988 disk in the appropriate floppy disk drive.

4.   To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press < ENTER >

copy drive:\ibmtok.386 destination

where drive is the floppy disk drive containing the WG0988 disk and destination is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG0988 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  < ENTER >:

copy a:\ibmtok.386 c:\windows\system


ELNK3.386 CORRECTS PROBLEM WITH SYSTEMS THAT HANG
WG0990

ELNK3.386 CORRECTS PROBLEM WITH SYSTEMS THAT HANG WITH NON-802.3 PACKETS

Introduction

When you use the Windows for Workgroups version 3.11 ELNK3.386 driver, your system may stop responding (hang) when it encounters non-802.3 packets. This problem typically occurs on extremely congested networks that contain a variety of packet types, especially non-NetBEUI packets.

The WG0990 disk included with this Application Note contains a new ELNK3.386 driver to correct this problem. The new driver correctly handles unknown packet types in heavy network traffic situations.

To install the new ELNK3.386 file

1.   Quit Windows for Workgroups.

2.   Make a backup copy of the currently installed ELNK3.386 file by typing the following at the MS-DOS command prompt and then pressing  <ENTER>

ren <drive>:<path>\elnk3.386 elnk3.old

where <drive>:<path> is the location of your Windows SYSTEM subdirectory.

For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then   press <ENTER>

ren c:\windows\system\elnk3.386 elnk3.old

3.   Insert the enclosed WG0990 disk in the appropriate floppy disk drive.

4.   To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press  <ENTER>

copy <drive>:\elnk3.386 <destination>

where <drive> is the floppy disk drive containing the WG0990 disk and <destination> is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG0990 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  <ENTER>

copy a:\elnk3.386 c:\windows\system


Updated NE2000.386 Allows WFW to Start Correctly
WG0991

Updated NE2000.386 Allows Windows for Workgroups to Start Correctly

Introduction

When you use the Windows for Workgroups version 3.11 NE2000.386 driver with a Novell NE/2 network interface card (NIC), your system may stop responding (hang) when you try to start Windows for Workgroups.

The WG0991 disk included with this Application Note contains an updated NE2000.386 driver to correct this problem.

To install the updated NE2000.386 file

1.   Quit Windows for Workgroups.

2.   Make a backup copy of the currently installed NE2000.386 file by typing the following at the MS-DOS command prompt and then pressing ENTER

ren drive:path\ne2000.386 ne2000.old

where drive:path is the location of your Windows SYSTEM subdirectory.

For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MSDOS command prompt and then press   < ENTER >:

ren c:\windows\system\ne2000.386 ne2000.old

3.   Insert the enclosed WG0991 disk in the appropriate floppy disk drive.

4.   To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press ENTER

copy drive:\ne2000.386 destination

where drive is the floppy disk drive containing the WG0991 disk and destination is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG0991 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press   < ENTER >:

copy a:\ne2000.386 c:\windows\system


Updated Files for Microsoft At Work PC Fax Version 1.0
WG0992

Updated Files for Microsoft At Work PC Fax Version 1.0

Introduction

The WG0992 disk included with this Application Note contains updated files for Microsoft At Work PC Fax version 1.0. The updated files correct the following problems:

•	Slow performance when you are using a shared fax device.

Now when you use a shared fax device, you receive better performance because At Work PC Fax polls from the client only when pending fax jobs are on the server.

•	Extended characters are not rendered on cover pages.

•	The redial level cannot be set from the EFAXPUMP.INI file.

You can now set the RedialLevel=n entry in the [EfaxPump] section of the EFAXPUMP.INI file. If RedialLevel is not set, or is set to 0 (zero), Microsoft At Work PC Fax redials only when the line is busy. If RedialLevel is  set to 1, Microsoft At Work PC Fax redials when any dial failure occurs (for example, the line is busy, the other party does not answer, or there is no dial tone).

•	Microsoft At Work PC Fax stops responding (hangs) when the EFAXPUMP.INI file becomes too large.

Previously, Microsoft At Work PC Fax would hang when the EFAXPUMP.INI file reached approximately 55 kilobytes in size. Microsoft At Work PC Fax now displays a warning message when the EFAXPUMP.INI file becomes too large.

•	Timing problems occur when you send a fax in facsimile format from an application that does not support running multiple instances during printing.

Microsoft At Work PC Fax now recognizes the [PCFaxCompatibility] section in the WIN.INI file. This allows Microsoft At Work PC Fax to keep track of applications that do not support running multiple instances during printing. The format of the [PCFaxCompatibility] section is as follows

[PCFaxCompatibility]

AppExeName=0x0001

where AppExeName is the application's filename (without its extension).

•	Shared CAS modems fail when capability is set to RES_SUPER_SUPER.

Previously, a shared CAS modem would return the unsupported capabilities resolution RES_SUPER_SUPER to the client. Shared CAS fax modems no longer return capabilities to the fax client since these are needed only by the shared fax server.

To install the updated Microsoft At Work PC Fax files

1.   Quit Windows for Workgroups.

2.   Insert the enclosed WG0992 disk in the appropriate floppy disk drive.

3.   To copy the files to the Windows directory, type the following at the MS-DOS command prompt and then press  <ENTER>

copy drive:\*.dll destination

where drive is the floppy disk drive containing the WG0992 disk and destination is your Windows drive and directory.

For example, if the WG0992 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  < ENTER >:

copy a:\*.dll c:\windows


Updated SERIAL.386 for Windows for Workgroups
WG1001

Updated SERIAL.386 Driver for Windows for Workgroups

Introduction

When you use Windows for Workgroups version 3.11 with serial communications software, you may experience the following problems:

•	If you are using a Pentium-based machine with a 16550 UART chip, your system stops responding (hangs) if there is data in the chip when the serial communications application attempts to open the communications port.

A problem with the 16550 UART implementation causes the chip to become trapped in a mode in which data is always detected in its FIFO buffer.

•	When you are using communications software, you may be able to make one connection after starting Windows for Workgroups, but any subsequent connections fail and may hang your system.

This problem occurs when SERIAL.386 sends an extra NUL character through the port when the communications software calls the CloseComm application program interface (API) function. While this does not normally cause problems, your second connection may fail with some modems.

The WG1001 disk included with this Application Note contains an updated SERIAL.386 driver that corrects both of these problems.

To install the updated SERIAL.386 file

1.   Quit Windows for Workgroups.

2.   Make a backup copy of the currently installed SERIAL.386 file by typing the following at the MS-DOS command prompt and then pressing  <ENTER>

ren drive:path\serial.386 serial.old

where drive:path is the location of your Windows SYSTEM subdirectory.

For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MSDOS command prompt and then press  <ENTER>:

ren c:\windows\system\serial.386 serial.old

3.   Insert the enclosed WG1001 disk in the appropriate floppy disk drive.

4.   To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press  <ENTER>

copy drive:\serial.386 destination

where drive is the floppy disk drive containing the WG1001 disk and destination is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG1001 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  <ENTER>:

copy a:\serial.386 c:\windows\system


SCHEDMSG.DLL Corrects French Headers
WG1002

Microsoft Mail 3.2 SCHEDMSG.DLL Corrects French Headers in Windows for Workgroups Mail

Introduction

When you reply to a reply from a Windows for Workgroups 3.11 Schedule+ meeting request, the header information may be converted to French. For example, the header appears as follows:

De: User B

A: User A

Date d'envoi: dddddddd, mmmmmmm dd, yyyy, hh:mmPM/AM

Objet: YES: Subject text

Microsoft Mail v3.0 IPM.Microsoft Schedule.MtgRespP

To: User A

Date Sent: yyyy-mm-dd, hh:mm

Période: ddd, mmm dd, yyyy,  hh:mmPM/AM - hh:mmPM/AM

Subject: YES: Subject text

The WG1002 disk included with this Application Note contains the SCHEDMSG.DLL file from Microsoft Mail version 3.2. Using this file with Windows for Workgroups version 3.11 Mail and Schedule+ corrects the problem noted above.

To install the updated SCHEDMSG.DLL file

1.   Quit Windows for Workgroups.

2.   Make a backup copy of the currently installed SCHEDMSG.DLL file by typing the following at the MS-DOS command prompt and then pressing ENTER

ren drive:path\schedmsg.dll schedmsg.old

where drive:path is the location of your Windows SYSTEM subdirectory.

For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MSDOS command prompt and then press  <ENTER>:

ren c:\windows\system\schedmsg.dll schedmsg.old

3.   Insert the enclosed WG1002 disk in the appropriate floppy disk drive.

4.   To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press ENTER

copy drive:\schedmsg.dll destination

where drive is the floppy disk drive containing the WG1002 disk and destination is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG1002 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  <ENTER>:

copy a:\schedmsg.dll c:\windows\system


MSODISUP Corrects Problems with 3Com 3c509 & 3c5x9
WG1004

Updated MSODISUP File Corrects Problems Using 3Com 3c509 and 3c5x9 ODI MLIDs

Introduction

If you use the 3Com EtherLink III (3c509) network interface card (NIC) and a 3Com ODI MLID (3C509.COM or 3C5X9.COM) with Windows for Workgroups version 3.11 and Novell NetWare is installed as your secondary network, your system may:

•	Stop responding (hang) when you copy large files across the network.

or

•	Inadvertently lose network connections.

The WG1004 disk included with this Application Note contains an updated MSODISUP.386 file that corrects both of these problems. The updated file correctly adjusts the counter for the number of outstanding packets to be copied off the NIC after the MLID fails to copy an incoming packet off the NIC.

The updated file allows you to successfully use multiple 3Com NICs with Windows for Workgroups. The updated file ensures that all adapter names are available for binding when multiple ODI drivers are loaded. For example, you can now have the 3c503 and 3c509 drivers loaded so that you can run two NICs on separate networks or send one protocol to one NIC and a different protocol to another NIC.

Note: Although you can use multiple different NICs, you cannot use more than one of the same NIC. For example, you can use a 3c503 NIC and a 3c509 NIC, but you cannot use two 3c503 NICs.

The WG1004 disk included with this Application Note contains an updated NETWORK.INF file that corrects binding entry errors with the 3Com EtherLink III 3c5x9 driver. The updated NETWORK.INF uses mlid=*:3c5x9.com instead of mlid=*:3c509.com.

To install the updated files

1.   Quit Windows for Workgroups.

2.   Make a backup copy of the currently installed MSODISUP.386 file by typing the following at the MS-DOS command prompt and then pressing ENTER

ren drive:path\msodisup.386 msodisup.old

where drive:path is the location of your Windows SYSTEM subdirectory.

For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MSDOS command prompt and then press  <ENTER>:

ren c:\windows\system\msodisup.386 msodisup.old

3.   Repeat step 2, but substitute NETWORK.INF for MSODISUP.386 and NETWORK.OLD for MSODISUP.OLD. For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MSDOS command prompt and then press  <ENTER>:

ren c:\windows\system\network.inf network.old

4.   Insert the enclosed WG1004 disk in the appropriate floppy disk drive.

5.   To copy the MSODISUP.386 and NETWORK.INF files to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press ENTER

copy drive:*.* destination

where drive is the floppy disk drive containing the WG1004 disk and destination is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG1004 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  <ENTER>:

copy a:*.* c:\windows\system


UPDATED NWLINK.386 Allows Routing Across Cisco Router
WG1027

UPDATED NWLINK.386 ALLOWS ROUTING ACROSS CISCO ROUTER

Introduction

When you are using the Windows for Workgroups version 3.11 NWLINK.386

file to connect to a network that uses a Cisco router, the following

problems may occur:

•	Windows for Workgroups workstations configured with the "IPX/SPX Compatible Transport with NetBIOS" option cannot communicate across a Cisco router when both Novell(R) routing and DECnet(TM) routing are enabled.

----or----

•	A Windows for Workgroups workstation displays the "Error 51:  Failure to Connect" message in response to the NET USE  \\<SERVER>\<SHARENAME> COMMAND.

These problems occur when NWLINK.386 does not correctly handle certain Cisco router addresses that begin with the letter A. Any address with the high-order bit set on an end or intermediate system results in NWNBlink truncating the routing address, which causes the network connection to fail.

The WG1027 disk included with this Application Note contains a revised NWLINK.386 file that corrects this problem.

To install the new NWLINK.386 file

1.   Quit Windows for Workgroups.

2.   Make a backup copy of the currently installed NWLINK.386 file by typing the following at the MS-DOS command prompt and then pressing   <ENTER>

ren <drive:path>\nwlink.386 nwlink.old

where <drive:path> is the location of your Windows SYSTEM subdirectory.

For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  <ENTER>

ren c:\windows\system\nwlink.386 nwlink.old

3.   Insert the enclosed WG1027 disk in the appropriate floppy disk drive.

4.   To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press  <ENTER>

copy <drive>:\nwlink.386 <destination>

where <drive> is the floppy disk drive containing the WG1027 disk and <destination> is the drive and directory of your Windows SYSTEM subdirectory.

For example, if the WG1027 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press  <ENTER>

copy a:\nwlink.386 c:\windows\system