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 ... 146 147 148 149 150 [151] 152 153 154 155 156 ... 165
3001
clrmame Discussion / Re: chds wrong name
« on: 19 April 2010, 19:31 »
ok...that was a very tricky one.....related to fullmerged sets where clones share identical chds which are not parent chds....blalblalblablablab....it should be fixed for the next version.

3002
clrmame Discussion / Re: Clrmamepro version.ini
« on: 19 April 2010, 19:30 »
ok..should work from next version onwards...

3003
clrmame Discussion / Re: chds wrong name
« on: 18 April 2010, 20:51 »
Thanks for the files....I will do some tests the next days.

As mentioned before, the scanresults tree is correct...nothing is shown, your sets are correct. Stats were always a pain in the a** and showing 4 wrong names there is simply wrong...so ignore it for now ;)

3004
clrmame Discussion / Re: Clrmamepro version.ini
« on: 18 April 2010, 20:22 »
I had a look at the code...and I guess it's rather easy to add....

3005
clrmame Discussion / Re: Clrmamepro version.ini
« on: 18 April 2010, 19:47 »
Where is the sense in keeping both versions? Either you have a 64bit system, then use the 64bit version, otherwise use the 32 one. No big need to have a different version file......I may have a look at the code if it's just a #ifdef thing ...but don't count on it.

If you really want both, you can downgrade the version.ini version number after updating one to update the other.

3006
clrmame Discussion / Re: Clrmamepro version.ini
« on: 18 April 2010, 19:34 »
Version.ini is identical for both versions.
Actually all files besides of the unrar dll and the cmpro executable are identical and can be shared.

3007
I've updated the wishlist a bit ;)
Paypal is also possible....or something for iTunes.....but of course cmpro is generally free.

Regarding chds: yep, chds belong to rompath\setname\chdfile.chd and compressed sets belong to rompath\setname.zip



3008
As mentioned before, the rebuilder does not rebuild chds.

If you decide to keep chds in the 'official' way, you keep them in rompath subfolders named after the set (e.g. d:\mame\roms\area51\area51.chd...ok a simple example because chd and setname are identically named...which is not always the case. CHDs never go into zip files. They are zlib compressed containers on their own, so another compression causes nothing but heavy memory usage when decompressing them.

You have to manually move the chds...but...actually you can let cmpro do some work for you. Move the chd files in your new rompath root folder and scan (with set+rom+chd+name+unneeded check/fix enabled).
Cmpro detects wrong placed chds and creates the needed subfolders for you and moves it (with the correct name) to it.

3009
clrmame Discussion / Re: chds wrong name
« on: 18 April 2010, 10:05 »
I do understand your issue. Why it lists 0/4 in the stats window while the scantree shows nothing is a bug...and I try to find out why. The scantree window is correct, the stats aren't.
That's why I asked you to send me the cmpro.ini file plus the belonging .cmp file from your profile in cmpro's settings folder. Thanks for the screenshot, I try to repeat this here...but the files would be better.


Edit: Can you make a screenshot of the Profiler->Options screen?

...and why do you initially think it's evilngt, p911, soulclb2 and tekken4 ????

3010
clrmame Discussion / Re: chds wrong name
« on: 17 April 2010, 06:04 »
I mean, what does the scan results tree window show? Not the stats window. Does it list anything?

And let me know your settings like merge mode, etc. Easiest would be to send me screenshots or even better: cmpro.ini and the to-your-used-profile-belonging-*.cmp file from cmpro's settings folder.

3011
clrmame Discussion / Re: clrmamepro 3.133 released
« on: 16 April 2010, 10:14 »
3.133a released...and you can remove your file mentioned in the posting above....

3012
1) well, a *complete* rebuild is usually only necessary if you got really messy folders otherwise scanning the rompaths is usually a better way to go. The rebuilder does not rebuild chd files (yet), it only rebuilds roms.
If your goal is to create one rompath with all romsets and chds in it...ok, fine...a rebuild operation may be a good start. The rebuilder does not care if files are archived (zip, rar, 7z) or are decompressed...if it finds something valid (in terms of hash matches) it creates all instances of the match in the destination folder (using the correct name then).
So you can do this....and move the chds afterwards manually.
Regarding CHDs, you need to decide how to store them. The 'semi-official' way (i.e. a rompath subfolder named after the set, similar to decompressed sets) or the 'semi-not-so-official' way, keeping them at a rompath root. For the latter option, you need to enable the support in cmpro's scanner advance option.

2) sure it is, since your maintenance is done by cmpro, you don't really have to care ;) There are some people who like to use 50+ rompaths (split by systems for example), but even there you got chds and roms in one and the same rompath. The only question is, which chd storing method you're prefering. Personally, I prefer the semi-official method.

3) Blue = "clone" (chd/rom), Black = "parent" (chd/rom). It simply indicates that the missing file is a clone chd...and actually if this is listed it means that you should recheck your settings...because...why does it list a missing clone chd? If the parent chd is missing too, it should hide the clone and if it only lists the clone it means, the identical parent was found...sounds a bit weird. What you should check is: Profiler->Options->Parse disk merge tags. That option should be enabled to avoid having obsolete chds.

4) There is no problem with the chds. Maybe you store them incorrectly (if kept in a rompath root, you need to enable Scanner->advanced->allow chds on rompath root) or as mentioned in 3), check the Profiler->Options->Parese disk merge tags option. (Enable it!). And of course don't use 3rd party dats, instead use a direct (official) MAME import for your profile.

3013
clrmame Discussion / clrmamepro 3.133a released
« on: 15 April 2010, 19:48 »
3.133a

fixed: crash at the end of a scan when not all sets are enabled

3014
clrmame Discussion / Re: clrmamepro 3.133 released
« on: 15 April 2010, 07:18 »
Well, the bug was pretty obvious (missing bracket in an boolean expression within a ternary operator which leads to an incorrect index) and is fixed now. New version...most likely next evening...

3015
clrmame Discussion / Re: chds wrong name
« on: 14 April 2010, 20:47 »
So....were they listed in your scan tree as wrong named (and not fixed)?

3016
clrmame Discussion / Re: clrmamepro 3.133 released
« on: 14 April 2010, 20:45 »
The crash only happens when you got some sets disabled (i.e. you did not enable all sets to scan...e.g. in Set Information window).


will be fixed for next release.

3017
clrmame Discussion / Re: clrmamepro 3.133 released
« on: 12 April 2010, 09:48 »
seems to be a crash with generating and optionally showing ths stats. will get fixed mid or end this week because im on holiday and replying via iphone only. dont be afraid it does not affect your scanning or your romsets.

3018
clrmame Discussion / Re: chds wrong name
« on: 10 April 2010, 15:24 »
ignore the stats. if nothing is listed in the treeview you're fine. will check the stats when Im back from holiday.
if they are listed though cmpro should be able to fix them unless the new name does not already exist. in that case you need to do some moving manually.

3019
clrmame Discussion / Re: clrmamepro 3.133 released
« on: 09 April 2010, 19:51 »
as mentioned on the mameworld news board i need more details. mail me cmpro.ini and the used settings file (.cmp) do the stats appear? maybe try to switch them off and try again. im on holiday and wont be able to check this before end of next week.

i dont experience this here so i need your config. try to minimize the problem and zip up all data and send it to me.


3020
clrmame Discussion / Re: scan status not saved (edit)
« on: 09 April 2010, 09:24 »
Not repeatable here.

Sounds a bit like cmpro wasn't able to save/load the fastscan information in the belonging cmpro fastscan folder. Be sure you:

1) got enough free diskspace
2) got full access rights for the cmpro folder and subfolders
3) did not install cmpro in an UAC controlled folder (Vista/Win7 only)

So you can monitor it a bit by looking in the fastscan folder (or its subfolders) to see if the belonging .fsc is written after a scan. That file holds information about which sets need a rescan *and* it also holds a checksum over the used datfile/mame import. So if the datfile/MAME import changed in the meantime for the used profile, you won't be able to do a SCAN without first doing a NEW SCAN.

Like: Scanning MAME .137u1, then updating to .137u2 -> You need to do a NEW_SCAN
Doing a NEW SCAN for MAME .137u1, loading a different profile (e.g. MESS), then loading MAME .137u1 again -> SCAN (not only NEW_SCAN) should be available.

Pages: 1 ... 146 147 148 149 150 [151] 152 153 154 155 156 ... 165

Page created in 0.18 seconds with 19 queries.

anything
anything