Main > Software Forum
Advance mame does not recognize roms?
RacerX135:
First I could not get any roms to be recognized in advance mame .61
then I got them recognized in vsyncmame .61 and they all seem to work
then I ran advancemame and they are in list but none of them work now
I would use advancemame but I cannot get it to run in my arcade monitor with rage128
anyway I have a commplete tombstone romset so I think I have complete roms. in mame32 they all work
thanks
Gary Pranzo
Davestar:
Racer,
What operating system are you running, DOS, ME, Win2k, and how are you trying to launch them command line, or Front End, and if Front end, which one? Are you using the standard directory structure for ADVMAME, or are you trying to point to different directories? As for your Rage128 in an Arcade Monitor, what HZ frequency does your monitor run 15, 25, or 31? Can you describe the problem further?
----------------------
Dave
RacerX135:
windows 98 in dos mode. (I boot skipping logo and GUI)
I use arcadeos for 15khz frontend
Standard directory c:\arcadeos\mame with subdirectories in standard spot
I have a 25" wg 15khz standard rez monitor
I use j-pac
OK I have full .61 rom set (tombstone) Works fine in win32 and I got it to work in vsync mame (But I cannot 15khz to work in vsync mame.
With standard mame .61 it does not even show any of the roms
with advancemame .61 it shows all roms but when you load a game you get missing romset errors. (I know the set is complete.)
also I cannot get advcfg.exe to work on arcade monitor. It works until you select the video mode then you get a exiting due to sigvev error.
Please help. When I did mame cabs with .37 and below I had none of these probs.
Thanks
Gary P.
Davestar:
Gary,
I was having similar errors with Advcfg, then I figured out I had the wrong version of ADVmame. I was using the I686 version instead of the K6 version, which solved my problem. Also are you using the standard roms directory under advancemame, or have you modified to look elsewhere on the drive, as that is a lot of space.
------------------------
Dave
Thenasty:
I know what is the exact problem. Advmame directory for ROMS is deafult to "ROM" your DIRECTORY is called "ROMS". Change it to "ROMS" in your ADvmame.rc