[Network]

This section specifies the parameters and options for installing networking components. The categories for these parameters include the following:

• Installation parameters
• Computer identification parameters
• Shared installation parameters
• Security parameters
• User interface options

Installation Parameters in [Network]

Clients

This parameter specifies the network clients to be installed. It is a list of the device IDs used in the INF files. These IDs are not limited to those in the Windows 95 INF files (NETCLI.INF and NETCLI3.INF). A site that has an INF file from another vendor can use any device IDs listed in it. However, if you are installing a client other than those listed in the INF files provided with Windows 95, you need to get an updated Windows 95 INF file from your vendor.

If you are installing multiple clients, the first client in this list will start first whenever the computer is started.

Specify multiple networks in a comma-separated list. If the list contains two network clients, or lists multiple networks with a primary-only network (such as IBM® OS/2® LAN Server), Windows 95 Setup presents an error message and displays the Network Configuration properties for changing the selection. The verification process that occurs in Setup still takes place.

The following table shows the valid device IDs for network clients as specified in NETCLI.INF and NETCLI3.INF (which are Windows 95 INF files).

Network Card Drivers

This parameter specifies the drivers to be installed for network adapters as a list of the device IDs used in the INF files. These IDs are not limited to those included in the Windows 95 INF files. A site that has an INF file from another vendor can use any device IDs listed in that file.

Important

In general, it is recommended that you rely on detection in Windows 95 Setup to install the correct driver and define the correct configuration settings.

When a network adapter is listed, the usual verification takes place. Windows 95 Setup chooses an NDIS 3.1 driver, if available; otherwise, it uses an NDIS 2.x driver.

For example, the following entries would install drivers for Intel® EtherExpress™ 16 or 16TP plus 3Com EtherLink II or IITP:

netcards=*PNP812D,*PNP80F3

Ignore Detected NetCards

This parameter specifies whether Setup will use the detected information to configure network adapters or use values specified by the netcards= parameter in the setup script.

Protocols

This parameter specifies the protocols to be installed as a list of the device IDs used in the INF files. These IDs are not limited to those in the Windows 95 INF files. A site that has an INF file from another vendor can use any device IDs listed in that file.

Note

If you are installing a protocol other than those listed in the INF files provided with Windows 95, you need to get an updated Windows 95 INF file from your vendor.

Setup verifies these settings, so it is possible to specify only the network clients and let Windows 95 Setup choose the protocols. For example, if you specify Clients=pcnfs50, then Windows 95 Setup adds NFSLINK.

The valid device IDs for protocols in the Windows 95 INF file (NETTRANS.INF) are the following.

Default Protocol

This parameter sets the default protocol (which is assigned LANA 0), which is the specified protocol bound to the specified network adapter (if the computer has more than one network adapter). If no adapter is specified, the default is the first instance of the specified protocol. Set this value if, for example, the computer will run software that requires a protocol to be bound to LAN adapter (LANA) 0, which can only be defined by setting that protocol as the default protocol. For more information about LAN adapter numbers, see Chapter 12, "Network Technical Discussion."

If netbios=1, you must set defaultprotocol=nwnblink if you want to specify IPX/SPX-compatible protocol as the default.

The folowing example sets the default protocol as an instance of NetBEUI bound to a particular adapter:

DefaultProtocol=netbeui,*pnp812d

Remove Binding

This parameter removes the binding between the two devices. This parameter is used to tune bindings in a setup script.

Services

This parameter specifies the network services to be installed as a list of the device IDs used in the INF files. These IDs are not limited to those in the Windows 95 INF files. A site that has an INF file from another vendor can use any device IDs listed in that file. When a service is listed in a setup script, the usual verification still takes place.

The only service installed by default is VSERVER (File and Printer Sharing for Microsoft Networks) if peer sharing services were enabled for Windows for Workgroups.

The following shows the valid device IDs defined in several different INF files.

1 Available in the ADMIN directory of the Windows 95 compact disc. For information, see Chapter 13, "Introduction to System Management."

For information about using the INFINST utility to set up files from the ADMIN directory on the Windows 95 compact disc for installation from a network directory, see Chapter 5, "Custom, Automated, and Push Installations."

Computer Identification Parameters in [Network]

Computer Name

This parameter sets the computer's network name.

Description

This parameter is the description for the computer (mainly used by peer servers such as File and Printer Sharing for Microsoft Networks).

Workgroup

This parameter sets the workgroup for the computer.

Shared Installation Parameters in [Network]

Hard Disk Boot

This parameter specifies whether, for a client computer running a shared copy of Windows 95 from a server, Setup should configure Windows 95 so that it starts from the hard disk but runs from a shared network copy.

The following table shows the settings for this parameter and the RPLSetup parameter, depending on how the computer runs Windows 95.

Remote-Boot (RPL) Setup

This parameter specifies that Setup should create a disk image on the network server for a remote-boot workstation during Workstation Setup. This parameter is ignored if a corresponding Workstation Setup value is not defined. (Therefore, setting RPLSetup=1 does not automatically set WorkstationSetup=1.)

Workstation Setup

This parameter specifies whether Setup configures a client computer to run Windows 95 locally or as a shared copy from a server. If this parameter is set to No (0), Windows 95 Setup runs normally. If this parameter is set to Allow (1) and if Setup is running from a server, Setup asks if the user wants to install Windows 95 as a shared copy or on the local hard disk. For more information, see Chapter 4, "Server-Based Setup for Windows 95." See also the table for the HDBoot parameter earlier in this section.

Display Workstation Setup

This parameter specifies whether the Setup user interface appears during installation of Windows 95 on a workstation that will run a shared copy of Windows 95. Setting this value to 0 forces the value defined for WorkstationSetup in the script.

Security Parameters in [Network]

User Security

This parameter specifies the security model to be used and, for user-level security, the type of pass-through agent (that is, server or domain). A client with a security provider must be installed for these values to have an effect.

Pass-Through Agent

This parameter specifies the pass-through agent for user-level security. This value is ignored in share-level security.

User Interface Options for [Network] Parameters

Display

This parameter controls whether any of the Network Configuration dialog boxes appear in Custom Setup.

Validate NetCard Resources

This parameter specifies whether to display a dialog box to resolve resource conflicts if a partial configuration is detected or if there is an IRQ conflict for a network adapter.