nullPointer

IrfanView is a pretty popular free app for batch manipulation of images. It has the benefit of being fairly user-friendly and has a good support community. For my part, I've become a big fan of ImageMagick for batch manipulation of images. There's a pretty big learning curve with it though, and you definitely need to feel comfortable using a command line interface.

This is slightly off topic, but I think it's ridiculous for MESS to all of a sudden decide that they need their own unique naming standard. I mean with MAME it's fine since MAME is the arcade emulator, but in the case of MESS these games are emulated on countless other emulators. Not to mention the fact that there are already several perfectly good (and much more mature) naming conventions. It's just dumb. Sorry for the rant.

Thanks Tom and Ben for all your hard work!

That’s perfect, thanks for posting the additional info. I’m kinda shooting from the hip here as Mame32 is of course older, and I haven’t even used MameUI for quite a while. Given that, these two settings may provide some leads I’m unfamiliar with the ArcadeMode setting (not sure if this exists in current versions of GameEx?), but it sounds like it might mess with or override the resolution settings. Maybe try running with ArcadeMode set to false? If that doesn’t work you could also try manually specifying the resolution as part of the MameOptions (as described in the preceding comment). Naturally in these situations it’s a good idea to back up your GameEx.ini before you start making experimental changes.

The common advice is to say that your ROM set must match your version of MAME due to differences in the actual ROM sets (right down to the actual ROM names) and the continually evolving MAME drivers. My advice would be to run your ROMs through your ROM verification program of choice. I prefer clrmamepro, but ROM Center is another excellent choice (if you're uninitiated, here’s a set of clrmamepro tutorials to get you started) Basically you’ll want to try to run MAME via the command line. Here’s some documentation on how to do just that.

What does your MAME command look like in GameEx (or ideally perhaps you wouldn’t mind posting your GameEx config)?

Note that this wouldn’t require a separate physical emulator, but rather two emulator slots pointing at the same emulator … but yeah stuf like this is hard to address in an ideal fashion. I wasn’t sure if you were running multiple games requiring custom input, or only Goldeneye. Have you tried simply altering the in-game control layout? Goldeneye isn’t super sophisticated in this capacity, but it does offer a number of pre-defined layouts (I think my preference is the one called Honey, but it’s been a while since I’ve played Goldeneye). If you have Project64 configured to use a battery save pack, you can save your game (i.e. not a save state), and the game will load up your control settings as part of that game save, at least for the campaign mode (not too sure about multi-player). At any rate making the modification in game is not nearly as jarring as resorting to the emulator settings. This can be addressed in two separate ways. For my part I simply exit out of Xpadder in the Launch After command and that works great for me. I know some users have reported problems with exiting out of Xpadder in this fashion, so rather than close Xpadder they simply load an empty profile as part of the Launch After command (i.e. Xpadder will let button presses pass through unmodified), thus allowing keystrokes to pass to GameEx normally upon return.

Hi Jaeron The following lines from your log look a bit suspect to me: Earlier in the log it shows that you're running MAME .141, so it seems weird that the application is attempting to verify ROMs using a MAME Plus verification schema. Perhaps your version of verify.dat is corrupt or (more likely) out of synch with your current version of MAME? Aside from that, there are a couple of standard questions that we should get out of the way. Forgive me if these questions cover the basic stuff, but we need to rule out a couple of things before diving in further. Does MAME run O.K. for you outside of GameEx? Also, does your version of MAME match the version of your ROM set?

That’s a really cool origin of your user name kaceyrayclare! When I first saw it I thought you might hail from the southern U.S. where the three part name is not so uncommon (as reflected by our venerated poet laureate Billy Ray Cyrus). Any hoo, glad your birthday has been a smashing success! Also how does the paper get transmitted through the phone lines?!

I’d recommend using some sort of key mapping software to achieve this. Xpadder is my favorite, so I have the most experience using that, but it’s certainly not the only option. I would create a number of game specific profiles in which the name of the profile matches the name of the ROM. That way you can leverage the [ROMNAME] parameter in GameEx to launch the controller profile specific to the game being launched. Using this method may create an interesting dilemma in that once you started naming controller mapping profiles you may have to name all your profiles. One way around this would be to use the emulator group feature in GameEx. Create one emulator entry for those games that rely on a common controller layout, and create another entry for all games requiring a custom controller layout. Then simply use the emulator group feature to bring those two emulator entries into one list.

Happy Birthday kaceyrayclare! May it be everything you could hope for!

GameEx fully supports any emulator which utilizes a command line interface. Note that several popular emulators utilize a command line interface in addition to a windows menu style interface. Additional support can be found for emulators that don't utilize a command line interface, but this support typically comes in the form of third-party loaders and scripts. I'd wager a guess that the list of emulators supported by GameEx is far bigger than the list of unsupported emulators. Hopefully that answer is not too obtuse. If you have any questions about setting up specific emulators within GameEx please don't hesitate to post back.

I don't think Han drinks either! ... I better have a couple for the both of you. Cheers Han!

Happy birthday Han! Have a great day! Hope you're enjoying the best possible birthday festivities that Ohio can offer! @Draco - I'm beginning to think that bottle of Crown you mentioned elsewhere is specifically reserved for these Birthday greet threads which are absolutely brilliant (and completely bonkers). Thanks for the laugh!

Awesome as always. Thanks Tom!

That would do it. It's been a while since I've done anything with it, but I believe that is still the recommended (active) branch of AutoHotKey.

Have you ever fooled around with AutoHotKey? It would be pretty simple to write a script to move the mouse cursor to the absolute lower left corner of the screen or somesuch. I think I may even have one laying around somewhere if you're interested. I'll have to take a look. Edit: It didn't take very much looking, so here it is. This is an excerpt of a script I wrote for Nestopia some time back. In this case the mouse is moved to the upper right side of the screen (just under the emulator menu), at the fastest speed possible. If you're interested here's the API documentation for the MouseMove function.

I still think the joke's on us. This guy is either: A bot (with a surprising aversion to peddling spam) A four year old Someone with a limited capacity for the English language Some combination of the above Once again, sincere apologies if number 3 is the case (although in this case I must defer to Adultery's previous question, "How high are you?"), but my money is still on number 1 (FWIW).

It might be helpful to post your emulator config that you're using for ZSNES. In the Setup Wizard go to the Emulator Selection screen, highlight the ZSNES entry, and click the 'Export Emulators' button (it's the bottom button in the center column of buttons). I don't use ZSNES myself, but I know that there's an advanced config designed for use with ZSNES (called ZSNES V6). To test it out you can go to the Advanced Emulator Setup screen for your ZSNES entry. Check out the dropdown menu field for Advanced Config and select 'ZSNES V6'. That may or may not help out with your issue, but it's definitely worth a try. Edit: This thread may be of interest to you

Thanks for all the great work guys.

Little bit more info might be helpful: What model of Core2 Duo do you have, and what model of cooler do you have (or what processor was it originally paired with)? Doesn't sound like you're overclocking, but . . . are you? My gut feeling is that the cooler will be fine. If you're not overclocking you've got a pretty decent amount of headroom before you start hitting critical temps. When in doubt fire up a good temperature monitoring utility (or the BIOS, which is OK for initial checking, but not really great for load testing obviously). RealTemp is my favorite tool for this purpose. Once you're feeling comfortable with day-to-day usage, you can load up IntelBurnTest (or stress test of your choice - traditionally Prime95 is the most popular) and see if your cooler is ready for the worst case scenario (this should always be used in conjunction with a temperature monitoring utility!).

Just out of curiosity is Cool kid a bot? Cause ... well ... hrm ... yeah ... so far his comments haven't been, shall we say erudite? No offense Cool kid, if you are in fact a human, otherwise I suspect you may be the first sign of a sentient SkyNet operative - in which case you must be dispatched with extreme prejudice.

Awesome, Thanks Tom!

Awesome update! Thanks Tom!