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 ... 119 120 121 122 123 [124] 125 126 127 128 129 ... 165
2461
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 27 February 2012, 23:22 »
???

Can you explain again when it is crashing for you. When you drag'n drop files?
Again, this is used daily by a lot of people and noone reported an issue with it.
Tell me what you're doing and when and where it crashes.

2462
well, I tested it against official 145 and found out that cmpro get fooled a bit by the identical set names.
I tweaked the detection a bit, so it should be fixed for next version.

By the way, "Set exists in various rompaths" can still happen. For example the stv bios is not part of the softwarelist stv...so if you only copied the folders, you created a not needed dupe.

2463
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 27 February 2012, 23:11 »
you should enable "ask before fixing" so it will prompt you the set before fixing it....and maybe *that* set causes the issue.

2464
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 27 February 2012, 22:55 »
I can't repeat your issue and it seems that noone else can...

There is a known crash when cmpro adds rompaths for you for sysdefpaths...maybe you ran into that one..
you can try this build, it fixes *that* issue:
http://mamedev.emulab.it/clrmamepro/binaries/cmpro20120227.zip

2465
clrmame Discussion / Re: new chd
« on: 27 February 2012, 21:11 »
even u3 doesn't seem to hold the updated sha1 values for various chds....see mameworld news msg board discussions

2466
hmm....I can't get it to delete any folder....and actually it should not remove any folder (even if empty) which is named after the set (and the set got chds).

Maybe you did not have all sets/systems enabled (see line right beside scanner tree window's set information button...does it list something like "not all systems/sets enabled"?)

2467
clrmame Discussion / Re: 4.03a & Dir2Dat bug
« on: 27 February 2012, 19:53 »
fixed for next version

2468
I will look at this this week. can you provide some more info ( maybe stepbystep instructions or some screenshots of the setup and messages )

2469
clrmame Discussion / Re: 4.03a & Dir2Dat bug
« on: 25 February 2012, 20:30 »
I will check dir2dat next week. regarding chd v5 you should wait till mamedev fixed it.

2470
ok more next week since Im miles away from any sourcecode

2471
clrmame Discussion / Re: new chd
« on: 25 February 2012, 20:25 »
you should have wait with the conversion since mame's u1 chdman got critical bugs as you can read in the mame msgboard

2472
as I said I will into it next week

2473
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 24 February 2012, 10:32 »
I will do further checking next week.

2474
The only thing which changed was the dupe check (since multisoftware list support allows identically named sets...). That's why I asked to scan without the fix options enabled to see what issue cmpro reports.

Of course it should delete all and not only some obsolete folders.

Next week I got more time to check this in detail

2475
clrmame Discussion / Re: clrmamepro 4.03a released
« on: 22 February 2012, 15:25 »
you should not convert yet since there are known issues with v5 chds...see mame forum...better wait

2476
clrmame Discussion / Re: clrmamepro 4.03a released
« on: 22 February 2012, 14:51 »
First of all, check the merge mode :) Maybe you just rebuilt a full merged set while you want split merged.

Or...maybe you really only have the parent (assuming indytemp is the parent) files....then of course the rebuilder only rebuilds these...

Then actually check what you/MAME is missing. You can do a crc32 compare with mame's -listxml output for example and see what is wrong with your files.

On a sidenote you might want to check system and set-information if you got all systems and all sets enabled....but I think you got....

2477
clrmame Discussion / Re: clrmamepro 4.03a released
« on: 22 February 2012, 14:16 »
Sorry but I don't keep old version binaries and you should definetly not use 3.x.
As mentioned, you should get rid of the indytempc issue by manually removing all instances of this set and readding them with the rebuilder and not fix-missing and a clean new scan afterwards.

2478
good remark...

Do you actually *HAVE* files in the folders?

Of course empty folders are removed...and if you have something different in there as a chd, cmpro will show you a set exists in more than one place message...that's why I asked to turn off the fix options for 1 scan to see what cmpro actually complains about.

2479
sounds wicked :)
I guess I can only look at this more deeply next week...

Try to disable the fix options. Then the scan tree output should list something....maybe something more than just "unneeded".

2480
clrmame Discussion / Re: clrmamepro 4.03a issue
« on: 22 February 2012, 08:14 »
it is definetly NOT caused by chdman since chdman is only called when you got the scanner advanced option enabled to do an unpack and calculation of sha1/md5 files....looking at your screenshot I see that it crashes during the uneeded checks.

You can send me your cmpro.ini file and the belonging .cmp file from cmpro's settings folder for your used profile.

Pages: 1 ... 119 120 121 122 123 [124] 125 126 127 128 129 ... 165

Page created in 0.179 seconds with 19 queries.

anything