Date: Tue, 10 Jun 1997 15:33:40 GMT From: fran AT isis DOT demon DOT co DOT uk (Fran Berry) Organization: DIS(organised) Reply-To: fran AT isis DOT demon DOT co DOT uk Message-ID: <12439@isis.demon.co.uk> To: opendos AT delorie DOT com Subject: Re: observations about tcpip apps... Lines: 34 Precedence: bulk Im article you write: > If you're having problems getting arachne to run, the etherppp driver > is the solution. I used the outboard epp driver, and a small dialppp.cfg > file to connect it to the inet, but you have to connect after you start > arachne. Otherwise, it won't find the driver. But, aside from that, > Arachne is nice, and handles graphics well. Hmmm, that's not been my experience. I gave up on etherppp because on my hardware it's both slow and a memory hog. Both Bobcat and Arachne run with the same setup under Novell DOS 7 using dosppp05 and the same batchfile (who's format also did service with umslip/phone and slipper/netdial) with only the client name changed. That file dials, logs in, loads the driver high and then starts the client. It's yet to fail, but it should be noted that I have a permanent IP address so I've not had to fart about getting it. The trick is to use Bobcat's WATTCP.CFG file for both of them and massage Arachne.cfg file accordingly, including changing the Connection parm to READY. My impression is that whatever is in ARACHNE.CFG will override WATTCP.CFG (this may be duff gen since it's been a while since I played with it) so comment out in ARACHNE.CFG all of the stuff WATTCP.CFG holds. Since almost everything TCP/IP in DOS either needs or can use WATTCP.CFG (with the glorious exception of KA9Q :) it's worth taking the time to get one sorted out. Fran. -- _________________________________ ______ ( Fran Berry ) ( ) (_) fran AT isis DOT demon DOT co DOT uk (____) (___________ Know Thyself