Automated Setup for Windows for Workgroups and TCP/IP

ID: Q98245

The information in this article applies to:

Microsoft LAN Manager, version 2.2
Microsoft TCP/IP-32 for Windows for Workgroups
Microsoft Windows for Workgroups version 3.1

SUMMARY

You can automate Windows for Workgroups (WfWG) setup by using the /h:FILENAME.SHH parameter documented on pages 3-22 to 3-30 in the Windows for Workgroups "Resource Kit." With a few extra steps, you can use this basic method to install the Microsoft TCP/IP protocol shipped on the WfWG connectivity disk with LAN Manager 2.2 as the transport protocol.

MORE INFORMATION

In order for the TCP/IP stack to be used with automated setup, you must edit the NETWORK.INF file on Disk #2 of the WfWG install set (on the network share if you are installing from the network) and add several lines taken from the OEMSETUP.INF file on the connectivity disk. Use a text editor to add the following lines to the indicated sections.

To the [transport] Section


   tcpip = "MS TCP/IP",104,ndis,tcp,real,0,lanabase,tcpip,tcpip_xif

Note: The stack ID value in field 2 was changed to 104 because the original value of 020 was recognized as a 0 in the SETUP.SHH file and the default NetBEUI protocol was installed.

To the Protocol Install Sections


[tcpip]
devdir = 1:umb.com,1:tcptsr.exe,1:tinyrfc.exe,1:emsbfr.exe
devdir = 1:tcpdrv.dos,1:nemm.dos,1:nmtsr.exe,1:tcputils.ini
netdir = 1:addname.exe,1:ping.exe,1:sockets.exe
netdir = 1:hosts,1:lmhosts,1:networks,1:protocol,1:services
netdir = 1:net.exe
windir = 1:win_sock.dll,1:wsockets.dll
load    = umb,@devdir\umb
load    = tcptsr,@devdir\tcptsr
load    = tinyrfc,@devdir\tinyrfc
load    = emsbfr,@devdir\emsbfr
device = tcpdrv.dos,@devdir\tcpdrv.dos     /i:@devdir
device = nemm.dos,@devdir\nemm.dos
sysparm=386enh,TimerCriticalSection,5000
sysparm=386enh,UniqueDosPSP,TRUE
sysparm=386enh,PSPIncrement,2

[tcpip_xif]
drivername = TCPIP$
param  = IPAddress0,"IP Address",chars,15,,0x08
param  = SubNetMask0,"Subnet Mask",chars,15,,0x08
param  = DefaultGateway0,"Default Gateway",chars,15,,0x08
param  = NBSessions,"Maximum number of sessions",int,"1,20,1",6
param  = NetFiles,"Netfiles directory",static,@netdir
param  = tcpsegmentsize,"TCP segment size",static,1450
param  = tcpwindowsize,"TCP window size",static,1450

If you are installing from disk, in order to be prompted for the correct disk, you should add the information from the [disks] section of SETUP.INF (Windows for Workgroups Disk #1), changing the identifier to one that is not used by the WfWG disks. For example:


   C =. ,"Enterprise Protocols for Windows for Workgroups",diskC

You then need to change the disk identifier in the [tcpip] section shown above. That is:


devdir = C:UMB.COM,C:TCPTSR.EXE,C:TINYRFC.EXE,C:EMSBFR.EXE).

NOTE: This is not necessary if you are installing from a network drive.

You can also modify the PRIORITY parameter in the NETWORK.INF [protman] section of TCPIP.

You can then use the TCP/IP stack ID with the TransportID parameter in your SETUP.SHH file (TransportID=104) and run SETUP /H:SETUP.SHH to install WfWG automatically with this protocol stack.

You can also edit the [tcpip_xif] section to automatically set parameters in PROTOCOL.INI that you want to use. For example, to set the netmask parameter to 255.255.0.0:


   param  = SubNetMask0,"Subnet Mask",chars,15,"255 255 0 0",0x08

REFERENCES

Windows for Workgroups "Resource Kit," pages 3-22 to 3-30.

Additional query words: 2.20 2.2 WFW31 WIN31

Keywords : kbnetwork nttcp
Version : :2.2; WINDOWS:3.1
Platform : WINDOWS
Issue type :