Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: hellothere123 on November 17, 2007, 11:03:14 pm
-
So I have mame32, do I need to download the new version or what?
-
Yeah just found about this a few days ago.
Actually I honestly don't understand why the MAME Devs just don't devote everything to a UI version.. but the regular MAME seems user friendly now anyway now.. no dos commands it seems
Mame32 from my understanding was for Windows because it was 32-bit.. but now that Windows is moving to 64-bit (can you run a 32 bit version of windows on a 64 bit processor such as an athlon 64??) it would get confusing so they just renamed it.
If you don't need to update for any particular game then no, no need to update
-
Actually I honestly don't understand why the MAME Devs just don't devote everything to a UI version..
How about:
-Because they're more interested in emulating the arcades, not working on a GUI.
-There are dozens of great FEs, so why reinvent the wheel. Especially when many people favor them over mameUI's GUI.
-Developing for mame is much faster if you call mame from the commandline or even seperate FE, instead of from an integrated GUI.
but the regular MAME seems user friendly now anyway now.. no dos commands it seems
Yup, haven't been any dos commands since 0.36b14 (May of 2001).
Mame32 from my understanding was for Windows because it was 32-bit.. but now that Windows is moving to 64-bit (can you run a 32 bit version of windows on a 64 bit processor such as an athlon 64??) it would get confusing so they just renamed it.
Not quite.
Back when mame32 first came out (0.26.1), the official mame was still 16 bit dos (AFAIK).
However, "mame32" became a misnomer soon after when official mame was compiled as a 32 bit dos app (not sure when that happened), but the name still stuck.
The misnomer stuck even after official mame became a windows application (commandline, yes, but still a 100% 32 bit windows app).
Finally the name changed when mame & especially mame32 started having official releases in both 32 & 64 bit versions. Instead of having "mame32(32)" & "mame32(64)" or whatever else they might have been called, the name was changed to a less confusing and more correct name that (IMO) it should have changed to six to seven years ago.
If you don't need to update for any particular game then no, no need to update
Agree.
-
When I use Mame (and not Mame32) it seems like it takes longer to load a game. Like it says something like unpacking or something like that. Compiling maybe? It's been a while.
Like it'll go Loading...15%...32%....64%...100% etc and then something else and goes through the same % thing
-
When I use Mame (and not Mame32) it seems like it takes longer to load a game. Like it says something like unpacking or something like that. Compiling maybe? It's been a while.
Like it'll go Loading...15%...32%....64%...100% etc and then something else and goes through the same % thing
It's only your perception. Mame and MameUI use the same code. The only difference in starting a game is mame shows progress, while MameUI goes through the same steps but hides them. The numbers you see probably are mame/mameUI unzipping & loading the ROMs, and certainly not compiling.
This of course is assuming you are comparing the same version number. There were a few versions of mame/mameUI that tested "against hacks" that was slow. Maybe that's what you remember and are comparing it to a current mameUI?
When I say developing is faster, it's because with an integrated GUI you have to exit the GUI before you can compile, and restart GUI before testing the game. With commandline or a separate FE, you don't have to spend the extra time exiting and restarting the GUI. You can leave the FE up and running, or the commandline box open (and no, you don't have to retype the whole line, just up arrow and bang you have it all there).
-
Ok testing a game on v120 with both
On Mame it loads and then does "Decoding"
oh wait so does Mame32
neeeevermind
Oddly I saw different times to opening the same game in mame if I had opened it already a minute before.
Anyway I think I'd go with MAME for the arcade unit so I can get some kind of cool Arcade like front end so people can't access the Windows part of the computer.
Can you make Mame and MameUI share the same set of ROMs? <- just by putting them both in the same directory as the ROMs?
-
Can you make Mame and MameUI share the same set of ROMs? <- just by putting them both in the same directory as the ROMs?
If you mean something like \mame\mame.exe, \mame\mameUI.exe, and \mame\roms . . . Yes. (Hint: edit \mame\ini\mame.ini to effect both mame and mameUI.)
You can also do something like what I do: \mame121\mame.exe, \mame121UI\mameUI.exe, \mame\roms, and have both point to \mame\roms in their respective "rompath"s. However, your way is better if you use the same version; mind is better for multiple versions of mame.
-
Man...how nice would it be if MameUI was to integrate clrmamepro functions right into it. Now that would be the shiznit!
-
Man...how nice would it be if MameUI was to integrate clrmamepro functions right into it. Now that would be the shiznit!
And against mame's license.