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 ... 147 148 149 150 151 [152] 153 154 155 156 157 ... 165
3021
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.


3022
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.

3023
clrmame Discussion / clrmamepro 3.133 released
« on: 07 April 2010, 22:11 »
added: introducing 'DIFF SCAN'. A new scan functionality which knows which
       sets did change from a previous datfile to the current one and with
       this option you will only scan the sets which did change.
       'Change' in terms of important changes which makes a rescan necessary
       (e.g. a checksum or rom name change, NOT a description change).
      
       When e.g. MAME updates, 99% of all sets stay the same, there is not
       really a need to rescan them (unless you changed them manually).
       You can now use the diff scan option. It's only selectable if at least
       one set differs and not all do differ.

       This function is robust against cache-clearing.
       In the set information window you can use the popup menu in the tree
       to show only the changed sets if you're interested in them.
      
added: archives in archives (...in archives...) are supported now for the rebuilder
       Removing rebuilt files is limited to the root level though.

added: writing profiler.xml file when you leave cmpro, you can use this xml
       for any of your own xslt/html building usage

misc:  updated unrar dlls
misc:  disabled systems are shown in title line set count and stats
misc:  renamed rebuilder logfile reason for skipped files
misc:  standard listinfo and xml dats don't necessarily require a description
       tag. In this case, the setname is used as description, too.

fixed: some line limit detection fixes on xml dat parser (MESS > .137 issue)
fixed: some wrong stats when using fastscan
fixed: wrong warning about a not recommmended scan appears rarely for fastscan
fixed: forgot to remove old cache files after dat update

3024
3.133 writes profiler.xml when you leave cmpro....that xml file can be used for your own xslt/html magic.

3025
3.133 shows a better string than "unknown"....

3026
ok...3.133 out...should work again with MESS.

3027
For cmpro 3.133 you don't need the description tag anymore.

3028
News & Communication / clrmamepro 3.133 released
« on: 07 April 2010, 22:01 »
added: introducing 'DIFF SCAN'. A new scan functionality which knows which
       sets did change from a previous datfile to the current one and with
       this option you will only scan the sets which did change.
       'Change' in terms of important changes which makes a rescan necessary
       (e.g. a checksum or rom name change, NOT a description change).
       
       When e.g. MAME updates, 99% of all sets stay the same, there is not
       really a need to rescan them (unless you changed them manually).
       You can now use the diff scan option. It's only selectable if at least
       one set differs and not all do differ.

       This function is robust against cache-clearing.
       In the set information window you can use the popup menu in the tree
       to show only the changed sets if you're interested in them.
       
added: archives in archives (...in archives...) are supported now.
       Removing rebuilt files is limited to the root level though.

added: writing profiler.xml file when you leave cmpro, you can use this xml
       for any of your own xslt/html building usage

misc:  updated unrar dlls
misc:  disabled systems are shown in title line set count and stats
misc:  renamed rebuilder logfile reason for skipped files
misc:  standard listinfo and xml dats don't necessarily require a description
       tag. In this case, the setname is used as description, too.

fixed: some line limit detection fixes on xml dat parser (MESS > .137 issue)
fixed: some wrong stats when using fastscan
fixed: wrong warning about a not recommmended scan appears rarely for fastscan
fixed: forgot to remove old cache files after dat update

3029
Actually it's not related to the software list tags but to some other line limitations. Will be fixed in next version.
However if you try to load the xml file into cmpro (and not using a direct import from the mess binary) you need to define a new engine.cfg entry like

engine (
   name MESS_DATFILE
   gamelist mess
   cachefile _messdat
   replace machine game
)

...but even with that you currently run into some xml detection line limitation.....as mentioned...this will get fixed.

3030
Can you mail me an example xml output please so I will have look at it later tonight?

3031
clrmame Discussion / Re: Strange problem with Carnevi1 CHD
« on: 05 April 2010, 16:27 »
so actually what I'm saying is:

if you keep your sets fully merged you only need the rompath subfolder for the carnevil parent set and keep all chds (the parent and the clone(s)) in there. Then you don't need the "allow chds in rompath root" option.

If you keep them split-merged, you need a subfolder for each one (parent and clones...)

if you want to store them in a rompath root, you need to enable that option and normally you can keep the chds in any rompath root then.

So...recheck your setup and let me know what looks wrong in your point of view....as mentioned in the previous post, best would be to send me the details (cmpro files) and maybe a short information which file is stored where....

3032
clrmame Discussion / Re: Strange problem with Carnevi1 CHD
« on: 05 April 2010, 14:53 »
Wait a second....it says 'unneeded folder'. I'm assuming you're using full merged sets then? If so, move the clone chd file to its parent folder (with the parent chd) and you can safely remove the unnecessary folder.

If I should do more investigation, please let me know more details....
Easiest would be to email me your cmpro.ini file, the used profile settings file (.cmp in cmpro's settings folder) and if the dat is not MAME based, the datfile.


3033
clrmame Discussion / Re: Strange problem with Carnevi1 CHD
« on: 04 April 2010, 18:47 »
Be Sure that you enable the allow Chd in rompathroot Option if you Store chds that Way. Also Be sure that your Chd is valid.
I will check this When Im back from Holiday and don't use a mobilephone to answer postings ;)

3034
clrmame Discussion / Re: Scan All to Fix Missing
« on: 09 March 2010, 08:29 »
Well,

I can tell you what users usually do when a new version of MAME is out:

0) Load the MAME profile (Profiler detects a new version of the mame exe and auto-updates its database)
1) Scanner, got all check and fix options enabled...Do a new scan and let them fix all..

...after that you should only have missing files, the ones which were added/replaced in the new version

2) drag'n drop new sets into the scan results window with auto-scan after drag'n drop and drag'n drop internally uses the rebuilder, where the rebuilder destination points to the existing collection.
3) repeat 2) until nothing is listed anymore (ok...new chds need to be moved to any rompath though, cmpro will move them to their correct place)

3035
if I remember correctly "skipped with reason unknown" simply means they were skipped with non of the 'problem things' like corrupt archive, problems while decompressing or destination file creation fails. So mainly if a file simply does not match anything valid.

3036
see...I never understood why "singe console roms" need a name which is 132947310897414 characters long if you got a nice description tag.
Besides of that, MAME is not fully 8.3 since years ;)

3037
Description is required, it's used internally for all kind of checks, sorting possibilities and displaying information.
I don't see a problem having it in the dat either.
Within cmpro it's stored only once anyway if it matches the setname and datfiles can be compressed.

Of course you might say, so if cmpro uses it only once if it's identical to the setname, why not cloning it during datparsing....hmm...I might think of it.

3038
you can use auto-detect rompaths in the systems dialog. It will scan your rompaths and picks the best fitting one for each sysdefpath.
...of course you need romsets in there to get something useful ;)

3039
no.

Don't put rompaths in rompaths for scanning

3040
generally, sysdefpaths are folders.

if you scan and want to use sysdefpaths, your sysdefpaths have to be setup as rompaths, too.

if you want to rebuild sets in sysdefpaths, your sysdefpaths don't need to be setup as rompaths (depending on your rebuilding idea...for example if you want to split your sourcesets into folders-by-system sets...)

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

Page created in 0.256 seconds with 16 queries.

anything