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 ... 105 106 107 108 109 [110] 111 112 113 114 115 ... 165
2181
commandline will be always limited by its length. so it may work for a couple of files but not for lets say 30 or more...unless there is an option for listfiles where a new file holds the filenames. I will check this

2182
ok...first little improvement(?)...
remove operation for external packers (rar/7z) test if the file in question really exists in the archive....

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

let me know if it really speedup things for you....

2183
should be easy to add a test if the file is actually in the archive (however it needs to read the table of contents of the archive again)...and I guess I can
a) filter out real existing files
b) (since the "remove" operation can handle multiple files at ones) maybe use @filelists options...

I will play around with it....

2184
clrmame Discussion / Re: 7z rebuild with @ in filename
« on: 21 January 2013, 20:57 »
ok I've checked the code and I can't repeat an issue with @ at filename start...so an added .\ is obsolete in my opinion... all operations (add, delete, rename) check (in case of 7z/7Z extension) if filenames start with an @....and in that case it automatically adds .\

So Zandro, can you send me a scenario (cmpro.ini, *.dat, *.cmp and the rom files in question) where I can repeat your issue?

2185
clrmame Discussion / Re: 7z rebuild with @ in filename
« on: 21 January 2013, 19:44 »
hmm...actually it should already handle @ at the beginning automatically....I've added an internal .\ fix for filenames starting with @ a long time ago...wonder why it did not work for the mentioned files...need to double check this.
And yes, currently it tries to remove the 'new_name' files first in case of a rename operation.....guess I can change this easily to do this only if the new_name does exist.

2186
clrmame Discussion / Re: 7z rebuild with @ in filename
« on: 21 January 2013, 15:36 »
I need to check when and where this is called. Usually cmpro moves a single file into a temporary folder, changes to that folder and calls the add or delete operation. That's why .\ doesn't harm in front of the filename since it is already "local directory".
If I remember correctly there is one case where cmpro adds multiple files...but even then it most likely only does a .\* then....

2187
ok I will have a look

2188
which brings me to my fav topic...Why the hell do people use old MAME versions at all.....

2189
The enabled option should not have a sideeffect for MAME.
There might be other dats (without baddump attributes) which accidently have inverted crcs somewhere...but not for the purpose of flagging the file as bad...purely accidently...then the rebuilder might create a wrong file in a wrong set.....but the chance is pretty small...

2190
You can look for rom status attribute values "baddump" (not "nodump"). If they appear, the dat does not use the inverted crc32 method anymore

But of course you can simply keep the option enabled...it does not really harm.


2191
exactly what I thought....your dat does not have any <disk ... elements, i.e. it does not list any chds....so of course cmpro complains about "set archive and set folder exist in same rompath" and of course any of your chd files become unneeded...

No idea where you got that datfile from...-as mentioned before- you should use a direct import from an official MAME binary (Profiler->Create...) instead using a 3rd party dat.

2192
clrmame Discussion / Re: 7z rebuild with @ in filename
« on: 17 January 2013, 13:38 »
7-Zip [64] 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18
Usage: 7z <command> [<switches>...] <archive_name> [<file_names>...] [<@listfiles...>]

The @ is used to use a listfile, so I guess 7zip gets confused...

You might try to specify .\%2 as clrmame 7z commandline parameter instead of %2...so maybe you can fool 7z by specifying the "current folder" (cmpro will add the file %2 from a current folder internally...)

..or maybe quotes around %2

2193
Well, you got folders named after a set and the set archived (as zip) in your rompath. This is obsolete.
Only exception are sets with chds (which seems to be the case), where you need to store the chd in a rompath subfolder named after the set. But clrmame handles this automatically and does not show such messages in this case.

Be sure you got all systems, sets/bios/devices and chd types enabled and get your data from an official MAME binary and do a fresh "new scan".
If that does not help, you can send me your cmpro.ini file plus the datfiles\*.dat and settings\*.cmp file for your used profile.

it seems that you scan a collection with chds with a datfile which does not include chds. thats why should use an official mame as profile data source

2194
maybe you can fool torrent7z by specifying .\%2 in the cmpro commandline option....

2195
Your assumption is wrong.

You cannot simply replace t7z with 7z....here is what your sent in details will create:

t7z.exe a -y -r -ms=off -mx9 E:\temp\dest\hustler.7z b

torrent7z_0.9.1beta/Thu Jul 23 03:08:33 2009
using 7-Zip (A) 4.65  Copyright (c) 1999-2009 Igor Pavlov  2009-02-03

warning: unsupported switch ignored: -r
warning: unsupported switch ignored: -ms=off
warning: unsupported switch ignored: -mx9
error: invalid argument: b

7z does not have a problem with this....

2196
Yes...that's what he's doing...
and again...torrentzip is NOT supported


2197
normally such a zip to 7z conversion is done with a commandline script....most likely faster than anything else....
..and actually 7z creates memory holes when used in MAME...haven't checked if that was fixed by now....

..as I said, the rebuilder prompt yes, that's something which should not stay....It should log the errors instead...but as I said...that's on my list already.

2198
I can rebuild a full mame set so quickly with zip and no-recompression. I wonder if I can even get a cup of coffee in between.
Besides of that...there is no need for a full rebuild anyway. Maybe if you're a starter who only got a mess on your hd...then you do it once. The rest is handled by the scanner and when a new MAME version comes out you add the few files with the rebuilder to your existing collection.

As you might already noticed: I don't really care that much about 7z (or even torrent7z)....such things don't have any priority. 7zip's SDK is let's say it polite: not the best...and currently there are no real good alternatives (well documented dlls (not COM based) or sdks) out there...I check the lib7zip project from time to time...but for current cmpro core, the external 7z exe will be used and I don't see a chance for a change soon.

2199
1) that's why the "remove parent/clone relationship" (for the sets in question) is the way if you want to still use fullmerged sets

2) Yes. There are a handful roms which aren't identical to standard MAME. In case you import them you most of them twice. Or simply don't import them and use the software lists in separate profiles. For neogeo you can then have 2 rompaths. 1st rompath is used for MAME while 1st  and 2nd are used when scanning the neogeo software list (where the 2nd only holds the software-list only ones).

2200
clrmame Discussion / Re: Understand batchrun options
« on: 14 January 2013, 09:13 »
you can still use the batcher to batch-scan/rebuild your profiles...but the rebuilder destination option should come from the profiles  themselves...

But I just got an idea....if your single profiles all use only 1 rompath, then you might simply use the batch options' "use 1st rompath" option for rebuilder destination...

Pages: 1 ... 105 106 107 108 109 [110] 111 112 113 114 115 ... 165

Page created in 0.199 seconds with 20 queries.

anything