Mame not getting focus when lauching from AM in anything but Window-Mode

[MachoMan22]

I am guessing this problem has a hardware or driver interaction, because I only have this problem on one older [2006] Dell tower PC I just recently purchased.  I tried several different versions of Windows 10 on this PC (Pro, Home, Home N).  The bios is updated, and the graphics driver is up-to-date according to Device Manager.  My other PCs/Laptops run Windows 10 Home, Windows 10 Home N, and Windows 8.1 with no problems in any display mode.

On the afflicted PC, when launching a mame rom from AM, AM begins its correct process by switching to a black screen, however MAME is never brought into focus.  My exit hotkey will bring me back to AM.  This problem seems to only affect Fullscreen Mode and Fillscreen Mode (default).  As long as I run AM on this PC in Window mode or in Window (no border) MAME will be given the focus it needs.

Has anybody had success at figuring out what hardware or driver issue causes this malfunction?

[Brian]

I'm having the same issue. I registered here to post the issue but you beat me to it. Not sure if it's related to drivers. I have a newer PC but needed a graphics card with s-video to connect to a CRT TV. I bought a used ATI 2400 XT and Windows 10 installed the driver. I'm unable to install any driver or Catalyst program since it's not supported I'm guessing. Either way, the driver Windows installed works fine.

[progets]

Look at this thread for suggestions http://forum.attractmode.org/index.php?topic=2589.msg17681#msg17681.

You could also try the experimental AM release here http://forum.attractmode.org/index.php?topic=2597.msg17721#msg17721.

[jimmer]

2.0.0.cr2 is the ONLY version in the 2's that works properly on my arcade cabinet:  Win7 64bit SP1 aerotheme (necessary) Intel HD2000 integrated graphics.

Give it a go and report back. It could be a good clue for the developers.

[Brian]

2.0.0.cr2 is the ONLY version in the 2's that works properly on my arcade cabinet:  Win7 64bit SP1 aerotheme (necessary) Intel HD2000 integrated graphics.

Give it a go and report back. It could be a good clue for the developers.

Thanks for the info. I tried your recommended version and MAME now focuses correctly.

[MachoMan22]

2.0.0.cr2 is the ONLY version in the 2's that works properly on my arcade cabinet:  Win7 64bit SP1 aerotheme (necessary) Intel HD2000 integrated graphics.

Give it a go and report back. It could be a good clue for the developers.

Wow, this worked for me too!  Thanks!!

Runs like a champ on version 2.0.0 rc2
I was worried that it would be too old of a revision to run the new Nevato layout, but that too works flawlessly.

Great suggestion!

So the PC which wouldn't run the newer versions of AM is running an internal Intel HD graphics card.  Driver date is 5/19/2016 version 9.17.10.4459    This was originally a Windows XP computer if I check the build information with Dell, which I am now running with Windows 10 Home N.

Any developers checking the forums might want to see if there is a conflict with the HD graphics systems since two users have had same symptoms vanish by reverting to AM version 2.0.0 rc2

[xod]

I've been having major headache with AM 2.5 -> MAME, and trying version 2.0.0-rc2, and it is working, I don't need to either run AM in windowed mode, or terminate explorer shell, or set random application's window "always on top", not anymore Thanks for the tip, and hope to see a fix for latest versions (cannot try the experimental since I'm on 32-bit OS).

[jimmer]

TRIPLE WHAMMY   

I can't remember who it was, but a year ago I found a post from someone saying version 2.0.0-rc2 solved their problems, and it solved mine too.

[MachoMan22]

How do we get this information in front of the developers?

I think the root cause may have other interactions with other AM functions that may drive people away from using AM.

[Kevin]

try my Program http://meinhtpc.bplaced.net/wordpress/?page_id=30

I don't know if this work for Mame. But my Programm can set the focus to all Emulators.

[raygun]

How do we get this information in front of the developers?

I think the root cause may have other interactions with other AM functions that may drive people away from using AM.

I'm aware this issue, but haven't been able to track it down or reproduce it myself to debug.
Knowing that it doesn't happen with 2.0.0rc2 is very helpful. I've gone back and looked at what might have changed and have a theory as to what might be causing this....

I've made a test patch in 2.5.1, would someone who is experiencing this please test one of the following and let me know if the problem is still happening?:

[edit: links removed]

cheers

[xod]

@raygun

I tested the 32-bit build, and unfortunately it's the same problem as the 2.4.1 for me. (Works when setting some window to "always on top" etc, just like 2.4.1)
Log when launching AM 2.5.1 (32-bit) -> MAME 0.78 -> 1942 below under normal conditions.

Code: [Select]

loading 1-n3a.bin   
loading 1-n4.bin   
loading 1-n5.bin   
loading 1-n6.bin   
loading 1-n7.bin   
loading 1-c11.bin   
loading 1-f2.bin   
loading 2-a1.bin   
loading 2-a2.bin   
loading 2-a3.bin   
loading 2-a4.bin   
loading 2-a5.bin   
loading 2-a6.bin   
loading 2-l1.bin   
loading 2-l2.bin   
loading 2-n1.bin   
loading 2-n2.bin   
loading 08e_sb-5.bin
loading 09e_sb-6.bin
loading 10e_sb-7.bin
loading f01_sb-0.bin
loading 06d_sb-4.bin
loading 03k_sb-8.bin
loading 01d_sb-2.bin
loading 02d_sb-3.bin
loading k06_sb-1.bin
loading 01m_sb-9.bin
                   
Unable to start video emulation
Error setting cooperative level: 88760245

[Brian]

@raygun: test patch didn't work for me either. Thanks for looking.

[raygun]

ok thanks for checking!  back to the drawing board....

[MachoMan22]

ok thanks for checking!  back to the drawing board....

@raygun, is there any other system/driver/hardware information we all could provide to you to make your next problem solving comparison/contrast?