Has anyone archieved to run Sonic Mania in Windows XP?

[Tailsnic Retroworks]

I have completed the game at 100% in my PC with Windows 10, so now I want to put the game in other PC that I have inside an arcade cabinet, which has WIndows XP.
The game doesn't open in it, and I have read that many people can't open it. Is there any solution?

[Pootis17]

did you read System Requirement it's Windows 7/8/10

[Dennis el Azul]

In the store page you can read this:

SYSTEM REQUIREMENTS
MINIMUM:
OS: Windows 7 / 8 / 10
Processor: Core 2 Duo
Memory: 2 GB RAM
Graphics: DirectX 9.0c compliant video card 256MB
DirectX: Version 9.0c
Storage: 400 MB available space
Sound Card: DirectX 9.0c Compatible

I'm sorry, I think you have to update. :(

[jej]

It might work since directx9 was on xp. But expect it to chug because of denuvo since you cab probaly has a core 2 duo.

[Tailsnic Retroworks]

Originally posted by ^5afro man DAN:

It might work since directx9 was on xp. But expect it to chug because of denuvo since you cab probaly has a core 2 duo.

It has an i3. The Windows XP is the SP2, for the 15Khz and drivers to work better

[Silent]

This shouldn't be too hard to patch... but I wonder is there even more than 2-3 people interested in it?

[wrz]

Someone on SonicRetro posted this information. A TLDR version is that XP does not have certain program functions (they are called APIs) that the NT 6.0 kernel (Vista) and newer have. Some of these APIs are Sonic Mania itself using them, while others are apparently Denuvo.

Credit to TuxKnux:

"I spent a lot of time trying to Mania to run on XP. GetTickCount64() merely returns the number of ticks since the computer has booted. It can be replaced with GetTickCount() as the functions are identical until the computer has been running for a month and a half, at which point, GetTickCount will overflow to 0 as it returns a 32-bit value, while GetTickCount64 returns a 64-bit value and thus will not. I have tested this replacement and it works.

There are four other kernel functions Mania uses that are incompatible with XP (InitializeCriticalSectionEx, QueryFullProcessImageNameW, and GetModuleFileNameW in kernel32.dll and SHGetKnownFolderPath in shell32.dll) which cannot be easily replaced. It's possible to create stubs for these functions in a file (e.g. kernelxp.dll) and hex edit the game to use that file instead of kernel32.dll, but I didn't want to spend the time to get that working. All these functions are supported on Vista, though, so the game should run on it even though it's below the minimum system requirements (I don't have a Vista system to test with; if someone wants to try it out, I'd love to hear the result).

Interestingly enough, when I replaced these functions with others that would obviously not work, the game crashes on Windows 7+. But on XP, Denuvo activates and prevents the game from running. So Denuvo might block Vista as well."

[Aemony]

I wonder if it even works on Vista without hacks, truth be told, as it seems to rely on the universal CRT DLL files that are only available on 7 and above.

[Silent]

Yeah Denuvo seems to be an issue... These listed functions could be replaced without much trouble, though. I have successfully replaced SHGetKnownFolderPath with an XP friendly equivalent once, at least.

[MrSnowKitten]

Hi, Silent! :)

I am interested in it as well and already posted the similar thread here (I've used wrapper libraries from One-Core-API - kernel32, vtdll, psapi, shell32 and propsys and managed to make it run enough for Denuvo to initialize and block any further action): http://steamcommunity.com/app/584400/discussions/0/1474222499229414326/

Note though I've renamed the libraries to not clash with the existent ones and patched the EXE accordingly. These wrappers were designed with full system integration in mind (which doesn't work for some reason), so you need to make duplicates of _native_ kernel32.dll and shell32.dll and rename those to kernelbase.dll and shellbase.dll for wrappers to work properly.

You can find the One-Core-API here: https://github.com/Skulltrail192/One-Core-API-Binaries

[Silent]

Still, unless Denuvo is removed it might make no sense to try and get it to run IMO. At least I'm not interested until it's removed.

Thanks for the link for OneCore libs though - interesting!

[Aemony]

You could also just go the Linux way and run it through Wine.

[Doktor Mandrake]

Originally posted by Aemony:

You could also just go the Linux way and run it through Wine.

Yup it works flawlessly on wine

But you know what some windows be like, they'll stick to XP and still claim windows is better! lmao

[Silent]

The problem is, dated PCs which were supported by XP and its drivers don't always work fine with Linux - been there, done that; one of the PCs I maintained works "fine" on XP but I'd fail to get it to work at sensible speeds on Linux due to its ATI GPU being really old.

[Aemony]

Originally posted by Silent:

The problem is, dated PCs which were supported by XP and its drivers don't always work fine with Linux - been there, done that; one of the PCs I maintained works "fine" on XP but I'd fail to get it to work at sensible speeds on Linux due to its ATI GPU being really old.

... Wow! You mean even Linux don't support those configs? That's honestly surprising, I didn't expect that of all things.

I saw that the One-Core-API files were based on ReactOS. Have anyone tested ReactOS proper? I've heard they're starting to finally get hardware support these years. Maybe it might be an alternative if Denuvo works in it (though chances are extremely low).

[JP32]

Originally posted by ^5afro man DAN:

It might work since directx9 was on xp. But expect it to chug because of denuvo since you cab probaly has a core 2 duo.

my laptop with c2d runs this game no problems at 30% cpu usage lol.