New
#121
See Coder for Life - Projects - Win 7 Customizer Tools
Its a utility I made for just that purpose.
See Coder for Life - Projects - Win 7 Customizer Tools
Its a utility I made for just that purpose.
ok so do i have to actually copy the bits in a hex editor?
or can i do the whole wim then renameto bin then replace in the dll?
Copy what bits? Using resource hacker or similar program will properly add in the bytes for you. Many resource editors will update the checksum automatically. You can run the program I linked to anyways. It will update the checksum if necessary or tell you that it is already up to date. You don't need a hex editor...
same here
but its very strange i have 1 copy of windows 7 and two boot options the the same win 7 and one boots up the flag and the other dosent
i asked aout the hex editor becasue you said you had success with a hex editor
Okay. PE files (EXE, DLL, SYS, etc) have two forms of security. The first is a checksum that every PE file has, although it is only checked on important ones. This is typically updated automatically with the resource editor, or can be done with the utility PEChecksum on my webpage. The second is a digital signature that is only put on code that really needs to be secured, such as winload.exe. This is the one you are probably having a problem with. To 'update' this you would need the original private key used to sign it (which Microsoft isn't going to give you) or you can sign it yourself like I listed before.
So if during the boot it says that the checksum is wrong, use PEChecksum.
If it says the digital signature is wrong, you need to re-sign the file.
I think I was talking about using the hex editor like they said on that site you found for disabling all signature checks. I successfully found all the values I needed to change, but it didn't work and Windows still complained about the file.
Do you have two winloads? Like one osload and one winload? That is what that webpage (the one you linked to before) told you to do. They told you to make two options so you wouldn't brick your computer. Sadly, their method only works for beta and RC Windows 7, not release Windows 7.but its very strange i have 1 copy of windows 7 and two boot options the the same win 7 and one boots up the flag and the other dosent
You shouldn't need a hex editor for anything unless you are really planning to muck around in Windows binaries. Then I would recommend IDA Pro with Hexrays. It isn't really a hex editor, it is a de-compiler and dis-assembler, allowing to see the code (possibly) that was written to create the file. Microsoft has however heavily obfuscated their code, and especially winload.exe. That's the reason no one has cracked the release version of Windows yet.
ok well im gonna reinstall becasue theres a lot of clutter and ill continue with this after that
what files do i need from the Windows 7 SDK to sign files?
id rather not have the whole SDK
From the Windows SDK you need: MakeCert, pvk2pfx, and SignTool. I also recommend grabbing CertMgr.exe while you are at it. The whole SDK is awfully big for just signing.
Keep us updated.
Several of us quiet ones are watching progress on this. :)