Arachne at FreeLists---The Arachne Fan Club!
On Wed, 21 Jul 2004 13:08:45 -0500, Sam Ewalt wrote:
> I already know that Arachne runs normally after SCANDISK has made
> repairs. It always does.
Yes, you said that. But what we need is to see whether the files
are damaged _before_ Arachne crashes.
> If I run SCANDISK first then Arachne won't
> crash. But I'd have to run it everytime before I start Arachne as
> the problem is very intermittent.
Yes, you WILL have to run it every time until we get the
information we need.
You can run SCANDISK /CHECKONLY which will check the files
without repairing any damaged ones. Then if you run Arachne and
it crashes, and you then run SCANDISK again, you can see whether
the same files (if any) are the only ones damaged, or whether
Arachne's crash has damaged some more.
What we need to know is whether Arachne is crashing BECAUSE files
are damaged, or whether the damage is cause by the crash.
>> @echo off
>> rem this is the batch file SPIDER.BAT
>> rem to run ScanDisk before Arachne is started.
>> scandisk.exe
>> cd\arachne
>> arachne.bat
> This batch file wouldn't work anyway as SCANDISK asks questions that
> require answers when it finds problems. And then has to be
> exited manually.
No it won't work totally automatically. And that is just as well,
because we need to know the results of the scan before Arachne is
run, to see whether the damaged files are the CAUSE of Arachne
crashing.
I would suggest that you alter the fourth line to
scandisk /checkonly
which requires you only to press "X" if no errors are found.
Then if Arachne crashes ONLY when it is run from damaged files,
we can be pretty sure that the damage in the files is the CAUSE
and not the RESULT of the crash.
,-./\ from Greg Mayman, in Adelaide, South Australia
/ \ "Queen City of The South" 34:55 S 138:36 E
\_,-*_/
v homepage http://users.tpg.com.au/gmone/index.htm
Arachne at FreeLists
-- Arachne, The Web Browser/Suite for DOS and Linux --