🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.ms-windows.setup
Article #1177

INFO: TCP on WFW -- READ THIS

#1177
From: Wailer at the Gates of Dawn
Date: Fri, 22 Jan 1993 20:37
102 lines
3393 bytes

To run Windows for Workgroups, Novell IPX, and TCP together, you need the
WINQVT/NET package and the DIS_PKT9 driver (from wuarchive.wustl.edu or
other mirror site: windows3/QVTNET31.ZIP and pktdrvr/DIS_PKT9.ZIP).  Then you
need to make some changes to your configuration files.  The examples that
follow assume that you have installed WFW with IPX and that everything is
working on your system.

Here are config.sys, autoexec.bat, and protocol.ini changes needed to run
tcp on top of the windows for workgroups ndis driver.  The lines you will
need to add begin with a "*" -- don't actually add the "*".  Your files may
have a different card driver than ne2000 and you will need to replace
"MS$NE2CLONE" in the `bindings=MS$NE2CLONE` line with the label for your 
card.  Simply copy the "BINDINGS=XXXX" line from the [MS$IPX] section.
Good luck.

###CONFIG.SYS###

device=C:\WINDOWS\protman.dos /i:C:\WINDOWS
device=C:\WINDOWS\workgrp.sys
device=C:\WINDOWS\ne2000.dos
*device=C:\WINDOWS\QVTNET30\dis_pkt9.dos
device=C:\WINDOWS\msipx.sys

###AUTOEXEC.BAT###

C:\WINDOWS\net start
C:\WINDOWS\msipx
*c:\windows\qvtnet30\pktint 
C:\WINDOWS\netx

###PROTOCOL.INI###

[network.setup]
version=0x3100
netcard=ms$ne2clone,1,MS$NE2CLONE
transport=ms$netbeui,MS$NETBEUI
transport=ms$ipx,MS$IPX
lana0=ms$ne2clone,1,ms$ipx
lana1=ms$ne2clone,1,ms$netbeui

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI

*[pktdrv]
*DriverName=pktdrv$
*bindings=MS$NE2CLONE	
*intvec=0x60	
*chainvec=0x66	

[MS$NE2CLONE]
DriverName=MS2000$
IOBASE=0x300
INTERRUPT=7

[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=MS$NE2CLONE
LANABASE=1

[MS$IPX]
DriverName=IPX$
MediaType=Ethernet_II (DIX)
BINDINGS=MS$NE2CLONE


EXPLANATION FROM uSOFT.

The answer is basically that you will not be able run PDIPX, but you should
be able to get MSIPX and QVT/Net working together fine.  Right now your
protocol stacks look something like:
+-------+----------+
|PDIPX  | QVT's TCP|
+-------+----------+
|Packet Card Driver|
+------------------+
With WFW they would look like:
+--------+-----------+----------+
|NetBEUI | MSIPX.COM | QVT's TCP|
|vnb.386 | MSIPX.SYS | DIS_PKT  |
+--------+-----------+----------+
|      NDIS Card Driver         |
+-------------------------------+

With WFW you get all the pieces above except DIS_PKT which is a part of
the Clarkson distribution.  It provides a packet driver interface on the
top but sits on top of NDIS instead of a real card.

None of this is "officially" supported by Microsoft, but I'm certain it
will work.  If you run into trouble, with it give me a shout.

-Blake

-- 
The Wailer at the Gates of Dawn              | banshee@cats.UCSC.EDU       |
Just who ARE you calling a FROOFROO Head?    |                             |
DoD#0667  "Just a friend of the beast."      | banshee@ucscb.UCSC.EDU      |
2,3,5,7,13,17,19,31,61,89,107,127,521,607....| banshee@ucscb.BITNET        |
Technical Details
Message-ID: <1jpltgINN50q@darkstar.UCSC.EDU>
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!hal.com!darkstar.UCSC.EDU!cats.ucsc.edu!banshee

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!hal.com!darkstar.UCSC.EDU!cats.ucsc.edu!banshee
From: banshee@cats.ucsc.edu (Wailer at the Gates of Dawn)
Newsgroups: comp.os.ms-windows.setup
Subject: INFO: TCP on WFW -- READ THIS
Message-ID: <1jpltgINN50q@darkstar.UCSC.EDU>
Date: 22 Jan 93 20:37:04 GMT
Organization: University of California, Santa Cruz
Lines: 102
NNTP-Posting-Host: am.ucsc.edu