docs/htmldocs/wfw_slip.htm

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