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.

3101

clrmame Discussion / Re: Show size of a datfile in clrmamepro/datworkshop pro

« on: 12 November 2009, 19:51 »

I put it on my list...however keep in mind, this value is the total of the decompressed romsize only....not very useful if you keep sets compressed or even got chds.

3102

clrmame Discussion / Re: Show size of a datfile in clrmamepro/datworkshop pro

« on: 12 November 2009, 13:19 »

First question would be: Which size are you talking about? The currently shown one in cmpro's statistics screen is the total of the rom size tags, i.e. decompressed rom size. No samples, no chds.
Another size could be the sum of file sizes in all rompaths...

3103

clrmame Discussion / Re: Will this work

« on: 12 November 2009, 11:50 »

Profiler -> load dat file for MAME .135 (or even better, use Create-> and import the data from the MAME .135 binary)
Settings-> setup rompath to point to your current 128 collection (setup sample paths optionally if you use them)
Scanner -> keep set+roms+chds+samples(if needed) enabled and enable all check and fix options and hit scan.

After that, you .128 collection is fixed for .135 but of course you will miss all new and replaced files.
Now you can drag'n drop (which internally runs the rebuilder) your .134 and .135 romsets into the scanner, cmpro will add them to the correct place.

Repeat this until a scan doesn't show any issues in the scan results tree anymore.


Beware: the chd format changed some versions ago, you need to update all chds via "chdman.exe -update".

3104

clrmame Discussion / Re: clrmamepro 3.131b released

« on: 06 November 2009, 12:24 »

aren't you mixing up double-rename here? The "allow double rename option" only checks if two old sets are renamed to the same new one.

So generally, no restrictions to parent/clone renaming should be done when creating the rename list...don't care for double of parent/clone renames....that list should stay the same...

...but when applying the renames to a nother dat, it should avoid double-renaming (i.e. not creating two equally named pngs...) and handle parent/clone handling (where the parent/clone relationships come from the old/new dats and not the 3rd-to-be-modified dat....which is a bit...hmm...annoying )

3105

clrmame Discussion / Re: clrmamepro 3.131b released

« on: 06 November 2009, 09:05 »

With the "check if parent exists", SetA would be renamed in SetC (parent).

Yiekes....nah....I don't think it makes sense. Ok, the 'parent stays parent' rule would fit but if the old parent shows e.g. a japanese flyer png and the new set 'C' shows a completely different title/language (there are such cases where clones do differ a lot) you will show a wrong flyer (as the original author might wanted to).

Hope I find some time at the weekend to rethink this whole thing....

3106

clrmame Discussion / Re: clrmamepro 3.131b released

« on: 05 November 2009, 18:27 »

With the "check if parent exists", SetA would be renamed in SetC (parent). This because no SetB.png existed in artwork123 BEFORE the rename.

hmmm....that means I need to analyze the 3rd dat/to be modified dat, too....hmm...something I wanted to avoid.

3107

clrmame Discussion / Re: clrmamepro 3.131b released

« on: 05 November 2009, 18:24 »

Hi Roman,
At the attached picture you can see there is something with some of the latest releases.(i dont know when it was started).
For both download options it shows the clone name.seond one should be parent name.the link is correct.only the writing is wrong.i think you forgot the variable name same for both .

Thanks for your great work.

fixed for next version

3108

clrmame Discussion / Re: clrmamepro 3.131b released

« on: 04 November 2009, 20:05 »

hmm...actually I think you can't get this information from the 2 dats...

let's assume this switch of 2 sets:

SetA (parent in old dat) -> SetB (clone in new dat)
SetB (clone in old dat -> SetA (parent in new dat)

Your rule would allow both renames.....

If now the artwork123 datfile holds only SetA.png, apply the changes will make it to a SetB.png....which is a clone....this may result in the fact that only clone shows the picture....(hope this was clear...)

My rule however would not allow the first rename (so it would stay SetA) but would allow the second rename...which will cause a "double rename"....hmm...again, not the best solution....need to handle this as well.

3109

clrmame Discussion / Re: clrmamepro 3.131b released

« on: 04 November 2009, 08:37 »

"if parent is moved to clone, but no new parent set is available

Hmm...a bit more tricky than the "don't rename if parent is renamed to a clone" (which I included last night already)...but I will do some brainstorming about it....

3110

clrmame Discussion / Re: clrmamepro 3.131b released

« on: 03 November 2009, 19:16 »

hmmm...actually I'm still not happy with that option...
I think I will change it in something like:

if the old set was a parent and is renamed to a non-parent in the new dat, you can use the option to allow this or not.

Background is that artworkdats usually keep parent set pngs....and frontends usually show the parent png if clone ones aren't given....

3111

clrmame Discussion / clrmamepro 3.131b released

« on: 02 November 2009, 20:54 »

3.131b

fixed: rename wizard's 'keep parent' option isn't working

3112

clrmame Discussion / Re: Norton will not allow cmpro 3.131a to run!!!

« on: 02 November 2009, 20:19 »

Well....while 64bit is state of the art with core2duo cpus....I don't say you have to update your system.
Either Norton will fix it themselves (false positives are usually fixed rather quickly...) or you can try the next version which will use a newer version of upx....

3113

clrmame Discussion / Re: Norton will not allow cmpro 3.131a to run!!!

« on: 01 November 2009, 21:58 »

Well, tough luck, get a security tool which works correctly and doesn't spit out false positives. Use the 64bit version if norton can't handle upx encoded 32bit builds....or really..get a better security program.

3114

clrmame Discussion / Re: An absolutely Commendable effort

« on: 01 November 2009, 20:47 »

for mame you can easily use the mame binary to get the data from. Profiler->Create...

3115

clrmame Discussion / Re: using the renamer wizard

« on: 01 November 2009, 20:45 »

yep...s_bastian is correct...load old dat, load new dat, hit DIFF, select your dat as modify dat and hit apply renames....it will create a new dat file with the renames applied

3116

clrmame Discussion / clrmamepro 3.131a released

« on: 28 October 2009, 21:12 »

3.131a

fixed: header support reported bad hashes when using the decompress and calc sha1/md5/full crc tests
fixed: rename wizard column sorting gets broken after using "Apply Changes"
fixed: merger shows merge options even when no parent/clone relationships are available

3117

clrmame Discussion / Re: 134 dats

« on: 24 October 2009, 14:29 »

done...now let's wait for 135

3118

clrmame Discussion / Re: 134 dats

« on: 23 October 2009, 20:42 »

wooho...found a little time....7 dats updated...4 to go...

3119

clrmame Discussion / Re: [clrmamepro] Doesn't allow me to Split/Merge sets

« on: 18 October 2009, 18:54 »

The datfile defines if you can split/fully merge sets. If the datfile doesn't hold any parent/clone relationships (or even hold statements like forcemerge modes), you simply can't split merge sets. Since the merger is a very old part of cmpro which is nearly not used anymore (since you can do everything with scanner/rebuilder), I assume it shows an enabled split/fully merge radiobutton by mistake.

Look at the datfile (or send it to me), if it doesn't hold any parent/clonerelationships, the behaviour is absolutely correct.

3120

clrmame Discussion / 134 dats

« on: 15 October 2009, 19:20 »

as you might notice...the artwork dats aren't up2date for 134...
well...you know...lack of time...so let's skip 134 and wait for 135 for which I hope I can update the dats....

...besides...you can of course use the renamewizard to apply the changes yourself