Modbin6 should be run in the “Command Prompt” of Win2000 or XP. It probably will work in Vista also. The subject BIOS and Modbin6 should be in a directory by themselves when using Modbin6. Depending on the other files names and extensions that might be in your working directory, the apparent corruption can occur, so don’t include any other file not necessary.
Modbin6 allows you, at a minimum, to:
1) Unhide(or hide) BIOS Items.
2) Edit the POST Screen message.
3) Edit the names of BIOS Items and settings.
4) Move any Item or multiple Items.
5) Change the Defaults of any Item.
6) Create a new group and move a Item(s) to it.
Modbin6 will fix the BIOS checksum when changing something and saving, but the checksum usually is not zero(00h). Modbin6 just saves what it calculates, and this is fine.
If the un-zipped BIOS file does not have a “.bin” extension, at the command prompt, type and enter: Modbin6 xxxxx.yyy where xxxxx.yyy represents the actual BIOS file name and extension. Or simply edit the file name to end in “.bin” as all BIOS files are binary files. Create a seperate directory and place the BIOS .bin files and Modbin6 in it and nothing else. I use a single letter for the directory so then when in the Command Prompt, I have to do a minimum of typing.
Modbin6 v2.04.01 dated 2/17/2007 screen shots cont:
One thing I don’t like is you can’t tell if a Item is hidden unless you go into it. The coloring never changes with hide/unhide settings.
When we go to save, we notice the same message that the latest CBROM issues. “-Adding MEMINIT.BIN 100%” This module has something to do with memory mapping I believe. It is extracted and re-inserted by both CBROM and Modbin recent versions.
The temp files now include several that CBROM 1.82 generates. The file “P35BA521.bin” is the BIOS I modified during this session.
If both Modbin 2.04.01 and CBROM 1.82 are going to be used on a BIOS, Modbin must be used first. If CBROM is used first, Modbin will(may) crash when trying to save the modified BIOS.