[Q] Win 8, bypass PAE/NX/SSE2 check

I did it, but still stuck at blue logo.

 

I'm going to reinstall win8, but I need to install Windows Updates or not?

 

if you want im installed updates

 

Please can you tell me can i install win 8 pro 32bit on my pc with this CPU
AMD Athlon XP 3200+ - AXDA3200DKV4E

if using patched files by @moderate ?

thanks

 

bootsect.exe is available in the PE of Windows 7 setup. I used it all the time.

When I used bcdedit in Windows 7 setup PE, it always recognized the BCD store automatically. I never had to specify it.

 

You need to login to view this posts content.

 

Here, I did the searching for you. I think it was post #117, but I overwrote the clipboard since then so??? Then I Googled to find out your processor's features.

Windows 8.x still requires SSE2 even with this patch, and the Athlon XP 3200+ only had SSE (1). Man, I remember back in the day how I wished I had the 3200+, not the 1700+.

 

Impressive...
You are very skilled. Will you patch W8.1 RTM after it will become available next month?

BTW: I see, that ntoskrnl.exe NX patch is version independant, while winload.exe patch and ntoskrnl.exe CMPXCHG16B patch are made to concrete versions... So what about those two hal* and one PAE patches, are they dependant on the version (and do they update file checksums too)? Could you make a list of supported file-versions?

Where we could donate?

When only NX bit check is patched, I think that Windows will always handle that correctly.

hmmm... those two hal files (hal.dll and halmacpi.dll) are same on my W8 x32 in VM... 8)

 

"Remove PAE check", "Remove SSE2 and NX check", "Fix hyper-threading in hal.dll", "Fix-hyper-threading in halmacpi.dll" and "Remove winload patchguard x86" work on all currently known file versions.

The CMPXCHG16B patch is specific to Windows 8.1 x64

The winload patchguard patches basically do the same thing: they just make the function ImgpValidateImageHash always return zero. Since 32 bit and 64 bit assembly code are very different, the patches for winload x86 and winload x64 have to search for totally different patterns when they try to locate ImgpValidateImageHash. I could also have made only one button for removing the winload patchguard and then the program could check if it has to apply the x86 or the x64 patch.

Yes, all patches update the PE checksum automatically.

SSE2 patch is supported in v1.4.

 

Jan, Jan, Jan, pls, could you make standalone PEChecksumFix.exe with GUI too, as I have many uses for it? Utility could display valid and stored hash and if they match or not.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I assume the 8.1 patch will also work in the same way on Windows Server 2012 r2.

 

You can easy find out by comparing files themselves (or KB updates later) between W8-1x64 and W2012R2x64.

 

Jan1, my old CPU support SSE2/PAE but not NX. In v1.4 "Remove SSE2 and NX check". What about "Remove NX check" only?

 

You need to login to view this posts content.

 

Use "Remove SSE2 and NX check" if you want to bypass SSE2, NX or both checks.

I tried to patch 6.2.9200.16420 with v1.4 and it worked.

 

Sorry, It has happened so, because your EXE doesn't open the dir from which it is runned, but it unfortunatelly remembers the dir from last patching (even if it was closed already). (So I tried by mistake, to patch some files twice.)
My mistake...

@All: I included v6-3-9431-0 x32 files to RAR above...