Rick,
I read your last two shares many times; and then just stewed for a bit. No
grumble, I agree with your logic completely. And, I understand all the
legacy issues in the eide system related to OS business. Here, I only use
W2Kpro or WinXPpro; and both w/NTFS filing systems.
I do accept that my trouble was the size of the disk (160GB) and the bios
of the m/b. Unfortunately, bios CR (often referred to as a final
Compliance Release) is/was the last bios for this old soldier. And, IIRC,
the increasing sizes of drives at that time was the driver for this CR
bios. It now appears that ABIT got it wrong way back when. No harm, no
foul. Stuff happens.
I did go back in my files and I still have the bios image just prior to CR.
Even thought of flashing back; for about a Usec! Nah. The machine is
retired; until I stumble on an old 40-80GB pata hard drive for cheap.
Thank you for the salient comments.
Duncan
At 17:03 10/26/2008 -0400, you wrote:
I agreed...
I listed three things and said to stay under 120G to avoid them all...
Then listed the one (the OS) most likely to be a problem.
Rick Glazier
--------------------------------------------------
From: "maccrawj"
UltraATA controller w/ BIOS support for LBA48 trumps system BIOS limits
on size.
Rick Glazier wrote:
Philosophy aside, you can sometimes get a PCI MB to boot from a UltraATA
controller card
and use a HD larger than 137G (or so), but getting the right combination
of MB BIOS booting
options and chipset driver and OS compatibility can be a problem.
Like someone said, if you stay under 120G, you might not trip any
limitations.
(Even the OSs will have HD size limitations...)
Mixing new with old can get messy fast...
