Microsoft KB Archive/99751

{| = WG0666: WFWG 3.10 Setup Information =
 * width="100%"|

Last reviewed: May 1, 1997

Article ID: Q99751 3.10 WINDOWS kbnetwork kbdisplay kbsound kb3rdparty kbfile kbappnote kbsetup The information in this article applies to:


 * Microsoft Windows for Workgroups version 3.1

Microsoft has an Application Note that discusses the installation requirements for Microsoft Windows for Workgroups, the differences between the setup programs for Windows for Workgroups and Microsoft Windows operating system version 3.1, new device drivers and files that ship with Windows for Workgroups, and the administrative setup options (the /A and /N switches). This Application Note is titled &quot;WG0666: Setup Information.&quot;

You can obtain this Application Note from the following sources:


 * Microsoft's World Wide Web Site on the Internet
 * The Internet (Microsoft anonymous ftp server)
 * Microsoft Download Service (MSDL)
 * Microsoft FastTips Technical Library
 * Microsoft Product Support Services

For complete information, see the &quot;To Obtain This Application Note&quot; section at the end of this article.

THE TEXT OF WG0666
Microsoft(R) Product Support Services Application Note (Text File) WG0666: SETUP INFORMATION Revision Date: 5/93 No Disk Included The following information applies to Microsoft Windows(TM) for Workgroups version 3.1.
 * INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY   |
 * ACCOMPANY THIS DOCUMENT (collectively referred to as an           |
 * Application Note) IS PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY     |
 * KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO   |
 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A    |
 * PARTICULAR PURPOSE. The user assumes the entire risk as to the    |
 * accuracy and the use of this Application Note. This Application   |
 * Note may be copied and distributed subject to the following       |
 * conditions: 1) All text must be copied without modification and   |
 * all pages must be included; 2) If software is included, all files |
 * on the disk(s) must be copied without modification [the MS-DOS(R) |
 * utility DISKCOPY is appropriate for this purpose]; 3) All         |
 * components of this Application Note must be distributed together; |
 * and 4) This Application Note may not be distributed for profit.   |
 * Copyright 1992 Microsoft Corporation. All Rights Reserved.        |
 * Microsoft and MS-DOS are registered trademarks and Windows        |
 * is a trademark of Microsoft Corporation. OS/2 is a registered     |
 * trademark licensed to Microsoft Corporation.                      |
 * 3+Share and 3Com and registered trademarks and 3+Open is a        |
 * trademark of 3Com Corporation. AT&T is a registered trademark of  |
 * American Telephone and Telegraph Company. Banyan and VINES are    |
 * registered trademarks of Banyan Systems, Inc. DEC is a registered |
 * trademark and Pathworks is a trademark of Digital Equipment       |
 * Corporation. TCS is a registered trademark of Eurotherm           |
 * International P.L.C. IBM and OS/2 are registered trademarks of    |
 * International Business Machines Corporation. NetWare and Novell   |
 * are registered trademarks of Novell, Inc. Olivetti is a registered |
 * trademark of Ing. C. Olivetti.                                    |
 * are registered trademarks of Novell, Inc. Olivetti is a registered |
 * trademark of Ing. C. Olivetti.                                    |

INTRODUCTION ============ This application note discusses installation requirements for Microsoft Windows for Workgroups, the differences between the Setup programs for Windows for Workgroups and Microsoft Windows operating system version 3.1, new device drivers and files shipped with Windows for Workgroups, and the administrative Setup options (the /A and /N switches). INSTALLATION REQUIREMENTS ========================= To install and use Windows for Workgroups 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.0 or later, and your Windows files must be included in your PATH statement. (If you have a version of Windows earlier than 3.0, 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 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.1 -

Full installation (286)          8.6 MB            13.8 MB  Upgrade 3.x (286)                 5.2 MB             6.6 MB  Full installation (386)           9.5 MB            15.0 MB  Upgrade 3.x (386)                 5.2 MB            10.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:

Microsoft Workgroup Client (all versions) Microsoft LAN Manager (version 2.1) Novell(R) NetWare(R) (all versions) Before starting a shared copy of Windows for Workgroups that is installed over one of these networks, please use the following guidelines:

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.

LAN Manager or Windows for Workgroups Network
If you are running a shared copy of Windows for Workgroups on a LAN Manager or Windows for Workgroups workstation, be sure to start the network workstation services before you start Windows for Workgroups. You can do this with the &quot;net start workstation&quot; command.

If you are using the Windows for Workgroups network drivers, you can start the workstation services automatically by placing either 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.

NOTE: Setup adds the AUTOSTART switch for you if you are installing on a 286-based machine.

UNSUPPORTED NETWORKS
The following networks that are supported under Windows 3.1 are not specifically supported in the Windows for Workgroups package. (Drivers for these networks are not shipped with Windows for Workgroups but might be available through your network vendor.)

No Network Installed Artisoft LANtastic (all versions) Banyan(R) VINES(R) (all versions) DEC(R) Pathworks(TM) (all versions) IBM(R) OS/2(R) LAN Server (all versions) IBM PC-LAN Program (all versions) Microsoft LAN Manager (version 2.0 and earlier) Microsoft Networks or compatible (all versions) TCS(R) 10Net (all versions) 3Com(R) 3+Share(R) (all versions) 3Com 3+Open(TM) (all versions) Setup does not detect these networks, and therefore cannot notify you if they are installed on your system. Check with your network vendor to obtain the necessary drivers before you install Windows for Workgroups over any of these networks. Then, perform the procedure below. Drivers that support using Banyan VINES and DEC Pathworks with Windows for Workgroups are available from Banyan Systems and Digital Equipment Corporation.

To use Windows for Workgroups with a different network
NOTE: This procedure won't be useful unless the drivers you obtained from your vendor are compatible with Windows for Workgroups. Open Control Panel, and from the Settings menu, choose Network. (Or choose the Network icon.) In the Network Settings dialog box, choose the Networks button. The Compatible Networks dialog box appears. From the Available Network Types list, select Unlisted Or Updated Network, and then choose the Add button. You will be prompted to insert the disk containing the network driver supplied by your vendor. When you insert the floppy disk, Setup installs the network driver. The new network should now appear in the Available Network Types group.

Select the network, and then choose the Add button. This adds the network to the Other Networks In Use list. Choose the OK button twice to exit the Networks dialog boxes. Close Control Panel and then reboot your machine. Important: To use the new driver(s), you must reboot your machine. DIFFERENCES IN SETUP PROGRAMS FOR WINDOWS 3.1 AND WINDOWS FOR WORKGROUPS 3.1 ========================================== This section discusses new features in the Windows for Workgroups Setup program, including network detection and dialog box changes.

NETWORK-DETECTION ISSUES
 Setup no longer prompts for a network type. Setup always selects Windows for Workgroups as the network type.  Windows for Workgroups 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. 

DIFFERENCES IN DIALOG BOXES
 Setup now 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 PROTOCOL.INI. If you don't confirm the detected network card, then 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 PROTOCOL.INI, 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 SYSTEM.INI. If Setup detects the existing LAN Manager 2.1 installation, Setup places the multinet= entry in  SYSTEM.INI and therefore skips the Compatible Networks dialog box.   The option to Restart Windows once Setup is complete is no longer available. This is because in order to load or upgrade network drivers, you must reboot your machine. DRIVERS AND FILES SHIPPED WITH WINDOWS FOR WORKGROUPS ===================================================== 

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

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(R)/AT&T(R)   Yes          No  Keyboard Mouse driver MSCDEX CD-ROM driver  Yes          Yes--updated. If there is an and TBMI2.COM file                  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 No           Yes  server) CLIPBRD.EXE (ClipBook No           Yes  Viewer) WINCHAT.EXE (Chat)    No           Yes WINMETER.EXE          No           Yes (WinMeter) MSMAIL.EXE (Mail)     No           Yes SCHDPLUS.EXE          No           Yes (Schedule) NETWATCH.EXE          No           Yes (NetWatcher) MSHEARTS.EXE (Hearts) No           Yes CALENDAR.EXE          Yes          No  (Calendar) SSMYST.SCR (Mystify   Yes          No  screen saver) ARCHES.BMP (Arches    Yes          No  wallpaper) CHITZ.BMP (Chitz      Yes          No  wallpaper) FLOCK.BMP (Flock      Yes          No  wallpaper) MARBLE.BMP (Marble    Yes          No  wallpaper) TARTAN.BMP (Tartan    Yes          No  wallpaper) CHORD.WAV (Chord      Yes          No  sound) TADA.WAV (Trumpet     Yes          No  sound) APPS.HLP (Application Yes          No  Compatibility Help) 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

ADMINISTRATIVE SETUP OPTIONS (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. Setup with the /A option (Administrative Setup) copies all the files from the Windows distribution disks to a single directory and marks them 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 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, 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.

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

The Windows for Workgroups Setup program reads NETWORK.INF 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, &quot;netdir&quot; and &quot;devdir.&quot; 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 CONFIG.SYS.

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 need to have your own hard disk drive to run Windows for Workgroups. Windows for Workgroups does not support diskless workstations or systems with no hard disk drive. The following table illustrates where Setup places the netdir and devdir files for different installations. Location of                   Location of        Location of  Windows Installation           Netdir Files       Devdir Files --

Nonremovable hard disk drive  Windows            Windows

Compressed (nonremovable hard Windows            Root  disk) drive

Removable drive (for example, Root               Root  SCSI)

Remote drive (Setup /N)       Root               Root

SETUP /H (BATCH MODE SETUP)
You can use Setup with the /H option to automate the Setup program. Windows for Workgroups 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.1 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 &quot;Microsoft Windows for Workgroups Resource Kit.&quot;

TO OBTAIN THIS APPLICATION NOTE
You can find WG0666.EXE (size: 19394 bytes) , a self-extracting file, on the following services:   Microsoft's World Wide Web Site on the Internet On the www.microsoft.com home page, click the Support icon. Click Knowledge Base, and select the product. Enter kbfile #|WG0666.EXE (size: 19394 bytes), and click GO! Open the article, and click the button to download the file. </li>  Internet (anonymous FTP) ftp ftp.microsoft.com Change to the Softlib/Mslfiles folder. Get WG0666.EXE (size: 19394 bytes) </li>  Microsoft Download Service (MSDL) Dial (425) 936-6735 to connect to MSDL Download WG0666.EXE (size: 19394 bytes) </li></ul>

For additional information about downloading, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q119591 TITLE    : How to Obtain Microsoft Support Files from Online Services You can have this Application Note mailed or faxed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (425) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area.
 * }