>Date: Mon, 14 Feb 2000 09:01:52 -0500
>From: Roger Turk <[EMAIL PROTECTED]>
>Subject: Arachne load error
>
>Steve,
>
>I have Arachne loaded on two computers, one is a 586/133 MHz with 8 MB ram 
>(originally a 486/33 MHz) and the second is a P75 with 40 MB ram.  The best 
>that I can do on the 586/133 is Arachne 1.48.  1.49 (with dynamic images) 
>won't load or crashes, I don't remember which.  On the P75, I have 1.60b1 
>loaded and it works great!
>
>Suggestions:  Turn the animated X-I logo off.  (In ARACHNE.CFG look for 
>"Logo" and change it to read, "Logo 0".)
>
>In ARACHNE.CFG, do you have the home page set to "home.arachne.cz"?  At some 
>point Michael P. changed his URL to this, but I can't remember when.
>
>Hope this helps.
>
>Roger Turk
>Tucson, Arizona  USA
>
>Steve Evans wrote:
>
>>>I've been trying for months, off and on, to get past "Arachne load error".
>I seem to have gotten further than many new Arachne users.  For now, it is
>version 1.50 (had the same trouble with version 1.49).  Let me know if you
>think 1.60 has any real chance of faring better.
>
>I've tried it on two machines --one a 386 with 2 megs of RAM and the other a
>486 with 8 megs RAM -- same symptoms on both.  Using MS-DOS 6.22, no EMS,
>DOS loaded high.  Before starting Arachne MEM shows 697k of conventional
>memory free and 6.9 MB XMS free.  I have tried to configure it as simply as
>possible.  Modem is a US Robotics internal set to port 1, irq 4.  I tried
>setting slower speeds.  I have tried substituting the actual port address in
>the Arachne.cfg, but it makes no difference --connection is usually
>successful anyway.  I am using everything as the Arachne installation set up
>automatically.
>
Roger,

How come no-one before mentioned trouble loading on p75 or 586/133 before?
What OS are you using?

Steve,


Have you tried checking "use bootp" in the external dialer setup yet?
(I got a load error due to insufficient memory with 1.60, bootp was the
solution)

(if the package driver loads, modem and port settings must be good)

Bart

Reply via email to