Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - MachoMan22

Pages: [1]
1
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?

2
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.

3
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

4
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?

Pages: [1]