jeffjohnvol

Although I'm a programmer by trade, I'm not familiar enough with windows scripting to know how to do that. Sounds like an interesting solution, but may be a little complicated for me. I think I'm leaning towards the dual directory solution that was discussed earlier. What if I used a USB flash drive as a "key" instead of a password? What would be interesting is if there was a way to have the GX data on a shared directory, say G: drive which maps to a certain directory on C:. Then if there was a script that could check for the existance of a file on say a USB jump drive, and then set the G: share accordingly (to either C:\GX\ or C:\GX_MATURE\, that might work. Then, I wouldn't need to worry about a password, I could use the USB flash drive as a "key". I could probably get a 256K version nowadays for under $5. Or for that matter, I suppose I could have two flash drives, each with 1GB one that has the normal configuration, and the other that has the MATURE configuration, and then just swap those out. Would that work?

So would that basically mean copying the GX folder to GX2 and then launching a different shortcut from the GX2 directory? Thanks.

I have a collection of ROMs, some of which are the japanese mature variety. They aren't too offensive if you don't mind nudity, but they are not ones I would want my kids to see. But if I have some guys over for poker, it would be nice to have them available. I have found how I can disable the mature section and run "update list" to remove them, but is there a way I can capture an update such that I don't have to run through the whole update a second time? I have a lot of ROMs and it takes awhile to do. Perhaps there's a config file that gets created that I can swap out? Thanks.

Come to find out, my keys got reconfigured somehow. When I hit Tab I found that I had to reconfigure my keys. The screen going black comment of mine, was related to the "Press 6 key to see controls in game". I was thinking that was the tab. Thanks. Jeff

I think when I hit the tab my screen goes black. I can try again Friday when I get home (I'm on the road alot). Thanks.

Yes, that is essentially the case, although I can't even find button two on the buttons I have on the arcade panel, so its probably right mouse or something. The GameEx was preinstalled, so sadly I haven't had to use the CP Wizard. Is that an executable I launch outside of GX, or is it on a menu? The funny thing is that when I launch the game directly from mame32, it works as the CP viewer shows it should (buttons 1 and 2 work from the first two buttons of the first row).

Hello, I'm a noob to this board so my apologies if I missed this somewhere, I read the faq and didn't see this answered, although it did answer several other questions I had. Background, I have a DreamAuthentics game cabinet with the button controls. The first player buttons have 7 buttons, two rows of 3, and then a 7th underneath that is mapped to my mouse button. Anyway, when I launch a MAME game from GameEx, the control buttons that are displayed aren't the ones that are used in the game. In other words, going into the game, GameEx shows two rows of 3 buttons (just like my panel) and for Xevious shows the first two buttons of the first row as "fire" and "bomb". In the game, these buttons don't function, but my 7th button (below the two rows) that is mapped to my mouse left click does the fire, but there is no way to use the second button. When I launch this game directly from mame32, the two top buttons work as I would expect. Can someone point me to how to map this properly? I can only play games that use one button. Thanks. Jeff

Of all the forums I have been on, this is the first one that I have been on that my first post offers a (potential) solution. I had the same concern and I found the following: http://www.daemon-tools.cc/dtcc/showthread...ighlight=script Basically, its another daemon tool product that gives you a gui to build your script. Its actually pretty cool. I tested it on Jedi Knight Outcast and it worked brilliantly. If you don't have SCSI drives you can ignore the YASU executable reference. I left the YASU part of and it still worked. Hope it helps, it did for me.