(Sorry I can't quote, I'm on the digest mode)

        Examining your autoexec.bat and config.sys I found out the 
following:

        You are using an old TCP/IP stack from Microsoft which 
isn't reliable. My advice is to dump it and use TCP 32B which is 
better. On the other hand, Arachne doesn't need a TCP/IP stack, as 
she already uses the built-in WATTCP. 
The aim is to find a packet driver suitable for your network card. 
If you still have got the installation diskette for your NIC, 
you'll find one there. If you don't have it, but you are aware of 
the type of the NIC, you'll be able to find a packet driver on the 
 Internet. Install the packet driver in the autoexec.bat. Don't 
forget to specify the vector, (usually 0x60),the interrupt and the 
I/O address used by the network adapter (you will find those most 
probably by thoroughly searching the "protocol.ini" file in 
Windows directory). 
        TCP 32B doesnt't load any TSR's at startup so you'll have 
plenty of conventional memory. You don't need Win32s to run it.
        The next step is to switch the Win98 machines to use 
TCP/IP as transport for the peer-to-peer network.(if you haven't 
already done this).
        Arachne will work in pure DOS. You won't be able to run it 
from the DOS prompt.
        This configuration works like a charm for me on a LAN with 
an NT server (not connected to the internet), a Linux server, 
about 40 Win'98 machines and several DOS/WIN3.xx ones. To connect 
to the Internet I need to supply Arachne with my IP (fixed, BOOTP 
doesn't work), the gateway's IP (to get out from LAN) and a DNS 
server (any of them works, as long as you know the gateway). I 
believe (but I don't know for sure) the Sygate acts like a 
gateway. My machine is a 486DLC/40Mhz with 8 MB RAM and an 
genuine NE2000 network card. I use the packet driver supplied with 
Arachne.
 
I wish you good luck!

Cristian Burneci
   

Reply via email to