FrankieO
Posts: 2
Joined: Sun Apr 28, 2019 4:35 pm

Windows Vista compatibility lost with Mame 0.209 ?

Dear all,

when updating to Mame 0.209 64 bit or MameUI64 Windows binaries I get the following error message on my Windows Vista Home Premium machine:

Procedure entry point K32EnumProcessModules could not be located

Is support for Windows Vista dropped intentionally ?

With Mame 0.208 the problem was not there.

There are several articles on the web dealing with the problem e. g.

https://docs.microsoft.com/en-us/window ... essmodules

Basically some functionality from psapi.dll was moved to kernel32.dl from Windows 7 onwards.
For details please check the explanations further down in the article.

Is there another recommended workaround for the problem ?
mhoes
Posts: 186
Joined: Wed Oct 26, 2016 12:26 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

Hi,

I'm not sure if support for Vista was dropped intentionally, but it wouldn't surprise me at all if Vista was no longer (intentionally) supported and tested by the MAME devs, as Microsoft ended support for Vista quite some time ago (April 2017).
Robert
Posts: 99
Joined: Thu Nov 06, 2014 12:44 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

(deleted)
Last edited by Robert on Fri Sep 23, 2022 2:49 am, edited 1 time in total.
VanBa
Posts: 2
Joined: Mon May 06, 2019 1:55 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

I got the same error message, trying to launch MAME 0.209 32-bit on a old Dell running Windows XP .

My goal was to check if, trying to launch Breakout [TTL], I will get the same error message I got using MAME0.208/209 on my MacBook:

Code: Select all

Caught unhandled St16invalid_argument exception: Continuation after numeric value ends: 2.52
Found 1 info blocks
Found block with 1 dangling allocations
I would like to know if the bug occurs in all versions, or in the Mac version only. I used the 0.208 downloaded from lngn.net, and the 209 downloaded from choccyhobnob.com.

What is the latest version compatible with Windows XP?
Can anyone try to launch Breakout [TTL] using a 64-bit version of Windows or Linux?
mhoes
Posts: 186
Joined: Wed Oct 26, 2016 12:26 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

VanBa wrote: Tue May 07, 2019 9:03 am I got the same error message, trying to launch MAME 0.209 32-bit on a old Dell running Windows XP .

[ ... snip ... ]

What is the latest version compatible with Windows XP?
Any form of support for XP probably ended quite some time ago (version 0.153 perhaps ?), since Microsoft ended support for Windows XP in April 2014 and it would surprise me if the MAME developers continued to support it after that date.
VanBa wrote: Tue May 07, 2019 9:03 am I used the 0.208 downloaded from lngn.net, and the 209 downloaded from choccyhobnob.com.
The place to get the official version is the mamedev website or the corresponding github page at:

https://www.mamedev.org/
https://github.com/mamedev/mame/releases/mame0209/
VanBa wrote: Tue May 07, 2019 9:03 am Can anyone try to launch Breakout [TTL] using a 64-bit version of Windows or Linux?
I tried Breakout TTL with MAME 0.206 64-bit on Windows 10 and it appears to run fine.
User avatar
Stiletto
Posts: 96
Joined: Thu Nov 06, 2014 4:11 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

mhoes wrote: Tue May 07, 2019 3:15 pm
VanBa wrote: Tue May 07, 2019 9:03 am I used the 0.208 downloaded from lngn.net, and the 209 downloaded from choccyhobnob.com.
The place to get the official version is the mamedev website or the corresponding github page at:

https://www.mamedev.org/
https://github.com/mamedev/mame/releases/mame0209/
Unless it's the precompiled MacOS version, which VanBa clearly is normally using. MAMEDev.org links to lngn.net and choccyhobnob.com for MacOS builds.
- Stiletto
mhoes
Posts: 186
Joined: Wed Oct 26, 2016 12:26 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

Stiletto wrote: Tue May 07, 2019 4:32 pm
mhoes wrote: Tue May 07, 2019 3:15 pm
VanBa wrote: Tue May 07, 2019 9:03 am I used the 0.208 downloaded from lngn.net, and the 209 downloaded from choccyhobnob.com.
The place to get the official version is the mamedev website or the corresponding github page at:

https://www.mamedev.org/
https://github.com/mamedev/mame/releases/mame0209/
Unless it's the precompiled MacOS version, which VanBa clearly is normally using. MAMEDev.org links to lngn.net and choccyhobnob.com for MacOS builds.
Oops. My bad. Sorry.
Robert
Posts: 99
Joined: Thu Nov 06, 2014 12:44 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

(deleted)
Last edited by Robert on Fri Sep 23, 2022 2:50 am, edited 1 time in total.
VanBa
Posts: 2
Joined: Mon May 06, 2019 1:55 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

News about the MacMAME-Breakout crash.

I tried MAME 0.209 for XP and no error occurs.
Even an older version of MAME for Mac (0.200) doesn't trigger the error reported in the post above. This happens only when using MAME 0.208 and 0.209, launching Breakout or Pong revision E (PongDoubles works fine).
Due to lack of hard disk space, I am unable to compile the program myself, I used the precompiled versions listed on the official website.

I'm going to open a discussion on the Bannister forum, in the "Non-Windows MAME support" section, because it seems a Mac-only problem.
But I have yet to find a Linux system to play with. Any help?
mhoes
Posts: 186
Joined: Wed Oct 26, 2016 12:26 pm

Re: Windows Vista compatibility lost with Mame 0.209 ?

VanBa wrote: Tue May 14, 2019 1:17 pmBut I have yet to find a Linux system to play with. Any help?
For what it's worth: I tried MAME 0.209 64-bit on Fedora 29 (the version that comes with the Fedora 29 distribution), and do not get the specific error mentioned here when starting Breakout [TTL]. However, I do get this error/warning:

Code: Select all

Carla assertion failure: "shmIds != nullptr && std::strlen(shmIds) == 6*4" in file libjack.cpp, line 133
The game seems to function ok, though, so my first gut feeling is that the two are not related.

-- EDIT --

I get that assertion failure on *every* invocation of MAME, even for something like 'mame -showusage', so I guess that means that this error and the one you get are definitely not related.

-- EDIT 2 --

This error seems to have something to do with audio, which kinda makes sense in my setup since I haven't got audio configured correctly on my Fedora 29 setup.

Return to “MAME Discussion”