Please be patient, I will let you know once I’ve found the edits on your iscflash.dll (I’m using slow computer right now, so the search within the file is very slow) Why create such a guide, and then not allow discussion!?!? It’s too bad he’s disabled comments on that, I’m sure that would have been discussed and tested at length. I wonder if that method, gets you around RSA Internally Signed BIOS or not, or only the RSA check at the flashing level. However, that does not work on some more recent BIOS, it only causes another error instead, then you can’t get around that one either unless you do the edit via programmer to the onboard BIOS first. That is a lot of edits though, so on a non-personal level (ie someone making a mod BIOS for someone else) it’s easier to just bypass the secure BIOS check by editing the iscflash.dll Thank you for the interesting post you linked at post #2 above, although he disabled replies, so you can’t see the amount of success vs failure with that method, it does look valid and proves a long drawn out edit can be done to fix the issue as well. dll - in general, this is done in assembly/hex, in assembly you find the coding that checks and invokes this error and bypass it by either jumping past it, or making it not happen (NOP it out > No Operation Possible > 9090) You’re welcome, please wait, I will tell you how to edit the.
0 kommentar(er)
