As with any program there are bound to be some hiccups, here are some suggestions to common perceived difficulties. Also, remember, Mame32 is now based on the core Mame[w] - if a problem exists in the Mame[w] code we inherit it. Always ensure before reporting problems with Mame32 that it *doesn't* happen in the Mame[w] version. If it does, there's not much we can do about it.  Mame is an ongoing documentation project, as such, some game may break from version to version as core changes occur beneath them.  Use a prior working version of Mame if the game you want develops problems.

1.       'My roms aren't being seen, the roms I had in version x don't work anymore.'

1.1.             This is a question that gets asked a lot, why do my old rom sets no longer work w/ newer versions of Mame32?  Mame is a documentation project, sometimes old rom sets are found to be using previously miss-dumped or damaged roms, which then need to be replaced as found.  Small color proms are also still trickling in. As new versions of Mame come on board the developers add support for new iterations and often add these files for missing games [or they will delete redundant files], this necessitates using that new updated set. Examples you might see are donkey kong, pacman, etc. from .33b. Run an audit on the game in question [highlight game, use alt-a to audit], it will tell you what files you are missing.  Those will likely have been added or altered recently. You will need to locate the changed files or download a new updated set. Note: do not email the Mame or Mame32 teams about roms.

1.2.             Mame utilises the idea of a parent / clone relationship for its games.  If you are trying to play a clone or a bootleg of a game, you will need the roms for the clone game, and the parent set.  Mame32 indicates the parent set of a clone at the bottom of the game properties tab. [alt-enter].

1.3.             Mame also utilises the idea of having single zip files to house the BIOS files for a large number of similar games, the NeoGeo games for example, share four BIOS files in every game.  Mame will look to neogeo.zip as the BIOS zip, if you have this file along with the other NeoGeo games, it will use it, otherwise Mame expect the BIOS files in every NeoGeo game. DECO cassette, CVS, and Playchoice are also BIOS games.  You will get errors if you do not have the BIOS files in some form.

1.4.             If you're getting the corrupt ROM message, secondary click on the game in the list and choose properties, do an audit on that game [or use alt-a] and you will likely find that you are missing a file or two. See item 1.1. above, it's probably a missing rom.

1.5.             F5/Refresh in the GUI. (do this anytime you alter your roms, renaming etc.)

1.6.             Ensure you have the appropriate folder view toggled, i.e. 'all games' and it doesn't have filtering on it to stop the display of the game you're looking for.

1.7.             Use the options • reset to default menu choice and check all of the items, restart Mame32.

1.8.             Final option, manually delete the registry key for Mame32 by running regedit.exe: HKEY_CURRENT_USER\Software\Freeware\MAME32

2.       Crashes & Non-Functioning Topics

2.1.             Delete the .hi, .cfg, or .nv files for the game that's troubling you.

2.2.             Check to see that you have a valid zip file and it's not corrupt or read-only.

2.3.             The game’s entry in hiscore.dat may be causing the crash, remove the entry and try again.

2.4.             If you're crashing during an audit or an F5 refresh, you probably have a corrupt .zip, extract it and re-zip. Pkunzip -t *.zip. Note the file that dies during the audit and concentrate on that one. Also verify that if you do not use zips that the folder is not empty, or contains partial or damaged roms.

2.5.             If seeing crashes or weird screen coloration, try disabling running background apps [in Win98, use msconfig.exe], Norton Crashguard, popupkiller, viruscans, fast find, the office bar, Intellimouse, even IE subscription updates, etc, try moving Mame32 away from compressed [DriveSpace, DoubleSpace, stacker] drives.  IntelliMouse and Office Toolbars are a known offenders in this category.  Also disable items in your system tray, like the CD player, etc.

2.6.             Use the options • reset to default menu choice and check all of the items, restart Mame32.

2.7.             Final option, manually delete the registry key for Mame32 by running regedit.exe: HKEY_CURRENT_USER\Software\Freeware\MAME32

3.       Performance Related Topics [sound scratchiness and stuttering]

3.1.             Mame32 will start to crackle, scratch, or echo if the game you are running is too taxing for your processor [Taito F3, Midway Wolf Unit, CPS2 games require a lot of horsepower].  You can visually confirm this by turning on FPS display with F11, and frame skip to auto with F8.  If the FPS dips anywhere or frame skipping rises anywhere during the game play, you know it’s maxing out your CPU and sound breakup could occur. The new blitter effects [partial scanlines, RGB effects] will impose further strain on your system, upwards of 50%. FYI, an AMD Athlon 1900 XP is able to do all current Mame32 games [.56] at greater than 100% fps at a resolution of 1600x1200x32 using RGB effects [the most stressful Mame32 settings].  Throw as much hardware at Mame as possible.

4.       Joysticks and Gamepad Topics

4.1.             To enable the joystick and mouse, remember you need to toggle them to the on position the first time you run Mame32, options • default options • controllers.

4.2.             Mame32 relies on DirectInput for joystick support, ensure your game pad is seen as present and active in the game controller control panel: start menu • settings • control panel • game controllers.

4.3.             Verify your joystick is seen as ID #1 in the game controllers control panel rather than being assigned a higher number.  If using multiple gamepads, ensure each one has its own ID#.

4.4.             Daisy chained gameport Microsoft Sidewinders [original] in Win2k do not work.  Use USB gamepads instead. Single Sidewinders may also cause odd behaviour like ghost button presses.

5.       Misc. & GUI Related Issues

5.1.             Getting property sheet errors on setting defaults or game properties? Get the Microsoft common controls update here: http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp, or update to IE4 or greater.

5.2.             If you are seeing icon palette corruption in the GUI when returning from a fullscreen game, try bumping up your desktop color depth to 24bpp or 32bpp.

5.3.             There may be some issues using the pure white color in the GUI as a font color choice or as a highlight, try silver or a slightly off white.

5.4.             Sometimes due to the Windows color scheme chosen, some small black ‘dots’ can display on the Mame32 icons in large icon view.  Try a different Windows color scheme.

5.5.             Seeing corruption in the screenshot/flyers/cabinets images? Resize the viewable area; Mame32 decimates the image if the area to display the image in is too small, resulting in colored patterns. [you can increase the viewable screenshot area by turning off status bar, and toolbar, and widening/heightening the screenshot pane].

5.6.             If you’re having trouble saving your keyboard mappings and configuration, verify that the *.cfg files are not read-only and that you have a \cfg directory.

5.7.             Tab menu no longer working? You’ve mapped it accidentally to something else apparently; delete the default.cfg file in the \mame32\cfg directory.

5.8.             My hi-scores aren’t being saved anymore.  For non-NVRAM games get the hiscore.dat file from www.mame.net. Remember not all games are converted to this method yet, see the hiscore.dat file itself for the list of supported games.

5.9.             The screenshot area was grayed out in Windows XP because of the inclusion of a preliminary file in .54 called mame32 manifest.  Remove that file to view the screenshot area artwork again.