Dec 152017
 
A description of how to run the TCP/IP protocol with Windows for Workgroups.
File WFWTCP.ZIP from The Programmer’s Corner in
Category Network Files
A description of how to run the TCP/IP protocol with Windows for Workgroups.
File Name File Size Zip Size Zip Type
WFWTCP.WRI 18176 6157 deflated

Download File WFWTCP.ZIP Here

Contents of the WFWTCP.WRI file


11nThe information provided here is an exert from Appendix E of the Windows for Workgroups Resource Kit. To purchase the Windows for Workgroups Resource Kit call Microsoft Sales at 800-426-9400.

Appendix
EIntegrating Additional Protocols with Windows for Workgroups
This appendix contains information that describes the procedures for installing and configuring the Microsoft TCP/IP, Microsoft ASYBEUI, Microsoft DLC, and AT&T StarLAN ISO protocols for use with Windows for Workgroups. A solid understanding of the network protocols that are described in this appendix is helpful, and will help to ensure a successful installation.

NoteThe information provided in this appendix is preliminary and was not completely tested by Microsoft at the time the Windows for Workgroups Resource Kit went to print (September 1992).

Windows for Workgroups fully supports connectivity to LAN Manager and Novell NetWare networks using NetBEUI and MSIPX protocols, respectively, as described in Chapter 8, Network Integration with Microsoft LAN Manager and Novell NetWare. Other protocols and networks may work with Windows for Workgroups, however, limited support may be available for these from Microsoft Product Support Services (PSS).
Integrated setup procedures that are supported by PSS will be available at a later datecheck the Microsoft Download Service (MSDL), CompuServe, and other electronic bulletin board systems for announcements of additional information. (See Appendix A for information on these resources.)

Related informationWindows for Workgroups Resource Kit. Chapter 6, Windows for Workgroups Initialization Files; Chapter 7, Additional Windows for Workgroups Information;Chapter 14, Troubleshooting Windows for Workgroups.
Microsoft LAN Manager Resource Kit


NDIS Transport Protocol Integration
Microsoft LAN Manager 2.1 provides support for several protocols not provided as part of Windows for Workgroups. These additional protocols include TCP/IP, ASYBEUI (used for remote asynchronous connectivity; also known as Remote Access Services or RAS), and DLC.
In general, any NDIS-compliant protocol can work with Windows for Workgroups. The issue is whether the protocol has been integrated with a SETUP installation procedure, or whether the settings files (for example, CONFIG.SYS, AUTOEXEC.BAT, and PROTOCOL.INI) must be hand-edited to configure the protocol. The protocol installer for use with LAN Manager was not revised before Windows for Workgroups was made available, but the procedures below describe how the settings files can be modified to use other protocols.
The protocols provided by Microsoft for use with LAN Manager will be modified to install on a Windows for Workgroups workstation, but they were not available at the time the Windows for Workgroups Resource Kit manual was released to print (September 1992).
The following information was compiled during the beta test for Windows for Workgroups and will aid you in getting these additional transport protocols to work with Windows for Workgroups.
Configuring the Microsoft TCP/IP Protocol
Installation of the TCP/IP protocol stack requires the manipulation of the CONFIG.SYS, AUTOEXEC.BAT, PROTOCOL.INI, and SYSTEM.INI files on Windows for Workgroups computers.
The following steps have been prepared to make the task easier. A completed example of each of these files has been provided at the end of this section for reference.
NoteThe following steps discuss the installation of the basic TCP/IP protocol stack. These procedures do not discuss the installation of the TCP/IP Utility pack. Thus, this installation won't permit the use of the sockets library.

1.Install MS-DOS LAN Manager on a computer.
Before installing TCP/IP, you must first get a copy of the files. This is easily done by installing MS-DOS LAN Manager on a single computer, and then copying the files on a floppy disk or a file share point for distribution to Windows for Workgroups computers.
NotePlease follow the procedures and installation prompts for installing the TCP/IP protocol stack. When prompted for the IP address, sub-net mask, and the default gateway address, you may want to use information for one of the workstations you will be installing. You will be adding this information manually to the PROTOCOL.INI file during the actual installation.
2.Copy the following files to a floppy disk:
C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\EMSBFR.EXE
C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\NEMM.DOS
C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\TCPTSR.EXE
C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\TCPDRV.DOS
C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\TINYRFC.EXE
C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\UMB.COM
C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\NMTSR.EXE
C:\LANMAN.DOS\TCPUTILS.INI
C:\LANMAN.DOS\NETPROG\PING.EXE
3.Install Windows for Workgroups on a computer.
4.Copy the TCP/IP files from the floppy disk in step 2 on the WINDOWS directory of the Windows for Workgroups computer. (If Windows for Workgroups was installed in a directory besides WINDOWS, copy these files to that directory.)
5.In the CONFIG.SYS file, insert the following lines immediately after the line that installs PROTMAN.DOS (before WORKGRP.SYS is referenced):
device=c:\windows\nemm.dos
device=c:\windows\tcpdrv.dos /i:c:\windows

NoteThe directories for the device drivers and the information pointer for the TCPUTILS.INI file (/i:c:\windows) may be different if Windows for Workgroups was installed in a directory other than that referenced in these procedures. Refer to the directory discussion in step 4.
6.Make the follow modifications to the AUTOEXEC.BAT file.
Immediately before the net start line, add the following line:
c:\windows\umb.com
Immediately after the net start line, add the following lines:
c:\windows\emsbfr
c:\windows\tcptsr
c:\windows\tinyrfc
c:\windows\nmtsr
7.Make the following modifications to the \WINDOWS\PROTOCOL.INI file:
After the last existing transport line in the [network.setup] section, add the following line:
transport=ms$tcp,ms$tcp

After the last existing LANA number line in the [network.setup] section, add the following line:
lana1=ms$elnkii,1,ms$tcp

NoteThe LANA number may be different if other protocols are being loaded before the TCP/IP stack. Also, the device driver identifier (shown as MS$ELNKII in these steps) is dependent on the type of network interface card you are using.
Add the following lines to the end of the PROTOCOL.INI file:
[ms$tcp]
drivername=tcpip$
nbsessions=10
bindings=ms$elnkii
lanabase=1
ipaddress0=11 1 7 99
subnetmask0=255 255 0 0
defaultgateway0=11 1 0 1

Notes
The lanabase= value must match the lanax= entry in the [network. setup] section. The bindings= entry is the section name ( [xxxxxx] ) of the device driver to which the TCP/IP stack will be bound. This value is dependent on the type of network interface card used. The ipaddress0, subnetmask0, and defaultgateway0 values are computer- and site-dependent. These values are provided as an example. Of special interest is that spaces are used as separators in the numbers instead of the more traditional periods.
Notice the nbsessions value was increased from its LAN Manager default value of 6, to increase the number of sessions supported by the TCP/IP device driver.
8.Make the following modifications to the \WINDOWS\SYSTEM.INI file:
After the [386Enh] section add the following line:
V86ModeLanas=1

NoteThe parameter for V86ModeLanas= is a list of LANA numbers that are supported by real mode protocol stacks. If TCP/IP has been given a different LANA number it should be used.
Increase the netheapsize= parameter in the [386Enh] section from its default value of 20 to 60.

NoteThe additional memory is needed as buffer space for passing network frames between real and protected mode.

9.Restart the target computer.
Once all steps are completed and verified, restart the computer to load the needed device drivers, and TSRs.
Figure E.1 details the active components of the TCP/IP installation.
#')1#')(KKjZ&MrEdMicrosoft DrawZ&MrEdHelv=hhqhbpfx&MrEd$x$y
[email protected]`[email protected]?CDL."Arial-2
Network Interface Device Driver2
0
ELNKII.DOS2
Protocol Manager for NDIS
2
PROTMAN.DOS2
@ [email protected] $D,&MrEd%[email protected]|&MrEd`?PTC\&MrEdp`@PTD\l
2
WORKGRP.SYS2
0.Virtual (Protect Mode) NetBeui Protocol Driver2
VNB.3862
` Virtual NetBios Interface Driver
2
@VNETBIOS.3862
Virtual Redirector 2
0
VREDIR.3862
Virtual Server
2
VSERVER.3862
` [email protected]#[email protected]`dD&MrEd

&MrEd @D&MrEdp

l2

TCPDRV.DOS2
00UMB.COM2
@P
TCPTSR.EXE
2
TINYRFC.EXE2
NMTSR.EXE"System---''C#"#!432!44C!4!!42#22&&&

Figure E.1

Active components in a NetBEUI and TCP/IP installation
Notice that NMTSR.EXE is an optional component and is used only with the PING utility.
The following are the final installation images of CONFIG.SYS, AUTOEXEC.BAT, and PROTOCOL.INI. Areas where you need to make changes manually (per the preceding procedure) are highlighted in bold.
The following is an example of a CONFIG.SYS file image:
device=c:\dos\setver.exe
device=c:\windows\himem.sys
device=c:\windows\emm386.exe noems x=b800-c800
dos=high,umb
files=30
buffers=10
lastdrive=z
device=c:\windows\protman.dos /i:c:\windows
device=c:\windows\nemm.dos
device=c:\windows\tcpdrv.dos /i:c:\windows
device=c:\windows\workgrp.sys
device=c:\windows\elnkii.dos
stacks=9,256

The following is an example of a AUTOEXEC.BAT file image:
c:\windows\smartdrv.exe
c:\windows\umb.com
c:\windows\net start
c:\windows\emsbfr
c:\windows\tcptsr
c:\windows\tinyrfc
c:\windows\nmtsr
@echo off
prompt $p$g
path c:\windows;c:\dos
set temp=c:\dos

The following is an example of a PROTOCOL.INI file image:
NoteThe ms$elnkii keyname used in the following example specifies the use of the 3Com EtherLink II network adapter card driver. Use the name of the network adapter card driver that is present in your existing PROTOCOL.INI file

[network.setup]
version=0x3100
netcard=ms$elnkii,1,ms$elnkii
transport=ms$netbeui,ms$netbeui
transport=ms$tcp,ms$tcp
lana0=ms$elnkii,1,ms$netbeui
lana1=ms$elnkii,1,ms$tcp

[protman]
drivername=protman$
priority=ms$netbeui

[ms$elnkii]
drivername=elnkii$
interrupt=5
ioaddress=0x300
maxtransmits=40
transceiver=external

[ms$netbeui]
drivername=netbeui$
sessions=6
ncbs=12
bindings=ms$elnkii
lanabase=0

[ms$tcp]
drivername=TCPIP$
nbsessions=10
bindings=ms$elnkii
lanabase=1
ipaddress0=11 1 7 99
subnetmask0=255 255 00
defaultgateway0=11 1 0 1

NoteHere is some additional information about TCP/IP installations:
WORKGRP.SYS will give a diagnostic error at startup (No NETBEUI section found in configuration information) if you do not have NetBEUI as an additional protocol. This is expected and harmless.
TCP/IP may require time to identify itself on the LAN/WAN before starting Windows for Workgroups. Therefore, if you start Windows for Workgroups automatically from AUTOEXEC.BAT, it is recommended that you place a PAUSE statement before you invoke Windows for Workgroups and allow approximately 10 seconds for the TCP/IP protocol to initialize before proceeding.

L."Arial-2
Network Interface Device DriverCwEsOokgc_z[WwSOK( xtpYlZi[ea]YbUQtMtw
s
o
kgc_[CWSOK7w;s-[.W.S.O1KC\E=O,gphp=pphp\\[email protected]\w\Y=Up(ppp\\=
=pp=p
\t\=N

=p8p=p
\==
[email protected]\=FppNpFw\\\\#\C\u=]==pp\5\7\O=pNpp\[email protected]@[email protected]!4\G\[\m\[email protected]@p\/=1m\[email protected]@p1\=m\[email protected]@p\=
@[email protected]
\*\@\Y\s\u=|[email protected]|{\\`=s\@[email protected]\=\s\[email protected]\\=2s\[email protected]\U= s\[email protected] 3'\5'=A'C'{'=ppp{''\(\(\(=)=9)=G)=Q)=])=j)=pp=p
j))\)\)\)\*\**\,*=Q)=])=j)[email protected],*g*\*=*=*=*=*=*=*=+=+=pp=p
+&+\7+\9+=t+*[email protected]+Y,\[,=l,|,,[email protected]@p,,\,\,\
-\-\-\/-\D-\F-\S-\g-\t-\-\-\-\pp--\-\-\-\-\-\.\.\.\%.\4.\H.\T.\j.\.\pp..\.\.=/-\[email protected]/1\1=1=/-\p=p|pf=/2!;(0E0,gphp=pphp ArialTimes New [email protected]


 December 15, 2017  Add comments

Leave a Reply