Updated from Mame32.101 to Mame32b & now some games won't play

[Odin]

I upgraded from Mame32.101 to Mame32b.106.  It appears that I have more games in the "Available" folder now, but a lot of them don't work.  When I try to load Star Wars or Tempest or Metal Slug or a variety of other games the screen flashes for a second and it goes back to Mame.  So I went back to Mame32b last verified working version but still no dice on the games that were previously working in Mame32.101..

Is this a setting that I need to change or are these games just not going to work with the newer version of Mame32?

Mame32b says those games are "working" but I can't get them to load up.  Any help is appreciated.

[gamecreature]

Check your roms. Sometimes a rom changes (or requires the support of a missing bios or parent rom) when Mame is updated.

[kiddk1]

is there a setting where you specify where the roms dir is in mame32b?

[Odin]

All the ROMS are recognized by Mame32b but some just stopped playing.  When I load the game the screen flashes black for a second and then it goes back to Mame.  The directory structure is OK because I can see the ROMS from Mame.  Either Mame32b stopped supporting some games that previous versions supported (I don't know why that would be) or I have a setting that needs to be changes somewhere (more likely).  I just don't know where to start looking.

[gamecreature]

Sometimes the program will assume the rom is okay when something (such as a bios) is missing. What happens when you validate?

[Odin]

I'm not sure I understand what you mean by "validate".  I can Audit the ROM and it says it's OK.

[unclet]

Can you download command line Mame and see if the game starts correctly? 

Did you verify all your v106 ROMS with ClrMamePro?  This will let you know whether the ROMs are correct or not....

[BobA]

Ran across the same problem in mame32.106  Noticed MSlug series was not playing.  Would load with no errors but would return to menu without starting game.  Command line mame106 worked fine so roms and BIOS are OK.  Updated to mame32.107 and MSlug works again.  Must have been a bug in mame32.106

[krick]

I upgraded from Mame32.101 to Mame32b.106.

There is no such thing as MAME32b.

There are two downloads available for version 0.106:

mame32s (the s stands for "source", as in source code that must be compiled)
mame32b (the b stands for "binary", meaning a ready to run executable).

The version you have is "MAME32 version 0.106" which is based on the MAME core version 0.106

[Pi]

It sounds as if MAME was trying to change to a graphics mode or refresh rate that your adaptor or monitor don't support. I can't recall the exact options you need to touch, but tell MAME to not change the resolution (so it uses the desktop resolution) and enable hardware stretch.