MSI Pro2-A BIOS Flash Problem...

[hito]

I have downloaded the 2.4 and the OC bios. I downloaded the 2.4 bios to edit the autoexec.bat so it would load the OC bios instead of the 2.4 bios. I right clicked on the file, was about to go to edit, and accidently went to open, and it loaded the 2.4 bios while I was in windows. I rebooted, and it seems that the 2.4 loaded successfully, however I did not want to flash to this bios. So anyhow, this time around I was able to go and edit the autoexec.bat file and I rebooted with the OC floppy, and the flash program loaded on DOS prompt. All seemed to have been going well, until a message popped up. The message was "The program file's BIO's - Lock String does not match with your system!" Now what does this mean? I'm currently running the MSI Pro2-A board, how could it not match? Any and all help will be appreciated.

Thanks

- hito

 

[SpongeBob]

It's fine, flash with the /nbl switch in the commmand line, this will get around your error. Example:a:\awd1111.exe /nbl

NBL = "No Bios Lock" protection

 

[Mavo]

This is from MSI's FAQ:

Question: During BIOS flashing procedure on K7T Pro2 or K7T Pro2A. Screen will show "The program file's BIOS lock string does not match with your system"

Answer: Use /nbl parameter
For example:
awdfl789 w6330vms.240 /nbl

I'm not sure if you should reflash with just the /nbl switch or add the switch to the list of switches in the autoexec.

 

[hito]

Thanks Spongebob and Mavo. I will add the /nbl switch to the autoexec.bat file and try again.

- hito

 

[hito]

Okay well, I flashed it with the OC bios. It went quite smooth, except for one little problem. I get a "unknown flash type" message. I tried to load the default settings and that didn't fix it. If I just leave it like this, will it affect performance or stability of the system in any way at all? I also noticed that on the post screen, on the bottom with the 2.4 bios, it changed the display from 686A to 686B. When I flashed the bios with the OC bios, it changed it back to 686A. Is this just a display error, or will it not use the full potential of my ATA100 drive? The only good thing that I so far see is that it increased my memory speeds a bit. Think it would be better for me to just go back to the 2.4 and wait for a new OC bios to come out?

- hito

 

[micron]

I would go back to 2.4, I was using the OC BIOS but when I ran a sandra bench on my ATA100 hard drive I got a score of 9000 so I went back to 2.4 and got my usual score of 23000.

 

[SpongeBob]

I got that "unknown flash type" message also. I went into the bios, loaded the defaults, rebooted, and it was gone. Then I went ahead and put my optimal settings back in the bios. I have heard some people still get that message even after doing that though. It shouldn't be a problem. I have better performance all around with the oc'ers bios than 2.4.

Micron, that's really wierd, only 9000 huh? Maybe your board is defective.

 

[Mavo]

SpongeBob: How did you flash your bios? Did you use the autoexec? What switches? Do you have the multiplier problems others are experiencing?

 

[SpongeBob]

By multiplier problems do you mean losing the lower multipliers when you flash? If so, I had that problem until I flashed to the oc'ers bios, which returned all the multipliers from I think 5.5 to 12.5. When flashing to the oc'ers bios I just extracted the award flash utility and the new bios onto a diskette, booted to the command prompt, and ran the flash program with the /nbl switch.

 

[Mavo]

Thanks for the info, SpongeBob. What I meant by multiplier problems is that some people have flashed to this new bios, got all the multipliers, but some multipliers were incorrect (eg. 7.5 was actually 11.5). I read this in the Turbo Bios Thread. Hmmm...maybe this problem is only found on the Turbo boards???

 

[SpongeBob]

Yeah I have not heard of that problem on the Pro 2-A, anyone else using Pro 2-A's know if this is strictly turbos?

 

[hito]

Thanks guys, well anyhow, I decided to stick to 2.4 and just wait for a new bios to hopefully come out and flash it to that and see what happens.

- hito

 

[deras]

yeah I get the unknown flash message and loading fail safe defaults did not fix things... also fail safe defaults only recognizes one of my sticks of ram....

this has been a tedious upgrade....