VOGONS


First post, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t

An old game that used to work with Windows 95 compatibility mode on Windows 10, no longer works. The Windows 95 compatibility mode did something that bypassed the issue, occuring without it. Now the compatibility mode no longer works. I thought maybe if someone can list the shims of Windows 95 compatibility mode, it'll work when the correct one is chosen. Where can I find such a list? Can the reader list some down?

previously known as Discrete_BOB_058

Reply 1 of 13, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

You can try the Application Compatibility Toolkit which is included in the Windows ADK for Windows 10 and 11.
It's unlikely that anything changed in any of the .sdb files but you never know.

How To Ask Questions The Smart Way
Make your games work offline

Reply 2 of 13, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
DosFreak wrote on 2022-03-02, 18:14:

It's unlikely that anything changed in any of the .sdb files but you never know.

That's what we (me and the developer of DxWnd) thought. Until he found a game that he fixed in 2016 for Windows 10 with compatibility settings, not work in 21H2/Windows 11.

ADK is fine, but it might become cumbersome to try every possible permutations.

previously known as Discrete_BOB_058

Reply 3 of 13, by teleguy

User metadata
Rank Member
Rank
Member

You will get a list when you select one of the compatibility modes in the Compatibility Toolkit.

Reply 4 of 13, by teleguy

User metadata
Rank Member
Rank
Member

..........

Reply 5 of 13, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
teleguy wrote on 2022-03-02, 19:09:

..........

That's fine, but are all of them associated with activating the Windows 95 compatibility mode.

previously known as Discrete_BOB_058

Reply 6 of 13, by teleguy

User metadata
Rank Member
Rank
Member

Yes that's only the fixes tat are part of the W95 compatibility mode. In total there are 434.

Reply 7 of 13, by teleguy

User metadata
Rank Member
Rank
Member

I just read the thread on the Dxwnd forum. The game no longer works on operating systems ranging from Win XP to Windows 10 (but used to before) so I doubt it's caused by a Windows update because most of those are no longer supported. What kind of hardware do you have?

Reply 8 of 13, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
teleguy wrote on 2022-03-02, 19:37:

I just read the thread on the Dxwnd forum. The game no longer works on operating systems ranging from Win XP to Windows 10 (but used to before) so I doubt it's caused by a Windows update because most of those are no longer supported. What kind of hardware do you have?

Pretty modern HW. Ryzen 5 1600, Aorus B450M, Nvidia GTX 1050Ti, 16GB RAM. The error in that game suggests some file access problems. I assume I have to try the IO related tweaks first.

previously known as Discrete_BOB_058

Reply 9 of 13, by teleguy

User metadata
Rank Member
Rank
Member

There's an issue with some old software not correctly identifying the MMX capabilities of Ryzen cpu's which results in crashes. 3dmark2000 and Max Payne are affected for example.

Reply 10 of 13, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
teleguy wrote on 2022-03-02, 19:51:

There's an issue with some old software not correctly identifying the MMX capabilities of Ryzen cpu's which results in crashes. 3dmark2000 and Max Payne are affected for example.

You might be correct, I think I should try to emulate the game on PCem Windows XP, and if that succeeds, a lga1151 intel pentium cpu.

I should also notify gho on trying this in his old machine, where it worked

previously known as Discrete_BOB_058

Reply 12 of 13, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
teleguy wrote on 2022-03-02, 19:59:

Glad to see a fix for the game. However I genuinely don't thing the case is same with Max Payne. My CPU is a Zen 1, and not Zen+ or Zen 2. The most I can think of is MMX issue or again memory management.

previously known as Discrete_BOB_058

Reply 13 of 13, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t

Ok after all the culprit is the EmulateHeap shim that changed after Windows XP SP1.

previously known as Discrete_BOB_058