wierd issue

[exibar]

Some games won't play via command line mame, citing a file part missing error (or sometihgn to that like).  But, when I fire up mame32, the game plays.....  What gives?

  Take TRON.ZIP for instance, it won't play at all via command line MAME, giving this error message:

C:\mame>mame tron
82s123.d12   NOT FOUND
ERROR: required files are missing, the game cannot be run.

 BUT, when I go and play it with mame32, it plays fine....  There is only one TRON.ZIP in my ROMS folder, is there another file that MAME32 finds but command line MAME doesn't find?

  I'm totally stumped by this wierdo thing!

  thanks all!
    Mike B

  If it's something stupid that I'm overlooking, please feel free to laugh at me, but please tell me what it is :-)

[exibar]

I guess the ROMS change over the years.... darn, even the old ones change ;-(

  I was using an old verion of MAME32 and .86 MAME command line....  

  I'm grabbing a complete set of .86 ROMS and will use those.  Do the ROMS change with every new build of MAME?  That would be a bummer to have to refresh all my ROMS with every new MAME build.....  

  Mike B

[bryan1945]

 I'm grabbing a complete set of .86 ROMS and will use those.  Do the ROMS change with every new build of MAME?  That would be a bummer to have to refresh all my ROMS with every new MAME build.....  

  Mike B

Not all the ROMs, but a chunk of them do.  As for new versions, there are sites that release update packs that contain just the new ROMs for each version, so if you have v.79 and get mame .86, you can grab .79>.86 pack, though you may need to do .79>.82, then .82>.85, and finally .85>.86.  

As for mame and mame32 not working and working, respectively, make sure you have a mame32 that is built on the same version of cli mame.

[u_rebelscum]

Some games won't play via command line mame, citing a file part missing error (or sometihgn to that like).  But, when I fire up mame32, the game plays.....  What gives?
...
  If it's something stupid that I'm overlooking, please feel free to laugh at me, but please tell me what it is :-)

Not anything stupid on your part, just a hidden thing.  Mame uses mame.ini in the mame folder.  Mame32 uses ini/mame32.ini.  They probably have different settings.