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 :
All known Microsoft 32-bit networking clients and their settings
All known Microsoft 32-bit networking services and their settings
All known Microsoft 32-bit networking protocols and their settings
Current user and machine name and description information
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 :
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 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)
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.
%LANEP.DeviceDesc%= LANEP.ndi, LANEP
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.
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.
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.
;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.
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: stands for the name of the Windows directory, typically C:\Windows.