Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

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.

81

clrmame Discussion / clrmamepro 4.023 released

« on: 18 September 2015, 19:34 »

4.023

fixed: cmpro did not mark old chd files (replaced with identical named but different checksum files) as unneeded
fixed: cmpro oversees some unneeded chds (dupe) chds in sysdef paths when the correct chd is also present (quizard sets)
fixed: cmpro doesn't warn about some unpacked rom files within chd subfolders if a rom archive also exists
added: setinformation "initial invert" option, which inverts your selection on database load (so you need to manually hit the invert button)

82

clrmame Discussion / 4.022 released

« on: 29 August 2015, 18:55 »

4.022

misc:  new compiler (VS2015) under Windows 10 Pro
misc:  7z/rar warnings are now shown in the warning window, not as a messagebox anymore which you have to click
misc:  profiler move/add datfiles overwrite prompts support yes/no to all
fixed: wrong "wrong case" set message when a chd is missing or a wrong named set
fixed: 7z/rar detection of obsolete folders fails in some cases
fixed: datfile nodump flag gets ignored in case of an additional size=0 entry
fixed: nodump without any size entry were not imported
fixed: wrong rar bad crc message when deleting full archives

83

clrmame Discussion / Windows XP Users

« on: 17 August 2015, 06:42 »

Background: I've switched from Visual Studio 2008 (yes..ancient) to VS2015 now....From the installation process I know that there are extra optional settings to support Windows XP builds....

But..come on..it's 2015 and noone should really use XP anymore....

so.......is there really a need for having a clrmamepro built which supports Windows XP?

84

clrmame Discussion / something to test

« on: 14 August 2015, 21:10 »

Well, time for a test build....

misc:  new compiler (Visual Studio 2015) and environment (Windows 10 Pro 64bit)
fixed: wrong "wrong case" set message when a chd is missing
fixed: 7z/rar detection of obsolete folders fails in some cases
fixed: datfile nodump flag gets ignored in case of an additional size=0 entry

I haven't done any checks if the exe files still work under XP/7/8...but I guess you will let me know.

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


actually a quick speed test is not that good. The vs2015 compiled exe seems to be a bit slower (scanning speed). I will check if it's related to the latest fixes or compiler optimization flags, etc....

85

clrmame Discussion / MAME 164

« on: 29 July 2015, 20:35 »

regarding MAME 164 and latest cmpro....

yes I'm aware of a wrong and empty "wrong case" message when a clone chd is missing

...but currently I'm busy...so...ignore it ;-) Guess it will disappear automatically if you got the chd in question....

86

News & Communication / clrmamepro 4.021 released

« on: 20 July 2015, 16:40 »

fixed: possible crash with corrupt settings file
fixed: rare issue where a sample parent set with no samples for its own and multi-softwarelist support is marked as unneeded
fixed: possible crash on cmpro start on read-only device or full device
fixed: structural issues and possible crash when using dats with releases and run into double name issues
fixed: double name check when using releases
fixed: some dialogs don't use "MS Sans Serif" as font...
fixed: adjusted some warning messages to use "SOFT" instead of "List"
fixed: setinformation "hide parent" does not work for listed disks
fixed: unpacked set with chds can be falsely detected as misplaced
fixed: rare typo based bug in checking unneeded sets/chds
fixed: hashcollision sets with nodumps can create circular fix-unneeded/fix-missing scenarios
misc:  better unneeded detection of chds within an identical setnames relation (softwarelists/Non-Software List)
misc:  better wrong sysdefpath detection of chds within an identical setnames relation (softwarelists/Non-Software List)
added: automatically detect mame and mess as xml root elements
added: supporting biossets with samples (and sampleof) elements

87

clrmame Discussion / clrmamepro 4.021 released

« on: 19 July 2015, 19:03 »

fixed: possible crash with corrupt settings file
fixed: rare issue where a sample parent set with no samples for its own and multi-softwarelist support is marked as unneeded
fixed: possible crash on cmpro start on read-only device or full device
fixed: structural issues and possible crash when using dats with releases and run into double name issues
fixed: double name check when using releases
fixed: some dialogs don't use "MS Sans Serif" as font...
fixed: adjusted some warning messages to use "SOFT" instead of "List"
fixed: setinformation "hide parent" does not work for listed disks
fixed: unpacked set with chds can be falsely detected as misplaced
fixed: rare typo based bug in checking unneeded sets/chds
fixed: hashcollision sets with nodumps can create circular fix-unneeded/fix-missing scenarios
misc:  better unneeded detection of chds within an identical setnames relation (softwarelists/Non-Software List)
misc:  better wrong sysdefpath detection of chds within an identical setnames relation (softwarelists/Non-Software List)
added: automatically detect mame and mess as xml root elements
added: supporting biossets with samples (and sampleof) elements

88

clrmame Discussion / nightly build....

« on: 22 June 2015, 19:50 »

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

fixed: possible crash with corrupt settings file
fixed: rare issue where a sample parent set with no samples for its own and multi-softwarelist support is marked as unneeded
fixed: possible crash on cmpro start on read-only device or full device
fixed: structural issues and possible crash when using dats with releases and run into double name issues
misc:  automatically detect mame and mess as xml root elements
misc:  supporting biossets with samples (and sampleof) elements

hope I can now concentrate on the "mame + software list chds with identical setnames issues"...

89

clrmame Discussion / clrmamepro 4.020 released

« on: 28 May 2015, 19:30 »

misc:  using "engine" and "game" elements as defaults which allow loading of new MAME binaries and dats without modifying engine.cfg
fixed: game name check might produce a wrong warning for full merged chd sets where the parent does not have chds
fixed: sampleclones check for sample-only sets fails and reports missing sets

90

clrmame Discussion / clrmamepro 4.018 released

« on: 12 March 2015, 19:30 »

fixed: official 7z bug which causes a crash when a fake 7z archive file is being processed
fixed: rebuilding bios files in hash collide full merge mode creates dupes (this also affects dat export)
fixed: wrong statistics "wrong named chd count"

91

News & Communication / clrmamepro 4.017 released

« on: 19 February 2015, 09:15 »

added: support for biossets with chds
fixed: obsolete missing game message for sample-only sets in multi-software list mode
fixed: deprecated dat export exports biossets as resource and game
misc:  updated to latest rar (5.21) and 7z sdk (9.38)

92

clrmame Discussion / clrmamepro 4.017 released

« on: 18 February 2015, 20:11 »

added: support for biossets with chds
fixed: obsolete missing game message for sample-only sets in multi-software list mode
fixed: deprecated dat export exports biossets as resource and game
misc:  updated to latest rar (5.21) and 7z sdk (9.38)

93

clrmame Discussion / clrmame 4.016 released

« on: 23 December 2014, 23:36 »

So what will change if you scan your MAME set with the new cmpro version:

- unmerged sets:
   (you don't use this for MAME, do you...), nothing changes...

- split merged sets:
   you will see some wrong placed roms now since clrmame did not kill parent/clone relationships
           
- full merged sets:
   you will see several wrong named roms (due to hash collisions)



So what's new:


misc:    Changed the way how hash collisions are handled. A hash collision happens when you got
         identically named files with different hashes within a parent/clone relationship.
         In the past cmpro either removed the parent/clone relationship completely or you were
         forced to split merged mode.
         Now, in case of a hash collision *and* only if switch to full merged sets (scanner,
         rebuilder or merger), the rom names of the clones will be switched to a naming convention
         which you can select. Default is setname\romname. You can select the naming in profiler
         options 'Naming pattern'. A flyover tells you which variables you can use
         there. %1 (plus something else) is mandatory here.

         Again, only if full merged mode and hash collisions are active.

         You also got an option there to say how many files get renamed. Either only the single hash
         collision clone file, or all files in this clone set or all clone files in all clones of this
         parent clone relationship.

added:   added option (Settings screen) to allow a full merge mode which ALWAYS stores parent/clones
         the way described above, no matter if a hash collision is there or not. This is the
         "hash collision name" mode. If you're using this, the upper mentioned selection of files which
         get renamed is obsolete. In this mode all clone files in the parent clone relationship are
         renamed.

added:   batcher rebuilder option "never compress files" which allows you to create unpacked sets

removed: "Possible wrong nodump definition found" cleanup step prompt. It's actually a special
         case of hash collision and so it's handled the same way as other collisions.

misc:    some intern changes so that you got theoretically 32k path length support (Hello Tosec..)
         If you need such long paths, you need to add "\\?\" in front of your rom/sample/add/rebuilder
         source/destination/etc paths..
         So for example:
         \\?\E:\temp\this is a long folder name right or wrong blabalbalblablablablabalabl\

misc:    updated to latest unrar dlls
misc:    merger works with subfolders
misc:    "double roms detector" during parsing handles weird merge tag combinations better
misc:    "double setname" is also performed when you're using "release" elements and switch modes

fixed:   belongs_to_parent check fails on 0-byte files
fixed:   weird messages when you enable the clone but disable its parent in full merged mode
fixed:   remove obsolete wrong merging or missing set messages (which normally get removed in 2nd scan)
fixed:   adding sampleonly sets may cause issues when you got softwarelist which share the setname

94

clrmame Discussion / Status

« on: 07 November 2014, 19:54 »

....cough cough....shouldn't there be an update already?

erm...well..yes...but the last weeks were exhausting...a lot of real-life work project work kept me extremely busy...

So what's the status on the hash collision thing..(subfolder idea..)...actually...I'm pretty much annoyed of it. You run into issues here and there if you have subfolders and switch modes (from full to split or vice versa). To sum it up...I'm not really happy with the solution at the moment...

I may release a test version with it enabled sooner or later or change the subfolder idea to something else...or roll that change back and release the small other updates...

In the meantime (most likely because I was annoyed looking at the old code) I played a bit (just some minutes actually...) with pugixml (pugixml.org) and was surprised how fast it is....and had the idea of keeping the DOM as internal storage basis and have some xpath layer upon it to work with it...
For a second I was in the mood to write a MAME-only scanner/rebuilder from scratch with all the new ideas..and a totally different way of how things work. Not endless lists of options, not supporting this and that, not cleaning the xml which MAME provides...not exporting here..no batch jobs there....scan/fix/rebuild...done...but again...I'd need more time...

So...please be patient...I guess the current main version works fine...maybe some little fixes soon....

95

clrmame Discussion / something to test

« on: 17 September 2014, 21:18 »

Handle with care....and on own risk....this is a TEST version...please keep this in mind....

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

besides of 32k path support (still fiddling with some things...)

misc:    Changed the way how hash collisions are handled. A hash collision happens when you got
         identically named files with different hashes within a parent/clone relationship.
         In the past cmpro either removed the parent/clone relationship completely or you were
         forced to split merged mode.
         Now, in case of a hash collision *and* only if switch to full merged sets (scanner,
         rebuilder or merger), the rom/disk names of the clones will be switched to setname\filename.
         So clone sets are stored in subfolders of the parent set. Again, only if full merged mode
         and hash collisions are active.

added:   added option (Settings screen) to allow a full merge mode which ALWAYS stores parent/clones
         the way described above, no matter if a hash collision is there or not

removed: "Possible wrong nodump definition found" cleanup step prompt. It's actually a special
         case of hash collision and so it's handled the same way as other collisions.


....I still have one open issue with Merger's nodump handling....but who uses nodumps...and who uses the merger...

96

clrmame Discussion / one more thing...

« on: 10 September 2014, 20:02 »

ok...while the 32k path support seems to work (wonder if anyone tested it yet)...I'm fiddling around with getting rid of killing parent/clone relationships when you got name/hash collisions within such a set relation....

Current situation: you can either force split merge mode or cmpro removes parent/clone relationship if a hash collision is found, no matter if you use split merged sets (where the problem does not occur) or not.... Only full merged sets would have a problem.

Future solution: In case you got a hash collision *AND* use full merged sets (scanner, rebuilder destination, merger destination), cmpro will store clone sets in set subfolders, while the parent and not affected clones keep their naming.
As a plus I want to introduce an optional setting which allows you to store all parent/clones that way, Parent files in the archive root, clones in subfolders.
The names will change instantly (depending on the size of the used database) if you switch the merge mode....

I've attached some screens...as demonstration sets I used some old 1942 MAME database entries which have a hash collision within their clones...1942abl and 1942p share some equally named rom files while their hashes differ...

1.png: showing split merged mode, all files keep their old naming
2.png and 3.png: switched to full merged mode, the affected rom names change to setname/romname format
4.png: a not affected set keeps the old naming, no matter if full merge mode is enabled or not

Works pretty fine already....you end up with subfolders for hash collisions.... I've decided to put all roms of the set in question into subfolders, not only the ones with hash collisions...looks better in my opinion...

To Do:
- add the option for the new merge mode where you always want to create clones in subpaths
- export dat function should of course use the normal naming
- check the other well known database read-in correction: nodumps which have a real-dump name clone inside their parent/clone relation....wonder if I can introduce something similar...

97

clrmame Discussion / september 3rd

« on: 03 September 2014, 14:16 »

Look what I've found while lurking through the past today....

Version 1.0 (03-September-1997)

    - first release (32-bit Windows Console Application)


oh man...it's 17 years....

98

clrmame Discussion / clrmamepro 4.015 released

« on: 19 August 2014, 20:47 »

ok...before I concentrate on the already mentioned storing/naming methods for full merged sets and hash collisions, I wanted to get rid of my current development version....

4.15

fixed: corrected handling of sets with only bios roms and sample clone (MAME 154 gp110 sets)
fixed: dir2dat not always writes cr/lf as line delimiter (deprecated format only)
fixed: rebuilder log shows no reason for already rebuilt files
fixed: rebuilder shows warning when rebuilding uncompressed file which already exists in destination
fixed: rebuilder recreates files (when not needed) when you use chds files as roms
fixed: crash when redrawing scan results (some rare circumstances)
misc: optimized general hash calculation / file read routine
misc: removed crc=-1 / 1 suspicious checksum check
misc: changed nes header file to be a bit less strict
misc: updated to latest ziparchive class lib, unrar dll
misc: parse rom merge tags enabled by default (on clean install)


sorry...no work yet on
- faster decompressed sets support
- +r/+h/+s warnings also in logs
- logfile name additions in case of using multiple instances...
such requests are still on my list...so don't worry ;-)

99

clrmame Discussion / mame .154

« on: 23 July 2014, 18:48 »

...is out and you might stumble about missing sets messages regaring model 110 sets....(black velvet etc...)

Such sets consists of a sample clone (genpin) and bios roms (gp_110) only....so you don't really have a blvelvet.zip....that's what cmpro currently complains about...

I guess for the time being you can't fool cmpro by adding an empty zipfile since it will moan about that...

...I will work on a solution as soon as I have time...till then...please ignore them.

100

clrmame Discussion / clrmamepro 4.014b released

« on: 17 April 2014, 19:53 »

4.14b

fixed: not initialized variable causes 7z decompress warnings in Windows 8.1 (64bit only)