Okay thanks.
I'll be working strictly with uncompressed ROMs.

There's something strange going on with a couple of Award V4.50 386 BIOSes I downloaded. I cannot open them with modbin as it claims there is a file checksum error.
However, the ROM checksum seems to be correct. Apparently Award BIOSes that have been opened with awdbedit exhibit the same problem. Anyone know what the deal is there?
Is there already a thread about this problem, or should I start a new one?

Have any of you looked at HDD translation/autodetection for the 64k AMI BIOS versions?

I don't know how late the 64k AMI BIOSes were used on a given board. If any of them received an update for larger drive translation or an update to the autodetect function courtesy of AMI and a generous board manufacturer, a byte comparison between an older version to the newer version may help zero-in on the replacement code. From there, you'd have to update any jump addresses for the BIOS you want to update - unless AMI BIOSes followed a standard layout/address structure, I suppose.

I am just spitballing. Not new to hex editors or assembly, but the contents of an AMI BIOS? My knowledge is maybe a couple of days old.

Totally possible that there is a hard cut-off date from moving from 64k uncompressed to LHA'ed 128k (or whatever it is) in order for AMI to even consider updating their drive calculations.

CkRtech wrote on 2025-05-02, 04:16:

Have any of you looked at HDD translation/autodetection for the 64k AMI BIOS versions? […]
Show full quote

Have any of you looked at HDD translation/autodetection for the 64k AMI BIOS versions?

I don't know how late the 64k AMI BIOSes were used on a given board. If any of them received an update for larger drive translation or an update to the autodetect function courtesy of AMI and a generous board manufacturer, a byte comparison between an older version to the newer version may help zero-in on the replacement code. From there, you'd have to update any jump addresses for the BIOS you want to update - unless AMI BIOSes followed a standard layout/address structure, I suppose.

I am just spitballing. Not new to hex editors or assembly, but the contents of an AMI BIOS? My knowledge is maybe a couple of days old.

Totally possible that there is a hard cut-off date from moving from 64k uncompressed to LHA'ed 128k (or whatever it is) in order for AMI to even consider updating their drive calculations.

Yes, I have thought of this 😁
Here, the 10/16/94 one here does not have LBA, and the 01/09/95 one does: https://theretroweb.com/motherboards/s/efa-4dmu-hl3s#bios
But, everything is shifted around, they didn't just simply patch in the LBA support, unfortunately.

jakethompson1 wrote on 2025-05-02, 04:20:

Here, the 10/16/94 one here does not have LBA, and the 01/09/95 one does: https://theretroweb.com/motherboards/s/efa-4dmu-hl3s#bios
But, everything is shifted around, they didn't just simply patch in the LBA support, unfortunately.

Yuck. Looks like they reclaimed some space above the $8000 BIOS copyright info and from the big block of $00 @ $DD42-$DFB1 and used it for some serious rewrite/replace under the BootSector Write/Possible Virus warning.

Anonymous Coward wrote on 2024-07-19, 02:35:

Okay thanks. I'll be working strictly with uncompressed ROMs. […]
Show full quote

Okay thanks.
I'll be working strictly with uncompressed ROMs.

There's something strange going on with a couple of Award V4.50 386 BIOSes I downloaded. I cannot open them with modbin as it claims there is a file checksum error.
However, the ROM checksum seems to be correct. Apparently Award BIOSes that have been opened with awdbedit exhibit the same problem. Anyone know what the deal is there?
Is there already a thread about this problem, or should I start a new one?

That should read 'open and saved with awdbedit'. This is an issue I've known about for some time. Best to do all modding with Modbin rather than awdbedit, although awdbedit has that convenient PCI routing table open for editing and the ability to swap the Energy Star logo.

On another front, has anyone had success in adding PS/2 mouse support to old Phoenix BIOSes? I have one from 1994, rev. 4.03c which doesn't work with a KBC-PS/2 mouse mod. It's an ALi 1429 board - EXP4349.