Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[geekbrain]

I loaded MAME 0.274 on my cabinet and ClrMAMEPro is having issues (no XML file being created) - see attachment pics.  ClrMAMEPro worked with 0.273 last month.  I use Microsoft RDC to do the updates - could it possibly be related to an Win11 update on my desktop PC and running ClrMAMEPro?  Did anyone have an issue with 0.274 or use Microsoft RDC? 

-Thanks-

[Roman]

Well, the screenshots actually describe what is happening. Your MAME executable file produces a bad or no XML output when it is called. clrmamepro calls it either with -listxml or -listsoftware and redirect its output to a temporary folder.
You can check what was exported by looking at the mentioned temporary place if the file is there or cut off. You can try to delete it if it's there and try again. Check access rights etc. Are you using the official MAME binary or a 3rd party built one? You can test the output yourself by running mame.exe -listxml > test.xml and check it.
And of course you can use such an exported xml file as input for clrmamepro, too.

This does not happen with the official mame binary on a let's call it 'standard PC'.

[geekbrain]

I had already tried   mame.exe -listxml > x.txt   using a command prompt run as an administrator.  It created the   x.txt   with 0 bytes.  I tried with your entry and same effect.  I tried restarting, disabling virus scanner (McAfee/Trellix), admin command prompt entry and ClrMAMEPro again.  Nada.  I had already MAME (both from   mamedev.org   and   progettosnaps.net   with no effect and checked the CRCs.

I think it has to do with new version of MAME.  From the website:

After several years, we’ve decided it’s time to start taking advantage of features of newer (or at least slightly less outdated) CPUs. Starting with MAME 0.274, official Windows binary releases will require so-called x86-64-v2 features. These features have been available in all popular x86-64 CPUs for close to a decade. They were introduced in the following CPU families:

Intel “Nehalem” (2008), or “Silvermont” (2013) for low-power CPUs
AMD “Bulldozer” (2011), or “Jaguar” (2013) for low-power CPUs
VIA “Nano C” and “Eden C” (both 2015)
If you still want to run up-to-date versions of MAME on older systems running Windows, you’ll need to compile it from the source code.

I am running a Core2 Duo processor.  So I think I am SOL unless I update my PC. 

[Roman]

hmm..interesting...but if you say a mame.exe -listxml doesn't work on your system, well, there is your answer.
It shouldn't be a problem to find such redirected outputs in the internet which then can be used as datfiles in clrmame/clrmamepro

[Bad A. Billy]

I had the same issue myself. I thought my Phenom II was "new" enough to not be concerned about it buuut...no go...
OC it worked just fine on all my other newer pewters...
You can still compile MAME yourself and CMP will pull the xml's just fine from that on your older PC.

But that brings me to another issue that reared its head while I was playing around with the above problem.
I tried both scanners on another PC(with a newer processor) and still couldn't get a good pull from MAME. So I tried 2 others
and both of them worked just fine. WTH?
Long story short, on the 1st computer I have the scanners set up on N: (a 6Tb drive), plenty of room for backups and profiles
right?  Well, I failed to notice that my C: drive (somehow) was down to >2gb free and the scanners were using that drive for the
temp files(I assume?) so there wasn't enough room for the files so it conked out with an error.

Roman: Is it possible to change the location of those temp files(if that is the problem - Does CM use it's own temp folder?) and
would that effect the speed of pulling the xml or the scan itself if someone had an older slower spinner drive in that location?
Just curious...

Again, thanks for all your work!

[Roman]

clrmame uses the temp folder only when it needs to decompress data temporarily.

This is done when
a) an archive is in an archive
b) adding files to an archive to another where the archive types differ (e.g. 7z to zip, rar to 7z) or when copying data from 7z to 7z archives. A direct zip to zip operation does not require a decompress (unless you don't force it in rebuilder->recopress), so that's one of the main reasons why people should think about using zip...in 2025 multi terabyte hds are cheap, so getting some gb extra by using soldid 7z is  -in my opinion- pretty obsolete. The wasted time is more expensive

By default the system's temporary folder is used (%TEMP%, which usually points to "C:\Users\your_user_name\AppData\Local\Temp").

To quote the readme file: "You can alter the temporary folder by modifying the "TempFolder" entry in settings.xml". So open the settings.xml file with an editor and look out for <TempFolder></TempFolder> and insert your prefered one.


....and all created temporary files will be removed on exit