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!

Pages: [1]   Go Down

Author Topic: clrmamepro 3.133 released  (Read 9745 times)

Roman

  • Global Moderator
  • Member
  • ****
  • Karma: 118
  • Online Online
  • Posts: 3308
  • Operating System:
  • Windows 7 Windows 7
  • Browser:
  • Firefox 3.6.3 Firefox 3.6.3
    • View Profile
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
Logged


Pages: [1]   Go Up
 

Page created in 0.206 seconds with 21 queries.