TT> The file "EA DATA. SF" gets very fragmented, this is the way OS/2
TT> stores the EA's on a fat drive. OS/2 puts the EA data wherever the
TT> heads on your harddrive happen to be at the time. This is usally by
TT> the file they are ment for. BUT, when you defrag your fat drive the EA
TT> file is EVERYWHERE and really causes a big slowdown. On one of my
TT> systems here a defrag of this file speeded up disk access by 3 times.
Actually, "EA DATA. SF" is intentionally fragmented to keep the 
EA's physically close to the files they are associated with.  In 
HPFS this happens automatically, but in FAT OS/2 has to do some 
tricks to approximate the same thing.  OS/2's implementation of
FAT (called "SuperFAT") is designed to operate that way; the EA's
aren't simply written to the disk "wherever the heads on your
harddrive happen to be at the time."
 * KWQ/2 1.2i * Internet: John.Thompson@ibm.net
--- OS/2 Warp\FastEcho\FD\ProBoard
(1:139/655)
---------------