forums.marpirc.net

It's been a long, long time since I last used UPX (many years). I stopped using it because it started to generate unusable EXE/DLLs. If you have UPX handy, then it should be able decompress files as well with the -d switch.

UPX is still developed - https://upx.github.io/

0.184 was the first released 64-bit binary. You can still build 32-bit versions from the source, if need be.

PP. wrote:So I use a random mame version and the command window will tell me? Thanks.

But if an inp won't even start?

Should still show it. So long as you're not running it from a double-clicked icon or the Run option, where the console disappears on exit.

PP. wrote:How can someone check the mame's version of an inp?

Run MAME from the command prompt, playing back an INP will tell you exactly what version was used.

Updated to use -window -nomaximize (removes some video hardware slowness). Still 64-bit 0.185. pacman 3999.63 malzak 541.17 ddragon 962.72 invaders 2621.93 tbyahhoo 337.64 stunrun 556.88 mrdrillr 228.16 cotton2 302.80 beastrzr 331.38 puzzloop 350.09 sfiiin 919.39 strider 1357.95 rsgun 267.01

Grabbed a 64-bit SDL WolfMAME 0.127, and oddly enough, I still get 580% on pacman. Modern OSes use up this much more CPU time? Seems weird.

EDIT: Ok, adding -nomaximize makes it run much faster. Intel must have crappy texture stretching or something.

Will pull 0.126 from the old box eventually, and hope that it'll run (it should). Might give a better idea as to how much speed is lost simply through MAME shifting from C to C++14 and various emulation improvements over the past 9 years.

Well, here we go. All I'll say is, MAME seems slower - especially with older drivers that don't need huge power to run. System: 3.7GHz Core i3-6100 Intel HD Graphics 530 8GB RAM Arch Linux (kernel 4.10.11) WolfMAME 0.185 (SDL, 64-bit self-compiled) Commandline options are the same as before. All val...

Well, I did finally get a new (cheapo) system about a month ago, probably about time this thread was updated.

That's certainly possible, especially with games that use DIP switches. Games that store settings in NVRAM, though, set their own defaults usually (or have an option to do so), and can still differ between regions.

My answer is more aimed at PP, who seems to have a bit of trouble figuring this out.

While it is entirely possible for documentation to be wrong, I'd be inclined to think that Namco has gotten difficulty settings pretty much right after using this same difficulty Rank setup for a fair while. You have evidence that the manual is wrong?

PP. wrote:3. Don't even know what is "manual scan". And why this manual scan should be conneted with Pacmania.

You forgot about the scan of the Pacmania manual already?

Only for this version. As shown before, it has been updated on Github.

It should work with 'make SUBTARGET=arcade' or just 'make' I would recommend not being logged in as root, this is not needed to build or run MAME, although that shouldn't stop it building. Try adding VERBOSE=1 to the make commandline, this will display each build command. Perhaps something is failin...