🚀 go-pugleaf

Svend Olaf Mikkelsen <svolaf@inet.uni2.dk> wrote in
message news:39787361.3040784@news.inet.tele.dk...
> Rod Speed <rod_speed@yahoo.com> wrote
>> Richard RUDEK <x@invalid.zeta.org.au> wrote

>>> I'd say, you probably ran into a side effect of
>>> using the "Auto" detect feature(s) of your BIOS.

>> I doubt it.

>>> If the partition table gets corrupted, it can cause the BIOS to
>>> decide to use a different type drive translation, other than LBA.

>> The bios AUTO setting doesnt use the partition
>> table. It just asks the drive about its parameters,
>> and the drive doesnt use the partition table either.

> This is definitely wrong.

We'll see.

> An Award BIOS with MODE set to AUTO will attempt
> to determine the translation from the partition table.

What evidence do you have for that assertion ?

How can it when the format of the partition table varys with the OS ?

> Award also will look at the partition table, if MODE
> is set to NORMAL, LARGE and maybe LBA.

What was being discussed was AUTO, not any one of those.

> If the partition table does not match the setting,

Doesnt arise with AUTO mode. And if the master boot
record got corrupted, the bios doesnt have the geometry
data from the MBR anyway and has to use JUST the data
the drive returns when queried about its details, just like
it has to do with a drive with no MBR or partition table.

> the BIOS will then return a disk geometry that looks
> as expected for the partition table, but the disk will
> be read and written at completely wrong locations.

Yes, like I said, that can certainly happen, but that does
NOT produce massive numbers of bad sectors with the
drive audibly recalibrating because of the very high error rate.

> This is a really nasty bug.

You appear to be confusing the undoubted problem with changes
to the mapping between the CHS values and the LBA block numbers
that can certainly vary with the OS level mapping, and what the bios
does at boot time with an AUTO drive type, what was being discussed.