I have also corrected the 4 byte additive checksum (with help of ADDCC v2). Used one 8 byte block for it Original rompaq did not bite, did not try the patched one, sorry I think the rompaq does some other check ie. CRC32 of the file or part of it (that what ie. Dell does with their server BIOS). I do not believe that the 4 byte additive checksum is at all valid/used here sebus
New experiences I've made some additionnal tests I tried to revert my Bios from F.0F to F.0E (original) With original rompaq.exe, I have an error... Rompaq don't want update my Bios because my Bios is newer than F.0E. With patched rompaq.exe (by mutante), my bios is successfully flashed without message (no question, nothing) and I "update" my Bios from F.0F to F.0E. After that, I tried to update to F.0F with patched Bios (by Yen) but my SLIC is always 2.0. Last test, I patch a F.0E Bios with custom SLIC and try to update from F.0F to F.0E. Rompaq complaints: Code: C:>ROMPAQ /U Reading file... (some seconds) The code used to verify the integrity of your BIOS does not match what is currently on your system. This could cause parts of the BIOS to be skipped when updating leading to unpredictable results including failure to boot. It is very strongly recommended that you not proceed with the update. Press F10=Continue, ESC=Cancel I pressed F10, my Bios is F.0E version but my SLIC is 2.0. So, I think different checksums are inserted in Bios and rompaq don't flash SLIC part because appropriate checksum is wrong. If Mutante (our asm killer) can investigate message show by rompaq (press F10 blabla) and find which part of bios file are checked, I think we can find a solution. Thanks all... and good night
Yes, Rompaq must check either CRC32 of the file or a checksum of a specific bit of it (which one?) Unless we can bypass this check we will get nowhere sebus
hello, First step: how to flash a mod file. There is 3 approachs , patching the flash tool, trying to find a CRC/checksum, memory patching with HxDEN. Now the first step was taken by memory patching with HxDEN. Second step: How to force the protected SLIC table to be update in case of Bios with 2 occurences. that's the challenge.
hello, no need to upload the "backuped file" I've check with Ultracompare, only the first marker zone is 2.1, the second one is still in 2.0, except that any difference. regards