StHiryu

-Done some testing about mentioned bug. Here is what I've found with a fresh and naked MameUI 0.226: 1-Launch one rom (outrun) and play. A outrun.ini is generated at the ini folder. 2-Create an arcade.ini with the following: # # CORE CONFIGURATION OPTIONS # readconfig 1 writeconfig 0 3-Launch outrun again. The outrun.ini file is not created anymore. This should be the desired behaviour. 4-All The File, Play ... options from the WinGui at the top left generates again an outrun.ini in the ini folder, even with the arcade.ini with writeconfig 0 (Right click on the game, Play and Record input..., makes the outrun.ini appears again too) 5-If you run the command from cmd --> Mameui64.exe outrun -aviwrite outrun.avi, the outrun.ini is not created. So it seems somehow those options from the GUI ignore the writeconfig 0 at arcade.ini

Yes I've said some releases ago. Anyway will try again when 227 comes out and post here.

Thanks for the work of all involved. Will see if the new mame exes can work on Xp. Also I will check some old bugs in the winui, most of them related to the "record to avi oputput" feature.

If I remember well, to add those tools you have to include TOOLS=1 in the make command, I'll try it in the next release.

MESS, MESSUI, MAME AND MAMEUI 0.226 32bit avaliable (Compatible with Xp). Download from: RETRODANUART GOOGLEDRIVE

HBMAME and HBMAMEUI 0.226 32bit (Compatible with Xp). Download from: RETRODANUART GOOGLEDRIVE

Yep but listfull outputs all the systems, not the avaliables. Thanks, no need to do that

Yes but is useless for me since ARCADE doesn't include the mess systems.

Is there any way to generate a list in a txt file of the avaliable games in MameUi's Avaliable folder ? Could be implemented in a future?

MESS, MESSUI, MAME AND MAMEUI 0.225 32bit avaliable (Compatible with Xp). Download from: RETRODANUART GOOGLEDRIVE

HBMAME and HBMAMEUI 0.225 32bit (Compatible with Xp). Download from: RETRODANUART GOOGLEDRIVE

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

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

MESS, MESSUI, MAME and MAMEUI 0.223 32bit avaliable (Compatibles with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

MESS, MESSUI, MAME and MAMEUI 0.222 32bit avaliable (Compatibles with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

Mame 32bit XP finally compiled https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

MESS, MESSUI, and MAMEUI 0.221 32bit avaliable (Compatibles with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing Awaiting the mame official build to release the 32bit exe

HBMAME and HBMAMEUI 0.221 32bit avaliable (Compatibles with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

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

HBMAME and HBMAMEUI 0.220 32bit avaliable (Compatibles with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing

MESS, MESSUI, and MAMEUI 0.220 32bit avaliable (Compatibles with Xp). Download from this GDrive folder: https://drive.google.com/drive/folders/1eiNztWEpk0C7CiiZXz0SMDM_eJOmb0FO?usp=sharing Awaiting the mame official build to release the 32bit exe

For mameui I use: make -j5 TARGET=mame OSD=messui STRIP_SYMBOLS=1 NOWERROR=1

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

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.