Weird Issue with "Insert Coin" and MAME - help!

[javeryh]

Can anyone think of a reason why Insert Coin (5 on keyboard) would work for some games but not for others?  I am trying to play Mr. Do!'s Wild Ride and I cannot insert a coin using a microswitch wired to "coin" on my iPac2.  If I try playing Ms. Pac-Man or whatever else (I've tested about 5 other games) the coin button works fine.  I checked the settings in the Tab menu for Mr; Do!'s Wild Ride and Coin is set to "5" so it's mapped correctly.  It's driving me crazy.

Here's a video of it in action:



EDIT: Just tested like 30 more games and both Asteroids and Mr. Do!'s Castle will also not recognize the coin inputs.  All other games appear to be working.

[KenToad]

What happens when you try to remap the non-functional button while playing the game? Does Mame identify the button press?

[javeryh]

What happens when you try to remap the non-functional button while playing the game? Does Mame identify the button press?

Yes.  I hit Tab while in game -> Input (this machine) -> scroll down to Coin 1 -> press enter to remap -> press coin return button on cabinet and it says "Kbd 5" like it should.

[KenToad]

What happens when you try to remap the non-functional button while playing the game? Does Mame identify the button press?

Yes.  I hit Tab while in game -> Input (this machine) -> scroll down to Coin 1 -> press enter to remap -> press coin return button on cabinet and it says "Kbd 5" like it should.

That's really weird. What version of MAME?

[javeryh]

What happens when you try to remap the non-functional button while playing the game? Does Mame identify the button press?

Yes.  I hit Tab while in game -> Input (this machine) -> scroll down to Coin 1 -> press enter to remap -> press coin return button on cabinet and it says "Kbd 5" like it should.

That's really weird. What version of MAME?

MAME .217 and corresponding roms.  Its really weird that it’s not limited to one game either.  It’s driving me crazy.

[spisi]

Did you check the .cfg or .ini files?

[javeryh]

Did you check the .cfg or .ini files?

I deleted “dowild.cfg” and it didn’t fix the issue.  Is there also a dowild.ini somewhere?

[meyer980]

I don't have a definite answer but some thoughts that may help.

1. Are you using AutoHotKey by chance at all? I found on a recent machine I setup that some games wouldn't coin up properly when I was using that to "simulate" key presses until I tweaked how long it triggered them for. I'm guessing you aren't, since you're using an IPAC already, but something to consider. Does it make a difference if you hold the button down longer for example? Or if you manually short the two wires together instead of using the switch? I wonder if some games were designed to expect a certain length of trigger or who knows what (maybe even as a security check). That's just me speculating though.
2.What happens if you change Mr. Do's Wild Ride coin button to another button on your CP just temporarily. Does it coin up then? If so, we'd know it's something unique about that slot on the IPAC potentially.
3. Since it's happening ONLY on specific games and is repeatable, I think you can rule out wiring which is nice to know!
4. As a double confirmation though, you could launch notepad in Windows and confirm when you hit your coin button "5" appears and nothing else.

Best of luck, these are the annoying things to troubleshoot.

[javeryh]

I don't have a definite answer but some thoughts that may help.

1. Are you using AutoHotKey by chance at all? I found on a recent machine I setup that some games wouldn't coin up properly when I was using that to "simulate" key presses until I tweaked how long it triggered them for. I'm guessing you aren't, since you're using an IPAC already, but something to consider. Does it make a difference if you hold the button down longer for example? Or if you manually short the two wires together instead of using the switch? I wonder if some games were designed to expect a certain length of trigger or who knows what (maybe even as a security check). That's just me speculating though.
2.What happens if you change Mr. Do's Wild Ride coin button to another button on your CP just temporarily. Does it coin up then? If so, we'd know it's something unique about that slot on the IPAC potentially.
3. Since it's happening ONLY on specific games and is repeatable, I think you can rule out wiring which is nice to know!
4. As a double confirmation though, you could launch notepad in Windows and confirm when you hit your coin button "5" appears and nothing else.

Best of luck, these are the annoying things to troubleshoot.

1.  I don't think I'm using Autohotkey... but honestly I don't know because I'm using Rocketlauncher and Hyperspin and there might be some built-in scripts that those programs are using.  Holding down the coin button does not make it register...

2.  If I change the Coin button to another button on the CP it works perfectly.  Quick press of the button adds a coin.  Good thinking - might mean an iPAC issue?

3.  I hope it isn't the wiring.  I have rewired the coin door 3 separate times now due to weird issues.  I even bought a multimeter to test the connections.  When I set it to test connectivity (the sideways wifi looking symbol) the output is a 1 and then when I touch the leads, the number starts jumping around to like 877 then 1650 at random.  It does not beep - the instructions say that it will beep during a connectivity test of the resistance is less than 30+/-20 ohms... whatever that means.  Also, the coin input works for most other games so doesn't seem like a wiring issue but I don't really know how it all works.

4.  Notepad open in Windows types 5s when I press the switch I assigned to "Coin 1" so the computer is seeing the button presses.

This is really frustrating me. 

EDIT: If I manually short the wires together I get a ---steaming pile of meadow muffin--- ton of coins to register.  So it doesn't seem like an iPAC or wiring issue.  This seems software related, right?

[meyer980]

Based on your EDIT note, I agree, I doubt it's a wiring issue. I'd also be surprised if it's an IPAC hardware issue - but based on your answer to #2 I don't think it can be ruled out completely. Continuity shouldn't be an issue since you're clearly getting input in some games and typing 5's.

I launched Mr Do's Wild Ride and didn't have any trouble coining up on my desktop computer with a couple keyboards I have on hand. I don't have an IPAC build nearby to test for ya though

My last suggestion would be to launch MAME straight from the .exe (instead of through Front End) and see if it works that way - just to make sure the FE isn't somehow capturing those inputs. I bet one of the other guys will hop in shortly and have some good advice, too. Hold strong!

[javeryh]

Based on your EDIT note, I agree, I doubt it's a wiring issue. I'd also be surprised if it's an IPAC hardware issue - but based on your answer to #2 I don't think it can be ruled out completely. Continuity shouldn't be an issue since you're clearly getting input in some games and typing 5's.

I launched Mr Do's Wild Ride and didn't have any trouble coining up on my desktop computer with a couple keyboards I have on hand. I don't have an IPAC build nearby to test for ya though

My last suggestion would be to launch MAME straight from the .exe (instead of through Front End) and see if it works that way - just to make sure the FE isn't somehow capturing those inputs. I bet one of the other guys will hop in shortly and have some good advice, too. Hold strong!

OK now I'm thoroughly confused... I launched straight from MAME exe and same issue - Mr Do's Wild Ride isn't accepting coin presses and Ms Pac Man accepts them on first button press... BUT I just figured out that Mr Do's Wild Ride DOES accept coins if I keep pressing - if I rapidly press the button (which I did out of frustration) it registered a couple of coins but it seems totally random.  Sometimes it takes 8 or 9 presses and then it will register 3 or 4 in a row and then go dead again for a bunch of presses.  WTF is going on?  Here's what's happening:

[vertexguy]

Just walking some thoughts to see if anything may help.

If windows cleanly sees your 5s in notepad without any delay and cleanly shows the exact number pressed both with slow presses and fast, then to me its software.  Your wiring is fine as is the ipac.

One test would be to use a different version of mame and test just one game that consistently isn't working.  If it works its maybe a weird mame version issue.

If it still doesn't work, but remapping to another button always works in mame, then its almost like something more specific to number 5 key is being intercepted by something else running and mame never gets it, or sporadically gets it.  Of course to be specific to one game and not the other makes it stranger and to me points to a config for that game.  Try eliminating other software like hyperspin from the mix..Gotta eliminate variables to find the root cause more easily.   

[lomoverde]

I just tried Mr DOs wild ride on my desktop.If i tap rapidly the 5/coin key the credit registers,if i press the key and hold down for slightly longer then release it the credit doesnt register.

Is the switch signal registering a long press or something?Can you change the length of the pulse thru software?

Ive just checked a few other games,Mr Do registers the credit on the downpress,as does Ms pac.Wild Ride and Castle register as the key is released but only if it was a rapid press,holding longer doesnt register.It must be the length of signal or something MAME recieves.

[javeryh]

Just walking some thoughts to see if anything may help.

If windows cleanly sees your 5s in notepad without any delay and cleanly shows the exact number pressed both with slow presses and fast, then to me its software.  Your wiring is fine as is the ipac.

One test would be to use a different version of mame and test just one game that consistently isn't working.  If it works its maybe a weird mame version issue.

If it still doesn't work, but remapping to another button always works in mame, then its almost like something more specific to number 5 key is being intercepted by something else running and mame never gets it, or sporadically gets it.  Of course to be specific to one game and not the other makes it stranger and to me points to a config for that game.  Try eliminating other software like hyperspin from the mix..Gotta eliminate variables to find the root cause more easily.   

Thanks - I’ll try a different MAME version and see if that does anything.  I am starting to think it is a cfg issue because the wiring seems fine and the buttons work on most other games. 

It doesn’t seem to be hyperspin because running MAME64 exe alone produces the same issue.  So at least that’s not it.  I’ll keep trying whatever people suggest!

I just tried Mr DOs wild ride on my desktop.If i tap rapidly the 5/coin key the credit registers,if i press the key and hold down for slightly longer then release it the credit doesnt register.

Is the switch signal registering a long press or something?Can you change the length of the pulse thru software?

Ive just checked a few other games,Mr Do registers the credit on the downpress,as does Ms pac.Wild Ride and Castle register as the key is released but only if it was a rapid press,holding longer doesnt register.It must be the length of signal or something MAME recieves.

Wow - I’m really glad someone else was able to reproduce this (sorry).  It sounds like there is an issue with the signal duration from the microswitches that is causing this...

There is something called “coin_impulse” in the ini file under CORE INPUT OPTIONS.  I wonder if there is a way to change the timing of the button press?  It’s not clear to me what changing that value does though.  Is that 1/0 as in on/off or is this a value in milliseconds?  I also don’t want to screw up any other games by changing this.  I can create a “dowild.ini” though and that overrides mame.ini.  I just copy mame.ini, rename it to romname.ini and put it in the ini folder (not in the root mame folder where mame.ini is located), right?

Seems strange that google brings up nothing with these games but maybe that’s because pressing “5” works fine and it is dependent on the type of microswitch I’m using (which are regular Happ switches for regular push buttons and the switches that came in the Happ coin door).

[lomoverde]

BTW IM using MAME0.219 and attract mode.

[PL1]

It sounds like there is an issue with the signal duration from the microswitches that is causing this...

There is something called “coin_impulse” in the ini file under CORE INPUT OPTIONS.  I wonder if there is a way to change the timing of the button press?  It’s not clear to me what changing that value does though.  Is that 1/0 as in on/off or is this a value in milliseconds?  I also don’t want to screw up any other games by changing this.  I can create a “dowild.ini” though and that overrides mame.ini.  I just copy mame.ini, rename it to romname.ini and put it in the ini folder (not in the root mame folder where mame.ini is located), right?

You may be onto something here.   

Some people have reported problems with the default pulse length on coin acceptors and fixed it by setting the coin acceptor pulse length dipswitch to 100ms.
https://forum.recalbox.com/topic/1575/mame-coin-button-sometimes-doesn-t-work/7

You can copy just the parts of mame.ini that you want to override into dowild.ini.

coin_impulse values:
  0 = obey driver
  <0 (i.e. -1) = disable impulse
  >0 = impulse time

Impulse time is probably either in seconds or miliseconds.
- The MAME docs here don't specify a unit of time.   


Scott

[javeryh]

It sounds like there is an issue with the signal duration from the microswitches that is causing this...

There is something called “coin_impulse” in the ini file under CORE INPUT OPTIONS.  I wonder if there is a way to change the timing of the button press?  It’s not clear to me what changing that value does though.  Is that 1/0 as in on/off or is this a value in milliseconds?  I also don’t want to screw up any other games by changing this.  I can create a “dowild.ini” though and that overrides mame.ini.  I just copy mame.ini, rename it to romname.ini and put it in the ini folder (not in the root mame folder where mame.ini is located), right?

You may be onto something here.   

Some people have reported problems with the default pulse length on coin acceptors and fixed it by setting the coin acceptor pulse length dipswitch to 100ms.
https://forum.recalbox.com/topic/1575/mame-coin-button-sometimes-doesn-t-work/7

You can copy just the parts of mame.ini that you want to override into dowild.ini.

coin_impulse values:
  0 = obey driver
  <0 (i.e. -1) = disable impulse
  >0 = impulse time

Impulse time is probably either in seconds or miliseconds.
- The MAME docs here don't specify a unit of time.   

Thanks for this.  I have tried the following with no luck:

Code: [Select]

coin_impulse 0
coin_impulse 1
coin_impulse 60
coin_impulse -60
coin_impulse 1000
According to THIS thread, Setting this value to 60 equals 1 second because it is based on framerate of the game.  However, for no reason whatsoever I just set it to:

Code: [Select]

coin_impulse 10
and it actually appears to be working!  I've only pressed the button like 10 times but coin is registering each time.  Going back over to docastle and coin is NOT registering.  So I created another file - docastle.ini and set coin_impulse to 10 and now that game is working.  So... we may have solved it.  I'm going to reboot the cab a few times and leave it running while I work in the background and testing it periodically.  I'll report back.  This is so freaking weird.

  to you guys.  This forum is awesome.

[PL1]

Great catch finding ozfalcon's observations in that other thread.   

In hindsight, it makes sense that MAME uses the number of frames for this variable.
- Greater stability for emulation if it's synced to the frame refresh rate rather than trying to use absolute time values.

Another interesting thing he found is the range of values.

WARNING - The coin impulse is a "BYTE" meaning it has a range of 0-255.
Any values over this may be either cycling 256 or unpredictable.
(Example the value of 256 gives NO coin_impulse and increments up the same as starting from 0)

Scott

[Vocalitus]

I found that issue too in .220.

[javeryh]

Great catch finding ozfalcon's observations in that other thread.   

In hindsight, it makes sense that MAME uses the number of frames for this variable.
- Greater stability for emulation if it's synced to the frame refresh rate rather than trying to use absolute time values.

I’m just so happy it is working.  It was really making me crazy and I was bummed out about things not working properly after spending so much time on it.

So... while we are on the topic of frame rates and before I start a new thread somewhere... some of the games I’m running like Donkey Kong and Ms. Pac-Man suffer from audio stuttering and I’m almost positive this is related to frame rate or vsync settings but I am not sure what to change in the ini to get it all to sync up properly.  It doesn’t make the games unplayable, just annoying.  Any ideas?

I found that issue too in .220.

Interesting... there is so little information on this topic (at least that I could find) and I would think it would be more widespread.  Maybe not enough people are playing Mr. Do!’s Wild Ride?  Heathens!

[Zebidee]

So... while we are on the topic of frame rates and before I start a new thread somewhere... some of the games I’m running like Donkey Kong and Ms. Pac-Man suffer from audio stuttering and I’m almost positive this is related to frame rate or vsync settings but I am not sure what to change in the ini to get it all to sync up properly.  It doesn’t make the games unplayable, just annoying.  Any ideas?

Use Groovymame instead.

The stuttering comes because the games' original framerates are not the same as your monitor's. GM will match the game speed to original vertical frequency and cleverly manages the difference with your monitor's refresh rate. You don't need a 15khz CRT to use GM, it works on VGA or any other monitor.

[javeryh]

So... while we are on the topic of frame rates and before I start a new thread somewhere... some of the games I’m running like Donkey Kong and Ms. Pac-Man suffer from audio stuttering and I’m almost positive this is related to frame rate or vsync settings but I am not sure what to change in the ini to get it all to sync up properly.  It doesn’t make the games unplayable, just annoying.  Any ideas?

Use Groovymame instead.

The stuttering comes because the games' original framerates are not the same as your monitor's. GM will match the game speed to original vertical frequency and cleverly manages the difference with your monitor's refresh rate. You don't need a 15khz CRT to use GM, it works on VGA or any other monitor.

So without breaking everything, can I just replace the groovymame.exe with the mame64.exe?

EDIT:  OK, I just downloaded GroovyMAME .217 (to match my .217 rom set) and unzipped it.  Looks like same file structure as regular MAME, complete with mame64.exe as the executable.  so if I just copy this over my MAME folder but keep my current mame.ini file, it should work, right?  All the settings in my front end that point to MAME should still point to the same file in the same folder.

[KenToad]

Probably goes without saying, but copy paste your mame  folder as mamebackup or something before overwriting files.

Glad the issues are being sorted. This thread is making me less interested in upgrading my setup.

 

[Zebidee]

By all means backup your mame folder, but the only things that might change are your mame.ini and maybe the files in INI and CFG directories.

All you'll need is the Groovymame executable, everything else is the same.

Groovymame works by itself, but it works best if you also have CRT_emudriver installed with a compatible GPU (AMD/Radeon). Without the driver installed GM cannot make use of switchres to change your resolutions on the fly (best). You'll basically be stuck at fixed desktop resolution, like an LCD monitor. There will be an error message in the log about not finding the driver. But yes GM does work without the driver installed and you don't even need a CRT.

OK, GM will be at its best with a compatible GPU. But let's assume for a moment that you don't have that GPU. Let's assume that you plan to run all games in 800x600@60hz.

First thing to do is delete your mame.ini, because it is easier this way. Then run groovymame.exe -cc to create a new mame.ini. Edit it for your roms directories etc.

Then run VMMaker, which should come with the CRT_emudriver package. You'll get an error message about no driver present, don't worry about this. Go to "Edit Settings", choose your monitor type (for this example choose VESA GTF 600). Then go to the last tab "mame" and browse to your groovymame executable. Click to "Export settings to groovymame". Click OK, you'll see a message "Exporting settings to mame.ini...". Type "exit" + return to quit.

Your mame.ini has just been updated with your VGA monitor's range.

There are a few settings in mame.ini you might need to pay attention to, if they aren't already correct:

video auto
resolution 800x600@60
super_width 800 (by default this will come up as 2560, so change it to your desktop max width)
syncrefresh               0
autosync                  1
autoframeskip             0
frameskip                 0
throttle                  1
keepaspect                1
unevenstretch             1
unevenstretchx            0
unevenstretchy            0
autostretchxy             0
intoverscan               0
intscalex                 0
intscaley                 0

Then try running a game like Flying Shark with:

"Groovymame64.exe -v fshark > fshark.txt".

Let it run a minute. Does the game look/sound right? Correct aspect ratio?  Quit and check the log file. Did the game run at 100%?

I hope everything I said there is right, I don't normally run it this way myself, and of course I don't know the software like Calamity.

Some other useful threads that discuss related issues:
http://forum.arcadecontrols.com/index.php?topic=146397.0
http://forum.arcadecontrols.com/index.php?topic=158259.0
http://forum.arcadecontrols.com/index.php?topic=152498.0

[javeryh]

By all means backup your mame folder, but the only things that might change are your mame.ini and maybe the files in INI and CFG directories.

All you'll need is the Groovymame executable, everything else is the same.

Groovymame works by itself, but it works best if you also have CRT_emudriver installed with a compatible GPU (AMD/Radeon). Without the driver installed GM cannot make use of switchres to change your resolutions on the fly (best). You'll basically be stuck at fixed desktop resolution, like an LCD monitor. There will be an error message in the log about not finding the driver. But yes GM does work without the driver installed and you don't even need a CRT.

OK, GM will be at its best with a compatible GPU. But let's assume for a moment that you don't have that GPU. Let's assume that you plan to run all games in 800x600@60hz.

First thing to do is delete your mame.ini, because it is easier this way. Then run groovymame.exe -cc to create a new mame.ini. Edit it for your roms directories etc.

Then run VMMaker, which should come with the CRT_emudriver package. You'll get an error message about no driver present, don't worry about this. Go to "Edit Settings", choose your monitor type (for this example choose VESA GTF 600). Then go to the last tab "mame" and browse to your groovymame executable. Click to "Export settings to groovymame". Click OK, you'll see a message "Exporting settings to mame.ini...". Type "exit" + return to quit.

Your mame.ini has just been updated with your VGA monitor's range.

There are a few settings in mame.ini you might need to pay attention to, if they aren't already correct:

video auto
resolution 800x600@60
super_width 800 (by default this will come up as 2560, so change it to your desktop max width)
syncrefresh               0
autosync                  1
autoframeskip             0
frameskip                 0
throttle                  1
keepaspect                1
unevenstretch             1
unevenstretchx            0
unevenstretchy            0
autostretchxy             0
intoverscan               0
intscalex                 0
intscaley                 0

Then try running a game like Flying Shark with:

"Groovymame64.exe -v fshark > fshark.txt".

Let it run a minute. Does the game look/sound right? Correct aspect ratio?  Quit and check the log file. Did the game run at 100%?

I hope everything I said there is right, I don't normally run it this way myself, and of course I don't know the software like Calamity.

Some other useful threads that discuss related issues:
http://forum.arcadecontrols.com/index.php?topic=146397.0
http://forum.arcadecontrols.com/index.php?topic=158259.0
http://forum.arcadecontrols.com/index.php?topic=152498.0

Thanks for this!  I think today is the day I ruin... I mean upgrade my setup.  I finally have a decent game list and all the artwork loading to the marquee display and all controls (insert coin, etc.) working as expected.  Spent most of yesterday testing out all ~180 games and deleting some that I won’t ever play and adding a few others that looked like fun. 

So now I’m going to try switching over to GroovyMAME to fix the last issue of audio stuttering.  I am certain to screw this up but no pain no gain.  I don’t think I have a GPU other than what came with the old i5 I’m using.  I tried installing nvidia control panel and it couldn’t find a compatible card.  So it seems like I’ll be running it without switching on the fly. 

The main thing I’m worried about is my MAME.ini file - I made a lot of tweaks to get things working just right like outputting video to correct monitor, adding scan lines, etc.  I’ll copy my entire MAME folder to my desktop before doing anything but the plan is to just replace mame64.exe with groovymame.exe, generate a new MAME.ini file and run a comparison with my old one so I can update the new one with all of my changes.

[Zebidee]

So now I’m going to try switching over to GroovyMAME to fix the last issue of audio stuttering.  I am certain to screw this up but no pain no gain.  I don’t think I have a GPU other than what came with the old i5 I’m using.  I tried installing nvidia control panel and it couldn’t find a compatible card.  So it seems like I’ll be running it without switching on the fly. 

Groovymame will of course be best when used with CRT_emudriver and a compatible video card so I recommend you get one. Fortunately they are quite cheap to buy. I would recommend something AMD/Radeon HD5000+, doesn't need to be fancy. You'll need a low-profile SFF card for your HP/compaq SFF desktop (or maybe not, you decased it didn't you?). There is a large list of compatible video cards (GPUs), as well as APUs and mobility/laptop processors. You can see the list and also download the drivers and access installation guides here:
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=295

Nvidia cards unfortunately won't work with CRT_emudriver.

The main thing I’m worried about is my MAME.ini file - I made a lot of tweaks to get things working just right like outputting video to correct monitor, adding scan lines, etc.  I’ll copy my entire MAME folder to my desktop before doing anything but the plan is to just replace mame64.exe with groovymame.exe, generate a new MAME.ini file and run a comparison with my old one so I can update the new one with all of my changes.

This is the way to do it.

If you have any other [romname].ini files in your mame INI directory, probably best to just delete them too (backup first with your vanilla mame). The [romname].ini files automatically override settings mame/groovymame chooses. However, because Groovymame generally does a very good job of choosing best resolution, refresh rate etc. you don't want any [romname].ini files ruining that for you. Best to let Groovymame handle it.

For further Groovymame support, best to ask on the Groovymame branch as regulars check in frequently and Calamity himself is often able to respond fairly quickly.

[javeryh]

So now I’m going to try switching over to GroovyMAME to fix the last issue of audio stuttering.  I am certain to screw this up but no pain no gain.  I don’t think I have a GPU other than what came with the old i5 I’m using.  I tried installing nvidia control panel and it couldn’t find a compatible card.  So it seems like I’ll be running it without switching on the fly. 

Groovymame will of course be best when used with CRT_emudriver and a compatible video card so I recommend you get one. Fortunately they are quite cheap to buy. I would recommend something AMD/Radeon HD5000+, doesn't need to be fancy. You'll need a low-profile SFF card for your HP/compaq SFF desktop (or maybe not, you decased it didn't you?). There is a large list of compatible video cards (GPUs), as well as APUs and mobility/laptop processors. You can see the list and also download the drivers and access installation guides here:
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=295

Nvidia cards unfortunately won't work with CRT_emudriver.

The main thing I’m worried about is my MAME.ini file - I made a lot of tweaks to get things working just right like outputting video to correct monitor, adding scan lines, etc.  I’ll copy my entire MAME folder to my desktop before doing anything but the plan is to just replace mame64.exe with groovymame.exe, generate a new MAME.ini file and run a comparison with my old one so I can update the new one with all of my changes.

This is the way to do it.

If you have any other [romname].ini files in your mame INI directory, probably best to just delete them too (backup first with your vanilla mame). The [romname].ini files automatically override settings mame/groovymame chooses. However, because Groovymame generally does a very good job of choosing best resolution, refresh rate etc. you don't want any [romname].ini files ruining that for you. Best to let Groovymame handle it.

For further Groovymame support, best to ask on the Groovymame branch as regulars check in frequently and Calamity himself is often able to respond fairly quickly.

Thanks.  Once I get going, I'll make a thread over there.  I do have some rom.ini files that I'll need to tweak too - that is how I'm solving the coin issues that this thread was initially about.

I just checked and I have a AMD Radeon HD 5450 graphics card in this computer.  Based on the link you provided it looks like GroovyMAME will work with this but installing and configuring CRT_emudriver looks... complicated.  I'm not even sure which version I should download because it looks like there are a couple choices for Radeon HD 5000 series graphics cards.  I'm going to start reading before I dive in and screw something up.  I'm not exactly great with computers as you can obviously tell..

[Zebidee]

Oh yeah, you'll need that coin impulse fix in relevant .ini files. Stuff like that won't matter so long as there is nothing that affect video/display options.

Installing CRTEMUdriver is actually a lot simpler than it looks (it daunted me at first too). A lot of it all comes down to just letting it do its thing.

The multiple choices for HD5450 is because there are desktop, APU (All Processor Unit, that is GPU built into mobo) and mobility (laptop etc) versions. This got me confused too first time I visited the site.

There are also options for "non-GCN (Graphics Core Network)" cards, but I have to be honest and say I still have no idea what this means.

The Catalyst 12.6 based driver works for my HD6450, suggest you try that first. If not, try the 16.2.1 based driver for your card.

There is a comprehensive guide with pics here, though it is focused on getting it working with a 15khz CRT, it is more or less same thing:
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?pid=1052#p1052