2801
clrmame Discussion / Re: possible bug report when updating new High-Res Flyer pack
« on: 06 January 2011, 11:16 »
Official zip only supports up to 4GB.
Use rar or 7z.
Use rar or 7z.
- 19 April 2024, 10:12
- 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.
2802
clrmame Discussion / Re: cmp can't update bin/cues [update]
« on: 05 January 2011, 10:02 »
Which version of 7z are you using and did you change the 7z settings in cmpro's settings/Compressor/7z?
They are set to not use any solid compressing...so actually if you used this to create the 7z they should work fine when being altered from within the scanner. If your 7zs come from a different source, they are most likely solid...
...but maybe 7z 9.x allows some altering of solid archives...will do some tests
...or is it a general issue with 7z files for you? maybe you can test it with some self-made small 7zs and a modified dat?
update...not a general thing....tested it with non-solid files and renaming inside 7z archives works fine
and another update...I tested a small but fully solid archive and renaming inside works fine, too (with 7z 9.20)....so which version are you using and maybe you can somehow provide me access to the files which cause issues?!
They are set to not use any solid compressing...so actually if you used this to create the 7z they should work fine when being altered from within the scanner. If your 7zs come from a different source, they are most likely solid...
...but maybe 7z 9.x allows some altering of solid archives...will do some tests
...or is it a general issue with 7z files for you? maybe you can test it with some self-made small 7zs and a modified dat?
update...not a general thing....tested it with non-solid files and renaming inside 7z archives works fine
and another update...I tested a small but fully solid archive and renaming inside works fine, too (with 7z 9.20)....so which version are you using and maybe you can somehow provide me access to the files which cause issues?!
2803
clrmame Discussion / Re: cmp can't update bin/cues
« on: 04 January 2011, 09:37 »
*Solid* 7z archives can't be updated/changed.
Why do you expect "Fix missing" to solve wrong named files? Fix name does this...
(Official) Zip only supports file sizes up to 4GB.
So...maybe some more details from your side (like what is stored where, what do you expect to get fixed, any error messages?) helps me to give a better reply...
Why do you expect "Fix missing" to solve wrong named files? Fix name does this...
(Official) Zip only supports file sizes up to 4GB.
So...maybe some more details from your side (like what is stored where, what do you expect to get fixed, any error messages?) helps me to give a better reply...
2804
clrmame Discussion / Re: New feature request....
« on: 27 December 2010, 17:24 »
good point... lets wait till 2011 
2805
clrmame Discussion / Re: New feature request....
« on: 27 December 2010, 08:35 »
so warningswindow aint enough? hmm.. will think about it after holidays...
2806
clrmame Discussion / Re: Clrmamepro isn't able to check 7z sets bigger than 4 GB
« on: 13 December 2010, 20:48 »
Ah...I guess I see now what you mean...well, actually the >4GB support of 7z files works fine.
The problem is more likely that when you got the "Decompress Rom & check crc32" or similar options enabled which try to decompress files into memory, you run into an out of memory error of 7z since it tries to decompress the full file into memory. You should see an error like "7z: ERROR SZ_ERROR_MEM -> ...." in the warnings window.
So...solution is: if you work with such big files, don't use such options...or switch to decompressed files. For 7z you currently got the limitation that it tries to decompress the full file.
I don't know if I find the time to look at the lates 9.x versions of 7z before xmas...
The problem is more likely that when you got the "Decompress Rom & check crc32" or similar options enabled which try to decompress files into memory, you run into an out of memory error of 7z since it tries to decompress the full file into memory. You should see an error like "7z: ERROR SZ_ERROR_MEM -> ...." in the warnings window.
So...solution is: if you work with such big files, don't use such options...or switch to decompressed files. For 7z you currently got the limitation that it tries to decompress the full file.
I don't know if I find the time to look at the lates 9.x versions of 7z before xmas...
2807
clrmame Discussion / Re: Clrmamepro isn't able to check 7z sets bigger than 4 GB
« on: 11 December 2010, 20:24 »
64 bit version of 7z works fine. Im using it myself. The problem is not in the external packer Guess the 4gb limit is based within the 7z reader which comes from an old 7z sdk....which lacks all kind of stuff not to even mention the code quality of the sdk.
I may have a look at it next week.
I may have a look at it next week.
2808
clrmame Discussion / clrmamepro 3.137a
« on: 09 December 2010, 20:47 »
3.137a
misc: support of parsing rom size entries in hexformat (0x...)
misc: support of parsing rom size entries in hexformat (0x...)
2809
clrmame Discussion / Re: Help
« on: 02 December 2010, 20:02 »
well, so most likely some files of your 1 set are used by different sets (usually proms)...so fix missing created them.....
As mentioned, cmpro can't magically create missing files...if you really miss one, you need to find it.
As mentioned, cmpro can't magically create missing files...if you really miss one, you need to find it.
2810
clrmame Discussion / Re: Help
« on: 02 December 2010, 08:30 »
Ah...sounds like you had fix-missing enabled.
If cmpro sees that a file is missing, it checks if it finds it somewhere
(e.g. in defined addpaths, in your backup folder and in other sets you already have).
Since there are several files which are shared through dozens of sets, fix-missing finds them and creates them in the set where it was missing. This doesn't mean you get a full set of course.
The Rebuilder is something which can be used to convert collections from one datasource to another (e.g. Kawaks To Mame, etc). It checks any found source file and -if it matches something in your currently loaded dat- it creates all instances of it in the destination.
The rebuilder can also be used as an Adder. Rebuilder destination should point to your current collection then....then you can easily drag'n drop new, not cleaned, unknown files into the rebuilder (or scanner) window, and cmpro adds them to their belonging place...or skips them if they don't match anything useful.
By the way, the statistics screen isn't something you really need....the more important thing is the scanner tree output since it tells you in detail what's wrong with your sets. If nothing is listed anymore there, you're done
By default, all sets are being scanned and reported...so if you only got 1 set, the rest of the 8000 are being reported as fully missing....you can hide such entries or can even limit the number of sets to scan....but that's something for tomorrow (or read the forum sticky items).
If cmpro sees that a file is missing, it checks if it finds it somewhere
(e.g. in defined addpaths, in your backup folder and in other sets you already have).
Since there are several files which are shared through dozens of sets, fix-missing finds them and creates them in the set where it was missing. This doesn't mean you get a full set of course.
The Rebuilder is something which can be used to convert collections from one datasource to another (e.g. Kawaks To Mame, etc). It checks any found source file and -if it matches something in your currently loaded dat- it creates all instances of it in the destination.
The rebuilder can also be used as an Adder. Rebuilder destination should point to your current collection then....then you can easily drag'n drop new, not cleaned, unknown files into the rebuilder (or scanner) window, and cmpro adds them to their belonging place...or skips them if they don't match anything useful.
By the way, the statistics screen isn't something you really need....the more important thing is the scanner tree output since it tells you in detail what's wrong with your sets. If nothing is listed anymore there, you're done
By default, all sets are being scanned and reported...so if you only got 1 set, the rest of the 8000 are being reported as fully missing....you can hide such entries or can even limit the number of sets to scan....but that's something for tomorrow (or read the forum sticky items).
2811
clrmame Discussion / Re: Help
« on: 01 December 2010, 08:19 »
Well, if MAME says "NOT FOUND", you're missing a file. clrmamepro can't magically create them for you. (well, if you got it somewhere it will find it for you though).
General quick start:
"Profiler->Create" to get romset data information from your mame executable. If prompts appear, click "yes to all"
"Settings->Path selector" setup your rom path (and optionally samples path if you use them)
"Scanner" -> select your prefered merge mode (if you don't know how your sets are merged, keep split-merged) and hit new scan....then look what's wrong with your sets. You can enable the fix options (right beside the check-checkboxes) and hit scan again to get the fixable issues fixed). If you do this you most likely end up with the stuff which is not fixable...for example: missing files.
Then you need to search them and you can use cmpro to add them to your collection (e.g. via rebuilder or scanner's fix missing option in combination with add-paths/settings)
General quick start:
"Profiler->Create" to get romset data information from your mame executable. If prompts appear, click "yes to all"
"Settings->Path selector" setup your rom path (and optionally samples path if you use them)
"Scanner" -> select your prefered merge mode (if you don't know how your sets are merged, keep split-merged) and hit new scan....then look what's wrong with your sets. You can enable the fix options (right beside the check-checkboxes) and hit scan again to get the fixable issues fixed). If you do this you most likely end up with the stuff which is not fixable...for example: missing files.
Then you need to search them and you can use cmpro to add them to your collection (e.g. via rebuilder or scanner's fix missing option in combination with add-paths/settings)
2812
clrmame Discussion / Re: Profiler slow to load
« on: 30 November 2010, 21:41 »
So....if you want to have a speedy profiler, add cmpro's settings and datfile folder to the virusscanner's exclusion list....they contain only text/xml files anyway....
2813
clrmame Discussion / Re: Profiler slow to load
« on: 30 November 2010, 19:48 »
and now to your full archive:
cmpro64.exe (3.137): 5 seconds
cmpro.exe (3.134b): 5 seconds
cmpro_3.89a: 2 min 1 second
cmpro_3.88: 1 min 59 seconds
well, as you can see it's fast enough for the current version...I think 5 seconds to process ~2600 dats and ~2600 settings files is ok.
There is no reason to keep such old (4.5 years!) cmpro versions like 3.89a or 3.88.
by the way, testing system was a 64bit Windows 7 on a C2D 6600 cpu with 4GB...and a fast HD....nothing really up2date l33t pc...
cmpro64.exe (3.137): 5 seconds
cmpro.exe (3.134b): 5 seconds
cmpro_3.89a: 2 min 1 second
cmpro_3.88: 1 min 59 seconds
well, as you can see it's fast enough for the current version...I think 5 seconds to process ~2600 dats and ~2600 settings files is ok.
There is no reason to keep such old (4.5 years!) cmpro versions like 3.89a or 3.88.
by the way, testing system was a 64bit Windows 7 on a C2D 6600 cpu with 4GB...and a fast HD....nothing really up2date l33t pc...
2814
clrmame Discussion / Re: Profiler slow to load
« on: 30 November 2010, 19:07 »
thanks....downloaded the archive and only decompressed the datfile and settings folder into a new instance of cmpro 3.137....started it and it took 4 seconds(!) to load 2638 datfiles and settings files...
....will do the same with your full archive later on.....but it seems to be your system at the moment....
....will do the same with your full archive later on.....but it seems to be your system at the moment....
2815
clrmame Discussion / Re: Profiler slow to load
« on: 29 November 2010, 20:15 »
It's quick as always here....so....any chance to send me your setup?
2816
clrmame Discussion / Re: Profiler slow to load
« on: 27 November 2010, 20:11 »
actually nothing changed for ages in the profiler. can you maybe send me your setup in a compressed form somehow?
maybe something changed on your system? a going nuts virusscanner? some self created settings files? will do some checks next week but would be great to have your config setup.
maybe something changed on your system? a going nuts virusscanner? some self created settings files? will do some checks next week but would be great to have your config setup.
2817
clrmame Discussion / Re: clrmamepro 3.137
« on: 25 November 2010, 08:33 »
On start, clrmame tries to remove and create its temporary folder. If this does not work it is a sign that you installed it into an UAC protected folder (and that prompt tells you to run it as admin).
That is one reason...
another is simple and most likely common, too: The folder is locked by the OS for some reason. In this case there might be a not deletable file inside the folder...maybe after some reboot it will work fine. In this case you don't need to run it as admin.
That is one reason...
another is simple and most likely common, too: The folder is locked by the OS for some reason. In this case there might be a not deletable file inside the folder...maybe after some reboot it will work fine. In this case you don't need to run it as admin.
2818
clrmame Discussion / clrmamepro 3.137
« on: 24 November 2010, 21:57 »
3.137
fixed: rare external packer file not found prompt issue
fixed: removing more than one file via external packers fails
fixed: several www profiler issues fix:
- does not load compressed xmls when generated via php
- wrong sorting after download
- popupmenu "refresh datfiles from" does not work correctly
- not always remembering selected tree/list item after refresh
added: www profiler shows author as column
misc: changed progress window and button bar design
Thanks to Alex Schütz for the artwork.
misc: updated unrar dll
misc: changed tempfolder failure text to uac warning
fixed: rare external packer file not found prompt issue
fixed: removing more than one file via external packers fails
fixed: several www profiler issues fix:
- does not load compressed xmls when generated via php
- wrong sorting after download
- popupmenu "refresh datfiles from" does not work correctly
- not always remembering selected tree/list item after refresh
added: www profiler shows author as column
misc: changed progress window and button bar design
Thanks to Alex Schütz for the artwork.
misc: updated unrar dll
misc: changed tempfolder failure text to uac warning
2819
News & Communication / clrmamepro 3.137
« on: 24 November 2010, 21:57 »
3.137
fixed: rare external packer file not found prompt issue
fixed: removing more than one file via external packers fails
fixed: several www profiler issues fix:
- does not load compressed xmls when generated via php
- wrong sorting after download
- popupmenu "refresh datfiles from" does not work correctly
- not always remembering selected tree/list item after refresh
added: www profiler shows author as column
misc: changed progress window and button bar design
Thanks to Alex Schütz for the artwork.
misc: updated unrar dll
misc: changed tempfolder failure text to uac warning
fixed: rare external packer file not found prompt issue
fixed: removing more than one file via external packers fails
fixed: several www profiler issues fix:
- does not load compressed xmls when generated via php
- wrong sorting after download
- popupmenu "refresh datfiles from" does not work correctly
- not always remembering selected tree/list item after refresh
added: www profiler shows author as column
misc: changed progress window and button bar design
Thanks to Alex Schütz for the artwork.
misc: updated unrar dll
misc: changed tempfolder failure text to uac warning
2820
clrmame Discussion / Re: The Basics...
« on: 21 November 2010, 17:29 »
well, yes, a job for the rebuilder.
1) either load a datfile for that old mame version or use the profiler's create option and point to the old mame exe. Be sure you've selected OLD_MAME to parse the correct old format
2) rebuilder source points to your new collection, rebuilder destination points to your future 37something folder
3) after rebuilding, let a rompath point to that new folder and scan....guess you will have a hard time finding old baddumps which were replaced later on...
1) either load a datfile for that old mame version or use the profiler's create option and point to the old mame exe. Be sure you've selected OLD_MAME to parse the correct old format
2) rebuilder source points to your new collection, rebuilder destination points to your future 37something folder
3) after rebuilding, let a rompath point to that new folder and scan....guess you will have a hard time finding old baddumps which were replaced later on...