#NULL: Device Problems
7 messages in this thread
Betty,
I need some help. I have a 500 with 1 MEG and another Drive,
Lately I had redone my startup sequence to use the new versions of DMOUSE V
1.25, and RUNBACK both of these use a NULL device which I have in my
mountlist but I have both programs using the same NULL: Device. I am also
running FAC II with a 64K buffer also VirusX 4.00 and JR-Beep. My question
is, ever sence I made these changes my 500 has been locking up no GURU's
just lockup's that I can not recover from, any thing that might help would
be helpful…
Thanks,
Bill Bryan
Bill,
One idea, do you have 'Mount NULL:' before you start dmouse or use
runback etc… also make sure that all programs that will keep running are
RUN'd (I had safereboot in my startup without running it once and the
computer just stopped when it got to it.)
Hope it's something like that, Greg.
Greg,
I have mounted the NULL: device in my startup sequence before
I used DMOUSE or RUNBACK, and every thing in the sequence has been RAN
except the AUTO-DETACHING Programs (I.E. DMOUSE). Any more ideas???
Thanks for the Help!
Bill Bryan
William,
Try MemGuard (It's on CIS, I don't remember where). At least that will tell
you when a prog is trashing low memory area.
I don't know how much this will help, but it may lead you twords the
answers.
JohnB 76256,3436
John,
Thanks for the Help!
Bill Bryan
Bill,
Usually the easiest way to locate the problem is to take away everything
you are using that is not standard – that is, comment out every one of
those new things from your startup-sequence. Then, add back one and try it
for a few days to make sure it is working OK. Then, add another – and so
on until you find the one that is causing the lockup. If that one is very
important to you, you might then try taking away one of the less important
ones at a time until you find out if two of the utilities are causing each
other to lock up. Isolating each one to try is the only way I know to
locate the one giving problems.
Betty
Betty,
Thanks, I 'll try and let you know!
Bill Bryan