Microsoft KB Archive/98245

= Automated Setup for Windows for Workgroups and TCP/IP =

Article ID: 98245

Article Last Modified on 11/17/2003

-

APPLIES TO


 * Microsoft LAN Manager 2.2 Standard Edition
 * Microsoft TCP/IP-32 for Windows for Workgroups 1.0
 * Microsoft Windows for Workgroups 3.1

-



This article was previously published under Q98245



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 &quot;Resource Kit.&quot; 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 = &quot;MS TCP/IP&quot;,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,&quot;IP Address&quot;,chars,15,,0x08 param = SubNetMask0,&quot;Subnet Mask&quot;,chars,15,,0x08 param = DefaultGateway0,&quot;Default Gateway&quot;,chars,15,,0x08 param = NBSessions,&quot;Maximum number of sessions&quot;,int,&quot;1,20,1&quot;,6 param = NetFiles,&quot;Netfiles directory&quot;,static,@netdir param = tcpsegmentsize,&quot;TCP segment size&quot;,static,1450 param = tcpwindowsize,&quot;TCP window size&quot;,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 =. ,&quot;Enterprise Protocols for Windows for Workgroups&quot;,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,&quot;Subnet Mask&quot;,chars,15,&quot;255 255 0 0&quot;,0x08

