On Sat, Jun 01, 2002 at 07:42:44PM +0000, Edenyard wrote: > On Wed, 29 May 2002 07:49:20 -0400 (EDT), Howard wrote: > > > I don't know anything about PCMCIA modems, but I have been playing > > around of late with a parallel port pocket modem (also "software > > driven") on an old 386 laptop, and am unable to load EPPPDD at all. > > However, both etherppp and LSPPP (new version .80) work well and I > > am running some smaller Internet apps. > > Thanks to both of you for the suggestions. I went off and located > LSPPP 0.8 and even read the instructions that came with it! Running it > on its own, I could get it to put all the essential information into > IP-UP.BAT, including DNS numbers. However, I simply could not get > Arachne to play ball with it. No fetching messages, no www pages - it > wouldn't even hang up properly. Trying it on my fully Arachne-working > office 486, it doesn't work there, where I know the original > bog-standard Arachne set-up works.
I just tried Arachne with LSPPP 0.8 on my desktop with internal hardware (ISA) modem (Practical) and found that: 1. It loaded from a fresh boot using it's own dialer and I was able to run Arachne and other programs. 2. It did not hangup and reset the modem when I unloaded it. If I tried to load it again it did not dial and hung on "Connecting to network...", requiring a reboot. My quick solution to #2 was to use my comm program (Conex) as a dialer which resets the modem before dialing and a utility called hangup.exe to make sure the modem is hung up after unloading LSPPP. See Sam's recent message with "Subject: How to use LSppp with modems that do not work with LSppp" where he uses COMTOOL as a dialer. > I went back to the LSPPP site and found two other things: LSPPPCFG > and also a patch for the CORE.EXE of Arachne V1.70r3. I followed all the > instructions for both and tried connecting again. Same result. I spent a > few hours messing about with this and it doesn't seem to be going > anywhere for me. I load the packet driver myself and run Arachne with Connection READY in arachne.cfg. I have always done it this way and never let Arachne mess with my packet driver setup. Howard E. -- <http://www.ncf.ca/~ag221/>
