If the RSDT doesn't match it won't hurt anything it just won't activate Win 7, if the modified BIOS deosn't properly overwrite the original RSDT. That's whay I made you give me the R/W Reprot for your BIOS. These HP OEM MB's sometimes don't overwrite that info properly.
I don't think that is needed. The /B switch is to program boot block and the /N switch is to program nvram so I think you should be alright. Just check and make sure you can get into the bios and reset any custom settings you might have had since they will have been cleared when the defaults were loaded. I hope that answered your question.
Thanks ippy, I was able to enter the BIOS setup just fine. So I don't need to reprogram the bootblock or nvram? Just curious as to why those commands are sometimes used to flash. I read that the boot block is the emergency part that allows a bad flash to hopefully recover, but why would anyone want to mess with that? I am also confused as to the checksum issue/error I received, is that normal after a flash? So now that I have 2.1 SLIC, you can mark your mod as successful & tested
Some BIOS's may require that the boot block/nvram be programmed but if it worked with out it for you then celebrate your new Win7 Activation. As far as the checksum error I have run into that a few times and simply needed to clear CMOS and load defaults. I have seen this with modded and unmodded bios's so don't stress over it to much.
Hi, thanks for the modded BIOS, however - it didn't work. I made a bootable USB stick with the necessary files and after booting I got this message: Obviously, the utility noticed a change in the file. Is it possible to fix it by adding/removing some switches in the AUTOEXEC.BAT file (following quotation)?