3261
clrmame Discussion / Re: clrmamepro scan problem with current MESS SVN releases
« on: 06 April 2010, 15:59 »
Can you mail me an example xml output please so I will have look at it later tonight?
- 12 May 2025, 08:09
- 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.
3262
clrmame Discussion / Re: Strange problem with Carnevi1 CHD
« on: 05 April 2010, 16:27 »
so actually what I'm saying is:
if you keep your sets fully merged you only need the rompath subfolder for the carnevil parent set and keep all chds (the parent and the clone(s)) in there. Then you don't need the "allow chds in rompath root" option.
If you keep them split-merged, you need a subfolder for each one (parent and clones...)
if you want to store them in a rompath root, you need to enable that option and normally you can keep the chds in any rompath root then.
So...recheck your setup and let me know what looks wrong in your point of view....as mentioned in the previous post, best would be to send me the details (cmpro files) and maybe a short information which file is stored where....
if you keep your sets fully merged you only need the rompath subfolder for the carnevil parent set and keep all chds (the parent and the clone(s)) in there. Then you don't need the "allow chds in rompath root" option.
If you keep them split-merged, you need a subfolder for each one (parent and clones...)
if you want to store them in a rompath root, you need to enable that option and normally you can keep the chds in any rompath root then.
So...recheck your setup and let me know what looks wrong in your point of view....as mentioned in the previous post, best would be to send me the details (cmpro files) and maybe a short information which file is stored where....
3263
clrmame Discussion / Re: Strange problem with Carnevi1 CHD
« on: 05 April 2010, 14:53 »
Wait a second....it says 'unneeded folder'. I'm assuming you're using full merged sets then? If so, move the clone chd file to its parent folder (with the parent chd) and you can safely remove the unnecessary folder.
If I should do more investigation, please let me know more details....
Easiest would be to email me your cmpro.ini file, the used profile settings file (.cmp in cmpro's settings folder) and if the dat is not MAME based, the datfile.
If I should do more investigation, please let me know more details....
Easiest would be to email me your cmpro.ini file, the used profile settings file (.cmp in cmpro's settings folder) and if the dat is not MAME based, the datfile.
3264
clrmame Discussion / Re: Strange problem with Carnevi1 CHD
« on: 04 April 2010, 18:47 »
Be Sure that you enable the allow Chd in rompathroot Option if you Store chds that Way. Also Be sure that your Chd is valid.
I will check this When Im back from Holiday and don't use a mobilephone to answer postings
I will check this When Im back from Holiday and don't use a mobilephone to answer postings
3265
clrmame Discussion / Re: Scan All to Fix Missing
« on: 09 March 2010, 08:29 »
Well,
I can tell you what users usually do when a new version of MAME is out:
0) Load the MAME profile (Profiler detects a new version of the mame exe and auto-updates its database)
1) Scanner, got all check and fix options enabled...Do a new scan and let them fix all..
...after that you should only have missing files, the ones which were added/replaced in the new version
2) drag'n drop new sets into the scan results window with auto-scan after drag'n drop and drag'n drop internally uses the rebuilder, where the rebuilder destination points to the existing collection.
3) repeat 2) until nothing is listed anymore (ok...new chds need to be moved to any rompath though, cmpro will move them to their correct place)
I can tell you what users usually do when a new version of MAME is out:
0) Load the MAME profile (Profiler detects a new version of the mame exe and auto-updates its database)
1) Scanner, got all check and fix options enabled...Do a new scan and let them fix all..
...after that you should only have missing files, the ones which were added/replaced in the new version
2) drag'n drop new sets into the scan results window with auto-scan after drag'n drop and drag'n drop internally uses the rebuilder, where the rebuilder destination points to the existing collection.
3) repeat 2) until nothing is listed anymore (ok...new chds need to be moved to any rompath though, cmpro will move them to their correct place)
3266
clrmame Discussion / Re: error log messages: SKIPPED Reason: Unknown
« on: 06 March 2010, 20:27 »
if I remember correctly "skipped with reason unknown" simply means they were skipped with non of the 'problem things' like corrupt archive, problems while decompressing or destination file creation fails. So mainly if a file simply does not match anything valid.
3267
clrmame Discussion / Re: [REQUEST] allow omission of <description> element
« on: 26 February 2010, 08:31 »
see...I never understood why "singe console roms" need a name which is 132947310897414 characters long if you got a nice description tag.
Besides of that, MAME is not fully 8.3 since years
Besides of that, MAME is not fully 8.3 since years
3268
clrmame Discussion / Re: [REQUEST] allow omission of <description> element
« on: 25 February 2010, 08:45 »
Description is required, it's used internally for all kind of checks, sorting possibilities and displaying information.
I don't see a problem having it in the dat either.
Within cmpro it's stored only once anyway if it matches the setname and datfiles can be compressed.
Of course you might say, so if cmpro uses it only once if it's identical to the setname, why not cloning it during datparsing....hmm...I might think of it.
I don't see a problem having it in the dat either.
Within cmpro it's stored only once anyway if it matches the setname and datfiles can be compressed.
Of course you might say, so if cmpro uses it only once if it's identical to the setname, why not cloning it during datparsing....hmm...I might think of it.
3269
clrmame Discussion / Re: clrmame scan reports existing set as MISSING
« on: 19 February 2010, 18:09 »
you can use auto-detect rompaths in the systems dialog. It will scan your rompaths and picks the best fitting one for each sysdefpath.
...of course you need romsets in there to get something useful
...of course you need romsets in there to get something useful
3270
clrmame Discussion / Re: clrmame scan reports existing set as MISSING
« on: 19 February 2010, 08:11 »
no.
Don't put rompaths in rompaths for scanning
Don't put rompaths in rompaths for scanning
3271
clrmame Discussion / Re: clrmame scan reports existing set as MISSING
« on: 18 February 2010, 22:27 »
generally, sysdefpaths are folders.
if you scan and want to use sysdefpaths, your sysdefpaths have to be setup as rompaths, too.
if you want to rebuild sets in sysdefpaths, your sysdefpaths don't need to be setup as rompaths (depending on your rebuilding idea...for example if you want to split your sourcesets into folders-by-system sets...)
if you scan and want to use sysdefpaths, your sysdefpaths have to be setup as rompaths, too.
if you want to rebuild sets in sysdefpaths, your sysdefpaths don't need to be setup as rompaths (depending on your rebuilding idea...for example if you want to split your sourcesets into folders-by-system sets...)
3272
clrmame Discussion / Re: clrmame scan reports existing set as MISSING
« on: 18 February 2010, 19:27 »
Because systemdefaultpaths not necessarily have to be rompaths. For scanning yes, for rebuildering or merging not necessarily.
3273
clrmame Discussion / Re: clrmame scan reports existing set as MISSING
« on: 18 February 2010, 07:07 »
..and of course you got
a) all your sysdefpaths added as rompaths in the settings window
b) SoulClb2 is stored correctly (either <your rompath>\soulclb2\rom 1.. rom n for decompressed sets or your rompath>\soulclb2.zip (.rar/.7z) for compressed sets
Without having more information about your settings I can't tell you what's wrong. If a) is not your issue, send me screenshots and cmpro.ini and the belonging .cmp file for your used profile in cmpro's settings folder
a) all your sysdefpaths added as rompaths in the settings window
b) SoulClb2 is stored correctly (either <your rompath>\soulclb2\rom 1.. rom n for decompressed sets or your rompath>\soulclb2.zip (.rar/.7z) for compressed sets
Without having more information about your settings I can't tell you what's wrong. If a) is not your issue, send me screenshots and cmpro.ini and the belonging .cmp file for your used profile in cmpro's settings folder
3274
clrmame Discussion / Re: Generate HTML Report Current Folder including Sub-folders possible?
« on: 13 February 2010, 09:09 »
maybe a better (and less time taking) idea would be to export the profile data as xml so you can code the html pages yourself
3275
clrmame Discussion / Re: Generate HTML Report Current Folder including Sub-folders possible?
« on: 13 February 2010, 08:57 »
well...theoretically...of course....practically...I put it on my list...don't expect to see it anytime soon since currently I got nearly zero time for bigger changes.
3276
clrmame Discussion / Re: Drag & Drop?
« on: 02 February 2010, 08:30 »
Welcome to the beautiful world of Vista and Windows7.
You can't drag'n drop files from a source to a destination where the user access rights differ.
So...either your source folder got different user rights than the cmpro application or viceversa.
You can fiddle around with running the application as administrator but usually it's enough to store cmpro in a not-UAC protected folder.
My setup: Windows 7 64bit ultimate, logged in as an administrator user
cmpro installed in d:\cmpro\cmpro.exe (so I avoid anything like c:\programs...) and the things I want to scan/rebuild are somewhere in h:\mame\roms for example.
You can't drag'n drop files from a source to a destination where the user access rights differ.
So...either your source folder got different user rights than the cmpro application or viceversa.
You can fiddle around with running the application as administrator but usually it's enough to store cmpro in a not-UAC protected folder.
My setup: Windows 7 64bit ultimate, logged in as an administrator user
cmpro installed in d:\cmpro\cmpro.exe (so I avoid anything like c:\programs...) and the things I want to scan/rebuild are somewhere in h:\mame\roms for example.
3277
clrmame Discussion / Re: creating mess dats
« on: 29 January 2010, 18:03 »
Profiler->Create->Emulator = MESS
3278
clrmame Discussion / Re: how to add CHD using clrmamepro?
« on: 27 January 2010, 21:00 »
Regarding the stats, well, cmpro counts nodumps (no matter if chd or full set or rom) as 'available' depending on the nodump-mode (required/optional/etc). So even if you scan an empty rompath, you automatically have some roms...the nodumps
3279
clrmame Discussion / Re: how to add CHD using clrmamepro?
« on: 27 January 2010, 14:42 »
ignore the stats (they are calculated differently, without caring for merge modes etc...)
look at the scan results tree output..that's the only important thing to care about. Everything listed there is an issue and it gives you detailed information about what is wrong.
look at the scan results tree output..that's the only important thing to care about. Everything listed there is an issue and it gives you detailed information about what is wrong.
3280
clrmame Discussion / Re: how to add CHD using clrmamepro?
« on: 26 January 2010, 21:09 »
the semi-official method is the one which follows the standard storing method for MAME:
rompath\setname\file 1 ... file n
this means, for example you got your roms in d:\temp\mame\roms and go the cap-jjk-160.chd file, you put it in
d:\temp\mame\roms\jojo\cap-jjk-160.chd
since jojo is the belonging setname.
So the semi-official method is to use rompath subfolders named after the set...similar to decompressed sets.
Since CHD files are containers (Compressed Hunks of Data), putting them in a zip is obsolete and would cause endless and very memory intensive decompress operations.
Since MAME .130 you can allow store chds in a rompath root...which is the 'weird mode' since you don't reallly see which set the chdfile belongs to (usually they are not so easily named like area51.chd for area51).
That chd-on-rompath-root level is supported by cmpro but you need to enabled it (scanner->advanced).
rompath\setname\file 1 ... file n
this means, for example you got your roms in d:\temp\mame\roms and go the cap-jjk-160.chd file, you put it in
d:\temp\mame\roms\jojo\cap-jjk-160.chd
since jojo is the belonging setname.
So the semi-official method is to use rompath subfolders named after the set...similar to decompressed sets.
Since CHD files are containers (Compressed Hunks of Data), putting them in a zip is obsolete and would cause endless and very memory intensive decompress operations.
Since MAME .130 you can allow store chds in a rompath root...which is the 'weird mode' since you don't reallly see which set the chdfile belongs to (usually they are not so easily named like area51.chd for area51).
That chd-on-rompath-root level is supported by cmpro but you need to enabled it (scanner->advanced).