Compaq 4130T Deployment Guide - Page 4

Modifying SYSTEM.INI and PROTOCOL.INI, Using a Specific Computer Name, Performing Enterprise- - drivers

Get Compaq 4130T - Armada - Pentium 133 MHz PDF manuals and user guides View all Compaq 4130T manuals
Add to My Manuals
Save this manual to your list of manuals

Page 4 highlights

Compaq Guide to PC Deployment 4 Preliminary services tcpdrv.dos tcptsr.exe tcputils.ini tinyrfc.exe umb.com Modifying SYSTEM.INI and PROTOCOL.INI SYSTEM.INI and PROTOCOL.INI are built dynamically during MNBU boot in order to automatically load the detected NIC's driver. Further modifications to these files may be accomplished by editing SYSINI.TMP and PROTINI.TMP for your specific needs. These two files contain the boilerplate text for the INI files. Note: The requirement that files are built dynamically requires that the MNBU diskette not be write protected. This requirement is also necessary due to Microsoft Client's creation of password list (.PWL) files. Using a Specific Computer Name If you wish to use a specific computer name instead of a randomly generated name, remove the line in AUTOEXEC.BAT that begins with "unique." REM **BEGIN RANDOM COMPUTER NAME GENERATOR** REMOVE -> unique /f:name.txt /s:ComputerName=Boot$ type name.txt>>\net\system.ini REM **END COMPUTER NAME GENERATOR* And edit NAME.TXT: ;UNIQUE Generated name ComputerName= Performing Enterprise-Specific Functions Place any enterprise-specific functionality at the end of AUTOEXEC.BAT after the statement: REM **BEGIN ENTERPRISE SPECIFIC FUNCTIONALITY** Typically, this will include commands such as NET USE to map a network drive containing an operating system installation image, WINNT.EXE /B to launch Windows NT Setup, or SETUP.EXE to launch Windows 9x Setup. For more information on using WINNT.EXE and the NET command (Windows NT Workstation 4.0) or SETUP.EXE (Windows 95 or Windows 98), refer to the appropriate Microsoft operating system documentation. Systems With Multiple Network Controllers DETECT.BAT uses a program called SYSINV.EXE to find the first NIC in the system (defined by PCI order). This NIC is referred to as NET0. The /eNET0 command line parameter can be found on the SYSINV.EXE line in DETECT.BAT. If you wish to identify another network controller instead of the default, change /eNET0 to /eNET1. The third controller is NET2 and so on. PRT/012A/0699

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
Compaq Guide to PC Deployment
4
Preliminary
PRT/012A/0699
services
tcpdrv.dos
tcptsr.exe
tcputils.ini
tinyrfc.exe
umb.com
Modifying
SYSTEM.INI and
PROTOCOL.INI
SYSTEM.INI and PROTOCOL.INI are built dynamically during MNBU boot in order to automatically
load the detected NIC's driver. Further modifications to these files may be accomplished by editing
SYSINI.TMP and PROTINI.TMP for your specific needs. These two files contain the boilerplate text for
the INI files.
Note:
The requirement that files are built dynamically requires that the MNBU diskette not be
write protected. This requirement is also necessary due to Microsoft Client's creation of password
list (.PWL) files.
Using a Specific Computer Name
If you wish to use a specific computer name instead of a randomly generated name, remove the line in
AUTOEXEC.BAT that begins with "unique."
REM **BEGIN RANDOM COMPUTER NAME GENERATOR**
REMOVE ->
unique /f:name.txt /s:ComputerName=Boot$
type name.txt>>\net\system.ini
REM **END COMPUTER NAME GENERATOR*
And edit NAME.TXT:
;UNIQUE Generated name
ComputerName=<YourName>
Performing Enterprise
-
Specific Functions
Place any enterprise-specific functionality at the end of AUTOEXEC.BAT after the statement:
REM **BEGIN ENTERPRISE SPECIFIC FUNCTIONALITY**
Typically, this will include commands such as NET USE to map a network drive containing an operating
system installation image, WINNT.EXE /B to launch Windows NT Setup, or SETUP.EXE to launch
Windows 9x Setup.
For more information on using WINNT.EXE and the NET command (Windows NT Workstation
4.0) or SETUP.EXE (Windows 95 or Windows 98), refer to the appropriate Microsoft operating
system documentation.
Systems With Multiple Network Controllers
DETECT.BAT uses a program called SYSINV.EXE to find the first NIC in the system (defined by PCI
order). This NIC is referred to as NET0. The /eNET0 command line parameter can be found on the
SYSINV.EXE line in DETECT.BAT.
If you wish to identify another network controller instead of the default, change /eNET0 to
/eNET1. The third controller is NET2 and so on.