Export (0) Print
Expand All

Setup Script Parameters

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Windows 95 Setup can be run with setup scripts to automate installation when you have defined the options and parameters to be installed on users' computers.

Customization actions that required editing Windows 3.x INF files are all accomplished by means of statements in setup scripts that use MSBATCH.INF format. For information about the procedures for creating and using setup scripts, see Chapter 5, "Custom, Automated, and Push Installations."

This section summarizes the parameters that can be used in setup scripts.

[Setup] parameters:

 

 

Devicepath
EBD
Express
InstallDir

InstallType
PenWinWarning
ProductID
SaveSUBoot

TimeZone
Uninstall (with BackupDir)
Verify
VRC

[System] parameters:

 

 

Display
DisplChar
Keyboard
Locale

Machine
Monitor
Mouse

PenWindows
Power
Tablet

[NameAndOrg] parameters:

 

 

Name

Org

Display

[InstallLocationsMRU] parameters: List of paths

 

 

[OptionalComponents] parameters: List of descriptions

 

 

[Printers] parameters: Printers to install

 

Network-Related Parameters

[Network] parameters:

 

 

Clients
ComputerName
Description
DefaultProtocol
Display
DisplayWorkstationSetup

HDBoot
IgnoreDetectedNetcards
NetCards
PassThroughAgent
Protocols
RemoveBinding

RPLSetup
Services
Security
ValidateNetcardResources
Workgroup
WorkstationSetup

[ netcard_ID] parameters:

Values from the INF file for the network adapter

 

[MSTCP] parameters:

 

 

DHCP
DNS
DNSServers
Domain
DomainOrder

Gateways
Hostname
IPAddress
IPMask
LMHostPath

PrimaryWINS
ScopeID
SecondaryWINS
WINS

[NWLink] parameters:

Frame_Type

NetBIOS

[NWRedir] parameters:

FirstNetDrive
PreferredServer

ProcessLoginScript
SearchMode

[NWServer] parameters:

BrowseMaster

Use_SAP

[VRedir] parameters:

LogonDomain

ValidatedLogon

[VServer] parameters:

LMAnnounce

MaintainServerList

The setup script parameters are not case-sensitive. They are also not required; if they don't appear in a setup script, Windows 95 Setup just uses default values.

Display of most Setup dialog boxes can be disabled in the setup script so that users cannot change any setting. If the dialog boxes are not disabled, sources of information for parameters are given the following priority:

  • Information specified in the setup script

  • User input

  • Detection information

In this section, the descriptions for an option can contain any of six possible entries, as described in the following table. For an example of the resulting file, see "MSBATCH.INF Sample File" later in this appendix.

Entry

Description

Parameter

The name of the parameter as it appears in a setup script

Values

The values that can be assigned to the parameter and what they mean

System policy

The name of the corresponding parameter for this entry in System Policy Editor; if no entry appears, there is no system policy

Default

The built-in value that is used if no other value is provided

[Setup]

This section sets parameters for control of the Setup process.

Device Path

This parameter specifies whether Windows 95 should check a source installation path to find INF files, rather than looking only in the Windows INF directory when installing devices. If this parameter is set to 1, network administrators can later add INF files to a single source location to ensure that up-to-date drivers are installed any time a new device is installed on computers running Windows 95. However, set this value to 1 only if the installation source files are in a network directory (not floppy disks or CD).

Notice also that Devicepath=1 causes the entire INF database to be rebuilt each time a user changes a network component or changes drivers for any device.

Parameter

Devicepath

Values

0 = Do not add a source directory path for INFs
1 = Add the installation source directory to the path for finding INFs

Default

0

Emergency Startup Disk

This parameter specifies whether to create the emergency Startup Disk during Setup (the command-line override for this is /ie). For a setup script intended for hands-free installation, you might want to specify ebd=0 so that the user isn't prompted to insert or remove the floppy disk. If you need to specify ebd=1, you can also add a reboot=0 entry, so that Setup will not attempt to restart the computer while the floppy disk is in the drive.

Parameter

EBD

Values

0 = Do not create an emergency Startup Disk
1 = Create an emergency Startup Disk

Default

1

Express

This parameter specifies whether the user can provide input during Setup. If express=1, then Windows 95 Setup uses only the settings specified in MSBATCH.INF or built-in defaults and does not ask the user to confirm or enter input. This setting disables most of the user interface for Setup.

Parameter

Express

Values

0 = Allow user input
1 = Run Setup using only values in MSBATCH.INF

Default

0

Install Type

This parameter specifies the type of installation for Windows 95 Setup.

Parameter

InstallType

Values

0 = Compact
1 = Typical
2 = Portable
3 = Custom

Default

1

Installation Directory

This parameter specifies the directory where Windows 95 is to be installed or, for shared installations, the machine directory.

Parameter

InstallDir

Values

directory name

Default

Windows directory, if present

Pen Windows Warning

This parameter specifies whether to display a warning if an unknown version of Pen Windows is installed.

Parameter

PenWinWarning

Values

0 = Do not display the warning
1 = Display the warning

Default

1

Product ID

This parameter specifies the product ID for your site, which is printed on the Windows 95 compact disk or your Certification of Authenticity.

Parameter

ProductID

Values

string

Default

none

Save SUBOOT Directory

This parameter specifies whether to save the SUBOOT directory for Server-based Setup.

Parameter

SaveSuBoot

Values

0 = Delete SUBoot directory
1 = Save directory

Default

0

Time Zone

This parameter specifies the time zone to set on the computer.

Parameter

TimeZone

Values

String enclosed in quotation marks, as described in the following list

Default

The time zone currently set on the computer

Time zone strings

 

 

 

Afghanistan
Alaskan
Arabian
Atlantic
AUS Central
Azores
Bangkok
Canada Central
Cen. Australia
Central
Central Asia
Central Pacific
China

Czech
Dateline
E. Europe
E. South America
Eastern
Egypt
Fiji
GFT
GMT
Greenwich
Hawaiian
India
Iran

Israel
Lisbon Warsaw
Mexico
Mid-Atlantic
Mountain
New Zealand
Newfoundland
Pacific
Romance
Russian
SA Eastern
SA Pacific
SA Western

Samoa
Saudi Arabia
South Africa
Sydney
Taipei
Tasmania
Tokyo
US Eastern
US Mountain
W. Europe
West Asia
West Pacific

Uninstall

This parameter is used to specify whether Setup should create a compressed backup version of the existing Windows and MS-DOS directories to be used for automatically uninstalling Windows 95. If you specify Uninstall=5, you also must add a value for BackupDir=path that specifies the directory where Setup should place the compressed backup files.

Parameter

Uninstall

Values

0 = Do not allow user to specify Uninstall options, and do not create backup files for uninstalling Windows 95
1 = Show Uninstall options for user to choose
5 = Do not show Uninstall options, but automatically create backup files for uninstalling Windows 95

Default

1

Verify

This parameter specifies whether to run Windows 95 Setup in Verify mode. This option is provided principally for use by OEMs. Most users have no reason to include this entry in a setup script.

Parameter

Verify

Values

0 = Do a full installation
1 = Run in Verify mode

Default

0

Version Checking

This parameter defines whether Windows 95 Setup will overwrite existing files automatically, even if the date of the local copy is later than the date for the file in the distribution source.

Parameter

VRC

Values

0 = Prompt user to confirm before overwriting more recent files
1 = Overwrite all without prompting for confirmation

Default

0

[System]

This section sets parameters for modifying the system settings.

Tip The correct entries for MSBATCH.INF can be copied from similarly named entries in SETUPLOG.TXT for a computer on which Windows 95 has been installed with devices identical to those that you want to install from a setup script.

The following entries are based on INF section names:

  • Locale= INF_section_name in LOCALE.INF (see also Chapter 34, "International Windows 95")

  • Machine= INF_section_name in MACHINE.INF

  • PenWindows= INF_section_name in PENWIN.INF

  • Power= INF_section_name in MACHINE.INF or similar file (for advanced power management support)

  • Tablet= INF_section_name in PENDRV.INF or similar file

The following entries use INF descriptions. The choice must be in the list of compatible devices for that class.

  • Display= INF_description in MSDISP.INF or a similar file

    For example, from the description %SuperVGA.DriverDesc%=SVGA for Super VGA, the entry in MSBATCH.INF would be display=svga.

  • Keyboard= INF_description in KEYBOARD.INF

  • Monitor= INF_section_name in MONITOR.INF

  • Mouse= INF_section_name in MSMOUSE.INF or a similar INF file

  • SelectedKeyboard= INF_section_name in MULTILNG.INF (specifies the keyboard layout)

Display Characteristics

This parameter sets the initial display characteristics.

Parameter

DisplChar

Values

ColorDepth, x, y where:
ColorDepth=bits per pixel
x = horizontal resolution
y = vertical resolution

Default

4,640,480

MultiLanguage

This parameter sets the type of multilanguage support installed for Windows 95.

Parameter

MultiLanguage

Values

English = Installs support for English and Western European languages
Greek = Adds additional support for Greek
Cyrillic = Adds additional support for Cyrillic
CE = Adds additional support for Eastern European languages

Default

English

[NameAndOrg]

This section defines the name and organization for Windows 95 Setup, and specifies whether the user is to be shown the Name and Organization dialog box.

Name

This parameter specifies the full user name for this installation.

Parameter

Name

Values

String

Default

None

Organization

This parameter specifies the registered organization for this installation.

Parameter

Org

Values

String

Default

None

Display

This parameter specifies whether the Name and Organization dialog box appears during Windows 95 Setup.

Parameter

Display

Values

0 = Do not display name and organization
1 = Display name and organization

Default

1

[InstallLocationsMRU]

This section specifies the paths to add to the list of directories that the user can choose when Windows 95 Setup prompts for a path. For example, this section could appear as follows to specify local and network file locations:

[InstallLocationsMRU]
mru1=a:\mru2=c:\mru3=\\winserver\source

To force the path for files from which to copy, use CopyFile= and related statements in an [Install] section and specify the complete path for the component files.

[OptionalComponents]

This section contains the descriptions that appear in the Optional Components dialog box in Windows 95 Setup.

To create entries for this section, type the description enclosed in quotation marks. Each description is followed by a 1 (install) or 0 (do not install). The strings that specify the optional components to install are defined in INF files.

Another way to define entries for this section is to copy the [OptionalComponents] section in SETUPLOG.TXT from a computer that already has all the optional components installed that you want defined in the setup script. For an example, the entries to install Briefcase and Net Watcher are as follows:

[OptionalComponents]
"Briefcase"=1
"Net Watcher"=1

The following lists show the strings for the optional components defined in the Windows 95 standard INF files. Additional strings can be defined by other application developers.

Optional component strings

 

 

Accessibility Options
Accessories
Audio Compression
Backup
Blank Screen
Briefcase
Calculator
CD Player
Character Map
Clipboard Viewer
Communications
Curves and Colors
Defrag
Desktop Wallpaper
Dial-Up Networking
Direct Cable Connection
Disk compression tools
Disk Tools

Document Templates
Flying Through Space
Games
HyperTerminal
Jungle Sound Scheme
Media Player
Microsoft Exchange
Microsoft Fax
Microsoft Fax Services
Microsoft Fax Viewer
Microsoft Mail Services
Mouse Pointers
Multimedia
Musica Sound Scheme
Mystify Your Mind
Net Watcher
Object Packager

Online User's Guide
Paint
Phone Dialer
Quick View
Robotz Sound Scheme
Sample Sounds
Screen Savers
Scrolling Marquee
Sound Recorder
System Monitor
System Resource Meter
The Microsoft Network
Utopia Sound Scheme
Video Compression
Volume Control
Windows 95 Tour
WordPad

[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.

Parameter

Clients

Values

Comma-separated list of client device IDs (see the following table)

Default

Defaults in NETDEF.INF

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).

Device ID

Network

LANT5

Artisoft® LANtastic® version 5.x and 6.x

NETWARE3

Novell® NetWare® version 3.x

NETWARE4

Novell NetWare version 4.x

NWREDIR

Microsoft Client for NetWare Networks

PCNFS50

SunSoft® PC-NFS® version 5.x and greater

VINES552

Banyan® VINES® version 5.52 and greater

VREDIR

Client for Microsoft Networks

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.

Parameter

NetCards

Values

Comma-separated list of network adapter device IDs

Default

Results of detection

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.

Parameter

IgnoreDetectedNetCards

Values

0 = Do not ignore detected adapters
1 = Ignore the detected network adapters and use the values specified for NetCards=deviceID

Default

0

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.

Parameter

Protocols

Values

Comma-separated list of protocol device IDs, as described in the following table

Default

Defaults in NETDEF.INF

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

Device ID

Protocol

DEC40

DECnet™ version 4.1 Ethernet protocol

DEC40T

DECnet version 4.1 token ring protocol

DEC50

DECnet version 5.0a Ethernet protocol

DEC50T

DECnet version 5.0a token ring protocol

IPXODI

Novell-supplied IPXODI protocol

MSDLC

Microsoft DLC (real mode)

MSTCP

Microsoft TCP/IP

NDISBAN

Banyan VINES NDIS Ethernet protocol

NDTOKBAN

Banyan VINES NDIS token-ring protocol

NETBEUI

Microsoft NetBEUI

NFSLINK

Sun PC-NFS protocol

NWLINK

IPX/SPX-compatible protocol

NWNBLINK

NetBIOS support for IPX/SPX-compatible protocol

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.

Parameter

DefaultProtocol

Values

A protocol device ID as defined in protocol= and, optionally, a network adapter device ID, as defined in netcards=.

Default

0

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.

Parameter

RemoveBinding

Values

Device ID, device ID

Default

None

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.

Parameter

Services

Values

Comma-separated list of service device IDs, as described in the following table

Default

Windows 95 Setup defaults, depending on the value of InstallType

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

Device ID

Service

INF file

BKUPAGNT

Arcada® Backup Exec agent

BKUPAGNT.INF

CHEYAGNT

Cheyenne® ARCserve agent

CHEYENNE.INF

JADM

HP® Network Printer service for Microsoft

HPNETPRN.INF

JANW

HP Network Printer service for NetWare

HPNETPRN.INF

NMAGENT

Microsoft Network Monitor agent1

NMAGENT.INF

NWSERVER

File and Printer Sharing for NetWare Networks

NETSRVR.INF

PSERVER

Microsoft Print Service for NetWare Networks1

MSPSRV.INF

REMOTEREG

Microsoft Remote Registry service1

REGSRV.INF

SNMP

Microsoft SNMP agent1

SNMP.INF

VSERVER

File and Printer Sharing for Microsoft Networks

NETSRVR.INF

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.

Parameter

ComputerName

Values

String of up to 15 alphanumeric characters and no blank spaces. The name must be unique on the network and can contain the following special characters:
! @ # $ % ^ & ( ) - _ ' { } . ~

Default

Generated from the first eight characters of the user name

Description

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

Parameter

Description

Values

48 characters long, containing no commas

Default

User name from licensing information

Workgroup

This parameter sets the workgroup for the computer.

Parameter

Workgroup

Values

String of up to 15 alphanumeric characters and no blank spaces. The name must be unique on the network and can contain the following special characters:
! @ # $ % ^ & ( ) - _ ' { } . ~

System policy

Workgroup settings (under policies for Microsoft Client for Windows Networks)

Default

Workgroup previously specified; otherwise, a new name is generated from user licensing information by taking the first 15 characters of the organization name. For example, an organization name of "Microsoft Corporation" results in "MicrosoftCorpo" as the default workgroup.

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.

Parameter

HDBoot

Values

0 = Start from the server or floppy disk if WorkstationSetup=1
1 = Start from the hard disk and run from the network

Default

0

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

Windows 95 location

HDBoot

RPLSetup

Hard-disk boot, Windows 95 on a server

1

0

Floppy-disk boot, Windows 95 on a server

0

0

Remote boot, Windows 95 on a server

0

1

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.)

Parameter

RPLSetup

Values

0 = Don't do a remote-boot setup
1 = Do a remote-boot setup if WorkstationSetup=1

Default

0

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.

Parameter

WorkstationSetup

Values

0 = Allow a standard setup (local files)
1 = Allow a shared workstation setup (run from a server)

Default

0

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.

Parameter

DisplayWorkstationSetup

Values

0 = Do not display user interface
1 = Display user interface

Default

0

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.

Parameter

Security

Values

share = share-level security
domain = user-level security passing to a Windows NT domain
msserver = user-level security passing to a Windows NT server
nwserver = user-level security passing to a NetWare server

System policy

User-level Access Control settings (under policies for Access Control)

Default

share

Pass-Through Agent

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

Parameter

PassThroughAgent

Values

Server or domain name

System policy

User-level Access Control settings (under policies for Access Control)

Default

No value, or the value of Workgroup if Security=domain, Preferred Server if Security=nwserver, or none. The default is the value of PreferredServer if Security=nwserver; otherwise, there is no default.

User Interface Options for [Network] Parameters

Display

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

Parameter

Display

Values

0 = Do not display
1 = Display

Default

1

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.

Parameter

ValidateNetCardResources

Values

0 = Do not display a wizard page
1 = Display a wizard page to resolve resource conflicts

Default

1

[netcard_ID]

The actual name for this section is the identifier for the network adapter, as defined in the related INF file. This section sets parameters for a specific network adapter, as defined in the [netcard.NDI] sections of the network device INF files provided with Windows 95.

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.

All entries for a [netcard_ID] section depend on the specific adapter. The actual parameters and settings for a specific network adapter can be found in that adapter's INF file in the Windows INF directory.

To locate settings for a network adapter, check NET.INF for entries such as the following:

CardBrand=brand of network adapter
INFFile=file where these settings can be found

In the related INF file for the specific network adapter, search for the adapter's name. For example, you might find the following entry for an Intel EtherExpress 16 network adapter:

;*********************************************************************
; *PNP812D  Intel Etherexpress 16 or 16TP
;*********************************************************************

The information in the netcard.INF file is followed by the specific settings, using this format:

;netcard model name
[adapter.NDI]
actual settings for adapter 

For example, for the adapter in the previous example, the following entry appears in the NETEE16.INF file:

[*PNP812D.ndi]
AddReg=*pnp812d.ndi.reg,EXP16.ndi.reg

Based on the AddReg= entry in this statement, you need to search for the [*pnp812d.ndi.reg] or [EXP16.ndi.reg] sections in the INF file to find the parameters required for a particular adapter. For example, for the related Intel EtherExpress adapter, the following sections appear in NETEE16.INF:

[*PNP812D.ndi.reg]
.
.
.
HKR,NDI\params\Interrupt,resc,1,04,00,00,00
HKR,NDI\params\IOAddress,resc,1,02,00,00,0
HKR,NDI\params\DMAChannel,ParamDesc,,"DMA Channel"

These entries describe the parameters that can be specified for the adapter in a setup script. Further, in this same part of the netcard.INF file, the statements also indicate the kinds and ranges of values that can be specified for a particular parameter. For example, in NETEE16.INF, the following statements indicate that for DMAChannel= you must specify an integer in the range of 1 – 3, where the default value is 1:

HKR,NDI\params\DMAChannel,type,,int
HKR,NDI\params\DMAChannel,default,,1
HKR,NDI\params\DMAChannel,min,,1
HKR,NDI\params\DMAChannel,max,,3

The following entry in NETEE16.INF indicates that for Transceiver= you can specify the values external or onboard (based on the first string that appears after the enum item):

HKR,NDI\params\Transceiver,default,,onboard
HKR,NDI\params\Transceiver,type,,enum
HKR,NDI\params\Transceiver,enum,external,,external
HKR,NDI\params\Transceiver,enum,onboard,,onboard

Based on the previous examples, the following shows an example of the [netcard] section you would add to MSBATCH.INF to set parameters for an Intel EtherExpress 16 or 16TP network adapter:

[*PNP812D]
Interrupt=
IOAddress=
DMAChannel=2
Transceiver=external

Notice that you only need to set values for the parameters where you do not want to use the defaults. For a list of possible parameters for some common network adapters, see "Windows 95 Network Adapter INF Summary" later in this appendix.

[MSTCP]

This section sets parameters for Microsoft TCP/IP. For more information about Chapter 12, "Network Technical Discussion."

DHCP

This parameter specifies whether TCP/IP is configured to use DHCP for dynamic TCP/IP configuration.

Parameter

DHCP

Values

0 = Don't enable DHCP
1 = Enable DHCP

Default

1

DNS

This parameter enables DNS name resolution. You must also set DNS=1 if you plan to use LMHOSTS for name resolution.

Parameter

DNS

Values

0 = Disable DNS
1 = Enable DNS

Default

0

DNS Servers

This parameter is a list of the DNS servers to use in the order to try them.

Parameter

DNSServers

Values

Comma-separated list of DNS server names

Default

None

Domain

This parameter sets the DNS domain that this computer is in.

Parameter

Domain

Values

String

Default

None

Domain Order

This parameter sets a list of DNS domains for host name resolution in the order to try them.

Parameter

DomainOrder

Values

Comma-separated list of DNS domains

Default

None

Gateways

This parameter lists the IP gateways (sometimes called IP routers) in the order they are to be used.

Parameter

Gateways

Values

Comma-separated list of IP addresses

Default

None

Hostname

This parameter sets the DNS hostname for this computer (usually the same value as ComputerName).

Parameter

Hostname

Values

String

Default

None

IP Address

This parameter sets the computer's IP address if DHCP is not enabled.

Parameter

IPAddress

Values

Internetwork Protocol (IP) address (###.###.###.###)

Default

None

LMHOST File Path

This parameter sets the path and filename of the LMHOST file.

Parameter

LMHOSTPath

Values

Path

Default

None

Primary WINS Server

This parameter sets the primary WINS name server.

Parameter

PrimaryWINS

Values

IP address (###.###.###.###)

Default

None

Secondary WINS Server

This parameter sets the secondary WINS name server.

Parameter

SecondaryWINS

Values

IP address (###.###.###.###)

Default

None

Scope ID

This parameter sets the scope ID.

Parameter

ScopeID

Values

String

Default

None

Subnet Mask

This parameter sets the IP subnet mask for TCP/IP if DHCP is not enabled.

Parameter

IPMask

Values

IP address (###.###.###.###)

Default

None

WINS

This parameter enables WINS for NetBIOS computer name resolution.

Parameter

WINS

Values

0 = Disable WINS
1 = Enable WINS resolution
DHCP = Enable WINS but get parameters from DHCP server

Default

1

[NWLink]

The parameters in this section specify settings for the IPX/SPX-compatible protocol and are valid only if protocols=nwlink is also specified in the setup script. For more information about these parameters as defined using the Network option in Control Panel, see Chapter 12, "Network Technical Discussion."

Frame Type

This parameter specifies the default frame type for IPX.

Parameter

Frame_Type

 

Values

0 = 802.3
1 = 802.2
2 = Ethernet II

4=Auto
5=Token ring
6=Token ring SNAP

Default

4

 

NetBIOS

This parameter specifies whether NetBIOS support for IPX/SPX should be installed.

Parameter

NetBIOS

Values

0 = Don't install NWNBLINK
1 = Install NWNBLINK

Default

0

[NWRedir]

For more information about these values for Client for NetWare Networks as specified using the Network option in Control Panel, see Chapter 9, "Windows 95 on NetWare Networks."

First Network Drive

This parameter specifies the first network drive to which to attach in login scripts for Client for NetWare Networks. This parameter overrides the equivalent setting in NET.CFG.

Parameter

FirstNetDrive

Values

Drive letter ("A" or "A:" are equivalent)

Default

F:

Preferred Server

This parameter specifies the NetWare preferred server. This parameter does not override the equivalent setting in NET.CFG.

Parameter

PreferredServer

Values

String

System policy

Preferred Server settings (under policies for Microsoft Client for NetWare Networks)

Default

None

Process Login Script

This parameter specifies whether login script processing is enabled when running Microsoft Client for NetWare Networks.

Parameter

ProcessLoginScript

Values

0 = Disable login script processing
1 = Enable login script processing

Default

1

Search Mode

This parameter specifies the NetWare search mode. The values correspond exactly to the values specified in NET.CFG for Novell NetWare.

Parameter

SearchMode

Values

0 – 7

System policy

Search Mode settings (under policies for Microsoft Client for NetWare Networks)

Default

0

[NWServer]

For more information about these values for File and Printer Sharing for NetWare Networks as specified using the Network option in Control Panel, see Chapter 11, "Logon, Browsing, and Resource Sharing."

Browse Master

This parameter specifies whether a computer configured with File and Printer Sharing for NetWare Networks can be elected browse master.

Parameter

BrowseMaster

Values

0 = This computer cannot be a browse master
1 = This computer can be a browse master
2 = This computer is the preferred browse master

Default

1

SAP Browsing

This parameter specifies whether a computer configured with File and Printer Sharing for NetWare Networks uses Server Advertising Protocol (SAP) browsing. Enabling SAP browsing allows a computer with File and Printer Sharing for NetWare Networks to be seen by any NetWare client, but the computer does not appear in a workgroup in the Network Neighborhood.

Parameter

Use_SAP

Values

0 = Disable SAP browsing (use workgroup style browsing)
1 = Use SAP style browsing

Default

0

[VRedir]

For more information about these values for Client for Microsoft Networks as specified using the Network option in Control Panel, see Chapter 8, "Windows 95 on Microsoft Networks."

Validated Logon

This parameter specifies whether logons are validated on a Windows NT domain. If you set this value to 1, be sure to specify a value for LogonDomain.

Parameter

ValidatedLogon

Values

0 = Don't validate logons
1 = Validate logon

Default

0

Logon Domain

This parameter specifies the Windows NT domain to use for logon validation. It can be set even if ValidatedLogon=0. If ValidatedLogon=1, you must set a correct value for LogonDomain to ensure that Windows 95 Setup has access to any required files on a protected network resource, and to ensure that the user can log on successfully when installation is completed.

Parameter

LogonDomain

Values

String

System policy

Log on to Windows NT settings (under policies for Microsoft Client for Windows Networks)

Default

value of Workgroup in [network]

[VServer]

For more information about these values for File and Printer Sharing for Microsoft Networks as specified using the Network option in Control Panel, see Chapter 11, "Logon, Browsing, and Resource Sharing."

Announce

This parameter specifies whether the computer configured with File and Printer Sharing for Microsoft Networks announces its presence to LAN Manager computers on the network. Setting this value to 1 increases network traffic but makes browsing faster.

Parameter

LMAnnounce

Values

0 = Don't announce VSERVER to the network
1 = Announce VSERVER to network

Default

1

Browse Master

This parameter specifies how the computer configured with File and Printer Sharing for Microsoft Networks behaves in a browse master election.

Parameter

MaintainServerList

Values

0 = Disabled (this computer cannot be a browse master)
1 = Enabled (this computer is the browse master)
2 = Auto (the computer can be a browse master if required)

Default

2

[Printers]

This section is used to install one or more printers during Setup by specifying a user-defined name for identifying the printer, the model name, and the printer port. Each printer to be installed has a separate entry in this section using the following syntax:

PrinterName = DriverModel , Port

The following restrictions apply:

  • The length of the friendly name for the printer name cannot exceed 32 bytes (31 characters plus a NULL character). If the name specified in the custom setup script is too long, Setup will truncate it to fit the requirement.

  • The model name must be recognized by Windows 95. You can see the list of supported printer models in the Add Printers wizard or in the printer INF files.

  • No commas or quotation marks can be used in any string.

Note: If the setup script contains a [Printers] section with no entries, the user will not be asked to select a printer the first time that Windows 95 runs.

Friendly Name

This parameter specifies the friendly name, model, and port for a printer to be installed. The printer's friendly name is the name that appears in the Printers folder. The model name must be the exact name of a printer driver that is supported under Windows 95; otherwise, Setup skips this entire section.

Parameter

PrinterName= any string that does not contain these characters:
\ , ; =

Values

DriverModel = The exact driver name for any printer model supported under Windows 95
Port = The port that this printer is attached to (such as LPT1) or a UNC path name to a network print queue

Default

None

The following example installs a local printer and a network printer:

[Printers]
"My BJC600"="Canon Bubble-Jet BJC-600",LPT1
"IIIsi Next Door"="HP Laserjet IIIsi",\\Server_1\PrtShr_1

[Strings]

The [Strings] section defines one or more string keys that Setup expands to the defined string and uses it for further processing. In other sections, a strings key can be used by enclosing it in percent signs (%).

Parameter

string_key = value

Values

string_key = A unique name made up of letters and digits.
value = Letters, digits, or other printable characters. It should be enclosed in quotation marks if the corresponding string key is used in an entry that requires double quotation marks.

The following shows three examples of strings keys:

[Strings]
MSFT="Microsoft"
M1="APEX DRIVERS"
DevDesc1=APEX DRIVERS SCSI II Host Adapter

[Install]

The [Install] section sets parameters for copying additional files as part of Windows 95 installation. The format for this section is identical to the format for the [Install] section in general INF files, as defined in Appendix C, "Windows 95 INF Files."

The following sections provide these examples for using the [Install] section for custom installations:

  • Installing custom bitmaps and shortcuts

  • Enabling user profiles and remote administration

  • Disabling TSRs and replacing protocols

[Install] Example: Copying Custom Files

This section describes MSBATCH.INF entries for copying custom files while installing Windows 95. In the following example, custom files are copied for a bitmap file containing a corporate logo plus a shortcut to be placed in the Network Neighborhood. These custom files must be created by the administrator and placed with the Windows 95 source files on the network.

[install]
CopyFiles=newfiles.Copy
[NEWFILES.Copy]   
my_corp.bmp      ; bitmap file
my_link.lnk      ; file that contains the shortcut
[DestinationDirs]
newfiles.copy=25   ; shared Windows directory

The statement in [DestinationDirs] specifies where files are to be copied. Common values include the following for shared installations:

  • 10 = machine directory

  • 11 = Windows SYSTEM directory

  • 25 = Windows directory

Notice that the most flexible means of providing custom links for multiple users is to use system policies. For information about using system policies to create a custom Network Neighborhood or a custom desktop, see Chapter 15, "User Profiles and System Policies."

[Install] Example: Enabling User Profiles and Remote Administration

If you plan to take advantage of user profiles and to allow administration of remote computers, you can enable these capabilities using setup scripts. The following entries are required in MSBATCH.INF to enable these features.

[Install]
AddReg=User.Profiles,Remote.Admin
[User.Profiles]
HKLM,"Network\Logon","UserProfiles",1,1
[Remote.Admin]
HKLM,"Security\Access\Admin\Remote",%Server_Domain_Username%,1,ff,00
[Network]
Security=domain_or_server   ;enables user-level security
PassThroughAgent=provider_name
services=remotereg   ;installs the Microsoft Remote Registry agent
[strings]
; specifies the server containing the group or individual account 
; to be allowed remote administration capabilities 
Server_Domain_Username = "server_or_domain\account"

To define the custom values required for enabling remote administration

  1. To enable user-level security, set the appropriate values in the [Network] section for Security= and PassThroughAgent=.

    For example, on a NetWare network, if the security provider is a server named NWSVR1:

    Security=server
     PassThroughAgent=NWSVR1
    

    On a Windows NT network, if the security provider is a domain named NTDOM1:

    Security=Domain
     PassThroughAgent=NTDOM1
    
  2. In the [Strings] key, define the value for %server_domain_username% to specify the location for the list of user accounts, plus the names of accounts for users who will be allowed remote administration capabilities for this particular computer.

    For example, for a NetWare network, the following specifies the server containing the group or individual account, plus the account name to be given remote administration capabilities:

    Server_Domain_Username = "NWSVR\HELPDESK"
    

    For a Microsoft NT network, the following specifies the domain containing the account, plus the account name to be given remote administration capabilities:

    Server_Domain_Username = "NTDOM1\ADMIN"
    

Important: You must also make sure that the related files supporting Microsoft Remote Registry services are installed with the Windows 95 source files. To do this, use INF Installer, as described in Chapter 5, "Custom, Automated, and Push Installations."

When you enable remote administration in this way, Setup automatically adds the appropriate Administrators account (including Supervisor and Domain Administrators under Windows NT) to the list of persons or groups allowed to administer the computer remotely, and sets the permissions required for remote administration.

Enabling user profiles in a setup script is the equivalent of selecting the items in the Passwords option in Control Panel named Users Can Customize Their Preferences And Desktop Settings and Include Desktop Icons And Network Neighborhood Settings.

To enable group policies

  • If you want to enable group policies for both the Client for Microsoft Networks and Client for NetWare networks, add the following entries to MSBATCH.INF:

    [Install]
     Addreg=User.Profiles.Reg, Group.Policies.Reg
     Copyfiles=Group.Policies.Copy
     [User.Profiles.Reg]
     HKLM,Network\Logon,UserProfiles,1,1
     [Group.Policies.Reg]
     HKLM,Network\Logon,PolicyHandler,,"GROUPPOL.DLL,ProcessPolicies"
     HKLM,System\CurrentControlSet\Services\MSNP32\NetworkProvider,
        GroupFcn,,"GROUPPOL.DLL,NTGetUserGroups"
     HKLM,System\CurrentControlSet\Services\NWNP32\NetworkProvider,
        GroupFcn,,"GROUPPOL.DLL,NWGetUserGroups"
     [Group.Policies.Copy]
     grouppol.dll
     [DestinationDirs]
     Group.Policies.Copy = 11
    

For information about user profiles and group policies, see Chapter 15, "User Profiles and System Policies." For information about remote administration of a computer's Registry, see Chapter 16, "Remote Administration."

[Install] Example: Replacing Configuration Entries

This section presents some sample entries for replacing entries in configuration files as part of Windows 95 Setup.

Depending on the common network configuration at your site, you may determine that you need to remove a line from one or more configuration files as a global procedure before starting Windows 95 Setup. For example, you may want to use a protected-mode protocol such as Microsoft TCP/IP instead of the real-mode version of TCP/IP currently being using on the target computers. The following kinds of entries can be used to make these changes during the installation process.

Note: If you want to remove TSRs when installing Windows 95 on a NetWare network, you should modify the NETDET.INI file rather than making modifications using MSBATCH.INF. For information, see Chapter 9, "Windows 95 on NetWare Networks."

[Install]
UpdateInis=update_prot.Ini   
UpdateCfgSys=Update_config.sys   
UpdateAutoBat=Update_autoexec.bat
[Update_prot.Ini]
system.ini,386enh,"device=mytcp.386"
[Update_config.sys]
[Update_autoexec.bat]

MSBATCH.INF Sample File

This section shows a sample setup script.

[Setup]
Express=0        ; allows user input
InstallType=1    ; Typical Setup
EBD=1            ; create startup disk
InstallDir=C:\WINDOWS
Verify=0
PenWinWarning=1
ProductID=999999999   
[NameAndOrg]
Name="User One"
Org="Your Company Name"
Display=1       ; User Information dialog box is displayed
[OptionalComponents]
"Accessories"=1
"Communications"=1
"Disk Tools"=1
"Multimedia"=1
"Screen Savers"=0
"Disk compression tools"=1
"Paint"=1
"HyperTerminal"=1
"Defrag"=1
"Blank Screen"=1
"Scrolling Marquee"=1
"Calculator"=1
"Object Packager"=1
"Backup"=0
"Phone Dialer"=1
"Clipboard Viewer"=0
"Microsoft Fax"=0
"Microsoft Fax Services"=0
"Microsoft Fax Viewer"=0
"Accessibility Options"=0
"The Microsoft Network"=0
"Audio Compression"=0
"Video Compression"=1
"Sound Recorder"=0
"Volume Control"=0
"Media Player"=1
"Microsoft Exchange"=0
"Microsoft Mail Services"=0
"Briefcase"=0
"Document Templates"=1
"WordPad"=1
"Dial-Up Networking"=0
"Direct Cable Connection"=0
"Mouse Pointers"=0
"Windows 95 Tour"=0
"Online User's Guide"=0
"Desktop Wallpaper"=0
"System Monitor"=0
"Net Watcher"=0
"Character Map"=0
"Curves and Colors"=0
"Mystify Your Mind"=0
"Flying Through Space"=0
"Games"=0
"Quick View"=0
"Sample Sounds"=0
"Musica Sound Scheme"=0
"Jungle Sound Scheme"=0
"Robotz Sound Scheme"=0
"Utopia Sound Scheme"=0
"CD Player"=0
[System]
"Display"="Tseng Lans ET4000"
"Keyboard"="Standard 101/102-Key or Microsoft Natural Keyboard"
"Machine"="MS_CHICAGO"
"Monitor"="NEC MultiSync 2A"
"Mouse"="Standard Serial Mouse"
"Power"="No APM"
"Locale"="L0409"
"UI Choice"="Win95UI"
"Multilanguage"="English"
[InstallLocationsMRU]
MRU1=C:\WINDOWS
MRU2=C:\User
MRU3=\\win_svr\source files\home_dir
[Network]
Display=0             ; Network Options do not appear in Setup 
ComputerName=W95_1
Workgroup=test_group
Description="This is a lab test computer"
Clients=vredir,nwredir
Security=Domain
PassThroughAgent=Test_domain
WorkstationSetup=0    ; not a shared installation of Windows 95
HDBoot=1   
[VREDIR]      
ValidatedLogon=   1
LogonDomain=test_domain

Windows 95 Network Adapter INF Summary

This section presents details about the settings for common network adapters, as defined in the [netcard.NDI] sections of the INF files provided with Windows 95. Other adapters are also listed; their settings can be found in the appropriate file in the Windows INF directory. The NET.INF file contains the master information for detecting and configuring network adapters. The specific INF files for network adapters include the following:

net3com.inf
netamd.inf
netflex.inf
netcable.inf
netdec.inf
netee16.inf

netcpq.inf
netgen.inf
nethp.inf
netibm.inf
netmadge.inf
netncr.inf

netnice.inf
netnovel.inf
netoli.inf
netppp.inf
netprot.inf
netracal.inf

netsmc.inf
netsmctr.inf
nettcc.inf
nettulip.inf
netub.inf
netxir.inf

For information about how to find entries for a particular network adapter in an INF file, see "[netcard_ID]" earlier in this appendix.

3COM

Cardbrand=3COM

INFFile=NET3COM.INF

[*PNP80F3]
Interrupt=
IOAddress=
DMAChannel=
MaxTransmits=
DataTransfer=
XmitBufs=
Transceiver=

The following adapters also have settings in the file NEC3COM.INF:

3Com EtherLink Plus®
3Com EtherLink III®
NCR Token-Ring 4 Mbs ISA
NCR Token-Ring 16/4 Mbs ISA

NCR StarCard
NCR® WaveLAN AT
TokenLink

Digital Equipment Corporation

Cardbrand=Digital Equipment Corp.

INFFile= NETDEC.INF

;DEC DE201 Etherworks Turbo TP
[*PNP80EB]
Interrupt=
IOAddress=
RamAddress=
MaxMulticasts=
Maxtransmits=
AdapterName=

The following adapters also have settings in the file NETDEC.INF:

DEC (DE211) Etherworks® MC/TP
DEC (DE212) Etherworks MC/TP_BNC
DEC (DE100) Etherworks LC
DEC (DE200) Etherworks Turbo
DEC (DE101) Etherworks LC/TP
DEC (DE202) Etherworks Turbo/TP_BNC

DEC (DE102) Etherworks LC/TP_BNC
DEC EE101 (Built-In)
DECpc 433 WS (Built-In)
DEC Ethernet (All Types)
DEC (DE210) Etherworks MC

IBM

Cardbrand=IBM

INFFile= NETIBM.INF

;IBM Token Ring
[*PNP80C9]
MaxTransmits=
Primary
Alternate=
RecvBufs=
XmitBufs=
MaxPacketSize=
ProductID=
NetworkAddress=
Iobase=
RecvBufSize=
XmitBufSize=

The following adapters also have settings in the file NETIBM.INF:

IBM Token Ring 4/16Mbs
IBM Token Ring II/Short
IBM Token Ring (All Types)

 

Intel

Cardbrand=Intel

INFFile= NETEE16.INF

;Intel Etherexpress 16 or 16TP
[*PNP812]
IOBaseAddress=
IRQ=
IOAddress=
Transceiver=
IOChrdy=
IOChannelReady=

The following adapters also have settings in the file NETEE16.INF:

Intel EtherExpress PRO
Generic 595
Intel EtherExpress 16 (MCA)

 

MADGE

Cardbrand=MADGE

INFFile= NETMADGE.INF

;Madge Networks Smart 16/4 PC Ringnode
[*PNP81D7]
RxTxSlots=
NetworkAddress=
MaxFrameSize=
RxBufferSize=
TxBufferSize=
MaxTransmits=
Watchdog=
CopyAllData=
AutoOpen=
OpenOptions=
NoMmio= 
PromiscuousModeX=
[MadgeISA]
IrqNumber=
IOAddress=
MemBase=
DMAChannel=

The following adapters also have settings in the file NETMADGE.INF:

Madge Networks Smart 16/4 Ringnode (All ISA Types)
Madge Networks Smart 16/4 AT/P Ringnode
Madge Networks Smart 16/4 AT Ringnode
Madge Networks Smart 16/4 ISA Client Plus Ringnode
Madge Networks Smart 16 Ringnode

Novell

Cardbrand=Novell

INFFile= NETNOVEL.INF

[ne2000]
InterruptNumber=
IOBaseAddress=
Interrupt=
IOBase=

The following adapters also have settings in the file NETNOVELL.INF:

Artisoft AE-1
Artisoft AE-2 or AE-3
Ethernode 16-AT3
National Semiconductor Ethernode *16AT

National Semiconductor AT/LANTIC NE1000 Compatible
Novell Ne2000 Plus
Zenith Data Systems NE2000 Compatible

Proteon

Cardbrand=Proteon

INFFile=NETPROT.INF

;Proteon Token Ring (P1392)
[*pnp81eb]
IntLevel=
IOBase=
DMAChannel=
LinkSpeed=
CardSpeed=
Media=
CableType=
DMAClock=
SAEN=
MaxTransmits=
NetworkAddress=

The following adapters also have settings in the file NETPROT.INF:

Proteon ISA Token Ring (1340)
Proteon ISA Token Ring (1342)
Proteon ISA Token Ring (1346)

Proteon ISA Token Ring (1347)
Proteon Token Ring (P1392+)
Proteon Token Ring (P1390)

Racal

Cardbrand=Racal

INFFile= NETRACAL.INF

; Racal NI6510
[*pnp8113]
IOBase=
MaxReceives=
MaxTransmits=
MaxMulticasts=

The Racal NI5210/8 or NI5210/16 adapter also has settings in the file NETRACAL.INF.

SMC

Cardbrand=SMC

INFFile= NETSMC.INF

;SMC9000
[*Smc9000]
Interrupt=
Port_Num=
Xt_Type=
Micro_Channel=

The following adapters also have settings in the file NETSMC.INF:

ArcNet Compatible
Pure Data PDI508+ (ArcNet)
Pure Data PDI516+ (ArcNet)
SMC® ArcNet PC600W,PC650W
SMC ArcNet PC120,PC220,PC260
SMC ArcNet PS110,PS210
SMC ArcNet PC270/E
SMC ArcNet PC130/E
SMC EtherCard™ PLUS 16 With Boot
ROM Socket (WD/8013EBT)
SMC ArcNetPC
SMC ArcNet PC100,PC200
SMC ArcNet PC110,PC210,PC250
SMC EtherCard PLUS TP (WD/8003WT)
SMC EtherCard PLUS With Boot
ROM Socket (WD/8003EBT)
SMC EtherCard PLUS (WD/8003E)
SMC StarCard PLUS With On Board Hub
(WD/8003SH)
SMC StarCard PLUS (WD/8003S)

SMC EtherCard (All Types except 8013/A)
SMC EtherCard PLUS 10T/A (MCA)
(WD 8003W/A)
SMC StarCard PLUS/A (MCA)
(WD 8003ST/A)
SMC EtherCard PLUS/A (MCA)
(WD 8003E/A or 8003ET/A)
SMC EtherCard PLUS With Boot
ROM Socket (WD/8003EB)
SMC EtherElite Ultra 16
SMC EtherElite Ultra 16 Tiger
SMC EtherCard PLUS Elite (WD/8003EP)
SMC EtherCard PLUS Elite 16
(WD/8013EP)
SMC EtherCard PLUS Elite 16T
(WD/8013W)
SMC EtherCard PLUS Elite 16 Combo
(WD/8013EW or 8013EWC)
SMC TokenCard Elite

Thomas-Conrad

Cardbrand=Thomas-Conrad

INFFile= NETTCC

;Thomas-Conrad (All Arcnet Types)
[*pnp8326]
Interrupt=
IOBase=
MemoryBase=
PacketSize=

The following adapters also have settings in the file NETTCC.INF:

TC6045
TC6145
TC6245
Thomas-Conrad TC6042

Thomas-Conrad TC6142
Thomas-Conrad TC6242
Thomas-Conrad TC4035
Thomas-Conrad TC4045

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft