checksum error means either dump is bad or flash was unsuccessful/incomplete

The AMI BIOSes probably have the same problem, it's just that those usually don't even display anything if the BIOS checksum is wrong. So yeah, either the dumps are not correct or there was a problem with the flash.

EDIT: MODBIN doesn't complain when trying to open the AWARD files, so I'd say they're probably OK. So it looks like either a problem during the flashing process or something is not right with the chip.

Updated my TL866 software and firmware. Tried 2 different Winbond EEPROMs. Both show no errors. Does it look like my settings are correct? Getting Code 13 10 on the post analyzer with no video.

Not that it would make any difference, but I've noticed you selected W29EE011 @PLCC32. From the first picture I can tell you are using a regular DIP chip, so you should choose the plain W29EE011. Again, both should work but just to discard any quirks of the TL866 software I suggest choosing the appropriate option for your chip.

The codes 13 10, is that with AMI or Award?

Tried switching to plain W29EE011 - no luck. The 13 10 is when using AMI. When using Award it gives the same screenshot I put up that shows 'BIOS ROM checksum error', then 1 short 1 long beep. Code: 41 0d

Yes you should not choose the wrong pinout/pincount on a EEPROM when trying to flash.
Go here: http://web.archive.org/web/19970707123816/htt … 6/4144/4144.htm
grab the Award bios directly and try again.

Correct pinout/pincount was selected this time. I tried both AMI and AWARD from the link above on Archive.org. (Thank you!)

Here are the results of each - still no workie:

https://youtube.com/shorts/btv0UOck9Co?feature=share <--AMI

https://youtube.com/shorts/_2m9VQgdhLk?feature=share <--AWARD

wait, first you got post screen with error, now you get no screen at all and boot loops? take off cache, downclock cpu, change ram, change cpu etc

The AMI BIOS code where it gets stuck (18) seems to be related to memory refresh test, but I can’t tell for sure without knowing exactly what BIOS core that is.

Can you post a close picture of the memory modules you’re using? Since it’s a 486 I would test with the following:

• Definitely use FPM: even though some revisions of the SIS chipset support EDO it’s not always compatible
• Populate only 1 memory bank (SIMM1 slot)
• Use single-sided modules if possible

YES!! Thanks to everyone! It was the FP RAM vs EDO.

By the way, either BIOS works, both Award and AMI!!

Great ! Glad you got it working.

Thanks! Its now setup for a Duke3d LAN party for this weekend.

Hi, I have am MSI MS-4144 motherboard that just died on me tonight with the dreaded Award BootBlock BIOS ROM checksum error. I was running the Award WF54S BIOS version with PS/2 support and it was working great until tonight. Would any of you kind gentlemen be able to program my BIOS Flash chip for me with your TL866 if I sent you the chip? I don’t have a TL866 and would prefer not to have to buy one. The Flash chip is the same Winbond W29EE011-15 as in the original post. Since this thread is really old I hope that someone on here will be able to help me. I really like this 486 board and definitely want to keep it running. Thanks to all!

Msi_4144_486 wrote on 2024-09-06, 06:02:

Hi, I have am MSI MS-4144 motherboard that just died on me tonight with the dreaded Award BootBlock BIOS ROM checksum error. I was running the Award WF54S BIOS version with PS/2 support and it was working great until tonight. Would any of you kind gentlemen be able to program my BIOS Flash chip for me with your TL866 if I sent you the chip? I don’t have a TL866 and would prefer not to have to buy one. The Flash chip is the same Winbond W29EE011-15 as in the original post. Since this thread is really old I hope that someone on here will be able to help me. I really like this 486 board and definitely want to keep it running. Thanks to all!

Hi,

A BIOS ROM Checksum Error message normally indicates a corrupt BIOS due to bit rot or a bad flash, but I know of at least two cases where bad RAM or a bad SIMM slot were the cause.

These MSI-4144 Award BIOSes are compressed and contain a decompression engine that decompresses all BIOS modules into RAM. After an integrity test, these modules are then copied to their allocated position in shadow RAM, and are run to do the POST.
If the integrity checks fails, the decompression engine jumps to the bootblock to start a possible BIOS recovery from floppy.
Because this whole process is done in RAM, what if there is a problem in the memory system? This could cause a memory corruption that would trip the integrity check with the same outcome of a bootblock recovery.

So this is where I would look first on your board. Flaky RAM? Corroded SIMM slots? Bad solder joints? Damaged traces near the SIMM slots?
Hopefully, you find something there.

Cheers, Jan

Hi Jan, thank you for the reply and suggestion to verify the memory SIMM modules. I was able to successfully recover the BIOS using the “hot flash” method with an old Soyo 440BX motherboard and celeron 300A CPU. After I booted the soyo board up I removed the 32-pin BIOS ROM chip from it and installed the Winbond W29EE011-15 BIOS ROM from the MS-4144 into the socket. Then I ran the excellent UniFlash 1.40 utility from the floppy drive and successfully was able to re-flash the W29EE011-15 back to a previous AMI BIOS version AF54S. The uniflash utility indicated that it was a successful flash. I then powered off the soyo board, removed the W29EE011 from it and replaced it back in the MS-4144. Then I held my breath and powered the thing up, and amazingly it booted right up ! After running some tests and adjusting some of the settings in the BIOS, I then proceeded to flash it again back to the same WF54S BIOS version with PS/2 mouse support that I had been running previously.

Everything has been running great for about a week now with my AM5x86-133ADZ @ 160MHz and Memtest86+ runs flawless with two 32MB and one 16MB SIMMs installed.

I don’t know what caused the BootBlock BIOS ROM checksum error, but UniFlash 1.40 definitely saved my motherboard and saved me from having to buy a TL866 ROM programmer. I hope this information helps some other folks out there that run into this problem in the future. Thanks to all in this thread, and lets keep these MS-4144s running!

Msi_4144_486 wrote on 2024-09-15, 22:54:

Hi Jan, thank you for the reply and suggestion to verify the memory SIMM modules. I was able to successfully recover the BIOS using the “hot flash” method with an old Soyo 440BX motherboard and celeron 300A CPU. After I booted the soyo board up I removed the 32-pin BIOS ROM chip from it and installed the Winbond W29EE011-15 BIOS ROM from the MS-4144 into the socket. Then I ran the excellent UniFlash 1.40 utility from the floppy drive and successfully was able to re-flash the W29EE011-15 back to a previous AMI BIOS version AF54S. The uniflash utility indicated that it was a successful flash. I then powered off the soyo board, removed the W29EE011 from it and replaced it back in the MS-4144. Then I held my breath and powered the thing up, and amazingly it booted right up ! After running some tests and adjusting some of the settings in the BIOS, I then proceeded to flash it again back to the same WF54S BIOS version with PS/2 mouse support that I had been running previously.

Everything has been running great for about a week now with my AM5x86-133ADZ @ 160MHz and Memtest86+ runs flawless with two 32MB and one 16MB SIMMs installed.

I don’t know what caused the BootBlock BIOS ROM checksum error, but UniFlash 1.40 definitely saved my motherboard and saved me from having to buy a TL866 ROM programmer. I hope this information helps some other folks out there that run into this problem in the future. Thanks to all in this thread, and lets keep these MS-4144s running!

So it was a corrupted BIOS afterall.
Great that you could fix the BIOS via the good old "hot flash" method! 😀

Another nice board saved!
Cheers, Jan