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 ... 101 102 103 104 105 [106] 107 108 109 110 111 ... 165
2101
clrmame Discussion / Re: Request for little feature
« on: 12 June 2013, 11:52 »
Can you describe your problem a little bit more in detail? Maybe with a step-by-step description or screenshots...and give me access to all relevant files....

2102
clrmame Discussion / Re: Request for little feature
« on: 24 May 2013, 09:20 »
I do some tests...but let me know if you find a little scenario when this happens

2103
clrmame Discussion / Re: Request for little feature
« on: 24 May 2013, 05:14 »
What exactly do you mean with "Not Autofix Dats in batchmode"?

2104
clrmame Discussion / Re: Request for little feature
« on: 23 May 2013, 18:49 »
you can try this...
http://mamedev.emulab.it/clrmamepro/binaries/cmp20130523.rar

this takes the lastWrite timestamp from the .dat file...

2105
clrmame Discussion / Re: Request for little feature
« on: 23 May 2013, 16:06 »
ok..showing it is no problem...but I want to be sure which date...

datfile creation / lastWrite / lastAccess date
or settings creation / lastWrite / lastAccess date

(e.g. settings lastAccess/lastWrite one will be 'the last time you've scanned or loaded the profile in the profiler....while lastWrite/lastAcess date for datfile would be the date when the datfile was added to the profiler folder (or modified...e.g. when you renamed it)

2106
clrmame Discussion / Re: Request for little feature
« on: 22 May 2013, 13:14 »
What did you edit here?
is something not working as expected?
damn...I'm lost in real life...

2107
clrmame Discussion / Re: Request for little feature
« on: 07 May 2013, 10:47 »
well...the dat header entry which is already shown is the version...and usually dat authors code a date in it :)

2108
clrmame Discussion / Re: Request for little feature
« on: 07 May 2013, 06:54 »
Please specify....

the date when you added it to cmpro?
the date listed in the datfile header?
...or anything else?

2110
as I said....for now it looks at the matched rom and picks the setname...and not the biosname in case it is a shared bios file....should be a 2 minute fix/compile...later when I'm home...

2111
Ah...guess the same place in the sourcecode is missing a handling for biosroms....it should take the n\ folder (since it belongs to *n*eogeo).....as long as you keep bios roms separated (there's an option for that).....

2112
yeah...bug...it always took the parent set into account even for roms which only belong to the clone...
...nice finding...

get this:

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

2113
%a should be ok.....hmm...
I quickly added %a\ and only rebuilt sonicwi2 and it created a folder "s" ....so it seems to work....no matter if full merge or split merged was used.....

maybe you can repeat it somehow in a small scenario?

2114
clrmame Discussion / Re: cbr,cbz.cb7,cbt file support
« on: 12 April 2013, 09:09 »
Cmpro is used beyond the emulation community for ages...

It's not on cmpro's schedule list to support renamed standard archive names.

Not to mention that I can influence the handling in 3rd party code (unrar.dll, 7z sdk or ziparchive library....which may or may not want archive extensions).

2115
clrmame Discussion / Re: chd wrong merged issue
« on: 01 April 2013, 08:01 »
I am

2116
clrmame Discussion / Re: chd wrong merged issue
« on: 01 April 2013, 06:02 »
lazyness of the author I guess

2117
clrmame Discussion / Re: cbr,cbz.cb7,cbt file support
« on: 31 March 2013, 19:04 »
never heard of them or saw them. where is the sense of using renamed archive types instead of the real ones?

2118
clrmame Discussion / Re: 7z warning issue 9.30 -> 9.20
« on: 31 March 2013, 19:00 »
well dont use 7z alpha versions ;)

2119
clrmame Discussion / Re: chd wrong merged issue
« on: 31 March 2013, 18:59 »
yes manually or your move the chd to a rompath root and the next scan will move them to their correct place

2120
clrmame Discussion / Re: clrmame get obselete soon?
« on: 31 March 2013, 18:58 »
you already got download options

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

Page created in 0.532 seconds with 20 queries.

anything