K4sum1

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.

The Windows 7 install on my T430 corrupted itself and deleted many files out of System32 for seemingly no reason, luckily I had a copy of XP on the laptop and used it for a bit as I was away from home and had no ISOs or sticks with me. I am working on a MC server so I decided I wanted to play MC. I remember 1.12.2 with a resource pack ran somewhat ok under 7 so I figured 1.16,5 with Sodium and whatever would work fine, but it would just freeze the entire laptop requiring me to either reboot or get the end task prompt ready and press enter while it was frozen. I found that if I deleted my settings it would open, but when I joined the server, I got 3-4 FPS on the lowest settings with no shaders and no resource packs. I'm wondering if anyone else has had a experience like this and if they know a fix or a workaround. I'm using the newest drivers I could find for the HD 4000.

Might be a better idea to go for 392.58, it's the last 7 driver of the 390 branch, and last to support 400 series if you add the device IDs.

Ask Ximonite for his 457.51 Vista driver

I was mentioning in my experience of using a older driver on 7. Also RDR2 is Vulkan or DX12, there's no DX11.

RDR2 is Vulkan, it can run with 431.36 (older than required, but modern enough to work I guess), I've done it. It's not a hard limit, unless later versions got a hard limit.

Which one should I use for 2003 x86? Do I need to integrate two things for 2003 x86 like with x64?

I've found that any NVMe SSD just works with a generic driver, you can use the Microsoft hotfixes, Phison driver, etc. You can probably get a better SSD for cheaper btw

Some things happened in the past and a split happened. I never did anything to Jody, or at least not that I can remember. I actually want to invite Jody to the forum, but I'm worried that I might break rule 2e. I wasn't really going to mention the forum for a while until someone mentioned Chuterix's post, and I decided to post in that thread. What crap lol? Guess I won't tell people on MSFN how to get PCSX2 1.7.3581 running on Windows 7 as that's apparently crap from my "forum". Name a single account that is a fake.