StHiryu

Yeahhh

MESS, MESSUI, MAME AND MAMEUI 0.244 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

HBMAME and HBMAMEUI 0.244 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

ARCADE32 0.244 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

At this time I've compiled mame, mameui and hbmame, hbmameui. Will try arcade with the change suggested by Robbert.

Couldn't compile 32bit version of arcade: Z:/Compartida/msys32/mingw32/bin/../lib/gcc/i686-w64-mingw32/9.3.0/../../../../i686-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/obj/x32/Release/generated/mame/arcade/drivlist.o:drivlist.cpp:(.rdata+0x21824): undefined reference to `driver_zortonbr_100' Z:/Compartida/msys32/mingw32/bin/../lib/gcc/i686-w64-mingw32/9.3.0/../../../../i686-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/obj/x32/Release/generated/mame/arcade/drivlist.o:drivlist.cpp:(.rdata+0x21828): undefined reference to `driver_zulu' Z:/Compartida/msys32/mingw32/bin/../lib/gcc/i686-w64-mingw32/9.3.0/../../../../i686-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/obj/x32/Release/generated/mame/arcade/drivlist.o:drivlist.cpp:(.rdata+0x2183c): undefined reference to `driver_zzblock' collect2.exe: error: ld returned 1 exit status mamearcade.make:282: recipe for target '../../../../../arcade32.exe' failed make[2]: *** [../../../../../arcade32.exe] Error 1 makefile:427: recipe for target 'mamearcade' failed make[1]: *** [mamearcade] Error 2 makefile:1133: recipe for target 'windows_x86' failed make: *** [windows_x86] Error 2

Make sure to clear all the inis in your ini folder, because it works at my side. Change your hbmame.ini with that line. Anyway this is an issue with the source code, not by compiling. Can't give you better assistance.

ARCADE32 0.243 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

HBMAME and HBMAMEUI 0.243 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

MESS, MESSUI, MAME AND MAMEUI 0.243 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

1-2-3-Yes to all, since all of them are arcade machines... 4-No since they are not playable. When mame achieves something like virtualpinball, I would include them.

No mame0242 tag at your github repository?

In order to resolver keyboard problem at 32bit mame builds, you need to set your system.ini file to: # # OSD INPUT OPTIONS # keyboardprovider dinput or # OSD INPUT OPTIONS # keyboardprovider win32

ARCADE32 0.242 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

HBMAME and HBMAMEUI 0.242 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

MESS, MESSUI, MAME AND MAMEUI 0.242 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

ARCADE32 0.241 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

MESS, MESSUI, MAME AND MAMEUI 0.241 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

HBMAME and HBMAMEUI 0.241 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

ARCADE32 0.240 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

HBMAME and HBMAMEUI 0.240 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

MESS, MESSUI, MAME AND MAMEUI 0.240 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

No, they should run fine with no hacks.

HBMAME and HBMAMEUI 0.239 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE

MESS, MESSUI, MAME AND MAMEUI 0.239 32bit avaliable (Xp compatible). Download from: RETRODANUART GOOGLEDRIVE