K4sum1

I'm thinking something happened. There's been nothing from @XPerceniol on MSFN or any activity on my forum since March 30th.

I guess I forgot to reply here. I appear to have fixed it by using 1.2.5. Not sure why it had issues at first, but it's been months without any weirdness.

You're kinda right though, I don't use XP, no GPU or USB drivers. At first I wasn't so sure about the idea, but thinking about it, having the 68 style UI with the 78 engine is actually pretty nice. Might try using this on my PC with 8.1 to see how it fares with the sites I use.

I finally got around to this again, gameplay is at 5 FPS basically lowest. I press F1 and FPS shoots up to the 30s-40s. The more text or whatever gets displayed the worse the frame rate gets. Doesn't make sense.

idk it still exists on Microsoft owned GitHub so

Yes, you need OCAPI and OpenJDK 17 (Adoptium). I haven't actually tested it but it should just work since Java 17 works.

Oh yeah, I heard SteamCMD could be used to replace the client, but not entirely sure. Maybe someone could make a somewhat decent GUI for it.

I forgot to report back or test.

I'll be looking at Steam. I'll hope to at least make something work after the last client, but seeing as how everything in modern Steam is a webview of sorts it's probably going to be impossible unless it still just works with the old CEF.

Has anyone figured out integrating drivers? (outside of USB 3) I need to know.

No, but you can probably modify the source of the program and compile it.

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?