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.

2741

clrmame Discussion / Re: Can someone please help me wit ClrMamPro?

« on: 07 March 2011, 18:37 »

If you only care about sets which changed between two versions use mamediff to create a diff-dat and use that.

But I think you don't want that. Correct me if I'm wrong but you got a .135 collection and now want to use them with .141.
As mentioned before you don't need to rebuild them especially not with recompression enabled.

First step is to load a .141 database (Profiler->Create->use your .141 mame binary)
2nd step is setting up rompaths (if not yet done)
3rd step is the scanner, enable all check and fix options and let it go. It will fix what can be fixed
4th step is "add the missing stuff"...if you collected roms between .135 and .141 you can e.g. drag'n drop them into the scan tree window...internally this runs the rebuilder - an Adder -. Afterwards, rescan.


Scanning a full MAME set on a Core2Duo machine takes maybe 15 seconds to a minute (depending on the used diskcache) and no fixing. If lots of things need to get fixed it takes longer of course.

Regarding the single files, as mentioned before, rebuilder is file based and creates all instances of files. Same for fix-missing in the scanner. If you don't want that, you need to limit the sets to the sets you have/want. Go to Scanner->Set Information for this and disable sets manually, via regular expressions, variables, file lists or available button.

2742

clrmame Discussion / Re: Can someone please help me wit ClrMamPro?

« on: 07 March 2011, 17:27 »

Ok....where to start....

Some general things...

Merging modes - They define how you can store sets which share a parent/clone relationship. For example there are 50 pacman sets where they usually only differ in 1 or 2 files while the others are identical throughout the sets. Now you have different methods of storing such sets.
"not merged" or "Unmerged" - all sets hold all the files...so a parent holds all the files and each clone holds the shared files as well....in other words....waste of diskspace. Your set count is identical to the set count in MAME.
"split merged" - very common method to store sets.  Again, set count matches the total count in MAME. The difference is that each set only holds the file it really needs, i.e. the parent sets hold the parent files and each clone only holds the file which is not share with the parent.
"full merged" or "merged" sets - compact form...you only have archives for the parent sets and they include all clones as well. Archives for clones don't exist.

Ok...next thing....Profiler, Settings, Scanner, Rebuilder...

Profler - for MAME, use the create option to quickly create a database from the mame binary
Settings - for now, used to setup rom and sample paths

Scanner is used to update your sets, fix issues, get a list of what is wrong with your sets.

Rebuilder is an Adder. It's file based and takes anything it finds in its defined source and copies/moves it to a given destination. It's usually used to rebuild sets from one emulator for a different one but is also commonly used for a quick way to add missing files to your collection. The rebuilder doesn't care about names, it can find out what the real name is and rebuilds all instances of the files it matched.

General way to update MAME is to

1) load the new data in the profiler
2) (if not done yet, setup rompaths, maybe sample paths if you need them)
3) go to the scanner and hit scan (default options are fine)
4) you can enable all fix options there and do another scan to fix all issues
5) after that you should only have missing files (which can't be magically created from nothing)
6) add missing files with the rebuilder (e.g. drag'n drop into the scan results window)
7) scan again and repeat 6/7 till nothing is listed in the scan tree window anymore


Speed:
Well, of course the amount of sets and your PC specs play a role. Rebuilding is fast if you don't use re-compression. Scanning is fast if you don't decompress files to check hashes. Virusscanners should be disabled for the romfolders.


You only have some sets, not all....
Generally you should check all sets and don't care so much about endless lists of fully-missing sets. There is an option to hide them. You can only scan subsets of the full MAME set as well...in Set-Information you got several options to only enable some sets.
You mention the rebuilder creates single files for sets you don't have....well...yes it does...it's its main purpose to do so. That's the cool thing about it. Also Scanner's fix-missing option can do that. If a rom file is missing (e.g. for a set you don't have), cmpro looks at various places if it finds it somewhere and adds it. This doesn't necessarily mean you get complete sets by that method...

As mentioned, the scanner popupmenu holds several options to either hide missing sets afterwards or remove incomplete sets.

Puuuh....should be enough for a start....

2743

clrmame Discussion / Re: Can someone please help me wit ClrMamPro?

« on: 06 March 2011, 21:05 »

I can give you  a detailed answer in about 24 hours when Im back on a real PC... please be patient.

2744

clrmame Discussion / Re: no clones

« on: 05 March 2011, 10:11 »

dont use " in select sets edit box....

2745

clrmame Discussion / Re: no clones

« on: 05 March 2011, 07:49 »

Hmm..works fine here.

after entering %c=?* in select sets, checking the logical not checkbox and hitting apply button the count changes to e.g. 5304/10383 (141u3) and doing a rebuild afterwards it does only create the parent files.....

The correct selection is also visible in set selection..only the parent sets are checked in the tree view on the left.... after hitting apply.

2746

clrmame Discussion / Re: Feature Request: Bump LZMA SDK version to support LZMA2

« on: 02 March 2011, 20:21 »

actually it's not really 7z itself, it's more the lack of free time...I will see what I can do...

2747

clrmame Discussion / clrmamepro 3.137d

« on: 01 March 2011, 20:45 »

fixed: removed trimming of xml attribute values for now since it disallows whitespace separators for export lists

2748

clrmame Discussion / Re: clrmamepro 3.137c released

« on: 01 March 2011, 19:40 »

hmm..interesting sideeffect...will check this....

...ah found it :O) The trimming of xml attributes kills the linebreak.....
will do an update soon

2749

clrmame Discussion / Re: Feature Request: Bump LZMA SDK version to support LZMA2

« on: 01 March 2011, 08:04 »

Hehehe...well, actually I'd like to get rid of the external packer for 7z completely and would like to use the current dll for reading and writing 7zs (and so LZMA2 would come for free)...but my current amount of time plus the lack of well documented dll function calls keeps this pending. If you got the time to find a good documentation and examples for the dll calls, feel free to send them to me...

2750

clrmame Discussion / clrmamepro 3.137c released

« on: 28 February 2011, 21:04 »

3.137c

fixed: 7z add/remove fails for files starting with @
fixed: scanner popup menu functions to delete/move incomplete/notfixed sets got rare issues when deleting files
fixed: removed very old chd extension workaround which causes issues now with chds with "."
fixed: xml parser misses attribute name/value trimming

2751

News & Communication / clrmamepro 3.137c released

« on: 28 February 2011, 21:04 »

3.137c

fixed: 7z add/remove fails for files starting with @
fixed: scanner popup menu functions to delete/move incomplete/notfixed sets got rare issues when deleting files
fixed: removed very old chd extension workaround which causes issues now with chds with "."
fixed: xml parser misses attribute name/value trimming

2752

clrmame Discussion / Re: Folders and new dat creation

« on: 24 February 2011, 17:45 »

Yep, it's tricky, but the option is correct....It's only a question of what is the root folder for dir2dat...

Let's assume the following:


D:\temp\test is your dir2dat root, the source folder

In there you got 3 files, one on root level, another one in a folder names Set1 and the last one in a subfolder of Set1, called sub1

D:\temp\test\141.xml

D:\temp\test\Set1\141.xml
D:\temp\test\Set1\sub1\141u1.xml


Dir2Dat will then create:


   <game name="default">
      <description>default</description>
      <rom name="141.xml" size="45487005" crc="a4debe29"/>
   </game>
   <game name="set1">
      <description>set1</description>
      <rom name="141.xml" size="45487005" crc="a4debe29"/>
      <rom name="sub1\141u1.xml" size="46985053" crc="3c6f4755"/>
   </game>


The first game for the one file since it can't find any useful set assignment for it, and the 2nd game takes everything from the folder set1 ...and *there* you got your subfolders

2753

clrmame Discussion / Re: Folders and new dat creation

« on: 23 February 2011, 13:16 »

yes, play around with "set-subfolder mode"

2754

clrmame Discussion / Re: Folders and new dat creation

« on: 23 February 2011, 07:35 »

Sure you can do that...the dat needs foldernames on romlevel...

game (
 name "Mega Man"
 description "Mega Man My Ultimate Collection"
 rom ( name "Mega Man\Mega Man 7" size ... crc ...)
 rom ( name "Mega Man\Mega Man X" size ... crc ...)
 rom ( name "Mega Man\Mega Man X 2" size ... crc ...)
 rom ( name "Mega Man\Mega Man X 3" size ... crc ...)
...
)


..of course you can even use more subfolders

 rom ( name "Mega Man\Mega Man X\Mega Man X" size ... crc ...)
 rom ( name "Mega Man\Mega Man X\Mega Man X 2" size ... crc ...)
 rom ( name "Mega Man\Mega Man X\Mega Man X 3" size ... crc ...)



Don't mix up the removal of zip folders structures with the upper storing method. There is an option (Settings->compressor->General->Mark useless folder structs as unneeded) to remove unnecessary directory tags inside zips (some zip programs tend to add this additional structure) to save some bytes...

2755

clrmame Discussion / Re: Problems rebuilding files starting with @ into 7z archives under Windows 7

« on: 16 February 2011, 08:03 »

Well, the internal fix will work the same...if the filename starts with a @, it will internally use .\@...

guess it shouldn't make a difference if you keep the .\ ....then it will be .\.\@ ....shouldn't matter

2756

clrmame Discussion / Re: Problems rebuilding files starting with @ into 7z archives under Windows 7

« on: 15 February 2011, 19:11 »

Hmm...theoretically it should work if you change your 7z settings to:

a -y -r -ms=off -mx9 %1 .\%2


not tested yet....guess I can 'fix' it for a future release



....'Fixed' for the next version already...

2757

clrmame Discussion / Re: Problems rebuilding files starting with @ into 7z archives under Windows 7

« on: 14 February 2011, 22:11 »

yep...it's looking for a filelist when the file is in the current folder and starts with @ (which is the normal case during working with 7z...it changes to the belonging folder).

Hmm....wonder if you can use quotes or any other escaping for such a case....

2758

clrmame Discussion / Re: Problems rebuilding files starting with @ into 7z archives under Windows 7

« on: 11 February 2011, 07:40 »

well, since cmpro simply calls the external 7z binary to add/remove files it seems that 7z got a problem with @ in filenames...

I can check this next week.



...or it's just you trying to add a file to a solid or locked archive...which fails since 7z can't do that with the given commandline options....and the @ doesn't play a role...

2759

clrmame Discussion / Re: Batch mode

« on: 05 February 2011, 20:41 »

It's the same rebuilder routine, no matter if single run or batcher, so the reason must be somewhere in your used options.....

...check the options again (batch versus profile), maybe turn on rebuilder logging....

2760

clrmame Discussion / Re: Batch mode

« on: 05 February 2011, 20:06 »

well, of course I need a lot more information like which set in which dat is ignored....generally, if a file is not rebuilt, it's not matched against the current dat, i.e. crc32+size match (and md5/sha1 match as an addition). Also it might get skipped if it's locked by a different application. Batchrun uses its own rebuilder settings (if set, they overwrite the profile own ones) ...but generally batchrun is just a sequentially call of the single profiles...so maybe you should compare the rebuilder settings batch vs profile....


...on the other hand, if you're talking about network drives, that it could be related to an issue where (esp. Samba) got problems and skips files....however it's a network drive configuration issue and not cmpro related...