bkenobi

If you want to run GameEx from multiple accounts, you may have to install it on each account so that you get the registry entries in each. I don't know if Tom set it up so that the registry stuff is in a global location or if it's user specific. Just so you know, you can install to the same location on each account and it shouldn't hurt anything as far as your settings.

Well, I really don't recommend doing this because you won't see ANY errors in GameEx and you could end up with an infinite loop. However, it would be pretty easy to run an AHK script that sits in the background and waits for a window with a title matching the GameEx error dialog. It could then run closewin on the dialog and then relaunch GameEx. If you need help with this script, let me know and I (or someone else who beats me to it) can help.

Just curious, but what software needs a joystick that can't use keyboard input? I originally was planning on using PPJoy to remap my GP-Wiz from 1 controller to 2, but found it too complicated and unnecessary.

Can you run the emulator correctly from the command line when the machine is shelled? Try running the same command line that doesn't work from shelled GameEx after killing the GameEx process and again from windows with no shelling. I can explain more if that isn't obvious.

Are you sure the movies exist for those games? If it displays a snap, I suspect that it didn't find a video snap with the same name as the rom name.

This is a bug in the way those fields are used. It looks like Tom will need to take a look at it and see whether we need to parse and edit the databases, or just adjust how GameEx utilizes the data from them (probably the latter).

It's no problem. Figuring out how to get everything working is half the fun. I've actually spent exponentially more time building and tweaking than I have playing games...and it doesn't bother me one bit! Actually, those specs aren't bad and should run MAME just fine (except for the few outliers like Seattle based roms). Yeah, just get a video card to play nice and you should be good to go.

Yup, if the emulator doesn't like long names or names with spaces, you only have 2 options. 1) Rename it as you suggested 2) Change the name in the command line to the shortened windows name like: This is a test.isoto thisis~1.iso I don't like the second option much, but it does work. Of course, if you have another file called "This is also a test.iso"the second one would become "thisis~2.iso"

In most cases, if the game's name has spaces, you can just add quotes around the romname stuff: [rompath][rom] becomes "[rompath][rom]" This might not work for all loaders, but I would give it a try.

I hope that PC was cheap. You seem to be spending a lot of time buying cards, RMA'ing them, etc to end up with an old PC running something most video cards can run. Just throwing it out there, but have you considered building/buying a new machine? I don't know anything about what you are running, but if it's giving you the blues now, who's to say it won't continue to even after you sort out the video card issue? As far as the error, did you google it? I had this error way back when as far as I can recall, and the message means that you have a driver confict. If you have an onboard video card, have you tried disabling it? Try uninstalling ALL video card drivers completely and restarting (make sure you have drivers available on restart to make reinstall easier). When I disabled the onboard video card, this error disappeared and has never returned.

I hate it when simply reading an error log gives the actual problem and it turns out I'm too lazy to look.

Oh yeah: 4) Disable info if you insert coins and try to play a game. (It's hard to play with that crap at the bottom )

All you had to do was ask... #InstallKeybdHook #SingleInstance force QuitWaitTime:=0 #Persistent SetTimer, WatchQuitCombo, 250 SetTimer, WatchMAME, 1000 return WatchQuitCombo: if GetKeyState("1") AND GetKeyState("2") { SetTimer, ComboQuitDown, 100 SetTimer, WatchQuitCombo, Off } return ComboQuitDown: if GetKeyState("1") AND GetKeyState("2") { QuitWaitTime:=QuitWaitTime + 100 if QuitWaitTime >=2000 { WinClose, MAME ExitApp } } Else { QuitWaitTime:=0 SetTimer, WatchQuitCombo, 250 } return WatchMAME: IfWinNotExist MAME { ExitApp }

Read the info from the DatUtil homepage.

Tom's suggestion is just about the bezel artwork that shows GameEx. The only settings for the screen saver game information are 'ON' and 'OFF' at the moment. This is a relatively new feature and has not been updated since its inclusion. I think your request is one of two or three that should probably be considered when it gets updated though. Screen saver game info update ideas: 1) swap the location of the info from the bottom to top/sides to avoid burn-in. 2) enable info for advance MAME 3) I can't remember right now, but there was a 3rd suggestion...

Fix the working path...

What is the AHK script doing? You can kill the script cleanly on its own, so if you post it, we can get it going. If it's the one I wrote, I post the question in that thread and I can edit it to include the code (I keep it running at all times, so it wasn't an issue for me).

Quick note. This quits when you hold keyboard 1 + keyboard 2, which is defaulted to P1 Start + P2 Start. If you remap your keys in MAME, just replace the 1 & 2 keys as appropriate. If you need a reference for what the keys are called check the AHK help file or search at www.AutoHotKey.com for "remapping". I would provide a direct link, but my stupid ISP has decided that AHK is inappropriate and/or contains malicious code...

Nope, that's new as of 0.107 or so. One thing you can do is either send Alt-F4 (Windows forced quit) or use the AHK WinClose statement above. Either *should* work, but it's possible MAME will steal the Alt-F4.

I didn't notice the corruption not occurring on the desktop in the last pic. I'm glad you got it sorted out! Btw, overheating manifests in many ways depending on the component that's overheating. In this case, it looks to me like it's a 3D accelerator issue since the 2D (desktop) isn't a problem. If Andy's going to replace the card, then good to go!

Install GameEx and run the Theme Editor from the start menu. There is a menu item that does it (I believe it's built into the open command. I have not done this personally, but I have seen a number of results from those who have used it and it looks good. I can take a look this evening if you need help and no one else gets to it first.

Probably a video card problem. Is it overheating? Check to see that the fan on it hasn't died. Could also be a conflict, but I'm banking on either a dead fan or a dying card altogether. Oh, it could also be caused by dust clogging fans or just insulating components from air flow...

Are you using the number keys on the top, or the keypad keys? The script looks for the standard number keys (above the letters) and if 1 and 2 are held down for 2 seconds, it sends the escape key. I don't think this will work with the current version of MAME since it requires raw input (the script is a bit old). If you want to see if it's detecting the keys, replace: Send {Blind}{Escape} with msgbox booooom! If it pops up a message box, it's working. If not, then your keys are not sending the standard 1 & 2 buttons. Not a problem, just requires an extra step. Also, it might be easiest to open notepad and save an empty text document as MAME (no extension). Keep it open while trying the script. That way, it will see "MAME" in the application name field and enter the IfWinActive section. Otherwise, you can just delete that line and the two brackets. Either way...

I haven't had this problem, but it appears that the data is incorporated in such a way that the string in the database can affect other code. This is the same way that people do buffer overrun hacking. Are you trying to hack GameEx? Tom! This guys trying to F' with your code! Tom, where are you?!