K4sum1

There's win10verhack, I use it to help install Windscribe, but it doesn't work for much, and is x64 only.

In the stock start menu dating all the way back to XP you can add it to the side with all the other options

Also no Administrative Tools option in the program pls fix.

lmao

why

I get this error trying to use it under Vista.

This works as long as you can get Java 8+ on your machine, and have a browser modern enough to render the Microsoft login page. https://github.com/olauncher/olauncher

You replying is going off the topic of extended kernels. I was talking about types of extended kernels.

For the Vista Extended Kernel, the actual intended update path is 2017 EOS + SHA-2 update. The 2018 rollup sometimes suggested is to get a base no updates install up and working with the kernel, but the path that it was changed to however long ago is just the 2017 EOS + SHA-2 update. Also the extended kernel does have some issues with certain applications. I think I prefer the VxKex style of kernel extension where no system files are touched and it redirects functions. Although I think the Vista Extended Kernel type extension would be more compatible with non-native applications.

Wait is v8 in your terms the BSOD fix?

Is 2003 x86 similar enough to have a v8 as well (compiled with /free pls) or is it too different.

@Dietmar Can you give me the hex values for x64 and x86 built with /free?

What about 2003 x86, or does that ACPI not have this issue? Also does debug/non debug change the hex?

I'm wondering how you made it. Do you have the diff for the modification?

How did you make this? Could or should it be used on machines that work fine without the hack?

This looks cool, might try it on 8.x next install I do, or on XP/Vista.

This was with an older version of the game, didn't think they'd make it required to update. Sucks as 431.36 gave better performance compared to latest.

Need AI to backport Firefox 110 to 2000

Yeah I manually replaced the ACPI and it got further.

They're trying to boot from the installer, using basic update .zips to install the new ACPI, but apparently that doesn't work as ACPI.SY_ has a old ACPI, so I'm manually doing it for them.

Same exact BSOD, same exact parameters.

I am very dumb and I will be explaining this to someone dumber than me so I need basic instructions on how to do that

I compiled the latest v7 for x64 for a friend and they get this BSOD. It appears to correspond to one of the "Know issues workarounds" but I'm not sure what to do. I asked what the specs were and I got HP 17-ca2003na. After looking it up, I highly doubt XP would work on it even if ACPI worked, but I still want to post about it to see what anyone has to say about it.

I'm wondering if it's the XP drivers, it's a known fact that Intel Windows drivers suck, but I didn't think the XP drivers would be like this. I'll get around to installing 8.1 on it soon and report back.

I see you made an account here. I suggested the 290X as it's the peak XP GPU if you want DP 1.4 and should also work fine with Vista. I also suggested the 1070 because it was really cheap in his market, but 1080 or 1080 Ti would be considered the peak for now.