Hi LD,

  LB>I cleaned up almost 6Mb of chains on the HDD before I installed 1.64

  LB>I then read & wrote some mail, visited a couple of web sites [Yahoo
  LB>yellow pages, a cartoon-a-week site] and exited Arachne.  Just out of
  LB>curiosity I did chkdsk/f again ... to see if maybe the lost chains
  LB>problem had been reduced.

  LB>Much to my shock I discovered that it was even worse than before!  500
  LB>plus chains made into files, and in checking the files I find every
  LB>message a wrote ended up as a chain, every GIF I visited, etc.


Good grief!

You have a sick system there, LD.

My boot-up always runs Norton Disk Doctor on my drives when I switch
on every morning (and the computer stays running until 10 every night).
I find a lost chain maybe once every 6 months, usually if I've been
playing with a new program or something that caused a major crash.

I've also been using the latest version of Arachne daily for the past
3 years and it has never caused problems like yours.

What OS are you using? I run MS-DOS 6.22 (+ 4DOS v5.0).
What disk-cache program are you using? I think it would be
very useful to try a different one and see if it makes any
difference.

Do you have another computer you could try, just as a temporary
trial? It could be that your disk-controller (or HD) is sick.

Whatever the reason, you have a serious problem, and I don't
think Arachne can be blamed, even though it is showing up your
problem.

Best regards,
Mike
   It
  LB>must have been just about everything that appeared on the screen that ended
  LB>up as a loose chain.  And these were *full* files, not just bits and
  LB>pieces mooshed together like before.

  LB>And no, they are NOT from Arachne crashes.  I didn't do the mail in 1
  LB>.64
  LB>as "installed" ... didn't do anything in 1.64 except look at a blank
  LB>page and watch the DNS ani-GIF spin.  Since I "upgraded" rather than
  LB>did
  LB>a new install, there have been no crashes.

  LB>I really don't want to have to rewrite my batch file for Arachne to
  LB>automatically do the chkdks/f and delete every chk file it finds. :<

  LB>l.d.


Reply via email to