dotexe1337

empty desktop: and here is a busy screenshot, just an example to show what it looks like when working on things: the theme is a customized version of the classic windows "Lilac" theme. all i did was change the title bars to a solid color instead of a gradient, and set the desktop color to a nice dark purple. classic shell is used with the "classic windows captions" theme for the start menu, t-clock redux for the taskbar clock and some other utilities such as caps lock indicator, which shows me my caps lock, num lock and scroll lock status. and even gives a nice little notification when i press one. and the mouse cursor theme is called "Metro X3", specifically the light black variant.

Hi, my name is dotexe. I am a computer programmer and am currently learning about PE hacking/patching, disassembly, and other things related to making extended kernels, and hope to make my own kernel for Windows 7 once I can figure out some more things.

Hi, I have attempted to patch a function into KernelBase.dll with no luck. winload.exe was patched by changing every mov whatever, 0xc0000428 to mov whatever, 0x0 so that the kernel can load. It seems there is some kind of discrepancy somewhere across the chain, as whenever kernelbase.dll is patched, no matter what patches are applied, the system will encounter an access violation late in the boot process. It's kind of strange because I ran the system through WinDbg, and when it crashes, the stack trace mentions that it's crashing when trying to call SetSystemPowerState, which isn't even part of KernelBase.dll, so the functions I'm patching in shouldn't even matter. This is why I think there may be some kind of extra security to prevent kernel patches in Windows 7, compared to Vista. Does anyone have an idea on what could be happening here?