MAMEWAH and LED's...

[KillerArcades]

I posted this in the software forum earlier, but wasn't getting responses (and i'm a tad impatient some times ), anyways, here's my woe:

So, my system shell's straight into my FE and I just switched to PowerMAME after completing my first LED loaded CP (looks awesome!! Pics will be coming, don't worry, I'm quite proud of it Cheesy), and powermame seems to be working as I expected (wonderfully that is), but here's my question:

Can anyone tell me how to get my mahuti's app to launch with mamewah so that I can have some lighting going on while inside mamewah?

thanks in advance,

[MYX]

Have MAMEWah launch PM then you get all the PM Functions.

[KillerArcades]

yeah, but I'm referring to having my LED's animating while in Mamewah before I launch PM.

I've got PM working pretty well, but it's while in Mamewah's menu's that I'd like my start button to be pulsing to draw people's attention to it for starting a game, etc.

[MYX]

oh. I see.

[Minwah]

Forgive me for not really knowing how you operate these newfangled LED things...but I guess you could use (in mamewah.ini):

startup_app_commandlines

...to specify an app to run to do it?  This would be run as soon as Mamewah starts...

[KillerArcades]

Ah, yes that sounds like exactly what I need, can you give me a sample ini line with that command line...? something like this:

startup_app_commandline                    (application filename, eg c:\app.exe)

just add that in the mamewah.ini Misc Options area...?

And if that's correct, then my next question is, will this startup_app be re-initiated every time I exit an emulator and come to mamewah if I turn it off in my emulator specific ini "external app" commands?

Right now, when I want to launch my NES emulator, I launch my LED control app (swiftled) through using the emulator specific ini file's "external application settings" lines to launch the lighting setup for my NES controls. So, if I use this startup_app commandline to launch my LED app in the FE, then I'll use these emulator specific external app commandlines to stop that sequence and then the second line to start my emulator specific lighting sequence, correct?

That then makes ask you if there a way to send a command/control to an external app upon exit of my emulators so I can stop a lighting sequence and return to the FE without that emulator specific lighting sequence still running?

And that then brings me back to the second question I had above about whether or not the startup_app command will be re-initiated/re-sent every time I exit an emulator and come back into mamewah, so I can consistently have one lighting sequence running in my FE, and different ones per emulator, etc.

Is that too much to ask. 

[Minwah]

Ah, yes that sounds like exactly what I need, can you give me a sample ini line with that command line...? something like this:

startup_app_commandline                    (application filename, eg c:\app.exe)

Yep:

### External Application Settings ###
startup_app_commandlines  c:\app.exe

And if that's correct, then my next question is, will this startup_app be re-initiated every time I exit an emulator and come to mamewah if I turn it off in my emulator specific ini "external app" commands?

That app is only run on Mamewah startup...simple as that.

Right now, when I want to launch my NES emulator, I launch my LED control app (swiftled) through using the emulator specific ini file's "external application settings" lines to launch the lighting setup for my NES controls. So, if I use this startup_app commandline to launch my LED app in the FE, then I'll use these emulator specific external app commandlines to stop that sequence and then the second line to start my emulator specific lighting sequence, correct?

Correct...and you could then use the 'post_emulator_app_commandlines' to run the 'FE LED' sequence again after quitting the emulator.

That then makes ask you if there a way to send a command/control to an external app upon exit of my emulators so I can stop a lighting sequence and return to the FE without that emulator specific lighting sequence still running?

Oh, I think I answered this above...

And that then brings me back to the second question I had above about whether or not the startup_app command will be re-initiated/re-sent every time I exit an emulator and come back into mamewah, so I can consistently have one lighting sequence running in my FE, and different ones per emulator, etc.

Nope, see above again.

One thing to note...you'll need to use the latest beta (v1.62b10) to use these features properly...but I think it will do exactly what you want, using the following settings:

(mamewah.ini):

startup_app_commandlines                  (use this to start the FE LED app, when launching Mamewah)
exit_app_commandlines                     (use this to quit the FE LED app when Mamewah is quit)

(emuname.ini):

pre_emulator_app_commandlines             (use this to quit the FE LED app, and start the Emu LED app)
post_emulator_app_commandlines            (use this to quit the Emu LED app, and start the FE LED app)

Note: for all the above settings you can specify multiple apps seperated by semicolons ( ; )..eg:

pre_emulator_app_commandlines c:\app1.exe;c:\app2.exe

Hope that helps

[KillerArcades]

Awesome! I think that's exactly what I need. I'll download your latest beta and give it all a shot tonight.

This is going to be so friggin' awesome!!!!!!!

[MikeT]

Thanks Minwah!!!!!

I needed this info as well - You're awesome!

Mike

[KillerArcades]

One question, where can I get the latest beta version you mentioned?  I can't seem to find it anywhere on your site.

thanks,

[KillerArcades]

nevermind, got the answer I needed.