Perhaps you are remembering this
http://support.microsoft.com/kb/305098
NOTE: If you enable 48-bit LBA ATAPI support by editing the preceding
registry key, but your system does not meet the minimum requirements,
you may observe the following behaviors:
Operating systems that do not have 48-bit LBA support enabled by default
(such as Microsoft Windows 98, Microsoft Windows Millennium Edition
(Me), or Windows 2000) that are installed on a partition that spans
beyond the 28-bit LBA boundary (137GB) will experience data corruption
or data loss.
DL wrote:
> I wish I could locate the Tech link that said otherwise
>
> "Pegasus (MVP)" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>>"Gordon Biggar" <(E-Mail Removed)> wrote in message
>>news:OxQN5$(E-Mail Removed)...
>>
>>>I have two older desktops (circa 2001-2002) that are using Intel boards.
>>>On
>>>the "later" of the two boards, I was able to download Intel's v. 19 of
>>>its
>>>Bios updates in order that the computer would recognize large-size disc
>>>drives (320 GB in the case of the later computer).
>>>
>>>I am running a 200 GB hard drive on the older of the two desktops, but
>>>the
>>>Intel download for that board is only v. 10, I believe. I don't think
>>>that
>>>that version supports the (48-bit?) software incorporated to enable
>>>large-drive recognition (I'm over my head here!). If I go to My Computer
>>>on
>>>this older desktop, the properties of my C drive are shown as 200 GB, but
>>>in
>>>the bios it only recognizes 137 GB (or thereabouts).
>>>
>>>What will happen as I approach this upper limit on the older computer?
>>>Is a
>>>simple workaround one of partitioning one's hard drive?
>>>
>>>Thanks in advance.
>>>
>>>Gordon Biggar
>>>Houston, Texas
>>>
>>
>>AFAIR, DOS used to rely exclusively on what the BIOS told it about the
>>hard disk parameters. Windows 2000 makes up its own mind. As b.jeswine
>>says, if the BIOS's interpretation of the hard disk parameters is
>>sufficient to get the machine started and hand over control to Windows
>>then you're safe.
>>
>
>
>