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 ... 149 150 151 152 153 [154] 155 156 157 158 159 ... 165
3061
clrmame Discussion / Re: Prob with Modifying url lists
« on: 12 January 2010, 15:13 »
Well, your request can be done if I change the url functionality a bit to support the common variables (%r, %s etc...) so you don't have a pre/post string anymore but a simple url with placeholders....then you'd be able to not specify a setname...

I will think about it.

3062
clrmame Discussion / Re: Prob with Modifying url lists
« on: 12 January 2010, 10:02 »
you can't get http://www.xxx.com/10yard.pdf

since it's lacking the setname. Coming from your dat, the setname is 'arcade' <game name="arcade">
The setname is always pasted after the prestring and before the poststring.

I also wonder why it creates http://www.xxx.com/arcade./10yard.pdf for you.
In detail I wonder where the "." after 'arcade' comes from if you used xxx;http://www.xxx.com/;/%R
There is no "." in there (unless you used a new dat where the setname is "arcade."

3063
clrmame Discussion / Re: Prob with Modifying url lists
« on: 12 January 2010, 09:41 »
actually for your example xxx;http://www.xxx.com/;/%R should do the job...(note the missing .)

It would open: http://www.xxx.com/arcade/005.pdf in case you right-clicked the rom-issue 005.pdf line in the set-issue line of 'arcade'.

xxx is the site alias
http://www.xxx.com/ is the prestring
'arcade' is the setname
/%R is the poststring where %R gets replaced with the rom name...

so prestring + setname + poststring results in: http://www.xxx.com/arcade/005.pdf

Don't forget to restart clrmamepro after modifying the urls ini file(s).

3064
clrmame Discussion / Re: Prob with Modifying url lists
« on: 11 January 2010, 19:11 »
Well, first of all, be sure what a setname and what a romname is. roms are inside sets. Like pacman(.zip) is a set with let's say bla1.bin and bla2.bin romfiles. So what do you want to open at http://www.xxxx.com then? pacman or bla1/bla2.bin?

clrmame builds the final URL for the site as follows:

prestring + setname + poststring

so 'xxx; http://www.xxx.com/%R;' matches:
xxx = site alias for menu
http://www.xxx.com/%R = pre string
and an empty poststring
the setname is the selected by the clicked entry

So yes, you will end up with http://www.xxxxx.com/bla1.binpacman for the upper example if you clicked on the rom (not the set).

If you want to access 'pacman' you need to use:
xxxx;http://www.xxxxx.com/;

If you want to access 'pacman.zip' you need to use:
xxxx;http://www.xxxxx.com/;.zip

If you want to access the selected rom in the set and assuming the set is not zipped you need to use:
xxxx;http://www.xxxxx.com/;./%R

Note, the setname is always pasted after the prestring and before the poststring.

3065
clrmame Discussion / Re: Help!
« on: 10 January 2010, 20:14 »
Well, "missing but fixable" can be fixed by turning on 'fix missing'.

However you don't need these chds since they are identical to the chd in their parent sets. And there, they already exist (since cmpro reports them already as fixable). So your output is a bit weird unless you used "not-merged sets".

So, please check the following (actually these are default settings...I doubt you changed them):

Profiler->Options->Parse Disk Merge Tags should be enabled (this is needed to allow the merging of disk images in case of they are have differently names defined)
Profiler->Options->Don't create dummy clones should be disabled

Your prefered merge mode is fully merged as you already told me, so that should be fine.

Then please do a "new scan" to recheck if these messages reappear.

...and of course I assume you're using a MAME binary to get the database data from and no 3rd party dat file...

3066
clrmame Discussion / Re: Help!
« on: 10 January 2010, 09:27 »
>One Zip file, containing a dump of the ROMs on the cabinet circuit boards. One CHD file per disk in the cabinet, so maybe multiple CHDs to cover hard disk and laser disk, tops. All files uniquely named to easily identify them, all in one directory. What needs more than this?

well, you haven't read carefully. That's exactly how MAME stores files.

"all in one directory" - that's your rompath (ok, usually people use more than one since they want to group sets
"one zipfile containing a dump of the ROMs" - correct, that's the 'set'.
"CHDs..." - there you got the choice how to store them, either 'your' way in a rompath root or in a set-subfolder (where the roms stay in their zipfile)
(Like d:\mame\roms\area51\area51.chd and d:\mame\roms\area51.zip (for the roms).

MAME supports zipped and unzipped sets, in case of an unzipped set, you quickly see the general storing method: rompath\setname\file 1 ... file n.


But of course, MAME also supports merging of sets....where you merge parent/clone sets in one or split them up.......but that's a different story.

3067
clrmame Discussion / Re: Help!
« on: 09 January 2010, 20:59 »
The official way of storing chds was always rompath\setname\chdfilename. Besides of that, MAME's official storing method for any file was always rompath\setname\file 1... file n....for decompressed sets which simply becomes rompath\setname.zip for compressed sets (file 1...file n is then inside the archive).

Back in the past due to a MAME bug it was possible to store them in a rompath root.
After the big CHD update in MAME .130 (oh yes, all chds need to be updated via chdman), Devs decided to re-allow the rompath at root level storage (which is still weird since you won't see to which set it belongs...since usually chdfilenames don't match a setname anymore but are chosen by the original hd/cd/whatever device).

If you want to use chds on rompath root, you need to tell cmpro so. Scanner Advanced->Allow CHDS in rompath root.

A set is a collection of roms and/or samples and/or chds. There are CHD-only sets, there are rom only sets and other combinations. Easiest is to see a set as the archive (.zip) which holds the single roms for example. A set + name check checks the name of the zip while a rom + name check checks the romfiles inside the archive.

>Why does Fishermans Bait want to rename 889ua.chd to *two* others - 889ja.chd *and* 889aa.chd?

Because the name check is set based and depending on the set it tries to find a best fitting name. And depending on your disk tag merge settings it decides which to use. Another reason to keep chds in the offical subfolder way.


So to sum it up: clrmamepro handles chds absolutely correctly in both storing modes, but you need to tell cmpro which one to use...(and the majority of users prefers the chd in subfolder mode).

3068
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 07 January 2010, 20:36 »
ah forget it.....I found the issue :O)

3069
clrmame Discussion / Re: Problem on CRC of darkhors
« on: 07 January 2010, 08:37 »
Not really. While it's rather easy today to fake a rom to match the size and crc32, it's nearly impossible to fake it so sha1 and crc32 and size matches.....or let's say, it's not worth the trouble to try so.

3070
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 05 January 2010, 16:43 »
yeah send me your files....the dat is definetly not the case for this.

3071
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 05 January 2010, 13:03 »
cmpro 3.132a does not report a comment in your sent rar....and actually it does not have one.

So...you're sure you scanned *that* rar with 3.132a? Got another file?

3072
clrmame Discussion / Re: Problem on CRC of darkhors
« on: 04 January 2010, 22:26 »
just for your information: mame is right, clrmamepro is right, the file exists, you need to find it. MAME .136 added a lot of eeproms but they do all exist out there.

3073
Weird....since this is definetly not needed here. As I mentioned, I run Win7 Ultimate 64bit myself and have no issues with rebuilding or removing files.

Having random issues when rebuilding files to an exernal drive usually means there are timing / hardware issues maybe related to Win7 drivers for your external harddrive.

You also mentioned that not all to-be-remove files are affected. Maybe the zipstructures are bad for these ones which can be checked by enabling the strict but slow zip scanner (in cmpro's compressor settings). But again...something random...no related to UAC at all.

3074
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 04 January 2010, 19:14 »
Just back from holiday...will check your file asap...

3075
Well, 64bit Windows 7 here myself. Being an admin user. No problems. Not needed to run it 'as administrator' or anything else.
I keep it in "d:\cmpro" and scan MAME files in "h:\MAME\ROMS".

I will check your settings later (just back from holiday...)

3076
clrmame Discussion / Re: Problem on CRC of darkhors
« on: 04 January 2010, 19:11 »

i cant find one with the correct crc

is it a problem of the dat? of clrmame? mine?



Well, it's your problem ;) MAME's database gives the hashvalues, so assume they are correct (however there were rare cases in the past where crc32 values were wrong but fixed in a later version).

So, you need to find the correct file.

Sorry for the late reply by the way...end of year holiday.

3077
clrmame Discussion / Re: datfile problem - double rom?
« on: 04 January 2010, 19:08 »
So what is the appropriate thing to do here? Should I click yes to rename it or no to remove from the set definition? Does anybody know why this would happen?

Sorry for the late answer....end of year holiday....
Well, yes, click yes :)

3078
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 27 December 2009, 15:39 »
works fine here with 3.132a. Mail me a rar file where it does not work for your.

3079
clrmame Discussion / clrmamepro 3.132a released
« on: 25 December 2009, 20:34 »
3.132a

fixed: missing bytes column falsely appears in www profiler
fixed: archive comments warning is broken for rar files

Merry XMas and a Happy New Year

3080
clrmame Discussion / Re: clrmamepro 3.132 released
« on: 25 December 2009, 09:23 »
hmm..yeah...bug...will fix this

Pages: 1 ... 149 150 151 152 153 [154] 155 156 157 158 159 ... 165

Page created in 0.17 seconds with 19 queries.

anything
anything