[ back to ComRing page ]


First, you will need to get lsl, pdether, and the net.cfg
file for converting the packet driver interface to odi so
that windows can use it.

You can get the files in this zip file:
http://tamale.net/Windows/dosplip.zip
On computer 1 add these lines to the autoexec.bat: 
cd\comring
comring A
lsl
pdether
After doing so, make sure to edit the net.cfg and check the values (I recommend changing the INT to 0x60 and take the extraneous buffers line out of the link support layer section, it usually helps performance/stability).

Here is an example of a working net.cfg: 

Link Support
        Buffers 12 1514
Link Driver PDEther
        INT 0x60
        FRAME Ethernet_II
        PROTOCOL IP   800  Ethernet_II
        PROTOCOL ARP  806  Ethernet_II
        PROTOCOL RARP 8035 Ethernet_II
        PROTOCOL IPX  8137 Ethernet_II


NOTE: Windows 98 seems to do better with "Buffers 8 1514"
instead of "Buffers 12 1514".

On computer 2 add these lines to the autoexec.bat: 

cd\comring
comring B
lsl
pdether

Do the same thing to the net.cfg on the second computer. Note you can probably use this technique with multiple computers using a comring cable but since all I have is a null-modem cable that’s all I was able to test with. 


On computer 1 go into settings -> control panel -> network
and add adapter.

Select existing ODI adapter.

Next add the tcp/ip protocol.

Click properties on the tcp/ip protocol.

Click select ip address and type in 192.168.0.1 for the ip
address.

Type 255.255.0.0 for the submask.

If WINS is enabled make sure to disable it.

Next add the client for microsoft networks.

Don't ask me why it needs this but it won't work without it.

Change the Primary Network Logon to Windows Logon.

Click the ok button and you should see windows reading from
its install files installing stuff.

When it asks you if you want to restart/shutdown click no.
Edit the net.cfg file.

If it adds more frame types delete them because pdether
doesn't like any other frame type except ETHERNET_II.
Now you can reboot your computer.

Also note that you can probably use other protocols other
than tcp/ip such as ipx.  I haven’t tested this however
since most win95/win98 apps use tcp/ip.

Do the same thing for the second computer except type 192.168.0.2 as the ip address in the tcp/ip settings.

The problems I had with this setup is that sometimes ftp transfers would stop unexplainedly. Most of the time I could cancel the transfer and resume without having to reboot. I think it has something to do with the buffers setting. Also there is a performance hit. I'm not sure how much because I don't really care about it but it is there. Although considering the fact that you're doing full speed serial transfers it gives me the most cpu power than any other serial transfer program I've tried (i/e doing other things while its transferring a large file). Try playing with the buffers value, memory pool, upgrading lsl to better version, etc. if you’re not satisfied with the connection.

Note:

You can probably do win3.1 <--> win95/win98 although I haven't tested this. Also you can do dos <---> win95/win98 using ka9q nos or wattcp. I haven't tested this either.