Nice find! A few questions.

In referencing a previous post,

feipoa wrote on 2020-08-21, 20:44:

We're looking for the DOS versions of AMIBCP for: BCP14.EXE (for core BIOS 07/07/91) BCP20.EXE (for core BIOS 12/12/91) […]
Show full quote

We're looking for the DOS versions of AMIBCP for:
BCP14.EXE (for core BIOS 07/07/91)
BCP20.EXE (for core BIOS 12/12/91)
BCP21.EXE (for core BIOS 06/06/92)
BCP21A.EXE (for core BIOS 11/11/92 and 08/08/93)
WBCP33.EXE (for core BIOS 12/15/93 (and 06/25/94?))
WBCP40.EXE (for core BIOS 06/25/94 and 07/25/94)
WBCP42.EXE (for core BIOS 07/25/94)
WBCP511.EXE (for core BIOS 10/10/94)

which versions do we have now? Looking at the links provided recently, and previously, it looks like we have:

BCP14
BCP14E
BCP20
BCP20E
BCP21
BCP21E
BCP21A
BCP21AE
BCP221
BCP221E
BCP347
WBCP
WBCP33
WBCP44
BCPW511E
GBCP2
GBCP3

I think the 'E' suffix was for 'evaluation', so probably not fully useful.

1)
Was anyone able to locate WBCP42 and WBCP511? WBCP511 would be used for those pesky 486's with a WIN BIOS, like the popular M919, some BIOS variants of the HOT-433, etc.

2)
Has anyone yet played with BCP14, BCP20, BCP21, etc to determine if the utility is able to sucessfully enable PS/2 mouse functionality, recalculate the checksum, and save the file?

Thanks!

I tried to open a 1990 core AMIBIOS from an SiS Rabbit 386 board using BCP14 and it gives me the error "use BCP20". When I use BCP 20, it tell me "use BCP14". Any thoughts on that one?

BTW, I made a post earlier about the fact that when you open the zip file there's an ad for the warez server that says they have pr0n. My post was deleted. Obviously somebody can't take a joke.

I ran a quick test with a few of these AMIBCP versions.

BCP14.exe worked fine with my AMI Mark V Baby Screamer (7/7/91). You can use either a single BIOS image or even/odd split files. The app will open/save in either format you choose. I was able to enable PS/2 and unhide BIOS options, similar to MODBIN. Checksum gets corrected automatically. I'm using the updated BIOS in this system now.

BCP21A.exe works with my Daewoo AL486V-D BIOS.

I used an XP machine to save the BIOS files and an EEPROM programmer to flash the EEPROM chips. I did not try to open the BIOS images from a live system and save it, however this option does exist.

I have a 286 with an AMI BIOS, but BCP14 was too new for it. As such, some systems will still need the manual approach to unhide options and enable PS/2.

Great find. Thanks for this! I have a large task ahead of me to retrofit all my systems and motherboards with the updated BIOS.

Has anyone had any luck opening a WIN BIOS with BCPW511E?

With a 10/10/1994 core, opening the 9190506.ROM file with BCPW511E returns: Incompatible BIOS Header !

There is an option to load Compressed BIOS Modules from BCPW511E. It wants files with *.SET or *.POS extensions. So I renamed my BIOS image from 9190506.ROM to 9190506.SET and saved another file as 9190506.POS.

When trying to open 9190506.POS, I get: BIOS file(s) not found

When trying to open 9190506.SET, I get: File(s) are Not of Proper Size!

I'm not sure what to do now, so I thought I should decompress the BIOS.

I experimented using amideco.exe, for which I get the following unpacked files:

I'm not sure what to do with these 5 files though. Maybe I'm using the wrong AMIBCP version? Maybe I need some AMI software to make a copy of my BIOS in some particular format? I'm just using my EEPROM programmer to grab the binary. I figure AMIFLASH v5.20 should be about the right vintage, but I couldn't figure out how to make a copy of my BIOS without having the software also update my BIOS firmware.

feipoa wrote on 2026-07-28, 13:50:

Has anyone had any luck opening a WIN BIOS with BCPW511E? […]
Show full quote

Has anyone had any luck opening a WIN BIOS with BCPW511E?

With a 10/10/1994 core, opening the 9190506.ROM file with BCPW511E returns: Incompatible BIOS Header !

There is an option to load Compressed BIOS Modules from BCPW511E. It wants files with *.SET or *.POS extensions. So I renamed my BIOS image from 9190506.ROM to 9190506.SET and saved another file as 9190506.POS.

When trying to open 9190506.POS, I get: BIOS file(s) not found

When trying to open 9190506.SET, I get: File(s) are Not of Proper Size!

I'm not sure what to do now, so I thought I should decompress the BIOS.

I experimented using amideco.exe, for which I get the following unpacked files:

The attachment amideco.JPG is no longer available

I'm not sure what to do with these 5 files though. Maybe I'm using the wrong AMIBCP version? Maybe I need some AMI software to make a copy of my BIOS in some particular format? I'm just using my EEPROM programmer to grab the binary. I figure AMIFLASH v5.20 should be about the right vintage, but I couldn't figure out how to make a copy of my BIOS without having the software also update my BIOS firmware.

Funny you mention WinBIOS 5.x. I've been experimenting with it on my own before these tools surfaced. I can decompress and recompile it. I'm working towards a goal of enabling LBA28 (128gb) on it through my M921 board. There are hidden/conditional values that can be enabled/set. It's also most likely possible to replace the built-in NCR SCSI option ROM with XTIDE or other fitting ROM of your choice.

I believe you need to use /E to open certain BIOS .ROM files with BCPW511E

BCPW511E /E refuses to open 9190506.ROM because it is an evaluation version. Changing byte 2066h of BCPW11E.exe from 75h to 0EBh using a hex editor allows opening 9190506.ROM (and presumably others). It then opens but with a few warnings about inconsistent default settings. When saving, you must "swap setup module" (don't know what that means) or it is too big. I didn't do any testing on the resulting ROM; perhaps it gets flagged as an evaluation version.

vetz wrote on 2026-07-28, 16:38:

Funny you mention WinBIOS 5.x. I've been experimenting with it on my own before these tools surfaced. I can decompress and recompile it.

How did you manage to re-compress the BIOS blocks? I remember figuring out that it used some variant of the LZH format, with simplified/minimal headers... I was able to decompress them in a similar way to what AMIDECO does, but when using a tool like LHA to compress them again (even if I didn't tamper with them) the resulting BIOS would always hang up during the POST decompression phase.

jakethompson1 wrote on 2026-07-28, 22:21:

When saving, you must "swap setup module" (don't know what that means) or it is too big.

It has to do with the layout of the M919 BIOS I'd assume which is also why /E has to be used (lower 64kbit). I'd just press Yes here.

feipoa wrote on 2026-07-28, 13:50:

Has anyone had any luck opening a WIN BIOS with BCPW511E? […]
Show full quote

Has anyone had any luck opening a WIN BIOS with BCPW511E?

With a 10/10/1994 core, opening the 9190506.ROM file with BCPW511E returns: Incompatible BIOS Header !

There is an option to load Compressed BIOS Modules from BCPW511E. It wants files with *.SET or *.POS extensions. So I renamed my BIOS image from 9190506.ROM to 9190506.SET and saved another file as 9190506.POS.

When trying to open 9190506.POS, I get: BIOS file(s) not found

When trying to open 9190506.SET, I get: File(s) are Not of Proper Size!

I'm not sure what to do now, so I thought I should decompress the BIOS.

I experimented using amideco.exe, for which I get the following unpacked files:

I'm not sure what to do with these 5 files though. Maybe I'm using the wrong AMIBCP version? Maybe I need some AMI software to make a copy of my BIOS in some particular format? I'm just using my EEPROM programmer to grab the binary. I figure AMIFLASH v5.20 should be about the right vintage, but I couldn't figure out how to make a copy of my BIOS without having the software also update my BIOS firmware.

If I remember correctly AMIDECO would output uncompressed files for each of the compressed blocks in the BIOS. You need to look at the headers of these DEC files it outputs, there will be AMIBIOSS<date> or AMIBIOSP<date>, presumably for "S"etup and "P"OST. I assume these would be the ".SET" and ".POS" files BCP expects.

TheMobRules wrote on 2026-07-28, 22:55:

vetz wrote on 2026-07-28, 16:38:

Funny you mention WinBIOS 5.x. I've been experimenting with it on my own before these tools surfaced. I can decompress and recompile it.

How did you manage to re-compress the BIOS blocks? I remember figuring out that it used some variant of the LZH format, with simplified/minimal headers... I was able to decompress them in a similar way to what AMIDECO does, but when using a tool like LHA to compress them again (even if I didn't tamper with them) the resulting BIOS would always hang up during the POST decompression phase.

Correct, its LHA (LH5 to be precise). It needs a little customization for it to repackage again, AMI's own 8-byte length header and correct offset. I haven't tested a repacked BIOS on real hardware yet, but it decodes byte-exact. I can share the python script if you want it.

Thanks for the replies.

128GB IDE support for the M919 and M921 would be nice. Will AthAMIed work on these WIN BIOSes without having to decompress the BIOS?

Opening BCPW511E in a hex editor, I changed address 2066h from 75h to EBh, then renamed the file BCPW511.EXE

Next I ran:

BCPW511.EXE /E 9190506
and
BCPW511E.EXE /E 9190506

and get: Error in File I/O !

at least it no longer says Incompatible BIOS header.

Next, I tried to rename the two files from AMIDECO which have the AMIBIOSS and AMIBIOSP as: 919.SET and 919.POS. I then ran

BCPW511.EXE /E 919 0
and
BCPW511E.EXE /E 919 0
and
BCPW511.EXE 919 0
and
BCPW511E.EXE 919 0

I get: Files(s) are Not of Proper Size !

Next, I tried to rename all the decompressed AMIDECO files in order, as 919.000, 919.001, 919.002, 919.003 and run:

BCPW511 919 4
I get Incompatible BIOS header

Anyone had success with a 10/10/1994 WIN BIOS with BCPW511?

feipoa wrote on 2026-07-29, 00:51:

Anyone had success with a 10/10/1994 WIN BIOS with BCPW511?

BCPW511 /E 9190506 pops right open for me. I obtained 9190506.ROM here: Re: PcChips M919 - voltage modification the easy way
I had it named BCPW.EXE previously, and just now renamed it BCPW511.EXE to make sure the exe name doesn't matter, and it still works.
I suggest trying from a clean directory, with no .SET or .POS files in it just to be safe. Just the .ROM.
I am using DOSBox, but it shouldn't matter; NTVDM should also work fine.

I downloaded your copy of 9190506.rom, but I still get Error in I/O file !

I'm not using DOSBOX. I've been using my M919 this whole time. I will try it on my XP machine.

I was able to open the M919's BIOS image using WinXP and BCPW511, however, I'm presented with this:

1Inconsistent Optimal Default in Register Tables for CMOS Register 42h.
2
3Press any key to Continue

After pressing continue, it presents the same message for Register 56h, 57h, and 59h.

Did you see this message?

Any ideas why the DOS version which comes with Win95c (MS-DOS 7) cannot open 9190506.ROM with BCPW511.EXE?

feipoa wrote on 2026-07-29, 01:15:

I was able to open the M919's BIOS image using WinXP and BCPW511, however, I'm presented with this: […]
Show full quote

I was able to open the M919's BIOS image using WinXP and BCPW511, however, I'm presented with this:

Copy code to clipboard

1Inconsistent Optimal Default in Register Tables for CMOS Register 42h.
2
3Press any key to Continue

Did you see this message?

Any ideas why the DOS version which comes with Win95c (MS-DOS 7) cannot open 9190506.ROM with BCPW511.EXE?

Yes, I got that message. It seems to work anyway. I mentioned it here Re: Where can I find "AMIBCP" (for DOS) ?
I just did further testing, and isolated the "error in file I/O" to inadequate FILES= in config.sys.

jakethompson1 wrote on 2026-07-29, 01:42:

feipoa wrote on 2026-07-29, 01:15:

I was able to open the M919's BIOS image using WinXP and BCPW511, however, I'm presented with this: […]
Show full quote

I was able to open the M919's BIOS image using WinXP and BCPW511, however, I'm presented with this:

Copy code to clipboard

1Inconsistent Optimal Default in Register Tables for CMOS Register 42h.
2
3Press any key to Continue

Did you see this message?

Any ideas why the DOS version which comes with Win95c (MS-DOS 7) cannot open 9190506.ROM with BCPW511.EXE?

Yes, I got that message. It seems to work anyway. I mentioned it here Re: Where can I find "AMIBCP" (for DOS) ?
I just did further testing, and isolated the "error in file I/O" to inadequate FILES= in config.sys.

Wow, thanks! I don't know what's an appropriate value for FILES, but I remember I've had some setups which had FILES=40. I've added this line to my M919 system's config file and I can now open the ROM.

vetz wrote on 2026-07-28, 23:13:

Correct, its LHA (LH5 to be precise). It needs a little customization for it to repackage again, AMI's own 8-byte length header and correct offset. I haven't tested a repacked BIOS on real hardware yet, but it decodes byte-exact. I can share the python script if you want it.

It would be great if you have it. I'm dealing with the BIOS from an AOpen VI15G (AMI WinBIOS, 12/15/93 core). I think there are some issues with the way it sets the chipset registers for mem/cache timings, for some reason it refuses to set the tightest timings.

I had a similar experience with an MSI MS-4132G, but that one had an older AMI Color BIOS core, so I was able to patch the BIOS code directly to set the proper timings. With this one, that part of the POST code is in one of the compressed blocks, and I've been looking for a way to rebuild the ROM image after patching the code.

Unfortunately, even though I can open this BIOS with WBCP33, I don't think it can help with this issue as I don't see any option to tamper directly with the chipset registers like on MODBIN, BCP seems to deal only with the values on the CMOS registers and the translation from CMOS register values to chipset register is done directly on the POST code.

When I edit, then save 9190506.ROM with BCPW511, I get these messages:

1Code Overflow ! Swap SETUP Module ?  (Y/N)

I press Y, and the ROM saves. I used my EEPROM programmer to write the binary to an EEPROM: W29EE011-15. Placing the EEPROM into the M919, it appears to work as it should.

With BCPW511, there are two settings to enable in the ROM to enable PS/2 mouse functionality. I bet someone could easily add PS/2 mouse support to the PC Chips M919 by copying the Biostar MB-8433UUD's wiring. In particular, UM8886BF pin 199 (mouse data), pin 200 (mouse clock), pin 56 (keyboard data), pin 57 (keyboard clock), and pin 9 (IRQ 12). You'd add a resistor to 5V, a cap to GND, and a series inductor (e.g. 2.2 K-ohm, 47 nF, 2.2 uH). Iive added this to my ever-growing list.

feipoa wrote on 2026-07-29, 03:26:

I used my EEPROM programmer to write the binary to an EEPROM: W29EE011-15. Placing the EEPROM into the M919, it appears to work as it should.

That's very good, thanks for confirming!

TheMobRules wrote on 2026-07-29, 02:01:

It would be great if you have it. I'm dealing with the BIOS from an AOpen VI15G (AMI WinBIOS, 12/15/93 core). I think there are some issues with the way it sets the chipset registers for mem/cache timings, for some reason it refuses to set the tightest timings.

I downloaded that BIOS from TRW. It's AMIBIOS 4.x so not exactly the same as the M921 BIOS which is 5.10. Running the script does not provide byte-exact on decode again, so something else is going on. I can look into it.

EDIT: Figured it out, its due to 4.x using LH4 compression.