--------------------------------------------------------------------------------Q: Virtually none of my MAME ROMS are working. I've got the latest versions. A: You need MAME ROMS which are compatible with MAME 0.37b5. This is a relatively older version. Many of the later version MAME roms will not work. Some ROMS can be easily converted (using freely available tools), others cannot. --------------------------------------------------------------------------------Q: Why isn't Neo Geo game 'X' not working?A: Currently, it's not included. Will be added later when more memory becomes available.--------------------------------------------------------------------------------Q: Why port MAME 0.37b5 and not some later version?Later versions of MAME tend to concentrate on compatibility as the cost of performance. Earlier versions are more in line with the hardware capabilities of our target machine - in this case the Dingoo. These earlier versions have some significant programming speedups which have been removed in later versions. Two examples are the use of internal 8-bit graphic rendering and dirty buffer handling.Later versions of MAME with ALL the drivers included can easily reach a size of 40-60MB - more than the amount of RAM available to the Dingoo (which is 32MB).So basically we're talking trade-offs here.--------------------------------------------------------------------------------Q: The game fails to start. A: Large games may exceed the Dingoo's memory limitations. Even some "smaller" games may fail to load. For example xmen.zip uncompresses to 9MB. MAME then needs to decode the graphics - often doubling the size of the graphic ROM areas. MAME also needs to allocate runtime memory to the emulated machine's hardware. This can vary enormously but sophisticated hardware often needs a lot of RAM again. There is no solution to this at the moment, though I have some ideas.Some games that don't start are 'Simpsons' and some others which are 'too big'.If the zipped ROM size is approaching 2-3MB it may not fit.Unfortunately the Dingoo Native OS only has 16MB of user RAM to play with out of the 32MB.If anyone know how to change this - PLEASE let me know ASAP!--------------------------------------------------------------------------------Q: My game fails to start. I don't think size is the problem.A: Okay, it may be a bug. Let me know on the forums.--------------------------------------------------------------------------------Q: How do I set the volume?A: Press SELECT+B to get access to the volume/screen menu. UP and DOWN change the volume component and LEFT and RIGHt set the desired level.--------------------------------------------------------------------------------Q: The game runs slowly. It runs fine on the GP2X or Wiz (or some other handheld).A: The GP2X/Wiz have a very nice selection of assembler-based libraries. In particular Cyclone and DrZ80. This can speed up games which use the M68000 and Z80 CPUs enormously. When the game  starts up, an information screen describes the hardware. If there are M68000/Z80 CPUs on this  list, this may be the problem. There possibly faster cores available for the Dingoo, I will  investigate for future releases.There are two ways of increasing the running speed of a game:(1). Switch off the sound from the Game Selector menu before launching the game.(2). Increase the Dingoo MHZ speed from the default 336Mhz.--------------------------------------------------------------------------------Q: Why can't I see the entire game screen?A: The hardware being emulated varies enormously. Some hardware has screen resolution which exceeds the Dingoo's 400x240 screen resolution. As a result, you can't see the entire game screen at once. Scaling the game screen to fit into the Dingoo's screen will solve this problem. Try using one of the scalers: Scale Best, Scale Fast or Scale Half. This can be combined with 8-bit/16-bit video options to increase quality at the cost of speed.--------------------------------------------------------------------------------Q: What's the underclock option for?A: First a bit of theory:Arcade machines have CPUs which are generally faster than they really need to be. For example, CPS1 machines have M68000 CPUs clocked at 10Mhz.When the game is running, it may only use 7Mhz worth of instructions, the rest of the time the machine is literally doing nothing - waiting for the next screen refresh.MAME (and other emulators) faithfully reproduce this behavior including the needless "waiting around". By under clocking the emulated CPU (to say 8Mhz), MAME has (20%) less work to do emulating the CPU  which can be used in other areas - generally rendering more video frames.Under clocking is purely experimental on the user's behalf. As a rule of thumb, underclocking to 80% is pretty much okay. Some games will not work as they rely on precise timing - usually based on the speed of the CPU. Modifying it's speed will result in the game not running as intended or worse, not at all.No harm can come from under-clocking - except for the game not working.--------------------------------------------------------------------------------Q: What the CPU Cores option for?A: There is a new option to use the FAME M68000 core instead of the standard Musashi M68000 core.The new core is now the default. It's somewhat faster and *almost* as compatible. So far the only game that I know of that doesn't work with FAME is Roadblasters.--------------------------------------------------------------------------------Q: After playing a few games the game hangs.A: Restart MAME after each game to be perfectly sure it will start properly.Sometimes you can play multiple games no problem, sometimes not.The problem is that in other versions of MAME4ALL there are two programs, the frontend launcher andthe actual MAME executable. The frontend calls MAME, and in turn MAME calls the frontend again.Each time, the program is effectively reloaded and completely reset. The Dingoo Native version cannot load other processes - except from the launcher so there is only oneprogram, effectively the frontend and MAME meraged together.Not everything is reset entirely when you finish a game so some variables are left "as-is".This causes some problems sometimes :-)--------------------------------------------------------------------------------Q: My game used to play fast, now it's slow.A: Is it an older game by Atari? Chances are it may be using the DISCRETE sound system.Check when the game starts, it tells you what sound systems are being used.I'm planning on making this faster in the next release to replace the floating point maths withfixed point maths. This should speed it up nicely.--------------------------------------------------------------------------------Q: My game is not working, what can I do?
A: Try the following:

* Just because it's in the MAME4ALL frontend, doesn't mean it will work! I don't test all the games, there are too many!* Check the log file. It's the first thing I do when something goes wrong. MAME4ALL writes a "mame.txt" file to the Micro SD card. Make sure you have one inserted!* Generally you should only run one game and then restart the MAME4ALL fronted. If you want to play another game, exit out of MAME4ALL and restart, even if the game is in the same module. You *can* start another game and chance it will work, but no guarantee.* Try restarting (power on and off or reset) the Dingoo A380 and run the desired game as the very first ROM run straight after powering up.* If the game is not being displayed in the MAME4ALL frontend check that the game is actually supported with this version of MAME4ALL. Check that you are running the right module! Some games have been moved around and some games are not in obvious modules. Check the gameslist.txt.* Check that you have the right version of the ROMS. MAME's set of ROMS have changed over the many years of it's existence. This version of MAME mainly uses m37b5 ROMs though some games require later versions. Typically these games have their versions noted in the whatsnew.txt.* Check that the game is 'likely' to run! If it's a really big game. ie. ZIP file is great than 3MB it may not work due to size.* Try running the game with default settings. ie. Remove the game's frontend and config settings from the MAME4ALL directory. If you are using my bundled frontend config files make sure the settings are compatible with your A380, especially the Mhz.* Try running the game using a directory with files unzipped already. ie if you are trying to run 'galaga' have a mame4all/roms/galaga directory with the contents of galaga.zip in this directory.* Try running the game without the hiscore.dat file. Sometimes the hiscore DB can cause issues. If you know what you are doing, you can also edit the hiscore.dat file as it's just a text file - remove any suspect game entries.* Try running the game in 16-bit graphics mode. Some games need this to display correctly. ie. Splatterhouse and other namcos1 games work faster in 8-bit mode but look better in 16-bit mode. See "games_16-bit.txt" for a list of ROMs for games that may look/work better with 16-bit mode enabled. Note: many of these may be perfectly fine in 8-bit mode.* Try running the game without sound (volume = OFF). This will not load some sound ROMS thus reducing memory requirements.* Try running the game at a slower clockspeed.