Haven't been using system much last couple of days, so hadn't done much
house cleaning. However, my son has been using the system rather
intensively [he moderates some web game chats, and is working with a
friend in Japan doing translations of Japanese games [PlayStation, etc]
into English. Much of it is highly graphics intensive, since everything
on games that isn't sound is graphics. <G>
So, being in only the base command.com shell, I did the terrifying
chkdsk/f
1,537 lost allocation units in 524 chains; 504 files resulted because DOS
ran out of directory entires at that point; deleting those files and doing
another chkdsk/f produced the remaining 20 files.
Over 3Mbytes of files.
No way was I going to check each file to see what it contained, but a
quick check of first 35 plus random checks produced pretty much the
results I expected.
smtp.log with something else appended -- 14 out of 35
html -- 1 out of 35
JFIF -- 12 out of 35
GIF89a -- 8 out of 35
So far the following items have been absolved of blame: computers [3],
SCSI Host Adapter Card, Smartdrive, NCache.
Since my son approaches a computer in a manner totally different from
mine, I think we should be able to rule out "operator error" also.
I did find one other horrendously big chain lying around on my C drive;
it appeared to be the graphics overlay for some graphic manipulation
program ... which I don't have on C: anywhere. So I have *NO* idea
where that 3.5Megabytes came from.
l.d.
P.S. Just about had dual heart failures around here today; it took me a
couple of years to put together the AutoCAD system my son uses, and more
than a few missed dinners out. Today when he installed his new CD drive
[multi-media to the max even] the computer started making a very
not-nice beep that didn't sound at all like a POST error message. Off
came the case, out came components, back went components one at a time
until that SOUND occurred again! It was his multi-GIG SCSI HDD where
the trouble lay. He had a bug on his HDD!! arghhhhh!!!! What can you
do? I suggested he replace ribbon cable or use a different attachment
on the multi-link cable he was using. And he eyeballed it very
carefully ... then he eyeballed it some more ... and voila! He *found*
the bug on his HDD! Literally, there was a bug on the HDD that had
managed to get between two pins of one of the switches and incinerate
itself into nice conductive carbon which then set the switch how it
shouldn't be set ... and cause that horrible SOUND, the cry of a drive
in trouble. He removed said cremated insect, cleaned carefully around
the pins of the switch, hooked up ribbon & power, and problem all gone
bye-bye. SHEEESH ... Well, at least that's one bug I can' blame on
Arachne; it's not on that system. <G>
--
Learn about B'FOR
Join B'FOR - B'mothers For Open Records
<a href="http://www.b-for.org">B'FOR www.b-for.org</a>
[Associate members of triad also welcome; membership confidential if desired.]
-- Arachne V1.64, NON-COMMERCIAL copy, http://arachne.cz/
