* An ongoing debate between Jasen Betts and Ben Ritchey rages on ...

 BR>> then it DOES exit properly, BUT the reason I'm running NDD is
 BR>> because of expected known errors in the directory structure
 BR>> (created by Linux probably & always there weekly). I can

 JB: > What does linux do to your disk? (what does NDD find)
 JB: > what kernel version? how are you mounting the disks? (or are you
 JB: > using mtools?)

The problem surfaced recently when trying to Defrag C: (it consistently
encountered out-of-memory errors while optimizing the directory that I could
not resolve by temporarily moving the majority of C: files to another drive
OR by skipping the optimization). I could not "see" anything
wrong, anywhere.
Normal daily operations were running flawlessly . Even Scandisk said all
was well ...

I ended up moving ALL of them, re-formatting, then moving them back (a manual
"defrag"). A few weeks later, same thing. Since only DOS &
Linux access the C:
drive it had to be one or the other.

After testing a new version of NDD on C:, and noticing that it "fixed" the
directory structure (NDD report showed invalid LFNs for several sub-dirs that I
only write to under Linux). Subsequent testing showed the NDD fix only worked
right after a Defrag when all LFN's were orphaned (a single Linux job would
void this ability to fix using NDD).

So  I figured the best thing would be an automatic NDD right after my
weekly defrag , but it's not so automatic. :(

Due to hardware limitations, I am using Mandrake-Linux v7.1 (kernel 2.2x). It
employs a standard mount for DOS partitions as vfat fs (I will eventually HAVE
to use mtools once I have DOSEmu running to my satisfaction) based on fstab.

--
Be well,

 : Ben   aka cMech    http://bellsouthpwp.net/c/m/cmech617/
 :
 +    WildCat! Board 24/7  (337) 232-4155  33.6kBps 8,N,1
--- GoldED+/DPMI32 v1.1.5-040330 r0405