Posted by scotto on 2, 2001 at 4:32 PM:
In Reply to: Well, I at leat can help with the settings and controls posted by GadgetMan on 2, 2001 at 2:26 PM:
I haven't tried it yet, but that sounds like a perfectly plausible solution.
: : Ok... I recently got a new computer, and after migrating my arcade stuff, some problems have cropped up. Some of the problems I had before that point.
: : Here's what I'm running: I have a Q*bert cab with a 19" arcade monitor. P1 controls are a hacked Gravis Gamepad, while P2 controls and the control buttons (tab, esc, 1,2,3), are via a hacked keyboard. I run AOS with both Mame and AdvanceMame. I renamed the Advancemame .exe and .cfg "amame" and placed them in the mame directory.
: : System is an Athlon 1Ghz/ 128mb/30G running windows ME. I launch AOS from a DOS window, and that works fine. Flipping between CPU and Arcade is done via a manual (soon to be auto) switchbox.
: : Problems 1:
: : Since I changed systems, I need to calibrate the joystick upon every launch of a game. It is identified properly and calibrated properly inside of windows, so that's likely not the issue, as I see it.
: No, it's most likely the method used to "transfer" your arcade emulation files from PC to PC. If you saved them to CD's and copied tem in, or some other method like that, the .cfg files are all read-only and don't update upon exiting a game. use the attrib -r function to set them to NOT read-only and try then.
: : Problem 2 (had before switching systems): After I save specific resolution/resizing options from the 'video' option in Advancemame, the game does not remember the settings on the next launch. I have to reconfigure this on each launch with games that are resized.
: I'm not an expert with Advancemame, but the above scenario may be in effect here. The ONLY files that don't matter (read-only or not) are the actual ROMS and SAMPLES. Everything else should NOT be read-only.
: That should do it.