Yep, depending on the board..865PERL boards are not flashing. as well as some other chipsets. Some additional sig or lock we cant circumvent (yet). Be sure to identify the bios as Intel with the tool to remove the intel lock.
Intel motherboards with ami bios Thanks, motherboard is S3210SHLC based on chipsets 3210 Server for Xeon processor. I took the Rom from Intel's web site and is 4 megs in size. Information on the net claims AMI bios yes or yes but............. I will try tonight at home to see if I can mod this otherwise I buy something else. I will let you know guys and post feedback so thanks again and do not want to waste anyone's time. As I said I am about to buy BUT if it cannot be moded I do not touch it.
Nope, what I downloaded is not recognized as AMI neither the Intel2AMI can open it and is from the official Intel site. The model is SH and not SHLC, this later one I cannot find it anywhere at all. I will not touch this then.
why does the 1.41 version say it cant be run on this version of windows?? error 5 this version of %1 is not compatible etc....
WHoo hoo I was able to mod my BIOS with this for my HP Pavillion a830n and add a SLIC2.1 table to a BIOS that had no SLIC table.
First I backed up my HP bios with the award desktop utility and used the the hp slic from the awardbios tool's folder then hit the button and there it was. Now all I had to do use use the award desktop flash utility the same one I used to extract the bin and hit the update button. HP Compaq slic table v 2.1was added to my BIOS entirely from the desktop. This is the tool to use.
Try with unticking in "dynamic options", "replace 1b module"... This will leave 1B module as it is and replace current slic in F0 module.
Yes! It works! I followed your advice and the tool worked for me, too! First, I tried modded BIOS with M-Flash's "Boot from BIOS file" feature - BIOS booted fine! Then I flashed BIOS using M-Flash without problems! Thank you very much, you are the best!
that just means it has "some" (fake or real) slic somewhere in bios and pointers are pointing to it. Best method is to replace that slic (because you are not changing 1B module, so its basickly 0 chance of bricking, since whole structure stays the same) and not adding new one thrue SSV method. There is also another benifit of keeping dynamic method, because its more "as manufactures" would do it. You can check if you slic is real or not, dump bios with amitool and open Fx module (340bytes in size) in some hexeditor, it should be clear pretty fast if its real or fake
Greetings SoLoR and thanks for the kind reply. 1. What sort of problems could arise if the original "fake" 2.0 slic is kept in place using SSV method? 2. If I choose accept, all modding options except Dynamic and MMTool are grayed out. Are the default options fine? One funny thing I observed, AMITool will report non-matching certs if verify certificate is clicked. Why? 3. Don't seem to find the dump option in AMITool. Care to elaborate? Sorry for the noob questions. First time user. Many thanks again.
1. none probably, pointers will get changed to newly introduced slic and old one will get ignored most likely 2. default options should work with 90% of mobos, afaik those mobos that can use some special options gets detected and options gets changed accordingly, verify button, checks cert to current slic inside bios. So eather you are checking it against default/fake slic or you did something wrong. 3. dump option is "*" button next to verify