Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: cnsf on April 13, 2016, 09:36:21 am
-
I have MAMEHooker working well in my Win 10 64 bit Pro MAME cab running Hyperspin as the front end. I use it to run my Q*Bert knocker.
Everything is fine in regular MAME games. When I try to run a console (Atari 2600, Sega Genesis, Colecovision or Intellivision), MAMEHooker causes MAME to go into a dialog box error loop. Once I select out of every error box, about 30, then MAME is running in the background properly (I have to alt-tab to it).
I tried running a separate instance of MAME for just the consoles in another folder (D:\emus2 vs D:\emus) so any inis would be separate.
I am running MAMEUIFX 0.171 and MAME64 0.171. I have the same problem with both builds.
Any suggestions? It was very tough to pin the problem down to MAMEHooker, but it is clear that when it is not running, everything is fine.
Thanks in advance.
-
It sounds like mame is sending a weird command to mamehooker when launching console games. I haven't tested mamehooker with the new merged builds. I'll look into it when I get a chance.
-
It sounds like mame is sending a weird command to mamehooker when launching console games. I haven't tested mamehooker with the new merged builds. I'll look into it when I get a chance.
Thanks. Very much appreciated.
-
It sounds like mame is sending a weird command to mamehooker when launching console games. I haven't tested mamehooker with the new merged builds. I'll look into it when I get a chance.
Thought I'd check in to see if there was an update. Thanks in advance.
-
Yeah read the interop SDK thread. Mame's output system has changed and it's screwed up. Until they fix it we are in a holding pattern.
-
Thought i'd check in again to see if there is any update. Is it a MAME issue or Windows 10?
-
Read the sticky.
-
Thanks! I'll try the workaround.