32bit binaries version

Hello everyone!

I wanted to keep, for those who still need it, the 32bit versions of some emulators. Can anyone help me by filling them in for me (and for my site)?

In order of importance these are needed:

MAME 0.218 (32bit)

MAMEUI 0.218 (32bit)

MESS 0.218 (32bit)

MESSUI 0.218 (32 and 64 bit, unofficial)

HBMAME 0.218 (32 and 64 bit, unofficial) 

ARCADE 0.218 (32bit)

MAMEARCADE 0.218 (32bit)

Many thanks!

mame, mess, mamearcade (in progress) => emufrance

mamexp, messui, hbmame/ui, arcade => st hiryu at https://www.1emulation.com/forums/forum/125-messui/ (in progress)

reposted on emufrance.

Many, many thanks!

I'm waiting...

Notes for 32-bit versions:
– dc (Dreamcast) and clones – crash at start
– hapyfsh2, kof2002um, kof2002umj all crash at start because the roms are too big to fit in memory.

 Beware that MESS on Emufrance is created from a newer source than Mame 0.218.

Then it's not good for my page...

you can use my scripts to create 32bit versions for them. The problem is for MAMEui/Arcade/MessUI/ that you need the source when the relase is created with 64bit. Im not sure when does that happens, with "tag0217 or when "MAME0217" is tagged in the source:

example: https://github.com/Robbbert/store1/releases

maybe we have to ask Robbert for that. then we have the source for the release to download and to compile. 

Example for MAME:

"git clone -b mame0218 --depth 1 https://github.com/mamedev/mame.git mame0218"

btw MessUI and HBMame are not available as 0.218 .....

Im asking Robbert .......he set "tagXXX" before compiling :-)

And my scripts does create x32 binaries ...but they do not start on Windows XP (missing blahblah). Seems that it need an older compile environment, Robbert has told me to use GCC 7.2 .....lets try this one.

Trying to build "something"

7.2 (on win7 and later) is minimal for Xp compatible build.

I can compile mess without worry, but for 2 more commit, I don't see the point of recompiling while it's totally based on the sources, it's more maniac than anything else at this level ^^

however, st hiryu has just finished the compilation, if you find something there :)

https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO

Hi AntoPisa, I've just compiled the Arcade32, MameUI and mamexp, you can check it at 1emulation.com as usual.

I didn't compile the HBMame and Mess since Robbert did'n release the 64bit versions.

Thanks for the binaries in the meantime. My script is finished but there is somewhere a "bug" as it does fail to compile. Need more time to check it.

It does:

- check online for the latest available "tag"

- download source for this "tag"

- compiles the x32 with tools and addon folder.

https://www.mameguide.info/32bit.jpg

my script is finished. It does work except for hbmame. (something in the source). I have no clue atm.....I will investigate it later.

If someone is interested for my script and manual (preparation compile environment and how-to):

https://mega.nz/#F!6EMWxARK!L7eahfnIC6ZdFAaHSqlFMA

I have added the compiled exe for the other builds.

Hi mucci,

- mameui32, mame32 ...difference?

 -For mamearcade, If I delete all the symbols I get 183MB and not 109 ^^

edit: mame32 for mame 32 bits ^^ being an "old" I thought of mameui (formerly mame32)

jep "delete the symbols" makes sense to save download bandwidth.

Thanks Jets and Sthiryu for the binaries.

Sorry, I haven't followed this discussion these days.

I took your files and uploaded them to the site, thank you very much.

Sooner or later I have to do it!

I haven't been compliling a MAME for years...

Thanks for your wonderful guide and script.

If I have problems I'll call you! ;)

Sounds interesting...

Antopisa you could have come to 1emulation like you used to..

You're right Robert, I was in a hurry...

btw I have uploaded an updated script -> it contains "strip_symbols=1" in the compile command. This should reduce the size of the exe.

Sorry I have not tested it yet .......test it on XP before uploading them on a website 

hmm seems that something has changed for HBMAME ....0.219 but tag displays as 0.217 ...grrrrrr....hmm or it is not the "final" 0.219 ;-)

No official release of HBMAME in February. It is hoped that the next one will be 0.220 in March.

As promised, I'm attempting to compile with your script (second version).

Everything is fine until the "Moving created files..." command is started: all compilations get stuck with the error message "Duplicate name or file cannot be found".

What do I have to do?

what have you tried to compile? has it compiled successfully? The move command tries to move the *.exe from the compile-folder, like mame0219/*.exe to the destination _mame/mame0219/

trying it myself with the 0.219 versions. start is ok:

--------------------------------------------------

     retrieving version numbers remote

   --------------------------------------------------

     MAME:   mame0219

     ARCADE: tag219

     MAMEui: tag219

     MESSui: tag219

     HBMAME: tag217

All updated to 0.219 except HBMAME. Downloading the sources now for the 0.219 versions .....

I've tried them all (excluding HBMAME).

I only realized now that my antivirus (Avira) has blocked and moved the "genie.exe" file 4 times.

I'm trying again, using the "clean" command.

Compilation locked on command "osd_windows.make" :(

hmm found a little display-bug in my script MEssui Version was not displayed in the menu correct (instead it displayed the HBMAME_version).

Im compiling them all now ......must go now .....lets see if it has finished the job when Im back ;-)

I've done it!

MAME compilation completed successfully.

Just one problem: the file size is almost double...

Maybe my compiling option is missing something ....I have asked Sthiryu

Updated the script -> I must use capital letters -> STRIP_SYMBOLS=1

Ok, as soon as I have time I do a new test with the updated script.

Thank you.

@Jets would you happen to have a 64bit version of MAME that'll work for Windows XP x64?  Preferably 0.217 or higher?

Thank you!

I tried the updated script, the file sizes are smaller now.

HBMame (tag217) doesn't compile the exe, though, it gives this error in the end:

Archiving libformats.a...
Archiving libemu.a...
Archiving libdasm.a...
makefile:1101: recipe for target 'windows_x86' failed
make.exe: *** [windows_x86] Error 2

jep I know Noone, I have reported Robert it but he (thats fine for me) has no idea why and not interested in investigating it ;-) .......Im testing it again with the 0.220 release of HBMAME

Keep in mind that XP is outdated!!!!!!!!!!!!! I do not edit/enhance my script for having XP x64 binaries as well, my mission has ended here. (feel free to do it yourself)

@Antopisa: Also note on your site that those binaries are not official ones (not from MAMEdev nor from Robert)  as Sthiryu mentioned in his downloads too.

@mucci, I hear ya regarding XP and especially XP x64.  I only update the romset and related binaries every 2-3 years.  I've had precarious setups in order to keep my arcade monitor working optimally realizing that one day it'll be harder and harder to get new hardware and OS's to support such low resolution and refresh rates.  

Then I image the boot disk and backup everything only to repeat it until it's really dead dead dead.  :)

32bit files are all "unofficial"; on the link (and inside the packages) I quote the author of the compilation.

@GoCRT_Driver: I have edited my script for building 64bit XP versions. I have not tested it myself if the exe are good as I don't have an 64bit XP.

https://mega.nz/#F!eRVzjAKK!DVFsug-AHER36I-DLSfwnA

hmm still fails compiling for HBMAME 0.220 .........grrrr, maybe when I have time I must investigate it 

Found some time to investigate the compile fails for HBMAME. Found a hint in https://github.com/mamedev/mame/issues/5741

And indeed the value in compile option "-j"  has caused this "..not found" error ......really? Yes really! I have played around and set the value to "-j25" and HBMAME and ARCADE has failed .....strange strange .......now I have set it to the low value "-j5" and it works for me. Yes I know it takes more time to compile it. I have started the script, removed the pause option and it has compiled successfully all emulators during my sleep time :-)

I have also optimized the code a little, it downloads the source only for those emulator you want to compile.

Manual and scripts can be found at https://mega.nz/folder/HZFlQALQ#7_j-rcBnkwRSgFsEEEjjLw

KEEP IN MIND: XP is outdated - compile-source is updated all the time and the compile environment not! ... it comes the time when .....

Compile info @MAMEdev https://docs.mamedev.org/initialsetup/compilingmame.html

 Thank you for the latest arcadeui64.exe

Hola a todos , me podrían ayudar a instalar mame en mí computadora xp ? No entiendo nada , donde puedo descargar el emulador y los juegos , si alguien me puede ayudar se lo agradezco de antemano, saludos

Google translate: Hello everyone, could you help me install mame on my xp computer? I don't understand anything, where can I download the emulator and the games, if someone can help me, I appreciate it in advance, regards

@Nahuelnonservium: Please post in english, second this topic is not for explaining how MAME works!

Create a new topic (english) and/or search the web for help. You can also use my guide @mameguide.info (english) or other website as Emueasy https://easyemu.mameworld.info (english) or https://wiki.mamedev.org/ (english). Sorry I don't know any spanish websites .....

Hello Mucci!

I just tried your mame64_XP_0222.exe version on my XP64 machine without luck. Hopefully i am not doing something stupid. 

What i did is, i downloaded the file and extretacted it in my "mame" folder, overwriting the old files. When starting MAME64 i get the following error:

"Procedure entry point K32EnumProcessModules could not be located in the dynamic link library KERNEL32.dll"

I found this in a reddit threat, maybe that helps:

"Programs that must run on earlier versions of Windows as well as Windows 7 and later versions should always call this function as EnumProcessModules. To ensure correct resolution of symbols, add Psapi.lib to the TARGETLIBS macro and compile the program with -DPSAPI_VERSION=1. To use run-time dynamic linking, load Psapi.dll.

Which basically means:

Use EnumProcessModules in your code

Link to Psapi.lib

Set up PSAPI_VERSION=1 as a preprocessor definition"

Any Idea what could be the problem?

Wishes,

Maria

PS:  I tried also compliling a version myself with your script (for 64 bit Mame 0220). The result is sadly the same :-(

Grab the Xp exes from here:

https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

As I am on XP64bit that sadly does not help :(

A 64 OS can run a 32bit executable and you can play mame32 with almost no difference. Anyway, you should compile the exe with and older GCC than the latest one, for example search for msys64-32-2017-12-26.exe

Yes but the idea is to have mame64 running on my OS, because it is much more perfomant. Concerning compiling: That is exacly what I did with the script. THis is why I am posting here. It did not work :-)

Read my reply (above):  "I have edited my script for building 64bit XP versions. I have not tested it myself if the exe are good as I don't have an 64bit XP."

Sorry that you are using an outdated OS and my script does not compile an exe for you. As Sthiryu already said you can also use 32bit sw on 64bit.

It should work "on paper" the 64 compile-script as I have used the same compile environment (msys64-2017-12-26.exe) as I used for the 32bit version (32bit  msys).

I have tried yesterday to install Windows XP 64 in a VM, but it does not continue the setup .......so I can not verify your answer yet

Keep also in mind that the MAME source can change in the future that it is not possible to compile XP builds! Replace this old piece