StHiryu

Why to discard non-working systems in the Gui version? Any impact on performance?

Seems to be a little bug in MameUI. Setting more than a single path in swpath at machine.ini, when you want to open a file the explorer opens the snap directory. For example in cpc6128.ini: -Media view, Floppy disk1,Mount file: swpath Z:\Juegos\Amstrad\Disks --> Works great, opens the Disk folder swpath Z:\Juegos\Amstrad\Disks; Z:\Juegos\Amstrad\Tapes --> Opens the snap folder Happened in .0217 as well.

MAMEUI 0.218 32bit avaliable (Compatible with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing No HBMAME and MESS this time

ARCADE32 0.218 32bit avaliable (Compatible with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

MAME 0.218 32bit avaliable (Compatible with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

Thanks, will release the 32bit binaries when mame is out

Compiled successfully mameui32 0.208 with the GCC 7.2.0, and it works in XP. Also I've compiled the 64bits version with the GCC 8, if you want to add it to the site, I can give you the link.

Yeah, it's about the issue #4818 at mame github (I don't have an account to write there). If you compile mame or mameui with the latest tools, the error message "GetTickCount64" appears in windows xp. However your build works, so it's because of that tools. I'm going to compile mameui64 with the updated tools to check the tomy handhelds bug. EDIT: Compiling with the latest MINGW GCC at mamedev the tomy handhelds now displays properly. I Suggest to compile MameUI32 with GCC 5.3.0 to keep compatibilty with XP, and MameUI64 with GCC 8.

Robbert, did you compile the build with the latest tools from mamedev?

If you can't, I can compile them, but at this time the source code at github is still at 205 version.

Nope, I've dowloaded mameui 0.182 and the behaviour is just like the official 205 latest release: The mouse pointer is captured in mame window unless you hit pause, so you can move it outside the window. Is not a local setting since this should affect to all the mame builds. Take a look at it, but it isn't a great problem. (I can upload for you the mame builds used for testing, if you want). Edit: The last Mameui build that works like the current mame 0.205 is 0.197.

There is an issue with mameui (not happening in official mame release): When you play any game with the mouse enabled in windowed mode, if you exceed any boundary of the screen, the emulator loses the focus and you can click any element from the windows OS. That didn't happen in older mameui versions. I can do a video if you don't understand the problem, but it's easy to reproduce.

According to my mametesters report #7182, the snapshot view section at miscellaneous tab should replace the "standard" option for "screen" in order to work properly with the new changes.

The Kof bug with the countdow finally has been fixed

Yes, the model1io rom was bad, sorry and thanks