tyt10fi.htm

一个学习tcp/ip协议的教程

DriverName=EXP16$

IOADDRESS=0x360

IRQ=11

IOCHRDY=Late

TRANSCEIVER=Thin Net (BNC/COAX)</FONT></PRE><P>This PROTOCOL.INI file defines the packet driver as PKTDRV$, the default driver with PC/TCP. The binding to the Intel EtherExpress 16 card used on the DOS machine refers to another section in the file that lists the address, IRQ, and some specifics of the EtherExpress card. These lines could have been included in the [PKTDRV] section but were separated for compatibility with the Windows for Workgroups PROTOCOL.INI file, which is similar in layout. The EtherExpress 16 card is set to use IRQ 11, memory address 360, and use the Thin Ethernet cable connector. The intvec line in the [PKTDRV] section does not define the IRQ for the network card; instead, it is an interrupt for the driver.<BR><P>A PROTOCOL.INI file for a system using a simpler network card than the EtherExpress can be shorter. A sample PROTOCOL.INI file for such a card might look like this:<BR><PRE>

<FONT COLOR=#000080>[PKTDRV]

drivername=PKTDRV$

binding=MS$ELNKII

intvec=0x65

chainvec=0x67</FONT></PRE><P>Finding the proper settings for the variables in the PROTOCOL.INI file can be a harrowing experience. If Windows for Workgroups is installed and running, the Windows PROTOCOL.INI file is a good source of information and can sometimes be copied without modification. Otherwise, the network card documentation can sometimes help.<BR><BR><A ID=E70E37 NAME=E70E37></A><H5 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>The PCTCP.INI File</B></FONT></CENTER></H5><BR><P>The PCTCP.INI file holds the kernel configuration information for PCTCP. In most cases, it can be left as supplied with the software. Tweaking the kernel parameters should be performed only after the network is installed and has been operating properly for a while. The PCTCP.INI file is quite lengthy, and care should be taken to avoid accidental changes, which can render the system inoperative.<BR><P>If the supplied installation script is not used to install PC/TCP, a minimum PCTCP.INI file must be created manually. Examples are included with the distribution media, usually under the name TEMPLATE.INI. There are two ways to create the PCTCP.INI file and configure it properly. The first is to use an editor and modify the template file. The alternative is to run the kernel configuration utility KAPPCONF.<BR><P>A minimum PCTCP.INI file needs to have the software serial number and activation key, the IP address, broadcast address, router address, a subnet mask, and information about the system in general. The minimum PCTCP.INI file would look like this:<BR><PRE>

<FONT COLOR=#000080>[pctcp general]

domain                 = tpci.com

host-name              = sinbad

time-zone              = EST

time-zone-offset       = 600

user                   = tparker

[pctcp kernel]

serial-number          = 1234-5678-9012

authentication-key     = 1234-5678-9012

interface              = ifcust 0

low-window             = 0

window                 = 2048

[pctcp ifcust 0]

broadcast-address      = 255.255.255.255

ip-address             = 147.120.0.11

router                 = 147.120.0.1

subnet-mask            = 255.255.0.0

[pctcp addresses]

domain-name-server     = 147.120.0.1

mail-relay             = 147.120.0.1</FONT></PRE><P>This configuration assumes that the SCO UNIX server (147.120.0.1) is the primary server for the network. The DOS machine's name (sinbad) and IP address (147.120.0.11) are shown in the PCTCP.INI file. As different features of PC/TCP are enabled (such as SNMP and Kerberos), new sections are added to the PCTCP.INI file.<BR><BR><A ID=E70E38 NAME=E70E38></A><H5 ALIGN=CENTER><CENTER><FONT SIZE=4 COLOR=#FF0000><B>The Windows SYSTEM.INI File</B></FONT></CENTER></H5><BR><P>If Windows for Workgroups is to be used on the DOS machine and you are going to use the PC/TCP drivers instead of a dedicated Windows for Workgroups TCP/IP package, the Windows for Workgroups SYSTEM.INI file requires modification. The Windows for Workgroups SYSTEM.INI file must be set to use the Windows for Workgroups driver instead of the PC/TCP driver.<BR><P>When the PC/TCP automatic installation process detects a copy of Windows, it makes changes to the SYSTEM.INI file for you. Some of these changes must be checked and modified to enable Windows to boot properly with the PC/TCP drivers. One of the most important changes is the commenting out of the Windows for Workgroups network driver and its replacement with the PC/TCP driver:<BR><BR><PRE>

<FONT COLOR=#000080>network.drv=C:\PCTCP\PCTCPNET.DRV</FONT></PRE><P>For Windows for Workgroups 3.1, confirm that the SYSTEM.INI file has these three sections, with these commands shown:<BR><PRE>

<FONT COLOR=#000080>[boot]

network.drv=wfwnet.drv

[boot.description]

network.drv=Microsoft Windows for Workgroups (version 3.1)

[386Enh]

device=c:\pctcp\vpctcp.386

device=c:\pctcp\wfwftp.386</FONT></PRE><P>Windows for Workgroups 3.11 has a slightly different SYSTEM.INI. It should look like this:<BR><PRE>

<FONT COLOR=#000080>[boot]

network.drv=wfwnet.drv

[boot.description]

network.drv=Microsoft Windows Network (version 3.11)

[386Enh]

device=c:\pctcp\vpctcp.386</FONT></PRE><P>At the bottom of the Windows for Workgroups SYSTEM.INI file, PC/TCP sometimes adds a block of information that looks like this:<BR><PRE>

<FONT COLOR=#000080>[vpctcp]

; These option settings may be added to SYSTEM.INI, in a

;   new section &quot;[vpctcp]&quot;.

; The next line tells VPCTCP how much copy space memory to request.

;   It is in units of kilobytes (x1024).  This value is only a bid,

;   as Windows may choose to reduce your allocation arbitrarily.

;   This value should be increased if using Windows applications which

;   call the PC/TCP DLL from another DLL; suggested value in such