1
clrmame Discussion / Re: 3 tiny issues
« on: 18 September 2015, 21:03 »
Great work, Roman. Thank you very much.
- 16 April 2024, 16:55
- Welcome, Guest
News:
The new forum is online, hope you enjoy it!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
clrmame Discussion / Re: 3 tiny issues
« on: 15 September 2015, 21:18 »
Before going further, I must clarify that I have only 19 CHDs in total, and I keep CHD scanning disabled. This is probably why I have issue #2, since I lack all those listed clone CHDs, and also the originals 
.
However, I don't mind using 'Allow CHDs in Rompath root', since I can easily manage such a limited CHD selection by hand, and use Audit all sets inside MAMEUIFX32, once for each new version, to see if they're still good or not.
As for issue #1, I created those folders in the past to make the scanner happy, and avoid any missing set error. I think those games listed were CHD-only some versions ago, then changed to have at least a rom in their set. For example, p9112 was like that until 0.157, when it had the nvram added.
No idea why the scanner suddenly gave errors on those romsets because of the empty folders, it was OK until very recently. Maybe I had some wrong settings in the past, or changed a few trying to solve #2...
As for #3, you're right, I used an expression to select the sets I wanted to exclude, then applied it and inverted. The expression is the following:
In any case, I'm attaching my configuration.
Thanks for investigating.
.However, I don't mind using 'Allow CHDs in Rompath root', since I can easily manage such a limited CHD selection by hand, and use Audit all sets inside MAMEUIFX32, once for each new version, to see if they're still good or not.
As for issue #1, I created those folders in the past to make the scanner happy, and avoid any missing set error. I think those games listed were CHD-only some versions ago, then changed to have at least a rom in their set. For example, p9112 was like that until 0.157, when it had the nvram added.
No idea why the scanner suddenly gave errors on those romsets because of the empty folders, it was OK until very recently. Maybe I had some wrong settings in the past, or changed a few trying to solve #2...
As for #3, you're right, I used an expression to select the sets I wanted to exclude, then applied it and inverted. The expression is the following:
Code: [Select]
%s=astropc.c; %s=cv1k.c; %s=gamtor.c; %s=hikaru.c; %s=namcos10.c; %s=naomi.c; %s=nexus3d.c; %s=segasp.c; %s=triforce.cNow I tried to do the opposite selection, using the 'logical NOT' flag, but I can't seem to get it working with 2 or more entries. Not sure if it's the expected behaviour or I didn't understand the expression syntax correctly.In any case, I'm attaching my configuration.
Thanks for investigating.
3
clrmame Discussion / 3 tiny issues
« on: 13 September 2015, 11:03 »
I finally got the time to scan my whole romset with the latest version of CMP.
All is OK now, but I have some tiny issues to report.
My settings: Merged zip sets, very few CHDs and some drivers disabled (naomi.c and a few others not working).
1) Some CHDs games gave missing ROMs error (see image below).
I actually had all the zipped sets (without the CHD) for each game, so I had no clue at first. Eventually, I figured out those were subfolders in the rompath and deleted them, after moving ALL the CHDs subfolders out, in order to get a hint from the scanner.
I understand roms in subfolders are allowed (no idea who actually use uncompressed roms), but I in the Profile, under the Compressor settings, 'Mark useless folder struct as unneeded (Scanner only)' was checked. Maybe CMP should have warned about those folders?
2) Some clone CHDs in Bios based sets gave different errors. If the folder wasn't created, gave a missing set error; and if existed, it gave a wrong merged rom set error (see image below)
In the end I checked 'Allow CHDs in ROMPath root', which solved my issue, but I think it's a workaround. Was there a better solution?
3) CMP stores the settings for my enabled/disabled drivers, but each time the cachefiles are removed, those settings gets inverted. So I enter 'Set Information' in the scanner and re-invert them. Is there a way to remember the settings correctly?
Thanks in advance.
All is OK now, but I have some tiny issues to report.
My settings: Merged zip sets, very few CHDs and some drivers disabled (naomi.c and a few others not working).
1) Some CHDs games gave missing ROMs error (see image below).
I actually had all the zipped sets (without the CHD) for each game, so I had no clue at first. Eventually, I figured out those were subfolders in the rompath and deleted them, after moving ALL the CHDs subfolders out, in order to get a hint from the scanner
.I understand roms in subfolders are allowed (no idea who actually use uncompressed roms), but I in the Profile, under the Compressor settings, 'Mark useless folder struct as unneeded (Scanner only)' was checked. Maybe CMP should have warned about those folders?
2) Some clone CHDs in Bios based sets gave different errors. If the folder wasn't created, gave a missing set error; and if existed, it gave a wrong merged rom set error (see image below)
In the end I checked 'Allow CHDs in ROMPath root', which solved my issue, but I think it's a workaround. Was there a better solution?
3) CMP stores the settings for my enabled/disabled drivers, but each time the cachefiles are removed, those settings gets inverted. So I enter 'Set Information' in the scanner and re-invert them. Is there a way to remember the settings correctly?
Thanks in advance.
4
clrmame Discussion / Re: Windows XP Users
« on: 30 August 2015, 09:58 »
Thanks a lot, Roman.
You have a donation incoming
You have a donation incoming
5
clrmame Discussion / Re: Windows XP Users
« on: 21 August 2015, 18:40 »
Compiling the 32bit version is so much a nuisance?
Anyway, I know the support has ended for XP, but I have no reason to upgrade. IMHO, the recent OS have a lot of bloatware, with higher requirements, less compatibility and very few real advantages.
I'd rather running an OS without support as long as I have an antivirus, a firewall and a browser actively updated.
Later edit: actually, I could copy my whole romset in my office computer (which has Win 7) and run ClrMamePro from there. Then, using a pen drive, I can take back home the fixed sets for each new release. So you may even drop the XP support, no big loss for me ;-)
Anyway, I know the support has ended for XP, but I have no reason to upgrade. IMHO, the recent OS have a lot of bloatware, with higher requirements, less compatibility and very few real advantages.
I'd rather running an OS without support as long as I have an antivirus, a firewall and a browser actively updated.
Later edit: actually, I could copy my whole romset in my office computer (which has Win 7) and run ClrMamePro from there. Then, using a pen drive, I can take back home the fixed sets for each new release. So you may even drop the XP support, no big loss for me ;-)
6
clrmame Discussion / Re: Windows XP Users
« on: 21 August 2015, 09:20 »
Well, the official MAME and most derivated builds still support XP. It's possible that many other people still uses it, besides me.
Please don't leave us behind. Thank you.
Please don't leave us behind. Thank you.
Pages: [1]