KGB - Kepler BIOS Editor/Unlocker

[CrazyNutz]

@CrazyNutz

What do you mean by "driver detection problem" in the note on kgb.cfg here:

# EXPERIMENTAL: This Setting makes the checksum calculate to
# the same value it originally was by manipulating an unused
# section of the bois. This may be needed for the new style
# UEFI vbios. Set this to 1 if you want to preserve the orig
# checksum. Set to 0 for the previous behavior of re-calculating
# the checksum. NOTE: if you're not having driver detection
# problems leave this at 0.

So UEFI vBIOSes, when used with Preserve_Original_Checksum = 0 will sometimes make Windows error out in detecting the drivers or something like that? According to error-id10t, the only problem of the old KGB program is that it can't compute properly the checksum of some UEFI BIOSes and so you should sometimes use Preserve_Original_Checksum = 1 to solve this. But what do you mean by "driver detection problems"?

I hope you reply on your own thread here.

There is a checksum of some value in each bios. If any changes are made in the bios this checksum must be recalculated.

For examples sake lets say its originally dec "78", if you make a change and recalculate the checksum, it will now be let say "107"

In some bioses (probably just uefi) if the original checksum "78" has been recalculated to something else, the nvidia driver may detect this and fail to load "no supported hardware detected" < some message like this.

This may be an attempt by nvidia to stop bios mods, my best guess anyhow.

So when you Preserve_Original_Checksum = 1, after a mod kgb forces the checksum to recalculate to the original value "78".
It does this by changing values in the padding (unused) sections of the bios so the checksum will = 78.

[kevindd992002]

There is a checksum of some value in each bios. If any changes are made in the bios this checksum must be recalculated.

For examples sake lets say its originally dec "78", if you make a change and recalculate the checksum, it will now be let say "107"

In some bioses (probably just uefi) if the original checksum "78" has been recalculated to something else, the nvidia driver may detect this and fail to load "no supported hardware detected" < some message like this.

This may be an attempt by nvidia to stop bios mods, my best guess anyhow.

So when you Preserve_Original_Checksum = 1, after a mod kgb forces the checksum to recalculate to the original value "78".
It does this by changing values in the padding (unused) sections of the bios so the checksum will = 78.

Got it. But what I don't understand is what would be the disadvantage if you keep Preserve_Original_Checksum to 1 all the time even when modding non-UEFI BIOS? Is there some disadvantage when recalculating the checksum by using the original value?

[kevindd992002]

Got it. But what I don't understand is what would be the disadvantage if you keep Preserve_Original_Checksum to 1 all the time even when modding non-UEFI BIOS? Is there some disadvantage when recalculating the checksum by using the original value?

CrazyNutz, please reply. Are you still busy?