Topic: code1d and code1db folders keep disappearing (Read 15869 times)

sup191 · « **on:** 21 February 2012, 05:11 »

I just upgraded from clrmamepro 4.02 to 4.03a and after doing a scan, it says I'm missing the code1d and code1db sets. I had folders created for them before upgrading, but they are now gone. If I recreate the folders and rerun a scan, clrmamepro keeps deleting them and then says they are missing. Every other chd only set has a folder created for them and they remain in place after a scan.

I'm down to the two code1d sets and I can't make them stay after a scan. I never had this problem with 4.02. Is this happening to anybody else?

Roman · « **Reply #1 on:** 21 February 2012, 08:41 »

Which MAME version are you using?
I'm asking since nothing really changed regarding to set placement/unneeded handling in 4.03.
However I haven't tested .145u1 yet, so maybe they changed something there.
...you keep your sets split-merged I guess....
So, if you're using a new MAME, you may want to have a look at the datfile if something is weird there or take this as basis as a manual movement of the sets/chds to a correct place.

I will have a look as well later this evening.

sup191 · « **Reply #2 on:** 22 February 2012, 01:49 »

I'm using the release of .145. I'm pulling the dat info from MameUI64.exe.
Yes, I have clrmamepro set for split sets. I haven't changed anything since running a successful scan with 4.02. When I saw you released an update, I installed it and ran the scanner again just to verify that I had everything cleaned up. There were actually about 15 empty folders that were in my chd folder that disappeared. I recreated the folders two at a time and then re-ran a scan. They were removed from the scan results. When I got to the two code1d(b) folders, I created them, re-ran the scan, and they were deleted.

I've gone into Profiler and cleared the cache. After rebuilding the datfile, I still get the same results. It just these two folders that are not playing nicely. If you need me to post/send anything, let me know. It's not a HUGE deal, but it is a little annoyance that I can't seem to figure out.

sup191 · « **Reply #3 on:** 22 February 2012, 02:13 »

I just did some more testing...

Without the two folders, both are listed as missing when I do a scan. If I create a folder named code1db and rescan, both folders are still listed as missing. If I create a folder named code1d, the next scan will find the folder and not list it as missing. However, it deletes the folder right after the scan, so the next scan will list it as missing since it has been deleted. The folder named code1db will not be deleted, but it will constantly be listed as missing.

Roman · « **Reply #4 on:** 22 February 2012, 08:17 »

sounds wicked

I guess I can only look at this more deeply next week...

Try to disable the fix options. Then the scan tree output should list something....maybe something more than just "unneeded".

oxyandy · « **Reply #5 on:** 22 February 2012, 08:22 »

I just do not get the problem here ??
Are you saying MAME needs 'Empty Folders' to work right ?
Are you saying CMP deletes these 'Empty Folders',
and you wish it did not ?

Those folders should have a CHD in each
code1d\922d02.chd
code1db\922b02.chd

Roman · « **Reply #6 on:** 22 February 2012, 08:25 »

good remark...

Do you actually *HAVE* files in the folders?

Of course empty folders are removed...and if you have something different in there as a chd, cmpro will show you a set exists in more than one place message...that's why I asked to turn off the fix options for 1 scan to see what cmpro actually complains about.

sup191 · « **Reply #7 on:** 22 February 2012, 17:00 »

There are no files in the folders because I am not currently collecting .chd files. I have made a chd folder with the names of the chd only sets in order to clear the missing warnings during scanning. In fact, I have around 50 or so empty folders in my chd directory and all of them clear any missing set warnings during a scan, other than the two listed in the topic. My main goal is to be able to do a scan every time a new MAME version is released and not have anything listed as missing after doing a scan.

I'll try disabling the fix options, but they have always been enabled on previous versions and I've never had any folders disappear.

sup191 · « **Reply #8 on:** 22 February 2012, 17:10 »

Quote from: oxyandy on 22 February 2012, 08:22

Are you saying MAME needs 'Empty Folders' to work right ?

No, this is only a CMP scan issue - nothing to do with MAME. MAME works fine.

Quote from: oxyandy on 22 February 2012, 08:22

Are you saying CMP deletes these 'Empty Folders',
and you wish it did not ?

Exactly. In CMP 4.02, all the empty folders with chd set names in my chd folder would prevent CLM to list them as missing during a scan without deleting anything.

Quote from: oxyandy on 22 February 2012, 08:22

Those folders should have a CHD in each
code1d\922d02.chd
code1db\922b02.chd

I'm not collecting chd files - the empty folders are just to clear the missing warnings in a CMP scan.

oxyandy · « **Reply #9 on:** 23 February 2012, 08:00 »

Ok sup191
if you are not collecting chd files..
the solution is.....
Do not use a dat that contains them, easy huh..
No need for those empty folders..
You can get a "ROMs Only" dat from here
http://www.emulab.it/rommanager

sup191 · « **Reply #10 on:** 24 February 2012, 04:43 »

That's a neat bandaid solution, but still doesn't solve the issue that there is something not working like before since the previous version did not have this problem.

In the long run, it's not a big deal, but it still is not functioning as intended.

oxyandy · « **Reply #11 on:** 24 February 2012, 05:39 »

Yes, in a way you are right,
CMP should have **deleted all those empty folders**
I have noticed when scanning / fixing CHDs CMP does do some interesting things.
But not vital, one day I will bring these points up with Roman.

The dat without CHDs is hardly (in your case) a bandaid solution,
it is a very practical one, if you do not want CHDs,
again don't use a dat that contains them.

sup191 · « **Reply #12 on:** 24 February 2012, 06:09 »

Oddly enough, CMP now DOES delete proper named chd folders and eliminates them from scanning, but not all folders. The ones that are closely named do not get deleted and stay missing in the scans, such as:

kollon
kollonc
code1d
code1db
spuzbobl
spuzboblj
etc...

Again, I know this isn't a huge deal, it's just that my method was working fine until the new update which is why I posted if anybody else was having the same issue. Since my ROMS are 100% complete, it's nothing I can't live with. I was just curious.

I did grab the ROM only dat from the link you posted and it works fine, although I wish it had the sample info in it also...

Roman · « **Reply #13 on:** 24 February 2012, 08:59 »

The only thing which changed was the dupe check (since multisoftware list support allows identically named sets...). That's why I asked to scan without the fix options enabled to see what issue cmpro reports.

Of course it should delete all and not only some obsolete folders.

Next week I got more time to check this in detail

oxyandy · « **Reply #14 on:** 24 February 2012, 10:36 »

Ok then, here is another page to bookmark
Progetto's MAME Samples and Samples DAT

Enjoy

And thanks Roman,
for looking into CHD handling with CMP

etabeta · « **Reply #15 on:** 25 February 2012, 06:59 »

mmm... from the top of my head, the only thing I think it could interfere here is that those sets all use a bios+the CHD, so maybe cmpro is making some weird assumption (e.g. some bios roms might be inside the folder?) due to some other option ticked

but I might be wrong, of course...

Roman · « **Reply #16 on:** 25 February 2012, 10:04 »

as I said I will into it next week

sup191 · « **Reply #17 on:** 25 February 2012, 17:56 »

Thanks oxyandy, I'll use the dat files from the links you provided until the issue is cleared up.

And thanks to Roman for looking into the issue and for creating the best ROM manager out there!

sup191 · « **Reply #18 on:** 25 February 2012, 17:59 »

Quote from: Roman on 24 February 2012, 08:59

The only thing which changed was the dupe check (since multisoftware list support allows identically named sets...). That's why I asked to scan without the fix options enabled to see what issue cmpro reports.

When I run a scan with all fix options off, it still displays the same thing as when they are on - The same folders (sets) show as missing.

Roman · « **Reply #19 on:** 25 February 2012, 20:28 »

ok more next week since Im miles away from any sourcecode

News:

Author Topic: code1d and code1db folders keep disappearing (Read 15869 times)