3321
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 12 December 2009, 19:13 »
you're welcome
- 14 May 2025, 11:14
- 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.
3322
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 12 December 2009, 16:57 »
hmm..nothing that dramatically changed...especially not during startup...weird...maybe it's the UPX packed exe....send me an email and I will send you a decompressed version (or try the 64bit build if possible 
3323
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 08 December 2009, 22:28 »
ah ok...the missing bytes header also appears in www profiler mode...will be fixed in next version...for 2009, ignore it 
3324
clrmame Discussion / clrmamepro 3.132 released
« on: 08 December 2009, 22:19 »
3.132
added: basic support for HyperSpin dat files
added: optional warning about archives (zip/rar) with comments (compressor settings)
added: missing/available bytes display in profiler and html report
added: rebuilder advance option to not create set folder when rebuilding to decompressed sets
misc: changed renamewizard keep parent behaviour to "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."
misc: show prompt after renamewizard modified a dat
misc: changed windows rect calculation which may solves weird border issue
misc: some minor code cleanup here and there
fixed: show wrong setname in download popupmenu
fixed: don't mark profile as green when a sysdefpath not assigned message pops up
fixed: separated biosfiles are wrongly counted as missing in fully missing sets
added: basic support for HyperSpin dat files
added: optional warning about archives (zip/rar) with comments (compressor settings)
added: missing/available bytes display in profiler and html report
added: rebuilder advance option to not create set folder when rebuilding to decompressed sets
misc: changed renamewizard keep parent behaviour to "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."
misc: show prompt after renamewizard modified a dat
misc: changed windows rect calculation which may solves weird border issue
misc: some minor code cleanup here and there
fixed: show wrong setname in download popupmenu
fixed: don't mark profile as green when a sysdefpath not assigned message pops up
fixed: separated biosfiles are wrongly counted as missing in fully missing sets
3325
clrmame Discussion / Re: Custom Audits
« on: 02 December 2009, 08:13 »
Go to Scanner->Set Information (bottom left button in the tree window).
There you got the chance to enable/disable the sets yourself either with use of variables, regular expressions or loading a list of sets. Either with or without automatically enabling parent/clones.
There you got the chance to enable/disable the sets yourself either with use of variables, regular expressions or loading a list of sets. Either with or without automatically enabling parent/clones.
3326
clrmame Discussion / Re: Show size of a datfile in clrmamepro/datworkshop pro
« on: 27 November 2009, 14:09 »
Missing Bytes/Total Bytes in profiler and html report implemented for next version.
3328
clrmame Discussion / Re: Merging a Fullset with a Parent-Clone dat. Scan? Merger? Rebuilder?
« on: 27 November 2009, 14:08 »
thought so :O)
3329
clrmame Discussion / Re: Filter (rebuild) a No-Intro set with a xml file
« on: 27 November 2009, 14:07 »
Basic hyperspin dat parser implemented for next version.
3330
clrmame Discussion / Re: Filter (rebuild) a No-Intro set with a xml file
« on: 24 November 2009, 15:10 »
Looks to be a very easy xml format....no size entries, no filename extensions listed...just name, description, crc32, manufacturer and year...
I guess I can quickly add a parser for that for the next version.
....however I still like the idea of somehow supporting xslt transformations somehow so that only the transformation needs to be defined...anyway..no time for that at the moment....or maybe in the rewrite (>2012)....
for now I will add an easy parser for that format...
I guess I can quickly add a parser for that for the next version.
....however I still like the idea of somehow supporting xslt transformations somehow so that only the transformation needs to be defined...anyway..no time for that at the moment....or maybe in the rewrite (>2012)....
for now I will add an easy parser for that format...
3331
clrmame Discussion / Re: Filter (rebuild) a No-Intro set with a xml file
« on: 24 November 2009, 13:13 »
simply send me some of their dats and I can check it
3332
clrmame Discussion / Re: Filter (rebuild) a No-Intro set with a xml file
« on: 24 November 2009, 10:17 »
Well...the official datformat is xml (even if nointro is still in old format).....and XSLT can be easily used to transform your Hyperspin XML into the official XML....
Either you learn and use XSLT....or you let me know where I can find out more regarding the "Hyperspin XML" format....
Either you learn and use XSLT....or you let me know where I can find out more regarding the "Hyperspin XML" format....
3333
clrmame Discussion / Re: Merging a Fullset with a Parent-Clone dat. Scan? Merger? Rebuilder?
« on: 21 November 2009, 17:15 »
Well...merging is possible (actually with scanner, rebuilder and merger)....but of course the used datfile has to support it. The datfile defines parent/clone relationsships. So first look for you would be the datfile...if it doesn't hold any parent/clone relationship tags ("cloneof"), then you simply can't merge sets.
If the datfile is organized in a way that merging is possible, you can simply change the scanner's merge mode and scan/fix to get the set merged.....by the way, the scanner's merge mode is a good thing to look at...if split or full merged is greyed out, the datfile doesn't have any parent/clone relationships defined.
If the datfile is organized in a way that merging is possible, you can simply change the scanner's merge mode and scan/fix to get the set merged.....by the way, the scanner's merge mode is a good thing to look at...if split or full merged is greyed out, the datfile doesn't have any parent/clone relationships defined.
3334
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.
3335
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...
Another size could be the sum of file sizes in all rompaths...
3336
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".
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".
3337
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)
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
)
3338
clrmame Discussion / Re: clrmamepro 3.131b released
« on: 06 November 2009, 09:05 »Quote
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....
3339
clrmame Discussion / Re: clrmamepro 3.131b released
« on: 05 November 2009, 18:27 »Quote
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.
3340
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