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.

2381

clrmame Discussion / Re: scans that take a really long time...

« on: 03 May 2012, 21:18 »

turn off fix missing and scanner->advanced->deeper check for missing files (or whateve it is named).... both options are not recommended for such 1-set-with-thousand-roms profiles like progetto artwork.

2382

clrmame Discussion / Some in between build.....

« on: 03 May 2012, 20:15 »

since I'm in the middle of something....and too busy to do a full release at the moment....so here's something to play with:

http://mamedev.emulab.it/clrmamepro/binaries/cmp20120503.rar

misc: reset profile to not scanned in case scan was skipped
misc: changed the error message for .7z files which aren't 7z archives
misc: added CMPro_TempFolder and CMPro_TempFolder_Clean settings to cmpro.ini to let
      you select the cmpro folder and optionally clean it on startup. Default value is
      the cmpro temp folder and data gets initially removed. You need to start/quit cmpro
      once to see this setting
misc: warnings window entries are logged to cmpro.log (cleared on startup)
fixed: chdversion check for merged sets can hide the result
fixed: xml parser failure when hitting an ending and starting xml comment in one line

2383

clrmame Discussion / Re: New feature request

« on: 02 May 2012, 20:33 »

fixed for next version

2384

clrmame Discussion / Re: Weird rebuilder / NTFS bug

« on: 02 May 2012, 20:33 »

ok...next version got an option to select the temp folder (in cmpro.ini) and decide if it gets initially cleaned.

2385

clrmame Discussion / Re: Modification Request

« on: 02 May 2012, 19:31 »

The 2 options for always and never remove rebuilt files do make sense.

The batcher options overwrite local profile settings. So if you got profiles which do have the remove-rebuilt option enabled, you may want to have an option to disable it. That's the 'never remove'. Or you got profiles which do have the remove-rebuilt option disabled and you may want to 'overwrite' the setting in the batcher....that's the 'always remove'. If neither one or the other option is enabled, the profile-local settings are used.

2386

clrmame Discussion / Re: New feature request

« on: 02 May 2012, 16:42 »

There is no new features.
The xml parser only gets confused with a closed and started xml comment in you dat (--><!-- ). I will fix that...in the meantime you can simply add a new line between the 2 comments...

2387

clrmame Discussion / Re: New feature request

« on: 30 April 2012, 19:21 »

can you send me the full file

2388

clrmame Discussion / Re: Modification Request

« on: 29 April 2012, 18:07 »

I add it to my batcher wishlist. generally it needs some more alignment with the standard dialogs. All I need is some free time....

2389

clrmame Discussion / Re: Weird rebuilder / NTFS bug

« on: 25 April 2012, 15:56 »

why do you actually have a problem with ntfs compression? it does not affect the files within the archives or mame in general...just wondering...

NTFS compressing already compressed files icurs a small overhead with no actual compression benefit.

But that doesn't play a role when the final zip/7z/rar romset is copied to a drive which is not set to ntfs compression. You may have a minimum overhead in cmpro's temp folder, but the final archive file in its final place is the one we have to care about...and if your partition is not ntfs-compressed, then you don't have this overhead.

2390

clrmame Discussion / Re: Problems with rom which have 7z extension

« on: 17 April 2012, 19:21 »

Well, the error message is partly wrong. It decompresses the file s7.7z into the temp folder (and there it uses a temporary name) and then it tries to read this .7z file. But actually it is not a 7z file and the 7z reader returns the error message. After that, the file is read as a standard file and gets rebuild. In a future version, cmpro will show a 7z error string ERROR SZ_ERROR_NO_ARCHIVE warning instead of a corrupt archive message.

Anyway, nothing to worry about...it's just a warning about a .7z file which isn't a 7z archive.

2391

clrmame Discussion / Re: Problems with rom which have 7z extension

« on: 17 April 2012, 10:52 »

Well, you can send me the file you're talking about....but actually the warning is only about a temporary file and only complains about having a 7z file without any files in it...e.g. when single files are removed from it but not the container itself (for whatever reason)...Nothing you have to worry about.

2392

clrmame Discussion / Re: Weird rebuilder / NTFS bug

« on: 13 April 2012, 19:17 »

maybe in a future version. I add it to my list

2393

clrmame Discussion / Re: Weird rebuilder / NTFS bug

« on: 11 April 2012, 17:01 »

why do you actually have a problem with ntfs compression? it does not affect the files within the archives or mame in general...just wondering...

2394

clrmame Discussion / Re: suggestion for an optimization for the rebuilder

« on: 11 April 2012, 13:29 »

The rebuilder is file based, not set based. It scans one file or one file within an archive and creates (adds) all instances of that file in case of a checksum match.
There might be some minor room for some small "look ahead" optimization....but don't expect anything anytime soon.

2395

clrmame Discussion / Re: convert newer collection to older? (139 > 119)

« on: 02 April 2012, 08:08 »

Different crc32 usually mean different roms.
There might be a chance that it's only a byte ordering change or a padding (which cmpro could handle if you enable "scanner->checksum->Run analysis/fix file if possible") but I doubt that...you need to find the old files and replace them.

2396

clrmame Discussion / Re: Weird rebuilder / NTFS bug

« on: 30 March 2012, 19:18 »

Ask Windows
No joking, cmpro doesn't have any influence on that.

2397

clrmame Discussion / Re: convert newer collection to older? (139 > 119)

« on: 30 March 2012, 09:49 »

Sure it's possible...well...if you understand what usually "updating" means, you see why downgrading is a bit more complex.

An update includes:
- reorganization of sets (place change, parent/clone behaviour)
- renames of files
- new additions of files
- ...
- removal or replacement of bad dumps  ...and there you go...of course if you downgrade you need to find such replaced files again.

So you simply load an old dat/mame in your profiler and rebuild your 'new' set to an old one....everything missing then did simply change in the past (bad dumps replaced with new ones or complete removals)....so find such old files and you're done.

Personally I think there is no reason to downgrade anyway....but...it's your choice...

2398

clrmame Discussion / Re: A couple of random requests...

« on: 28 March 2012, 19:41 »

use this then

http://mamedev.emulab.it/clrmamepro/binaries/cmpro20120328.rar

2399

clrmame Discussion / Re: A couple of random requests...

« on: 28 March 2012, 16:24 »

how about a warningswindow log file and a batcher log file.....then at least you get all warnings and in the batcher log you can see if a scan was done or not...

2400

clrmame Discussion / Re: A couple of random requests...

« on: 28 March 2012, 15:18 »

well....adding it to the list means nothing :O)
It's a huge list by now and I pick things from there from time to time....