🚀 go-pugleaf

prplhaze (prplhaze@metronet.com) wrote:
> problem: random development 3 times in 2 months of x-linked files in 
> windows dir with loss of all files and subdirectories. this is NOT 
> preceeded by gpf or system freeze; no problems with actively running 
> programs prior to closing windows before this occurs.
[snip]
> occurrence: at random times during bootup or typing win from dos prompt
> get "bad command or filename" message        ^^^^^^^^^^
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   How appropriate!  :-)

> dos runs fine
> from dos "dir" of c:\windows reveals no file listing
> scandisk reports many x-linked files and scandisk.log localizes x-linked 
> files to c:\windows after running "autofix"
> surface scan of hd is clean
> viral scans with fprot and wscan negative each time
> when restore c:\windows from tape backup able to run windows ok; no other
> programs seem affected and can't find evidence of data loss elsewhere.
> rechecked scsi cable connections, id #s, termination, etc; reseated card

> questions:
> 1. why only involvement of windows directory

   Probably because whatever is corrupted (or rogue) is in the WINDOWS 
subdirectory, and only is affecting the current directory.

> 2. what is process in disk writing that creates x-linked files - is this
> software;scsi bios/adapter;hd disk cache.

   It shouldn't ever happen.  DOS puts data in a buffer and tells the 
BIOS to write it to the FAT.  The data goes through the cable through the 
adaptor.  Then through another cable to the h/w cache if any, and then to 
the platter.  Now if there's any corruption going on after DOS sends it, 
one would expect other data to be garbled as well.  If your recently 
modified files are otherwise ok, it's most likely to be software.

> 3.what writes to fat as this seems to be corrupted

   It should be only DOS or utilities like CHKDSK or Norton Disk Doctor 
or DISKEDIT.  Of course, sometimes there's a bad pointer that causes 
corruption; I've seen parts of WordPerfect files in the FAT, and Word 4.0 
(DOS) used to trash disks sometimes.

> 4.anyone aware of hardware/software with direct disk access that may 
> write to or affect fat or hd.

   Viruses (shouldn't be a problem here, given that you used F-PROT 
v.219), the aforementioned utilities.  Hardware would have to be pretty 
specialized, and you'd know you have it.

> 5. pointers, suggestions; where do i go from here? is this a sign of 
> intermittent failure of a component which is about to fail totally?

   I'd try reinstalling Windows (and perhaps your Win apps) from originals
rather than tape.  If your backup is corrupted and you reinstall, you
merely reintroduce the problem.  You might want to keep Dr.  Watson
running to see whether it picks up anything (probably won't help, but 
unlikely to hurt).  Consider installing DOS from originals as well.  
Again, not likely to help, but what the heck.
   Make sure that you are using the upgrades of your software, e.g., Word 
6.0.x instead of just 6.0  I think it's up to revision 6.0.c now.
   If the corruption continues, I'd take a look at the FAT with a disk
utility to see exactly what happened.  It might help to show what
happened. 

> thanks much; i'm really stumped here because i can't predict when it will 
> occur and changes i make have to wait and see.

   Hope this helps.  Keep us posted.

   -BPB