On 7 Jan 00, at 6:26, Klaus Hameyer wrote:
However, the COMPAQ still balks. I split the batch files
into pieces and it is definitely the packet driver that
is holding up the show on the COMPAQ. I doubt whether
the problem is in memory since I am running DR-DOS 7 and
MEM shows 618 bytes free.
----------------------------------------------------------
Klaus,
When I first got this combination to work, I found that my
login script, netdial.scr was somehow stopping the
packet driver, so I removed the last two lines of the
original and it worked. You have my working netdial.scr
file. Also, have you been able to load
epppd high? Mine is often 70K, and needs to go high
if possible to get it out of arachne's conventional memory
area. One way to get a memory report within Arachne
is Desktop-Tools-Memory. I do this now on
arachne installations where I cannot connect. Your
problem may not be in total memory available, but
in conflicts between items getting placed in various
locations in memory. I have a graphics
card for my Compaq, so I could get 16.7 m colors,
and I found that dmouse.com or fmouse.com would
conflict to the point that when Arachne tried to boot
up after the packet driver loaded, etc. my screen
would go blank. I had to just turn the machine off,
and go back to my 25K logitech mouse driver on this
one. On my Compudyne, with a Tsang graphics card,
I can use dmouse.com just fine, and save some
memory. Also, I have heard that some programs
expand a little when running:
--------------------------------------------------------------------
"Some device drivers load in at one size but expand
to grab more memory when they begin to run"
-------------------------------------------------------------------
This relates to the DEVICEHIGH SIZE command,
like this: devicehigh size=39E0 mouse.sys
according to my dos 5 book. I have not had to
use this myself and have no experience with it.
-------------------------------------------------------------------
Another item to try is to REM out various lines in
autoexec.bat on a trial basis to see if one of them
is conflicting somehow. I found share.exe to be one
that was suspect. There may be others, drivers, etc.
that could be conflicting. If you find one that's it,
you may have to specify a memory area for it,
This is a little hard to control, so I just REM out
items until Arachne connects. or try
and do without the item. Check also in config.sys.
-----------------------------------------------------------
All of this is just thoughts to give you the benefit
of my latest work on it. Hopefully others will
contribute also, especially if and when you narrow
the problem down.
Thanks,
Michael L. Dawley
Pearl, Mississippi
Compaq Deskpro 575 - Pegasus Mail for Windows
