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.

2221

clrmame Discussion / Re: Different folder for bios and software

« on: 03 January 2013, 08:55 »

If you already have them split up on your hd, you can try the auto-assign button (which tries a best match to assign them). Otherwise you need to double-click the single lines (2nd or 3rd column) to assign them manually.

2222

clrmame Discussion / Re: Different folder for bios and software

« on: 02 January 2013, 21:36 »

You can assing them in the "systems" dialog.

2223

clrmame Discussion / Re: I have a question on this.

« on: 30 December 2012, 16:16 »

there are no issues with the others either if you tell the profiler how to read them in correctly. but anyway a direct exe import is always the easier choice

2224

clrmame Discussion / Re: I have a question on this.

« on: 30 December 2012, 08:03 »

mess' xml is different from mame's elementwise. so of course you need other profiler parser settings than DATFILE when reading in the file.

2225

clrmame Discussion / Re: I have a question on this.

« on: 29 December 2012, 12:18 »

it only replaces the not existing checksum in the datfile with one from the parent/clones

2226

clrmame Discussion / Re: I have a question on this.

« on: 29 December 2012, 08:28 »

it does not harm if you select 'yes'.

2227

News & Communication / cmpro 4.09a released

« on: 10 December 2012, 20:27 »

4.09a

misc:  take over a set bad dump chd status flag for all parent/clone instances of that chd

2228

clrmame Discussion / cmpro 4.09a released

« on: 10 December 2012, 20:25 »

4.09a

misc:  take over a set bad dump chd status flag for all parent/clone instances of that chd

2229

News & Communication / cmpro 4.09 released

« on: 05 December 2012, 12:44 »

4.09

fixed: rename profiles (which are based on a xml dat) corrupts xml structure
fixed: fix missing doesn't look into parent set in rompaths in full merge mode it might oversee missing but fixable roms
misc:  changed size of compressor settings window

2230

clrmame Discussion / cmpro 4.09 released

« on: 04 December 2012, 19:19 »

4.09

fixed: rename profiles (which are based on a xml dat) corrupts xml structure
fixed: fix missing doesn't look into parent set in rompaths in full merge mode it might oversee missing but fixable roms
misc:  changed size of compressor settings window

2231

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 04 December 2012, 08:01 »

well, actually it's your own decision

I did not enable it by default because the "merge" tags in MAME were too often too wrong (pointing to wrong roms, just missing or holding bad checksums) in the past. cmpro can detect such errors during datfile parsing and fixes them, but still....I did enable the chd merge tags though...
For romsets, I actually also like to have the correct file names which otherwise get lost due to merging...but again, it's your personal taste....

I still wonder why people always come up with the set size argument. Comeon...HD space is cheap and if you're collecting MAME sets, you should not care about a minimum space gain by using the merge tags, full merging in general or 7z...

Last but not least....people should use this forum if they have questions/problems or may found a bug...it doesn't help when endless discussions are kept on a different forum. Normally I can fix issues within a day or two...when I know about them...when I got a scenario where I can easily repeat the problem...

Thanks for any support!

2232

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 04 December 2012, 06:02 »

to sum it up, case closed, cmpro is ok now.

2233

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 04 December 2012, 00:55 »

look at the size. Your file is 131072 and it should be 131073....
how should cmpro guess the missing byte?
if "run checksum analysis" (and "fix if possible") is enabled (chd + checksum options window), it tries to pad with 00, 01 and 0xff if I remember correctly...and checks the checksum after that....but generally cmpro can't guess missing bytes....

131073 is however a very odd (ha ha ha) file size...maybe a bug in the dat.

but anyway...give the checksum analysis a try...

2234

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 03 December 2012, 21:37 »

so I did a little bit of research...

First of all, there is no file loss at all...as oxyandy said already, the files are in the archive but are listed as missing in the tree view...which is correct for this check, since the files do not exist with that name (rebuilder will of course create them since they are dupes and do exist with a different name).

The reason why you're stuck is that the fix missing (or test for missing-but-fixable) routine did not look into the parent set in case of full merged sets. It did however look into the parent set in addpaths or backup folder but not directly in the same set in the rompath...

You might want to try this build which includes this lookup (and a little goodie for oxyandy)

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

2235

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 03 December 2012, 10:36 »

If you're coming from a set where you had "parse merge tags" enabled (and so you did not need them) and you're now scanning them with a disabled "parse merge tags", they are of course missing...because this mode is strict...different rom names result in different rom files.

However, fix-missing (or rebuilder) should find them and create them automatically for you... If that's the scenario I don't see anything wrong (or even something like "cmpro ate my roms"...

but I will check your scenario tonight...

2236

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 03 December 2012, 10:04 »

well, I'm currently at work so I can't check it for now...
regarding "parse rom merge options"...It is disabled because:

- the merge tags in the (MAME) dats were too often too wrong in the past (pointing to wrong roms, holding wrong checksum information and so on). Actually during cleaning up the datfile I've added verification tests in the past to fix such bad merge tags automatically....

- I'm more a fan of having the correct number of files in the sets with the correct naming....even when fully merging the sets you can differ the clone names then..(so you got multiple files with the same checksum and different names). In days of multi terabyte hds and users who do collect mame roms, space shouldn't be an argument here...I still wonder why people switch to 7z because of this...


what I wonder about:

"Without  "Parge ROM Merge Tags"  ticked CMP will report 5 missing ROMs,
on a simulated update from 0.147 to 0.147u3.. (my mini.dats)
With a Merged Set, either ZIP or 7z.. (When in fact, the files are in the archive)"

Where does it report them? In the stats? Well...the only correct values are the scan tree view. Don't care about the stats at the end...I never claimed they are correct...since they rely on so many factors. If nothing is in the treeview you're done.

2237

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 03 December 2012, 08:40 »

So since people tell me that there is a post on pleasure dome form (which I cannot access) on this...

Can anyone clearly say there is or there is not a problem, and if there is, can send me a scenario for it?

2238

clrmame Discussion / Re: HOW TO: exclude romsets from scan (e.g. gambling, mechanical, CHDs, etc)

« on: 02 December 2012, 21:33 »

nice....

just a comment, the filter settings separated by semicolon in set information form a boolean OR, not an AND, so using the "logical not" checkbox forms a not(a) or not(b) or not(c)....which may not what you expect....so for such cases the invert button is usually better....

2239

clrmame Discussion / Re: clrmame is losing or deleting sets

« on: 02 December 2012, 21:30 »

long thread...and actually I just (22:20) came back from a weekend trip....and after a long drive I'm too tired to read the full thread....
actually I will check oxyandy's "Hi Roman,Here is two mini dats and an archive..." setup in the next days to see what's going on...

Before checking, of course people have to be aware that:
- deleted files from 7z archives are moved to backup but in a zip archive
- there are some cases (depends on the parent/clone changes from one dat to another and the order of the sets), where you need to rebuild files from backup to get them back. This is intended.
- there are some cases where a scan shows missing sets and you simply have to do a fastscan to get the clear result.
- if you don't care about dupes you need to use profiler's option to parse rom merge tags
- if you do care about fake clones (fully identical sets), there's also a setting there...

It's absolutely needed to send me scenario where I can rebuild issues. So a minimum combination of cmpro (with settings, cmpro.ini, datfile) and a minimum set of roms. I want to press a button and see the problem.

2240

clrmame Discussion / Re: Using "Rename Profile" causes XML dat corruption

« on: 30 November 2012, 20:27 »

Your dat does not have an utf8-bom....
(use e.g. notepad++ to save it as utf8 (with bom) and it shows up fine in the profiler)

It's an old style dat (not xml), so it needs a bom....only XML files are taken as utf8 by default...