Hello John,
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.
JT>Actually, "EA DATA. SF" is intentionally fragmented to keep the 
JT>EA's physically close to the files they are associated with.  In 
JT>HPFS this happens automatically, but in FAT OS/2 has to do some 
JT>tricks to approximate the same thing.  OS/2's implementation of
JT>FAT (called "SuperFAT") is designed to operate that way; the EA's
JT>aren't simply written to the disk "wherever the heads on your
JT>harddrive happen to be at the time."
May or may not be, but, I stand by my statement "if you defrag your
fat drive, the 'ea data. sf' file should be defraged also.
Tim Taylor
timtaylor@tusco.net
timtaylor@clover.net
XXXWarpin Through The '90sXXX
___
 * MR/2 2.26 #337 * (Dos + Windows + ATM) < OS/2 Warp!
--- Maximus/2 2.02
---------------