![]() ![]() You will notice that there is a lot of blank space around and below the 'MZ', this is header information and is of no interest. Somewhere between here and the 104 string is where we need to find and modify the JNZ (byte code 75)Ĩ. This is the code that MS uses for start of an EXE. from here search up and find HEX values «4d 5a», you can just scroll up a few pages till you see 'MZ' in the ASCII pane. Find HEX Values -> «31 00 30 00 34 00 2d 00 55», this should be the be the first part of the '104-U.' error string in wide character format (2 bytes/char) see step1.jpg.ħ. Tools -> OpenRAM -> Ezh2o -> Entire MemoryĦ. use Insyde BIOS editor - EZH2O (I used EZH20 2.1.0.4)ĥ. obtain your bios.fd file obtained from HP (or whatever manufacturer)Ģ. What follows is a general procedure to allow you to modify your own BIOS safely (I hope).ġ. I found the 104 - Unsupported wireless network device detected string in the memory dump and the Microsoft EXE signature just above which lead to the breakthrough (at least for me). After not being able to find my subsys codes, I started looking around a bit. And using all of the tips on how to use the EzH2O and WinHex tools, I was able to figure out the byte that needed to be changed to ignore the PCIe wireless whitelist altogether. I used the F.34 BIOS for a Compaq Presario C700 series. I have figured this InsydeFlash thing out. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |