Microsoft KB Archive/115787

= Configuring PC/TCP for Windows for Workgroups 3.11 =

Article ID: 115787

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Windows for Workgroups 3.11

-



This article was previously published under Q115787



SUMMARY
This article explains the configuration procedure of FTP Software's PC/TCP version 2.3 for Windows for Workgroups version 3.11.



MORE INFORMATION
There are three configuration options available of running PC/TCP version 2.3 in Windows for Workgroups version 3.11, which are with NetBEUI only, NetBEUI and NetBIOS, and NetBIOS only.

NetBEUI Only
 Choose Real Mode NDIS Driver (NDIS2) during the Windows for Workgroups Setup procedure. Make the following changes to the CONFIG.SYS file:  Verify the following line:

Device= :\ \ifshlp.sys

 Remove any entries that load the Protocol manager or an NDIS-specific NIC driver.  Make the following changes to the AUTOEXEC.BAT file:  Make sure that the NET START command precedes any TSRs (Terminate and Stay Resident programs).

NOTE: Remove the NETBIND command if it exists.</li> Add the following line to load the PC/TCP kernel after the NET START command:



</li></ul> </li> Make the following changes to the SYSTEM.INI file:  Verify and add the following line to the [Boot] section:

Network.drv=wfwnet.drv

Secondnet.drv= :\ \pctcpnet.drv

</li> Add the following line to the [386Enh] section:

Secondnet=drive:\path\vpctcp.386

</li> If you are going to use PC-NFS to mount remote drivers or printers, add the following line to the [386Enh] section:

Device=drive:\path\wfwftp.386

NOTE: You must use the WFWFTP.386 file available through FTP Software Technical Support BBS at (508) 659-6240. The filename is WFW311.EXE. The WFWFTP.386 file created for Windows for Workgroups 3.11 will also work with Windows for Workgroups 3.1, but not the other way around.</li> Verify and add the following entries are in the [network drivers] section:

Netcard=

Transport=ndishlp.sys,*netbeui, :\ \dis_pkt.gup

LoadRMDrivers=Yes

</li></ul> </li> Make the following changes to the PROTOCOL.INI file:  Add a [PKTDRV] section and the following entries:

[PKTDRV] DriverName=PKTDRV$ Bindings= IntVec=  ChainVec=

NOTE: Common interrupts available for entries IntVec and ChainVec are 0x60 and 0x65, respectively.</li></ul> </li> Restart your computer to start running Windows for Workgroups over the NetBEUI stack.</li></ol>

NetBEUI and NetBIOS
<ol> Follow steps 1 - 5 from the previous section of NetBEUI Only.</li> Add the following line to the AUTOEXEC.BAT file:



</li> Make the following changes to the PROTOCOL.INI file:  <li>In the [network.setup] section, change the lana0= entry to lanax= (where x is the next available adapter number).</li> <li>In the [NETBEUI] section, change LANABASE=0 to LANABASE=x (where x is the same number as the adapter number in the previous bullet).</li></ul> </li> <li>Make the following changes to the PCTCP.INI file: <ul> <li>In the [pctcp netbios] section, include the following NetBIOS specific parameters:

[pctcp netbios]

Ncbs=64

Names=32

Sessions=n (where n equals the same value that is assigned to the Tcp-Connections= entry in the [pctcp kernel] section of the PCTCP.INI file).

</li></ul> </li> <li>Restart your computer to start running Windows for Workgroups over the NetBEUI and NetBIOS stacks.</li></ol>

NetBIOS Only
<ol> <li>Follow all the steps in the two previous sections of NetBEUI Only and NetBEUI and NetBIOS.</li> <li>Comment out the NetMisc= and Transport= entries in the [386Enh] section of the SYSTEM.INI file by placing a semicolon in front of each entry.

For example:

;NetMisc=


 * Transport=

</li> <li>Restart your computer to start running Windows for Workgroups over the NetBIOS stack.</li></ol>

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

<div class="references_section">