· Win /d:x

Starts Windows for Workgroups 3.11 with the full upper memory area excluded. This is the same as adding "emmexclude=a000-ffff" to the [386Enh] section of the SYSTEM.INI. Use this switch if you suspect that Windows is overwriting a ROM device (such as a netcard) that is loaded in the upper memory area. If this switch fixes your problem, you should then add an EMMExclude= setting to the [386Enh] section of the SYSTEM.INI. You should adjust the setting to only exclude the ROM device that is being overwritten. Note that in order for this to work successfully, there must not be a UMB provider (Emm386, Qemm386, etc.) loaded in the CONFIG.SYS file.

· Win /d:s

Starts Windows for Workgroups 3.11 with the [386enh] mode switch "SystemROMBreakPoint=OFF" set.. This is the same as adding "SystemROMBreakPoint=OFF" to the [386Enh] section of the SYSTEM.INI. For more information on the "SystemROMBreakPoint=" switch, see Chapter 4, "Windows for Workgroups 3.11 Initialization Files."

· Win /d:v

Starts Windows for Workgroups 3.11 with the [386enh] mode switch "VirtualHDirq=off" set.. This is the same as adding "VirtualHDirq=off" to the [386Enh] section of the SYSTEM.INI. For more information on the "VirtualHDirq=" switch, see Chapter 4, "Windows for Workgroups 3.11 Initialization Files."

· Win /d:f

This switch disables the WDCTL "32 Bit Disk Access" driver. This is the same thing as setting "32bitdiskaccess=off" to the [386enh] section of the SYSTEM.INI. Note that this will only apply to machines that have Western Digital 1003 compatible controllers in them.

The following switches are new to Windows for Workgroups 3.11:

· Win /n

This switch starts Windows for Workgroups 3.11 with no Windows protect mode network drivers loaded. It is useful if you think one of the network drivers is causing your problem. You might also use this switch if you are using a portable computer when is not hooked up to a network card.

· Win /d:t

This switch starts Windows in "troubleshooting" mode. Windows will start with no virtual device drivers (VxDs) loaded. This is a good switch to use if you suspect a VxD conflict. When running in this mode, MS-DOS applications can not run, communications applications can not run, and networking functionality is disabled unless you have started the real mode redirector.

· win /d:c

This loads Windows without loading the 32-bit File Access driver, VFAT.386. This switch can be used to troubleshoot whether 32-bit File Access is the source of trouble. This is the same thing as setting removing the 32-bit File Access drivers from the [386enh] section of the SYSTEM.INI.

*.CLN Files

Immediately after the Windows for Workgroups 3.11 Setup program is complete, Windows for Workgroups 3.11 creates backup versions of the SYSTEM.INI, WIN.INI, and PROTOCOL.INI and names them SYSTEM.CLN, WIN.CLN, and PROTOCOL.CLN.

These .CLN files can be extremely useful when trying to solve configuration problems on a machine that worked properly after completing Windows for Workgroups 3.11 Setup, but then stopped working, due to modifications made to the system either by changes to Windows Setup, or by newly installed software. It is recommended to use the MS-DOS copy command rather than simply renaming the .CLN file to the appropriate .INI file. Simply renaming the old .CLN file will leave you with no backup copy.

If Windows for Workgroups 3.11 was working properly and is not any longer

1. Exit Windows for Workgroups 3.11.

2. Rename the currently troubled versions of SYSTEM.INI, PROTOCOL.INI, and WIN.INI to SYSTEM.BAK, PROTOCOL.BAK and WIN.BAK.

3. Copy SYSTEM.CLN to SYSTEM.INI.

4. Copy PROTOCOL.CLN to PROTOCOL.INI.

Note If you have modified the network setup for Windows for Workgroups, it may not be necessary to replace the WIN.INI with the WIN.CLN file. Replacing the WIN.INI file is recommended if you have difficulty after installing a new application or other Windows component.

5. Copy WIN.CLN to WIN.INI.

6. Restart Windows for Workgroups 3.11.

Note Since Network configuration information is stored in the PROTOCOL.INI and SYSTEM.INI, any Network configuring that is done after running the Windows for Workgroups 3.11 Setup program will not be stored in the PROTOCOL.CLN and SYSTEM.CLN.