3 <TITLE>Peter Karrer Announces SLIP for WFW</TITLE>
\r
6 <H1><I>Winserve</I></H1>
\r
8 <H2><I>Peter Karrer Announces SLIP for WFW</I></H2>
\r
13 I've discovered a way to run WfW's TCP/IP-32 over a SLIP packet driver. This
\r
14 allows WfW users to do Windows networking over dialup lines just like it is
\r
15 possible with NT and the Windows 95 beta!
\r
17 For instance, you can mount Microsoft's FTP server as a network drive in File
\r
18 Manager or connect to an MS Mail post office over the Internet. Of course,
\r
19 the usual Internet stuff works as well. Another interesting site is
\r
20 WINSERVE.001; check out www.winserve.com.
\r
22 This method should work with any class 1 (Ethernet II) packet driver. However,
\r
23 I'm not in a position to try anything else than SLIPPER/CSLIPPER.
\r
25 <H3>Files you need:</H3>
\r
26 <B>WFWT32.EXE:</B> ftp://ftp.microsoft.com/bussys/msclient/wfw/wfwt32.exe
\r
28 Microsoft's free TCP/IP for WfW. It's a self-extracting archive which
\r
29 should be executed in an empty directory.
\r
31 <B>SLIPPER.EXE:</B> ftp://biocserver.bioc.cwru.edu/pub/dos/slipper/slippr15.zip
\r
33 Peter Tattam's SLIP packet driver. CSLIPPER.EXE is a variant which supports
\r
34 VJ header compression.
\r
36 <B>PDETHER.EXE:</B> ftp://sjf-lwp.idz.sjf.novell.com/odi/pdether/pde105.zip
\r
38 Don Provan's ODI-over-Packet Driver shim. This *must* be version 1.05 (or
\r
43 Novell's LAN Support Layer. If you're an owner of Windows 3.10, you'll
\r
44 have it on one of your install disks. Use "expand a:lsl.co_ lsl.com" to
\r
45 expand it. Microsoft has stopped bundling LSL.COM with WfW 3.11, though.
\r
46 The newest version of LSL.COM can be downloaded as part of
\r
47 ftp://ftp.novell.com/pub/netware/nwos/dosclnt12/vlms/vlmup2.exe.
\r
48 However, it's not clear if this one may be legally used outside Netware
\r
53 A configuration file for LSL and PDETHER. It should contain the following
\r
62 Protocol IP 800 Ethernet_II
\r
63 Protocol ARP 806 Ethernet_II
\r
64 Protocol RARP 8035 Ethernet_II
\r
69 A little hack of mine to disable the COM port used by the SLIP packet driver.
\r
70 Usage is e.g. "discomx 2" to disable COM2. This should be run before
\r
71 starting WfW, otherwise you'll get "device conflict" messages. Here it is:
\r
73 begin 644 discomx.com
\r
74 F,=N)V8H.@`"P(+^!`/.N3XH="=MT!DN`XP/1XS')!R:)CP`$S2``
\r
78 (Save this text to disk as <I>filename</I>, then run "uudecode <I>filename</I>".
\r
79 uudecode can be found, for instance, at
\r
80 ftp://ftp.switch.ch/mirror/simtel/msdos/starter/uudecode.com )
\r
84 An optional file which should be stored in your Windows subdirectory. It is
\r
85 used to map NetBIOS computer names to IP addresses. Example:
\r
88 198.105.232.1 ftp #PRE # ftp.microsoft.com
\r
89 204.118.34.11 winserve.001 #PRE # Winserve
\r
92 <H3>How to install it:</H3>
\r
95 <LI>Put the files mentioned above into a directory, e.g. C:\SLIP.
\r
97 <LI>Put the following lines into AUTOEXEC.BAT:
\r
100 slipper com1 vec=60 baud=57600 ether (may vary with your modem setup)
\r
103 discomx 1 (must correspond to SLIPPER's COM port)
\r
105 (If you use another vec= setting, you must update that in NET.CFG as well.)
\r
106 Use CSLIPPER instead of SLIPPER if your SLIP provider supports VJC.
\r
110 <LI>Under Windows Setup, choose "Change Network Settings".
\r
111 <LI>Select "Install Microsoft Windows Network".
\r
112 <LI>In "Drivers...", choose "Add Adapter"
\r
113 and install the "IPXODI Support driver (Ethernet) [ODI/NDIS3]".
\r
114 <LI>In "Add Protocols...", select "Unlisted or Updated Protocol". When asked for a
\r
115 driver disk, enter the directory where you expanded WFWT32.EXE.
\r
116 <LI>Configure TCP/IP (IP address, enable LMHOSTS lookup, try 204.118.34.11 as primary
\r
117 WINS server). Remove all other protocols (NetBEUI, IPX/SPX).
\r
120 <LI>Windows will probably update the first lines of AUTOEXEC.BAT with
\r
123 c:\windows\net start
\r
124 c:\windows\odihlp.exe.
\r
126 The "odihlp" line must be moved behind the "pdether" line.
\r
128 <LI>Windows will also update NET.CFG with some "Frame" lines. These must
\r
129 be removed (except "Frame Ethernet_II").
\r
131 <LI>Somehow, you will have to dial in to your SLIP provider. I do it manually
\r
132 before slipper (or cslipper) gets loaded, using a DOS-based terminal program.
\r
133 But there are some automatic dialers around. I've seen recommendations for
\r
134 ftp://mvmpc9.ciw.uni-karlsruhe.de/x-slip/slip_it.exe.
\r
136 <LI>To connect to Microsoft's FTP server (or Winserve) go into File Manager,
\r
137 choose "Connect Network drive" and enter "\\ftp" or "\\winserve.001" into
\r
141 <H3>How it works:</H3>
\r
143 Microsoft's TCP/IP-32 requires an NDIS3 interface. NDIS is Microsoft's way
\r
144 to interface with a network.
\r
146 WfW also contains an NDIS3-over-ODI "shim", whose real mode component is
\r
147 ODIHLP.EXE. ODI is Novell's way to interface with a network.
\r
149 SLIPPER is a Packet Driver (PD) for use over serial lines. PDs are everybody
\r
150 else's way to interface with a network. SLIPPER's "ether" option makes it
\r
151 look like an Ethernet PD to applications using it.
\r
153 A "shim" is a program which simulates a network application programming
\r
154 interface on top of another.
\r
156 There is no NDIS SLIP driver which would work with WfW.
\r
158 There is no NDIS-over-PD shim.
\r
160 However, there's an ODI-over-PD shim (PDETHER) and an NDIS-over-ODI shim
\r
163 OK, so let's do NDIS-over-ODI-over-PD!
\r
165 This should have worked all the time; however, a non-feature in PDETHER
\r
166 versions < 1.05 has prevented the method from functioning until now.
\r
168 <B>Questions, suggestions etc. please to
\r
171 Peter Karrer pkarrer@ife.ee.ethz.ch
\r