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 ... 102 103 104 105 106 [107] 108 109 110 111 112 ... 165
2121
clrmame Discussion / Re: [SOLVED] strange 7z warnings
« on: 25 March 2013, 07:32 »
Time to switch to extended path length with a 32k :)
But hell...I guess I need to touch too many places to support it...but never say never....however too busy with real life at the moment

2122
clrmame Discussion / Re: CrlMAMEPro not responding
« on: 24 March 2013, 08:23 »
exactly...official XP SP3 is damn old by now already....guess it even comes with auto update.....(not to even mention the MSDN releases or a simple download)

2123
clrmame Discussion / Re: strange 7z warnings
« on: 22 March 2013, 19:26 »
well, as long as I don't have one of the specific 7z files I can't really help....
the SZ_ERROR_FAIL message comes when a 7z SDK returns an error code 11....great, ain't it....could be everything....maybe a locked file which cannot be opened/closed...no idea...as I said...without having the 7z itself, I can't really help...

....did I mention that 7z is and stays a pita....still wonder why people like it....

2124
clrmame Discussion / Re: CrlMAMEPro not responding
« on: 22 March 2013, 07:56 »
As I said, cmpro can be very busy...e.g. when un7zipping huge archives from archives etc....or scanning thousands of decompressed files and calculating sha1 values.....normally you simply have to wait or disable options which might be some speed eaters...(usually md5/sha1 related options or scanner->advanced->deeper check for fixable file (or whatever it is called))

2126
as always, send some files :) dat/roms/settings/ini

2127
clrmame Discussion / Re: CrlMAMEPro not responding
« on: 08 March 2013, 10:46 »
It might be busy with full cpu working threads, simply hit it several times.....

2128
You turn off all set specific check options (set = collection of roms and/or samples and/or chds.....so you turn off all checks which work on the folder/archive itself. The rom checks work on the files within the folder/archive). When turned off you will e.g. not notice if the set was renamed in a future dat (I admit this is only very rarely happening for artwork based dats, but still it already happened with them).

So turning this off is in my opinion not a good workaround for a wrong storing method.

Why is there an option, well, because cmpro got an option for everything :) From 1997 onwards it had the ability to turn on/off any possible check/fix since some advanced users required this. The normal use case is to use the default settings (which includes enabled sets/roms/samples/chds checks).

The storing method originally comes from MAME. Well, artwork dats are - compared to MAME sets - different, since they put all files into 1 set. But still the 2 storing methods should be followed to audit them. Keep in mind that everything found in a rompath which does not belong to a set is unneeded, that's why you should separate your profile's rompaths.

If you keep them decompressed or compressed is fully a personal taste.

Last but not least you need to keep in mind that when it comes to filenames and paths generation (e.g. when fixing or reading files), cmpro will generate rompath\setname\ or rompath\setname.zip(.rar/.7z). So if you don't follow the storing methods you will end in chaos sooner or later...

2129
clrmame Discussion / Re: Upgrading MAME sets
« on: 25 February 2013, 15:02 »
Cmpro can be used for up and downgrading of any kind....it simply tells you what you're missing (by comparing your files on your system against the ones specified in the loaded dat) so you can directly jump from .146 to .148u1 or from 146 to .140 if you like...there is no need to do it version by version.

In 99% of all upgrade cases, files moved to backup are bad dumps which were replaced in the new mame versions.
There are some exceptions when sets were in MAME and have been taken out for whatever reason, then such files may become nessary in the future again.

Downgrading is of course a different case...then the files in backup are valid files for the new version which are not known to the old one...

2130
Do NOT disable sets.

You need to change your storing method. Again, you need to use the storing methods:

rompath\setname\file 1.... file n (for decompressed sets)
rompath\setname.zip (.rar/.7z) (for compressed sets, where the archive then holds file 1 ... file n)

Yes, you may need to add another folder level for your files then, e.g. I:\Mame\ArtFiles\Cabinets
Depending on other profiles you may even think of another level or specify exclude folders (settings, path selector).

There won't be support for any other storing method.

By the way, if you're using decompressed sets you should disable scanner/advanced/deeper check for fixable missing files....this is usually a slow-down option when handling decompressed sets.

2131
There are 2 supported storing methods:

rompath\setname\file 1.... file n (for decompressed sets)
rompath\setname.zip (.rar/.7z) (for compressed sets, where the archive then holds file 1 ... file n)

Looking at the datfile you see that the setname is <game name="cabinets"> "cabinets".

"My cabinets files are located in I:\Mame\Cabinets" ....so your rompath needs to be setup to "I:\Mame" if you follow the upper rule.

Now it sounds a bit like I:\MAME is used for other stuff (which the cmpro scanner most likely will mark as unneeded), you may think about having another subpath where you put your cabinets...




2132
clrmame Discussion / Re: 4.010 not recognising files
« on: 23 February 2013, 18:47 »
second test...with your setup....et voila....no rebuilt files....but the answer is easy:

No set at all is enabled in Scanner->setinformation. (You can also see this in the window title line saying Sony - PlayStation 2 201330217 17-34-34 | 0/1 Sets, i.e. 0 of 1 set is enabled...in other words NONE.

And that's because you got a "Select Sets" entry:
*(Japan)*;*(Korea)*;*(China)*;*(Asia)*;

...the one file you have in the dat is "(Europe)"..... so it's not enabled..


So...you should check which sets you got enabled and which not....(Scanner->Setinformation)

2133
clrmame Discussion / Re: 4.010 not recognising files
« on: 23 February 2013, 18:42 »
well...ok...startet cmpro, added your dat in the profiler, setup a rebuilder destination and drag'n dropped the Chess Challenger (Europe) (En,Fr,De,Es,It).bin file in it and it gets successfully rebuilt in that destination...so no issue with a plain cmpro install...

....will check you cmpro.ini and .cmp file later...but it seems that either your system or setup causes the problem.....

2134
clrmame Discussion / Re: 4.010 not recognising files
« on: 23 February 2013, 18:40 »
thanks...I've downloaded them...

2135
clrmame Discussion / Re: 4.010 not recognising files
« on: 23 February 2013, 17:37 »
dont forget the dat if they are different

2136
clrmame Discussion / Re: 4.010 not recognising files
« on: 23 February 2013, 11:23 »
any chance that I can download the files somewhere?

these and maybe your cmpro.ini and the belonging .cmp file from the cmpro settings folder....

2137
clrmame Discussion / Re: Little glitch with a dark theme
« on: 20 February 2013, 15:57 »
I wonder why it shows a white background for the progress bar since I simply print out the text without setting any (background) color there....I may look into this...but don't really count on anything soon....

Using skins and themes is so 1990..... :)

2138
clrmame Discussion / Re: clrmamepro 4.010 released
« on: 19 February 2013, 06:19 »
thank you!!!

2139
News & Communication / clrmamepro 4.010 released
« on: 14 February 2013, 22:31 »
4.010

fixed: 7z working with filenames starting with an "@" fails if the filename also contains a space
fixed: header support: possible infinite loop when file is too short
fixed: header support: wrong hash calculation (in file and memfile) when file is too short
fixed: detection of prefered archive type falsely failed for unpacked sets causing creation of zips
misc: unneeded check also detects obsolete chd folders
misc: explicity test folder for no entries to avoid possible deletion of NTFS junctions
misc: check if file really exist in 7z/rar archives before trying to remove them. Gives a small speed gain

2140
clrmame Discussion / clrmamepro 4.010 released
« on: 14 February 2013, 20:22 »
4.010

fixed: 7z working with filenames starting with an "@" fails if the filename also contains a space
fixed: header support: possible infinite loop when file is too short
fixed: header support: wrong hash calculation (in file and memfile) when file is too short
fixed: detection of prefered archive type falsely failed for unpacked sets causing creation of zips
misc: unneeded check also detects obsolete chd folders
misc: explicity test folder for no entries to avoid possible deletion of NTFS junctions
misc: check if file really exist in 7z/rar archives before trying to remove them. Gives a small speed gain

Pages: 1 ... 102 103 104 105 106 [107] 108 109 110 111 112 ... 165

Page created in 0.284 seconds with 20 queries.

anything