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

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.

1

clrmame Discussion / Re: missing set: Chaos Field (Jpn, Sega Direct)

« on: 25 May 2018, 21:38 »

You are the man Roman!

Just tried the new build against MAME 0.197 and the errors are gone!
I really didn't expect a fix so quickly.
Your dedication to cmpro is simply amazing!

Thank you so much and have a great weekend.

2

clrmame Discussion / Re: missing set: Chaos Field (Jpn, Sega Direct)

« on: 25 May 2018, 20:36 »

I will try tonight and report back with results. 

3

clrmame Discussion / missing set: Chaos Field (Jpn, Sega Direct)

« on: 25 May 2018, 13:22 »

I recently came across a problem which I've been unable to resolve.
Starting with MAME 0.196, I keep getting the following error when scanning the software lists for the "Sega Dreamcast GD-ROMs":

Code: [Select]

Chaos Field (Jpn, Sega Direct) [folder: cfieldsd - parent: cfield - size: 0]
missing set: Chaos Field (Jpn, Sega Direct)

Chaos Field (Jpn, Sega Direct, Rev. 1) [folder: cfieldsd1 - parent: cfield - size: 0]
missing set: Chaos Field (Jpn, Sega Direct, Rev. 1)

This happens when the merge mode is set Split Sets.
Please note that I am using the xml from the MAME's hash folder as the datfiles to be scanned for software lists. Those datefiles are all selected within cmpro and scanned in batch mode using the split set option under the scanner tab.
If I instead change the merge mode to merged sets, the scanning process is successful and no error are returned but I would prefer to keep the merged mode consistent across all software lists.
This problem also exist with MAME 0.197 but did not exists with MAME 0.195 and prior versions.

Help would be greatly appreciated. 

4

clrmame Discussion / Re: cmnpro 4.034 released

« on: 03 March 2018, 20:08 »

yesss...Looking perfect!   
I also re-scanned all software lists in batch mode to make sure everything was still green.

Did you find out or remember why the old code was intentionally using the filename as sort criteria? Just curious.
I'm guessing this new code will be merged into the main branch for the next official release.

Thanks a million Roman. This is very appreciated!

5

clrmame Discussion / Re: cmnpro 4.034 released

« on: 01 March 2018, 20:56 »

yes...I was definitely mistaken when I said earlier that this was working in previous version. 
In any case, I'm happy to see we're both on the same page. 

6

clrmame Discussion / Re: cmnpro 4.034 released

« on: 01 March 2018, 19:52 »

I understand and agree with your response but in my screenshot "path\Sega 32x cartriges" comes before "path\3DO M2 CD-ROMs".
Shouldn't it be the other way around?
You'll also see other profile names in that screenshot that are out of order.

7

clrmame Discussion / Re: cmnpro 4.034 released

« on: 01 March 2018, 17:39 »

Good afternoon Roman,

Thank you for your reply. I think I know what's happening here.
Your screenshot shows loaded and scanned profiles which is a step passed what I was observing or reporting. Sorry for the confusion!
Right after you drag and drop the xml files from the hash folder then click on the "[NEW DATAFILES]" folder in cmpro, the list of profiles will initially be sorted on the filename or "name" attribute of the "softwarelist" elements of those hash file.
This is where I was trying to sort the profile list so that I could remove the "VTech V.Reader - Storio cartridges" profile from before performing a scan in batch mode.
I just repeated this steps this morning to confirm that the problem was still present.
Once the profiles have been scanned, sorting on the Profile column will work as expected.

I'm attaching a screenshot which should depict the problem.


Again, thank you so much for this awesome tool! 

8

clrmame Discussion / Re: cmnpro 4.034 released

« on: 28 February 2018, 20:52 »

Good afternoon,

I just upgraded to 4.034 this morning and noticed that after I dragged all the xml files from the MAME 0.195 hash folder then attempted to sort the resulting list by clicking on the Profile column, the software lists names were not ordered alphabetically as in previous versions. The Profile column displays the description attribute of the softwarelist element but the new sorting behavior appears to be using the name attribute or filename as its sort field. From what I can see, version 4.033 sorting was based on the description attribute which is what's visible to the user. Is this the intended behavior?

Thank you for your help

9

clrmame Discussion / Re: clrmamepro 4.031a released

« on: 22 October 2016, 10:56 »

Thank you Roman.

I really appreciate your quick response and the explanation!
I feel relieved to know that my sets are indeed complete.

Your tool is a must for people that want to maintain perfect sets.

 

10

clrmame Discussion / Re: clrmamepro 4.031a released

« on: 21 October 2016, 20:36 »

Hello Roman and thank you for keeping cmpro alive.

I just updated clrmamepro to this latest release cmp4031a_64.zip and scanned my complete rom sets but version 4.031a statistics dialog states that I'm missing 10 roms and 306 samples as seen below. The previous version 4.030a indicated that nothing was missing.
Additionally, the scanner results window does not show any error messages after the scanner completes. I also noticed that Active ROMs section (At the buttom of the statistics dialog) appears to indicate that no roms are missing (see below Active ROMs 266037/266037).
Just as a test, to eliminate the possibility of having a corrupt cmpro installation, I extracted cmp4031a_64.zip into a different folder, recreated my profile, scanned my roms and samples folder, but once again I got the same results as below.
Any idea what I might be doing wrong?



Missing
·Sets                 0/36759
·ROMs                 10/266037
·CHDs                 0/900
·Samples              306/17391
·Bytes                148kb/208gb

Fixed Wrong Case
·Sets                 0/0
·ROMs                 0/0
·CHDs                 0/0
·Samples              0/0

Fixed Unneeded
·Sets                 0/0
·ROMs                 0/0
·CHDs                 0/0
·Samples              0/0

Fixed Wrong Name
·Sets                 0/0
·ROMs                 0/0
·CHDs                 0/0

Fixed Wrong Size
·ROMs                 0/0

Fixed Wrong Date Time
·ROMs                 0/0

Wrong Hashes
·Wrong CRC32 ROMs     0
·Wrong SHA1 ROMs      0
·Wrong MD5 ROMs       0
·Wrong SHA1 CHDs      0
·Wrong MD5 CHDs       0

Corrupt Containers    0

---------------------------------------

Active Sets           36759/36759
·Parents              5104/5104
·Clones               22647/22647
·Others               8939/8939
·BIOS                 69/69

Active ROMs           266037/266037
·Parents              46231/46231
·Clones               154060/154060
·Others               59900/59900
·bad dumps            1916/1916
·no dumps             3514/3514
·verified dumps       0/0
·BIOS                 416/416

Active CHDs           900/900
·Parents              111/111
·Clones               169/169
·Others               319/319
·bad dumps            172/172
·no dumps             128/128
·verified dumps       0/0
·BIOS                 1/1

Active Samples        17391/17391
·Parents              746/746
·Clones               16389/16389

Active Bytes          208gb/208gb