I think that in memory patching, rompaq patch o HPflash patch will not work, I think that when the computer resets to copy the new bios over old bios, checks new bios, so we only have one solution find how it checks it. Or perhaps I'm missing something?
Let me tell you only as a comment that I checked the BIOS history of my new notebook (8530p). The interesting thing is, that the first version of it's BIOS (F.02) came with a SLIC 2.0 and it was updated this year to a SLIC 2.1 by HP itself. It only has one SLIC marker in it but it's a EFI BIOS though. Nevertheless very interesting thing... So there is of course a way to update the BIOS to a new SLIC. We just have to find out the way!
We probably have to force the tool to flash the bootblock..I guess the BBL has an additionaly checksum like other bioses as well...
a bit off-topic, but.... from what I see posted here, laptop BIOSes are very difficult to MOD, a special thread for, Dell, HP, and the Lenovo ways, no to mention Toshiba's own BIOS. We are blessed to have this forum and all the experienced modders helping, but one question keeps humming in my head. Which brand is easier to MOD, yea I know phoenix is hard, but is there one that wont make you wanna pull your hair off trying to figure out how to do its BIOS?
The second occurrance of SLIC..... Well it seems HP has copied a range of B000h bytes just a second time.. First occurrance at offset E5000-EFFFFh Second occurrance at offset F5000-FFFFFh. The sums at both blocks according to ADDCC and my mod are the same. It's NOT a bbl code, but a protected area..... the first seems to be updated the second is protected......what about to make the bios to read the first SLIC? I'll have a look...
The question is why it's in the BIOS image when it's in a protected area that is not updated? Has anyone looked at the HP DMI Tools that posted someone? There is a possibility to change the OS SKU from XP to Vista and vice versa. I don't know what notebooks are supported by this tool, but if there is such a tool, there MUST be a way to change the SLIC in the protected area.
Ofcourse I have update both SLIC and then corrected some text (i hope innocuous) bytes to make additive checksum match.
This is why I hace changed rom.bin today I hace seen that only one slic table was changed ar the previous one What do you think?
There is no modified BIOS, the modification has been done in memory during re-flash the original unmodified F.16 @ SLIC 2.0. After starting the upgrade process, the updater checked the ROM for errors. After the successful check you can modify the ROM to be flashed with a hexeditor and save the changes to the memory (IIRC). Following the modification you can continue with the update process with the modified BIOS, So in reality you trick the updater program itself. I think the backed up ROM could not be flashed to another notebook because of CRC check error, but it works on that given computer. I hope I could help to clear up things. Personally I own a 6510b so I hope someone creates a method/program which works in any circumstance.