"cquirke (MVP Windows shell/user)" <
[email protected]>
I ran two 100gb drives in a hardware RAID0 array in Win98SE for a year or
more without problems. SE saw the drive as 200gb and never burped. I never
came even close to filling it with data, nor was even 137gb approached, but
the full 200gb was recognized by the OS.
That's very interesting, and surprising - though perhaps less so, if
never filled up. I use Win98SE DOS Mode as a side-boot for XP, and
I've had varying mileage there. Usually, everything works - F-Prot
for DOS scans everything even on F: (the last 2G on the HD), ScanDisk
is OK, etc. But sometimes, if E: is full (crossing the 137G?) I get
serious data corruption if I push my luck, e.g. dirs full of trash
names as arbitrary data is seen as the "dir", etc.
Also, on such full E:, I get F-Prot throwing "unable to read..."
errors when scanning from DOS mode.
I've also seen tragedies when > 137G HDs are used from XP Gold, i.e.
before SP1. Bonked partition tables, boot records, ugly stuff.
When you say RAID, do you mean RAID 0 as 200G, or RAID 1 mirroring so
that the same data's on both as 100G? Where do you find 100G HDs, are
they SCSI or something? I've only seen 80G and then 120G. Did you
have to use "special" drivers and partition types for the RAID? If
so, then perhaps that extended the OS's capabilities?
------------ ----- ---- --- -- - - - -
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
