Deploying Windows 98 Using Batch 98 and Infinst.exe

  • Article
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.
On This Page

The Msbatch.inf
Installing with Msbatch.inf
Creating the Msbatch.inf
Infinst.exe
Multiple Machine-Name Save
Msbatch.inf Issues
Appendix - Sections of Msbatch.inf

The Msbatch.inf

Msbatch.inf may be used to configure almost all portions of Windows 98 setup for use in corporate environments. Many portions of Windows 98 may be modified using the Msbatch.inf. The settings that can be modified may include network settings, installing protocols and services and installing optional components such as communications and disk tools. These settings help to standardize Windows 98 installation on multiple computers, as in corporate environments. Batch setup settings may also be used to restrict user choices during setup.

The following is a list of entries that are documented in the Windows 98 DDK that are common to Batch installs.

Type of INF File Section

Purpose

Type of INF File Section

Purpose

INF file header.

The standard header for all INF files.

Delete Registry sections

Deletes subkeys or value names from the registry.

ClassInstall section

Installs a new class for a device in the Class section of the registry on a Windows 98 machine.

 

 

Disk Names section

Identifies and names the disk(s) that are the source of files that are copied to the hard disk during installation. Also names the files that are on each of the installation disk(s).

Update Autoexec.bat and Config.sys sections

Manipulates lines in the Autoexec.bat and Config.sys files. Note: Some Windows 95 Config.sys settings do not work, such as addDevice Files, Stacks, and Buffers.

Install sections

Identifies the other sections in the INF file that describe the resource requirements of a device and which add entries to the registry, copy files, etc.

Ini File to Registry sections

Moves lines or sections from an INI file to the registry, creating or replacing an entry under a specific key in the registry.

CopyFiles sections

Names the files copied from the source disk(s) to the destination directories during device installation.

Update Ini File sections

Replaces, adds, and deletes entries in an INI file.

Rename Files sections

Names the files to be renamed when they are copied from the source disk(s) to the destination directories during device installation. Also gives the new filenames on the destination directories.

Update Ini Fields sections

Replaces, adds, and deletes fields in the value of a given entry in an INI file.

DelFiles sections

Names the files to be deleted from destination directories during device installation.

Strings section

Defines one or more names that represent a string of displayable characters.

Add Registry sections

Adds subkeys or value names to the registry, optionally setting values.

 

 

Note: The most commonly used entries are documented on Page 11, Common Msbatch.inf Issues.

Installing with Msbatch.inf

Windows 98 no longer uses either the Netsetup directory structure from Windows 95 did or Windows 95's Netsetup program. The network install is now accomplished by copying the contents of the Win98 directory from the Windows 98 CD to a share on a server.

Steps to install:

  1. Copy the Win98 folder to a share on a server

  2. Create the appropriate inf file(s).

  3. Place all infs in the setup directory or on network boot floppies.

  4. Run Setup on a test machine to make sure the inf does what is desired.

When running Windows 98 setup with an inf file, by default the warning to remove floppy disks before Setup restarts the computer does not appear. Be sure all floppy disks are removed from drives before starting setup or after the copy files process has started.

By default, Setup.exe searches for the file Msbatch.inf and uses the settings it contains. To use another inf, put the path to the file after Setup.exe on the command line.

Setup.exe switches

Below is an example of a command line argument used to run setup.

Setup.exe <path to file>\<filename.inf> /is /iq /iv

Note: /IW is not necessary anymore because the ShowEula= setting in the [Setup] section of a msbatch.inf file disables the Microsoft Software License Terms.

When installing Windows 98 with a Msbatch.inf script there are many cases where input is required, one of which is Scandisk. In order to get past these screens without input, the /is and /iq Setup switches may be used. Batch installs cannot suppress some other Windows 98 setup dialog or message boxes, (for example, not enough disk space).

/IS – Tell setup to skip running ScanDisk. It is recommended that disk maintenance software is run prior to Windows 98 setup. (Warning running setup without conducting a Scandisk first may be potentially dangerous since there will be no disk integrity check.)

/IQ – Skip check for cross-linked files

/IV – Do not display the setup billboards. While the billboards do not require any input, they do take time to load and may make setup take longer.

Some setup switches that are valid in Windows 95 may not be longer available.

For more information on other Setup switches please refer to the Windows 98 resource kit, Chapter 2, "Setting Up Windows 98".

Creating the Msbatch.inf

While creating and modifying the Msbatch.inf file may be done manually, and is some times necessary, Microsoft has supplied two tools designed to simplify the process -- Microsoft Batch 98 and INF Installer (Infinst.exe).

Microsoft Batch 98

Batch.exe is a tool that makes it easy to create Msbatch.inf files to automate the Windows 98 Setup process. To install Microsoft Batch 98, run Setup.exe from the Windows 98 CD \tools\reskit\batch directory. Each of the System Settings configures a different area within the inf file.

Cc750055.batch981(en-us,TechNet.10).gif

Batch.exe Options

Batch 98 has several options to configure an inf file for setup: Gather Now, General Setup, Network Options, Optional Components, Internet Explorer Options, and Advanced Options.

Gather now

If run from a Windows 98 machine, Batch 98 may scan the registry for known settings to automatically create a useable Msbatch.inf file. Click the button "Gather now," and batch setup scans for settings in the following areas :

 

CHECK

All known Microsoft 32-bit networking clients and their settings
 

CHECK

All known Microsoft 32-bit networking services and their settings
 

CHECK

All known Microsoft 32-bit networking protocols and their settings
 

CHECK

Currently installed printers
 

CHECK

Current time zone
 

CHECK

User-level security settings
 

CHECK

Current Windows directory
 

CHECK

Current user and machine name and description information
 

CHECK

MRU (Most Recently Used) settings

Note: By default, the "Install Printer During Setup" checkbox in General Setup Options is unchecked. This box must be checked to actually add printers to a Batch Install.

Some things that Batch.exe cannot determine :

X

Un-install options

X

Some installation options pertaining to batch setup only (for instance, the 'no to all' option)

X

Net card settings

General Setup Options

Options pertaining directly to Windows 98 install are set in General Setup Options.

The following items are configured in this option:

  • What directory to install to

  • Product ID

  • Setup user profiles

  • Uninstall Settings

  • Printers

  • User Information, such as computer name, workgroup, and company name

  • Emergency Boot disk creation

  • Regional Settings

  • Auto Answer 'Yes' to the EULA

    Removal of Default Desktop Icons

    • My Documents

    • Network neighborhood

    • Internet Explore and OE

    • Recycle Bin

    • Setup MSN

    • Online services folder

  • Do not show Windows 98 Welcome screen

  • Do not show Windows registration wizard

Optional Components

Optional Components selects which optional components to install— for example, Accessories, Internet Explorer additional components, Screen Savers, etc.

Internet Eplorer

Internet Explorer Options is where Internet Explorer is configured, setting the following options:

  • Quick Launch Toolbar

  • Channel Bar Enabled/Disabled

    Default Display options

    • Use Classic Desktop or Active Desktop

    • Browse folders in new Windows or Same

    • Single click or double click to launch

  • Setup Internet Explorer Homepage and Support Online URL

  • Security

  • Proxy server Settings

Note: This tab can not set up remote dial options for Internet Explorer because the modem needs to be installed before dial-up networking is configured.

Advanced

Advanced Options permits adding a .reg file that was created by exporting the Registry, setting up system policies for download, and enabling/disabling software and hardware updates via the browser.

Network Option

Network Options is where Protocols, Clients, Services and Access Control are installed and configured. Using the Additional Clients tab, additional network options may be set. Here is a list of common IDs.

Device ID

Description

Novell32*

Novell 32 Bit Client

Vinesifs*

Banyan VINES Client

Ndiswan

Protocol wrapper for virtual private networking adapter

LANEP

ATM LAN Emulation Client (Added as Protocol)

Bancom*

Banyan VINES protocol for Windows

Novellipx32*

Novell IPX 32 protocol for their client

Remotereg*

Microsoft Remote Registry service

Snmp*

Microsoft Simple Network Management Protocol (SNMP) agent

* These IDs are not included within the list of default Windows 98 services and protocols. INFInst is needed to install them.

To find an unknown Device ID, check in the appropriate INF file for the item being installed. Check the [strings] section for the correct 'friendly name', which in the example below is the "ATM LAN Emulation Client" which is in the Lanep.inf file. Then do a search for the DeviceDesc (in this case LANEP.DeviceDesc). A manufacturer section that contains the ID should be found. The Device ID is the last word on the line with the description, in this example LANEP.

[MS]
%LANEP.DeviceDesc%=   LANEP.ndi, LANEP
[strings]
LANEP.DeviceDesc="ATM LAN Emulation Client"

Note: Make sure to start the search for DeviceDesc at the top of the inf file, the [strings] section is typically towards the end and it is common to start the search from the current location in the file.

Infinst.exe

While the Batch.exe utility creates Msbatch.inf files, the Windows 98 Inf Installer (Infinst) tool reads any compatible Windows 98 standard inf file and incorporates it into the setup folder. It does this by adding entries to the Custom.inf file, modifying any existing inf files for Plug and Play information and copying drivers specified in the inf file. Infinst is located in the \Tools\Reskit\Infinst directory of the Windows 98 CD.

Infinst permits the addition of new software components or hardware drivers to the Windows 98 Setup program at a setup installation point. When Windows 98 is installed, Setup automatically detects all hardware and installs the necessary drivers by checking the Windows INF directory for the correct file. However, some hardware drivers are not included in Windows 98 or need to be updated to include new files. With Infinst.exe, the new hardware infs and the associated drivers may be added to the Windows 98 setup installation point. When Windows 98 is installed from this installation point, the new drivers are installed as if they were part of the original Windows 98 Setup program.

Caution: Adding an Inf with the same name as one already included with Windows 98 or previously added with Infinst.exe overwrites the original inf file in its entirety. So if there are options (hardware, services, etc) that are in the original inf but not in the new inf the original options will be lost.

Examples of using INF Installer

The following is an example of adding the Microsoft Remote Registry service and an imaginary network adapter driver from the imaginary company "MyNicCompany" known as MyFastNic.

The Remote Registry service may be found on the Windows 98 CD in the Tools\Reskit\Netadmin\Remotreg\ folder and the inf we are looking for is Regsrv.inf. The inf file obtained from MyNicCompany is MyFastNic.inf, and it, along with its list of drivers, are located in c:\Mynic.

Launch Infinst.exe and type the path to the updated inf file in the 'Inf to add to Windows 98 setup' box. Also type the path to the Windows 98 setup files in the 'Windows 98 Setup.exe" box. As shown in the diagram below, Infinst.exe looks for Setup.exe to determine the proper location. When the correct settings are listed in the dialog box, click 'Add Inf'. INF Installer processes the inf file and makes all the appropriate modifications. Infinst.exe saves a log file in the Windows 98 setup folder called Infinst.log.

Cc750055.batch982(en-us,TechNet.10).gif

When installing the Microsoft Remote Registry Service, Infinst.exe first creates a default Custom.inf file in the directory listed as 'Windows 98 Setup.exe'. INF Installer then creates a Wininf directory in the same location, and copies all the default Windows 98 inf files into this Wininf directory. Infinst then searches the default Windows 98 inf files for a matching ID for the Microsoft Remote Registry Service. When Infinst finds no matches, it copies the Remote Registry inf file (Regsrv.inf) to the setup directory (not the Wininf directory) and copies the files specified in the CopyFiles section of Regsrv.inf to the same location. Infinst.exe then modifies Custom.inf to include the Regsrv.inf in Windows 98 setup and writes a log of its changes to the Infinst.log, also in the setup directory.

If an existing Windows 98 driver is found, the steps are slightly different. For the purpose of this example, assume that there is a driver for the MyFastNic card that shipped with Windows 98. When installing when there is already an inf for the device, Infinst still creates the default Custom.inf file and Wininf directory if they do not already exist and copies the default inf files to the Wininf directory. However, when it searches for a matching ID for the MyNicCompany card and finds a match, it copies the inf file with the matching ID to the setup folder and comments out any lines that are duplicated in the new inf file – see example below.

[MyNicCompany]

;Commented out by Infinst on 6/20/98 on behalf of MyFastNic.inf-> %PCI\VEN_ffff&DEV_ffff.DeviceDesc%
=PCIMYfast.ndi, PCI\VEN_ffff&DEV_ffff  ; My Fast Nic

Infinst then copies the new inf file to the setup folder and copies all files listed in the CopyFiles section of the new inf to the same location. It then updates the Custom.inf to include the new inf, and logs its changes to the Infinst.log file.

Custom.INF

The Custom.inf has three main sections. They are the [BaseWinOptions], [CUSTOM_PRECOPY] and [load_inf] sections. [CUSTOM_PRECOPY] tells setup what files to copy over to the Wininst0.400 directory during Windows 98 setup. [load_inf] is used for infs that need to be loaded during setup, such as network cards and services, and CD-ROM drivers. Microsoft recommends against using [load_inf] for devices that may be detected or enumerated after setup, such as video cards and modems. [BaseWinOptions] is the section for files that are to be copied over to the <Windir>\INF directory.

Note: <Windir> stands for the name of the Windows directory, typically C:\Windows.

Example of Custom.inf:

[CUSTOM_PRECOPY]
CopyFiles=infinst.temp.dir.files

 

[infinst.temp.dir.files]
regsrv.inf
MyFastNic.inf

;infinst 6/20/98 (regsrv.inf)
;infinst 6/20/98 (MyFastNic.inf)

[BaseWinOptions]
infinst.install

 

[infinst.install]
CopyFiles=infinst.inf.files

 

[infinst.inf.files]
regsrv.inf
MyFastNic.inf

;infinst 6/20/98 (regsrv.inf)
;infinst 6/20/98 (MyFastNic.inf)

[Strings]

 

[load_inf]
regsrv.inf
MyFastNic.inf

;infinst 6/20/98 (regsrv.inf)
;infinst 6/20/98 (regsrv.inf)
;infinst 6/20/98 (MyFastNic.inf)

Multiple Machine-Name Save

During a large rollout of Windows 98 each machine needs its own computer name and in cases where static IP addresses are in use, a unique IP address. This may become time-consuming to specify each user within General Setup Options\User Info and save each inf manually. However, with Batch 98, the "Multiple Machine-Name Save" option from the File menu may be used to create many custom inf files at once.

Cc750055.batch983(en-us,TechNet.10).gif

To begin, create a Machine Name file. This is merely a text file with each computer name entered on its own line, and terminated with a carriage return/line feed (press ENTER after typing each name). To include an IP address for a given computer, put a single comma after the computer name and then type the IP address. Subnet mask, and other IP options are not configurable here because they are not specific to just one machine. A single blank line signifies the end of the machine-name file. No error checking of these values is performed by the batch-mode save process. The "Save Files" button saves files with the file name Bstpxxxx.inf (where xxxx is the line number the machine name was entered on in the Machine Name file). On Microsoft networks, computer names may contain only alphanumeric characters and these characters:

! @$ % ^ ( ) { } _ ~

Note: some of these characters may cause problems with some programs. For example, the @ symbol causes problems with some MAPI applications so it is recommended to use just standard ASCII characters.

The following shows an example of a text file for multiple machine-name save:

Zarg!
P133_Mega_Machine, 128.2.3.4
KCF
Print_Server_1
Duke, 128.3.4.5
Scarlett
Rhett

Note: Another workaround is to leave the Computer name and workgroup name blank during the install and after setup is completed Windows 98 will instruct you to enter the name. However, this alternative does not provide a static IP address.

Msbatch.inf Issues

The Install section of an INF

  • Add STRING values

  • Add BINARY values

  • Add DWORD values

  • Delete a Registry value

  • Add/Delete Entry to Autoexec.bat

  • Copy Files

  • Update INI files

To add custom entries into the registry (like RunOnce), an [Install] section in the Msbatch.inf file needs to be created.

The [Install] section points to AddReg, CopyFile, UpdateINI, or any other sections that are needed to make specific customizations. The most common are the AddReg and CopyFiles sections, which are documented on the next two pages.

Note: Adding devices to the Config.sys is not currently possible.

The following is an example of the Install section of an Msbatch.ing

[Install]

;; Install section

AddReg=Update.REG

;; Modify Registry Values

UpdateAutoBat=UPD.Auto.Bat

;; Modify Autoexec.bat values

UpdateInis=UPD.Sys.ini

;; Modify the MSDOS.SYS

 

 

[Update.REG]

 

HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup,"Run the Mike Batch File",,"start c:\mike.bat"

 

 

 

 

 

[UPD.Auto.Bat]

 

CmdDelete=net

;;Deletes all net commands
;;i.e. net start, net init, ect

CmdAdd=echo, "Admin added this entry"

 

 

 

[UPD.Sys.ini]

 

%30%\msdos.sys,Options,,"BootKeys=0"

;;Adds BootKeys to the Msdos.sys

Adding a Registry entry

[AddReg] Section

RegRootKey, SubKey, Value-Name, Flag, Value

Examples:

  1. Add a String value to the Registry to the RunOnce key to launch a bat file

    HKLM,Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup,"Run the Mike Batch File",,"start c:\mike.bat"

  2. Add a DWORD value to the Registry

    HKLM,Software\Microsoft\Windows\CurrentVersion\Policies\Explorer,NoWindowsUpdate,0x10001,0

  3. Add a Binary value to the Registry

    HKLM,Software\Microsoft\Windows\CurrentVersion,RegDone,1,01,00,00,00

Here is a definition for each example above for each portion of the entry.

  • RegRootKey =

    HKCR – HKEY_CLASSES_ROOT

    HKCU – HKEY_CURRENT_USER

    HKLM – HKEY_LOCAL_MACHINE

    HKU – HKEY_USERS

    SubKey =

    • Software\Microsoft\Windows\CurrentVersion\RunOnce\Setup

    • Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

    • Software\Microsoft\Windows\CurrentVersion

      Identifies the subkey to set. Has the form key1\key2\key3....

    Value-Name =

    • "Run the Mike Batch File"

    • NoWindowsUpdate

    • RegDone

      Identifies the value name for the subkey. For string type, if the value-name parameter is left empty, the value of the subkey is set to the default value for that registry entry.

    Flag =

    • NULL

    • 0x10001

    • 1

      Optional. Establishes the value data type and the AddReg item action.

      Here is a list of acceptable Flag values:

      String - No value needed (quotes set data type)

      Dword - 0x10001

      Binary - 1

    Value =

    • "start c:\mike.bat"

    • 0

    • 01,00,00,00

      Value to set. This parameter may be either a string or a number in hexadecimal notation. At least two fields are required; however, one may be null.

      Note: Remember that registry entries are case dependant, so make sure the case of the AddReg entry matches the case that is currently in the registry.

Copy files with batch installs.

Be sure and use the SourceDisksNames and SourceDisksFiles sections to prevent errors during installation when using CopyFile= in the Msbatch.inf.

Example:

[Install]

 

CopyFiles=My.comp.bmp

;;Tells the setup to copy the files in this section

 

 

[My.comp.Bmp]

;;Defines the files names to copy

cool.bmp

 

company.bmp

 

 

 

[DestinationDirs]

;;Set the directory in which to copy using the LDID of the directory, defined appendix C of the Windows 98 Resource Kit and the SDK and DDK.

My.comp.Bmp = 10

 

 

 

[SourceDisksNames]

;;Set the name of the disk which to copy from

1=Disk_1_Desc,,0

;;Disk_1_Desc sets it to the setup directory.

 

 

[SourceDisksFiles]

;;Specifies source file locations and sizes

cool.bmp=1,bmp,0

;;Disk number defined in SourceDisksNames, sub

company.bmp=1,bmp,0

;; directory, and size. 0 works as a NULL and
;; will work with all file sizes

Custom Network Card Install

Windows 98 does not ship with drivers for all brands and models of network adapters. In addition, some network card options are not enabled during setup by default. I/O address, interrupt, or other options may be set using a batch install. To manually set network card settings, perform the following steps:

  1. Add the line 'IgnoreDetectedNetCard=1' in the [Network] section of the inf

  2. Specify a network adapter (or multiple adapters) on the 'netcards=' line

    Add a section to the Msbatch.inf with the heading of the network adapter's Device ID. The Device ID may be found in the network adapter's inf file, as are the specific settings that can be configured during setup. To determine the Device ID of the network adapter, perform the following steps:

    1. To find the inf file used for a specific network adapter, from the Start Menu click Find, click Files or Folders, and type '*.inf' in the Named box, and the name listed for the network adapter in Control Panel/Networks or Device Manager in containing text on the advanced tab.

    2. This will bring up all inf files containing the name of the network card. Open them up individually in Notepad, and search each file for a [Strings] section containing the Friendly name for the card.

    3. In the [Strings] section, the friendly name will be on the right side of an equal sign. On the left side of this equal sign will be the DeviceDesc for the particular hardware.

    4. Search the file for an entry starting with the DeviceDesc. The example listed below is for an Intel EtherExpress(TM) PRO/10+, and the entry in question is the line %*pnp8132.devicedesc%=*pnp8132.ndi, *pnp8132

    5. The Device ID for this network adapter is pnp8132, the last entry on this line. Find the .ndi section for this ID (*pnp8132.ndi in this case). Here may be found a list of AddReg settings performed when the card is installed. Part of this section will be used to set the network adapter's parameters during setup.

  3. Copy the desired AddReg lines from the .ndi section to the adapter's Device ID section in the Msbatch.inf and modify as appropriate for the installation. Some network adapter drivers, as in the example below, point to other areas for the AddReg lines. In the case of the example, add the desired AddReg lines contained in the sections [*PNP8132.ndi.reg] (not shown) and [epro.reg] and modify them appropriately.

Note: The settings are typically located in the .ndi section of the inf file. Some drivers may vary, contact the driver's hardware vendor if it is believed the network adapter uses a different format.

Example of a Intel Ether Express Pro/10 (IRQ=5, I/O=300, and TP connector)

NETPRO10.INF settings:

[INTEL]

**%*pnp8132.devicedesc%=*pnp8132.ndi, ***pnp8132

%*INT1031.devicedesc%=*INT1031.ndi, *INT1031, *INT1030

[strings]

*pnp8132.devicedesc="Intel EtherExpress(TM) PRO/10+"

*INT1031.devicedesc="Intel EtherExpress(TM) PRO/10+ (PnP Enabled)"

[*PNP8132.ndi]

AddReg=*pnp8132.ndi.reg,epro.reg

LogConfig=*pnp8132.LogConfig

[epro.reg]

…..

; Resources

HKR,,INTERRUPT,1,04,00,00,00

HKR,,IOADDRESS,1,02,00,00,00

; Transceiver Type

HKR,Ndi\params\TRANSCEIVER,ParamDesc,,"Transceiver Type"

HKR,Ndi\params\TRANSCEIVER\enum,"0",,"Auto-Connector"

HKR,Ndi\params\TRANSCEIVER\enum,"1",,"AUI Connector"

HKR,Ndi\params\TRANSCEIVER\enum,"2",,"BNC Connector"

HKR,Ndi\params\TRANSCEIVER\enum,"3",,"TPE Connector"

MSBATCH.INF settings:

[Network]

IgnoreDetectedNetCards=1

netcards= *pnp8132

[*pnp8132]

INTERRUPT=5

IOADDRESS=300

TRANSCEIVER="TPE Connector"

Custom Network card Installation for older Legacy Devices

Some network adapters may not function with the above information. An AddReg for the network adapter may be needed in many cases where the above does not work.

[Network]

 

Netcards=m_isa_FFFF

;;The identifier found in MyNic.inf

 

 

 

 

CardBrand=MyNicCompany

;;Copy this information out of the Inf

INFFile=INF\MyNic.INF

;;file that is used for the Network Adapter

AddReg=m_isa_FFFF.ndi.reg

;;In this case it was the MyNic.inf

CardBrand=MyNicCompany

 

INFFile=INF\MyNic.INF

 

 

 

[isa_FFFF]

;; These settings are grabbed from the

Interrupt=10

;; MyNic.inf's [isa_FFFF.Params] section

IOAddress=A20

 

DMAChannel=5

 

DataRate=16

 

Appendix - Sections of Msbatch.inf

 

batch984

Windows 98 Resource Kit; Appendix D, page(s): 1445-1482

General System and Network Settings

Section

Command

Description

[Setup]

 

Used to configure the SETUP options

 

Express=0/1

0 - Allow user input (Default).
1- Don't allow user input.

 

InstallDir="<local directory>"

Location of Destination directory (%windir% is default)

 

EBD=0/1

0 - No Emergency Boot Disk
1 - Create Emergency Book Disk (Default)

 

ChangeDir=0/1

0 - Don't display Choose Install Directory.
1 - Display the Choose Install Directory Dialog.

 

OptionalComponents=0/1

0 - Don't use the Optional Components section.
1 - Use Optional Components in Msbatch.inf

 

CleanBoot=0/1

0 = Do not force a clean installation, perform an upgrade instead.
1 = Force a clean installation.

 

PenWinWarning=0/1

0 – Do not show warnings about unknown versions of Pen Windows.
1 – Show warning. (Default)

 

InstallType=0/1/2/3

Select the type of Install
0=Compact 1=Typical (Default),
2=Portable 3= Custom

 

TimeZone="<string>"

Pre-set the Time Zone. See the Windows 98 Resource Kit for sample

 

Uninstall=0/1/5

0 – No Uninstall or backup files.
1 – Show Uninstall options for user choice (Default).
5 - Force saving Uninstall data

 

BackupDir="<local directory>"

Directory to store Uninstall data to

 

NoDirWarn = 0/1

0 = Warn me before overwriting an existing Windows installation directory
1 = Overwrite the existing Windows installation directory without warning me

 

NoPromptBoot=0/1

0 - Don't reboot the system for PCI and PnP enumeration.
1 - Reboot the machine for PCI and PnP enumeration (Default).

 

ShowEula=0/1

0 – Don't show EULA
1 – (Default) Show EULA

[System]

 

Set CUSTOM hardware option

 

MultiLanguage=<string>

English – support for English and Western Languages (Default)
Greek – Adds additional support for Greek
Cyrillic – Adds additional support for Cyrillic
CE – Adds additional support for Eastern European language.

 

(The following entries are based in INF section names:)

 

 

Locale=INF_Definition

Name found in Locale.inf

 

PenWindows=INF_Definition

Name found in Penwin.inf

 

Power=INF_Definition

Name found in Machine.inf or similar file (for advanced power management support)

 

Display=INF_Definition

Name found in Msdisp.inf.
For example, from the description %SuperVGA.DriverDesc%=SVGA for Super VGA, the entry in Msbatch.inf would be display=svga.

 

Keyboard=INF_Definition

Keyboard.inf

 

Mouse=INF_Definition

Mouse.inf or similar file

 

Tablet=INF_Definition

Name Found in Pendrv.inf or similar file

[NameAndOrg]

Name and Organization section

 

 

Name="<string>"

User's Name

 

Org="<string>"

Company Name

 

Display=0/1

0 - Don't prompt for user input on Name and Org.
1 – Prompt for user input (Default)

[Network]

 

Network Option Section

 

ComputerName="<string>"

Computer Friendly name

 

Workgroup="<string>"

Workgroup name

 

Description="<string>"

Computer Description

 

Display=0

0 - Don't prompt for Computer Name, Workgroup, etc.
1 – Prompt for user input (Default)

 

Clients=VREDIR, NWREDIR

Clients to install

 

Protocols=NETBEUI, NWLINK, MSTCP

Protocols to install

 

Services=VSERVER

Server to install

 

IgnoreDetectedNetCards=0

0 - Do not ignore the detected network card (Default).
1 - Ignore the detected network card.

 

Security=<string>

share - share level security
nwserver - user level security via NetWare server
domain - user level security via NT domain.
msserver - user level security via NT Workstation.

PROTOCOL Sections

Section

Command

Description

[NWLINK]

 

IPX/SPX protocol section

 

FrameType=1/2/3/4

1 – Ethernet_II
2 – 802.2
3 – 802.3
4 – Auto

 

NetBIOS=0/1

0 - Disable NetBIOS over IPX/SPX
1 – Enable NetBIOS over IPX/SPX

 

 

 

[MSTCP]

TCP/IP protocol section

 

 

DHCP=0/1

0 - Don't enable DHCP.
1 - Enable DHCP (Default)

 

DNS=0/1

0 - Disable DNS (Default).
1 - Enable DNS.

 

WINS=0/1/DHCP

0 - Disable WINS
1 - Enable WINS (Default)
DHCP - Get WINS from DHCP server

 

Hostname=<string>

TCP/IP Host Name

Redirector Sections

Section

Command

Description

[NWREDIR]

MS Client for NetWare Networks

 

 

FirstNetDrive=<drive>:

Login drive letter

 

PreferredServer=<server>

Preferred NetWare Server

 

ProcessLoginScript=0/1

0 - Don't Process NetWare Logon Script
1 - Process Login Script (Default)

[VREDIR]

 

MS Client for MS Networks

 

LogonDomain="<domain>"

Validation domain name

 

ValidatedLogon=0/1

0 -Don't validate logons (Default).
1 - Validate logons.

Optional Components

Section

Command

Description

[OptionalComponents]

Optional Components to install

 

 

"Accessibility Options"=0/1

Don't install the Accessibility options

 

"Briefcase"=0/1

0 - Don't install the Briefcase.
1 - Install the Briefcase.

 

"Net Watcher"=0/1

0 – Don't install Netwatcher
1 - Install Netwatcher

 

"Online User's Guide"=0/1

0 - Don't install the Online User's Guide
1 - Install the Online User's.

 

"Paint"=0/1

0 – Don't install MSPaint
1 - Install MSPaint..

 

"Quick View"=0/1

0 – Don't install Quick View components
1 - Install Quick View components.

Adding Printers

Section

Command

Description

[Printers]

 

Add the below printers

 

Class Printer=<- Friendly name>

Example would be Class Printer=HP LaserJet III,LPT1