tyt10fi.htm

tcpip14study_14天学会TCPIP编程裁减移植_好书啊!

[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

;   instances is at least 28.

MinimumCopySpace=12

; The next line tells VPCTCP the segment (paragraph) number of the

;   beginning of memory reserved for devices, BIOS, and upper-

;   memory blocks (which could contain TSRs).  All calls below the

;   PSP of Windows or above this parameter are not processed by

;   the VxD but rather are passed-thru to the kernel untouched.

HiTSRFenceSegment=A000h

; eof</FONT></PRE>

<P>For most installations, this block can be left as it is. The comment lines (those beginning with a semicolon) are ignored by Windows, whereas the two variables established in these sections are used by PC/TCP. There is no need to delete this information. However, as the first note indicates, users of PC/TCP might have to increase the values to account for heavy usage.

<BR>

<P>If the target system is running Windows 3.1 (not Windows for Workgroups) there are more changes to be made, because the SYSTEM.INI file and network-dependent initialization files do not have the proper format yet. To configure a Windows system, changes must be made to the PROGMAN.INI and SYSTEM.INI files.

<BR>

<P>Windows 3.1's PROGMAN.INI file controls the startup of the Windows Program Manager. Normally, this is modified by the PC/TCP installation script, but if a manual installation has been performed, changes must be made with a text editor. The PROGMAN.INI file must have the following lines added:

<BR>

<PRE>

<FONT COLOR="#000080">[Groups]

GROUP16 = C:\PCTCP\PCTCPDOS.GRP

GROUP17 = C:\PCTCP\PCTCPWIN.GRP</FONT></PRE>

<P>The numbers next to GROUP should be higher than any existing number, usually listed sequentially for convenience. In this example, the list of groups ran to number 15.

<BR>

<P>Changes to the Windows 3.1 SYSTEM.INI file must be made in a few sections. In the [386Enh] section, add a line for the PC/TCP device driver:

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">device=c:\pctcp\vpctcp.386</FONT></PRE>

<P>A [vpctcp] section must be added with the following entries:

<BR>

<PRE>

<FONT COLOR="#000080">[vpctcp]

MinimumCopySpace=12

HiTSRFenceSegment=A000h</FONT></PRE>

<P>See the discussion of Windows for Workgroups SYSTEM.INI file for more information on these variables.

<BR>

<P>Some additional entries might be necessary if the network driver is located in high memory, if there is a conflict with the default serial port IRQs, or if a Token Ring network is used. See the PC/TCP installation manual for complete change information in these cases.

<BR>

<BR>

<A ID="E69E133" NAME="E69E133"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Windows for Workgroups using NetBIOS</B></FONT></CENTER></H4>

<BR>

<P>As mentioned earlier, Windows for Workgroups can be set to use IP packets. This requires a NetBIOS driver for both Windows for Workgroups and PC/TCP. The architecture of such as system is shown in Figure 10.2. The Windows for Workgroups packets are sent through PC/TCP's NetBIOS and then into the normal PC/TCP stack.

<BR>

<P><B><A HREF="10tyt02.gif" tppabs="http://www.mcp.com/817948800/0-672/0-672-30885-1/10tyt02.gif">Figure 10.2. Windows for Workgroups with </B><B>NetBIOS.</A></B>

<BR>

<P>To install Windows for Workgroups in this manner, Windows must first be set up to use the Microsoft LAN Manager option. This is usually a matter of selecting the LAN Manager option from the Network window if it is not already the default setting. (Consult the Windows for Workgroups documentation for more information.)

<BR>

<P>The configuration files must also be changed to reflect the new architecture. The AUTOEXEC.BAT file has the network initiation command, the network kernel driver, and a NETBIOS command:

<BR>

<PRE>

<FONT COLOR="#000080">C:\WINDOWS\NET START

C:\PCTCP\ETHDRV

C:\PCTCP\NETBIOS.COM</FONT></PRE>

<P>A NETBIND can be performed instead of a NET START command, although the latter is preferable. The NETBIOS command must come after the NETBIND or NET START command.

<BR>

<P>The CONFIG.SYS file is similar to that seen earlier, with the same drivers. A sample CONFIG.SYS file for this type of architecture looks like this:

<BR>

<PRE>

<FONT COLOR="#000080">DEVICE=C:\WINDOWS\PROTMAN.DOS /I:\C:\WINDOWS

DEVICE=C:\WINDOWS\EXP16.DOS

DEVICE=C:\PCTCP\DIS_PKT.GUP</FONT></PRE>

<P>This starts the protocol manager, the card driver, and the NDIS packet converter. This example uses the Intel EtherExpress 16 card driver.

<BR>

<P>The PROTOCOL.INI file is the same as the previous example. A sample PROTOCOL.INI file for the Intel EtherExpress 16 card looks like this:

<BR>

<PRE>

<FONT COLOR="#000080">[PKTDRV]

drivername=PKTDRV$

bindings=MS$EE16

intvec=0x60

[MS$EE16]

DriverName=EXP16$

IOADDRESS=0x360

IRQ=11

IOCHRDY=Late

TRANSCEIVER=Thin Net (BNC/COAX)</FONT></PRE>

<P>Finally, the SYSTEM.INI file requires that the Windows for Workgroups network driver be used and not the PC/TCP network driver. This might require editing the SYSTEM.INI file, as noted earlier. The SYSTEM.INI file should contain the following lines:

<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

TimerCriticialSection=50000</FONT></PRE>

<P>The last line in the [386Enh] section might have to be added manually. The version number in the [boot.description] section changes to (version 3.11) with the later version of Windows for Workgroups.

<BR>

<BR>

<A ID="E69E134" NAME="E69E134"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Testing PC/TCP</B></FONT></CENTER></H4>

<BR>

<P>After making all the changes previously mentioned, the DOS machine is rebooted for testing. If no error messages are displayed when the new commands are executed, the system is ready for testing the TCP/IP protocol stack. The simplest test is to use ping to ensure that the TCP/IP software is talking to the local machine, then use it to test the remote machines.

<BR>

<P>Machine name information for other machines hasn't yet been added to the PC/TCP DOS system, so IP addresses must be used with ping. The following is an example of a ping command for the local machine (147.120.0.11), the SCO UNIX server (147.120.0.1), and the Windows 95 machine (147.120.0.10) on the sample network (which has not yet been installed and hence should not communicate):

<BR>

<PRE>

<FONT COLOR="#000080">C:\&gt; ping 147.120.0.11

host responding, time = 25 ms

Debugging information for interface ifcust  Addr(6): 00 aa 00 20 18 bf

interrupts: 0 (2 receive, 0 transmit)

packets received: 2, transmitted: 3

receive errors: 0, unknown types: 0

     runts: 0, aligns: 0, CRC: 0, parity: 0, overflow: 0

     too big: 0, out of buffers: 0, rcv timeout: 0, rcv reset: 0

transmit errors: 0

     collisions: 0, underflows: 0, timeouts: 0, resets: 0

     lost crs: 0, heartbeat failed: 0

ARP statistics:

arps received: 1 (0 requests, 1 replies)

     bad: opcodes: 0, hardware type: 0, protocol type: 0

arps transmitted: 2 (2 requests, 0 replies)

5 large buffers; 4 free now; minimum of 3 free

5 small buffers; 5 free now; minimum of 4 free

C:\&gt;