Mike,
My system is not sick. My HDD is not sick. My controller is not sick.
Those things don't often cause "lost chains" anyway.
If it were my system, my HDD, my controller, or just my inneptitude,
then "lost chains" in the hundreds would show up on *every* partition
and logical drive on my HDD, with more chains showing up on the drives
accessed the most -- like C: where DOS resides or H: where the games are
that everyone plays.
The problem has been that Arachne somehow just doesn't handle things
well, and "lost chains" linked to Arachne -- or at least crashes of
Arachne -- have been around for a *very* long time.
I went through approximately 30 pieces of mail yesterday after clearing
out the chains, my son was on about 1.5 hours today because he moderates
a "chat" about video games, and I've gone through about 20 pieces of
mail today ... and chkdsk/f showed 604 allocation units lying around
that were placed into 170 files.
No lost chains on *any* of the other drives -- C: thru' U: -- just on
the J: where Arachne lives.
BTW, the disk cache isn't the problem because it happens reguardless of
which one is used; temp files aren't the problem because temp is set to
the RAM drive; I routinely use Norton to check and optimize my drives,
and SCSI drives are notoriously reliable to begin with. The problem has
always lain within Arachne. Michael apparently changed something to
make things "run better" and files simply are not being properly
"deleted" at all now. It used to be an attempt to recover what
purported to be a complete file would often result in a corrupted mess;
now I'm afraid to look at what trying to unerase a "deleted file" would
produce.
l.d.
P.S. There have been no crashes since the flawed install yesterday.
