On Fri, 11 Feb 2000 23:21:01 -0600, Jack Cotter wrote:

> Michael Dawley,

> This is a continuation - ran out of gas last night!

> I don't think the use of  EPPPDD is a solution to the problem .
> I suspect that there is a timing problem using EPPPD on these machines.
> Maybe the "DD" version will serve as a work around until a real solution
> can be found.

> I ran it with the normal Arachne setup last evening and the packet
> driver stayed resident for the first time on that machine using Arachne.
> However the redirected output to ppp.log caused Arachne to kack, but the
> driver was resident.

> I'm in a catch 22 right now with Arachne. The packet driver WILL NOT
> stay resident using EPPPD so I can't see what's wrong. It WILL stay
> resident with the diagnostic version, but then there is nothing wrong!
> Probably have to do a quick learn on DOS standard error.

<snip>

Jack,
 Something just occurred to me.
Are you loading EPPPD "high" with
Connection @lh epppd.exe>>PPP.LOG

If so, then you'll need to change this line
IP_Address PPP

Change it to
IP_Address BOOTP

With "IP_Address PPP", Arachne looks at PPP.LOG to see if EPPPD is loaded
With "IP_Address BOOTP", PPP.LOG is not used to see if you are online.

I am currently connected using
Connection @lh epppd.exe>>PPP.LOG
IP_Address BOOTP
IP_Grab IP address set to

This is my current PPP.LOG
---begin PPP.LOG---
---end PPP.LOG---

That's right.... it does not exist.

 For some reason that I do not understand, the redirect into PPP.LOG is
not working when EPPPD is loaded high.

 This might explain why it works OK with EPPPDD (debug version)
Perhaps the redirect into PPP.LOG _is_ working when EPPPDD is loaded high.

I'll get EPPPDD and test this theory.
------------------------

 That was it!!!
Here's my current setup.

Connection @lh epppdd.exe>PPP.LOG
IP_Address PPP
IP_Grab local

---begin PPP.LOG---
sifaddr ppp0: local 204.179.144.60, remote 204.179.144.20, netmask 255.255.255.0.
---end PPP.LOG---

 As you see, I also had to change my IP_Grab line to indicate "local".
(the word preceding my IP address in PPP.LOG)
When using EPPPD.EXE, this doesn't seem to matter.
("IP address set to" is _not_ what my ISP sends)

 So, from what I can see.
This problem exists only if EPPPD.EXE is loaded "high".
EPPPDD.EXE _can_ be loaded high and everything works fine.

-- 
Glenn McCorkle [EMAIL PROTECTED] North Jackson, Ohio, USA
DOS prog. for QV cameras http://www.angelfire.com/id/glenndoom/qvplay.html
Other stuff http:[EMAIL PROTECTED]/
            Arachne, The Web Browser for DOS
   Open the 'DOOR' to the WWW. Keep the 'windows' closed.
      http://arachne.browser.org/ http://arachne.cz/

Reply via email to