I've discovered a way to run WfW's TCP/IP-32 over a SLIP packet driver. This allows WfW users to do Windows networking over dialup lines just like it is possible with NT and the Windows 95 beta!
For instance, you can mount Microsoft's FTP server as a network drive in File Manager or connect to an MS Mail post office over the Internet. Of course, the usual Internet stuff works as well. Another interesting site is WINSERVE.001; check out www.winserve.com.
Microsoft's free TCP/IP for WfW. It's a self-extracting archive which should be executed in an empty directory.
Peter Tattam's SLIP packet driver. CSLIPPER.EXE is a variant which supports VJ header compression.
Don Provan's ODI-over-Packet Driver shim. This *must* be version 1.05 (or above).
Novell's LAN Support Layer. If you're an owner of Windows 3.10, you'll have it on one of your install disks. Use "expand a:lsl.co_ lsl.com" to expand it. Microsoft has stopped bundling LSL.COM with WfW 3.11, though. The newest version of LSL.COM can be downloaded as part of ftp://ftp.novell.com/pub/netware/nwos/dosclnt12/vlms/vlmup2.exe. However, it's not clear if this one may be legally used outside Netware environments.
A configuration file for LSL and PDETHER. It should contain the following text:
Link Support Buffers 8 1600 Link Driver PDETHER Int 60 Frame Ethernet_II Protocol IP 800 Ethernet_II Protocol ARP 806 Ethernet_II Protocol RARP 8035 Ethernet_II
A little hack of mine to disable the COM port used by the SLIP packet driver. Usage is e.g. "discomx 2" to disable COM2. This should be run before starting WfW, otherwise you'll get "device conflict" messages. Here it is:
begin 644 discomx.com F,=N)V8H.@`"P(+^!`/.N3XH="=MT!DN`XP/1XS')!R:)CP`$S2`` ` end(Save this text to disk as filename, then run "uudecode filename". uudecode can be found, for instance, at ftp://ftp.switch.ch/mirror/simtel/msdos/starter/uudecode.com )
An optional file which should be stored in your Windows subdirectory. It is used to map NetBIOS computer names to IP addresses. Example:
18.104.22.168 ftp #PRE # ftp.microsoft.com 22.214.171.124 winserve.001 #PRE # Winserve
cd \slip slipper com1 vec=60 baud=57600 ether (may vary with your modem setup) lsl pdether discomx 1 (must correspond to SLIPPER's COM port)(If you use another vec= setting, you must update that in NET.CFG as well.) Use CSLIPPER instead of SLIPPER if your SLIP provider supports VJC.
c:\windows\net start c:\windows\odihlp.exe.The "odihlp" line must be moved behind the "pdether" line.
Microsoft's TCP/IP-32 requires an NDIS3 interface. NDIS is Microsoft's way to interface with a network.
WfW also contains an NDIS3-over-ODI "shim", whose real mode component is ODIHLP.EXE. ODI is Novell's way to interface with a network.
SLIPPER is a Packet Driver (PD) for use over serial lines. PDs are everybody else's way to interface with a network. SLIPPER's "ether" option makes it look like an Ethernet PD to applications using it.
A "shim" is a program which simulates a network application programming interface on top of another.
There is no NDIS SLIP driver which would work with WfW.
There is no NDIS-over-PD shim.
However, there's an ODI-over-PD shim (PDETHER) and an NDIS-over-ODI shim (ODIHLP etc.)
OK, so let's do NDIS-over-ODI-over-PD!
This should have worked all the time; however, a non-feature in PDETHER versions < 1.05 has prevented the method from functioning until now.
Peter Karrer email@example.com