EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

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.

Messages - Roman

Pages: 1 ... 116 117 118 119 120 [121] 122 123 124 125 126 ... 165
2401
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...

2403
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...

2404
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....

2405
clrmame Discussion / Re: A couple of random requests...
« on: 28 March 2012, 13:17 »
I'll add it to my list

2406
critical = the created archive is corrupt for whatever reason, disk is full or the filename is illegal (e.g. too long for the filesystem)

2407
Well, usually you get an archive error only if something critical happened during writing to an archive (i.e. reading a bad zip will list something in the warningswindow but does not prompt). So the prompt makes sense normally....I will think about an ignore option though.

Regarding rebuilding 7z vs standalone 7z....pretty easy: The rebuilder is file based. If the crc32 hash matches something in the database it will additionally check sha1/md5 (optionally, if available)...this needs decompressing to memory (which -due to an old 7z sdk- is done at once and not done blockwise). Then it adds that one file to the destination archive....as mentioned file by file...that takes long. If you do it in a batch you 7z up a folder most likely and 7z handles it at once...

2409
clrmame Discussion / Re: chd version check bug
« on: 26 March 2012, 13:04 »
I will check that later tonight

2410
News & Communication / clrmamepro 4.05 released
« on: 22 March 2012, 22:05 »
clrmamepro 4.05

added: profiler options option to prompt for software lists import during MAME/MESS import
added: chdman settings option to optionally show version mismatches during scan
misc: auto expand not fixed items in tree control
misc: improved scanner matching for identical named sets / softwarelists (with BIOS roms)
misc: updated to latest ziparchive lib
misc: updated to latest unrar lib
misc: scanner adv option to remove not renamed sets to backup now also applies to roms
misc: removed border from tree scan output (minor cosmetics)
fixed: warning about missing sysdefpaths rarely shows only "..." instead of list
fixed: batch rebuilding doesn't care about forcepacking attributes in dats

2411
clrmame Discussion / cmpro 4.05 released
« on: 22 March 2012, 20:43 »
clrmamepro 4.05

added: profiler options option to prompt for software lists import during MAME/MESS import
added: chdman settings option to optionally show version mismatches during scan
misc: auto expand not fixed items in tree control
misc: improved scanner matching for identical named sets / softwarelists (with BIOS roms)
misc: updated to latest ziparchive lib
misc: updated to latest unrar lib
misc: scanner adv option to remove not renamed sets to backup now also applies to roms
misc: removed border from tree scan output (minor cosmetics)
fixed: warning about missing sysdefpaths rarely shows only "..." instead of list
fixed: batch rebuilding doesn't care about forcepacking attributes in dats

2412
clrmame Discussion / Re: small request
« on: 22 March 2012, 20:07 »
well, 405 won't have the datfile command yet....but I got it on my list....405 will have an option to hide such warnings....

2413
clrmame Discussion / Re: small request
« on: 20 March 2012, 21:38 »
I was just asked if the chdversion can be made optional anyway....so I guess that will be added...
...by the way, you can hide it by unchecking the checksum checkmark after a scan.

2414
clrmame Discussion / Re: Rebuilder options - batch mode
« on: 16 March 2012, 13:26 »
Thanks for the feedback...

2415
clrmame Discussion / Re: Rebuilder options - batch mode
« on: 15 March 2012, 20:13 »
try this one:
http://mamedev.emulab.it/clrmamepro/binaries/cmp20120315.rar
forcepacking attributes should work in batch mode now...

don't know if I fully understand your "when no specific rebuild compression settings are applied via the rebuilder tab". Generally, the profile option is used and is overwritten by the batcher option...

so...let me know if the new build is ok

2416
clrmame Discussion / Re: Rebuilder options - batch mode
« on: 15 March 2012, 08:08 »
thanks...I will check the forcepacking one. That should definetly have the highest priority.

If nothing is specified in batch-mode's rebuilder tab, then the original settings from each profile is used.

2417
clrmame Discussion / Re: SoftwareLists where detected??
« on: 15 March 2012, 08:06 »
Don't import them.

For MAME they don't really make sense since MAME simply double neogeo/stv/etc roms for its software lists.
For MESS it makes sense.

As the prompt says...if you're not familiar with softwarelists, don't import them :)

2418
clrmame Discussion / Re: Crashes in 4.04
« on: 14 March 2012, 19:41 »
you might want to give this:

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

a try...please let me know if it still crashes for you....

2419
clrmame Discussion / Re: Crashes in 4.04
« on: 14 March 2012, 09:16 »
Well...yes...not an easy task I know.......since not only the files in the rompath might be affected but also files in the backup folder.

Usually you should be able to see the setname in the progress window when the crash happens (I hope the progress window is still visible when the system error prompt appears)...that could be a start....you can then e.g. limit the files to that set (and its parents) by entering the name in scanner->setinformation->select sets and hitting apply...the next scan will then only work on that file...

You said it happens during fixing....maybe you can try to disable all fix options...then you can scan and see which files have issue listed....and try to recreate that (limited to the sets in question) in a clean new scenario...
This would also help to check which fix operation might be the reason (name, case, unneeded, etc..)..

as mentioned, a start would be to send me your cmpro.ini file and the .cmp file from your cmpro settings folder...


2420
clrmame Discussion / Re: Crashes in 4.04
« on: 14 March 2012, 07:37 »
any update on that? or anyone else who got that?

Pages: 1 ... 116 117 118 119 120 [121] 122 123 124 125 126 ... 165

Page created in 0.135 seconds with 19 queries.