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.

Topics - Roman

Pages: 1 2 3 [4] 5 6 7 8 9 10
61
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

62
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"

63
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)

64
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)

65
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

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

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

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

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

70
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 ;-)

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

72
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)

73
clrmame Discussion / clrmamepro 4.014a released
« on: 26 March 2014, 19:50 »
4.014a

fixed: accidently reintroduced 7z case fix issue when using 7z exe's rename operation

74
clrmame Discussion / clrmamepro 4.014 released
« on: 24 March 2014, 20:06 »
4.014

misc:  switched to 7z CPP SDK core now
         Unpack operations and hash calculations are now done blockwise.
         So you should not run into memory issues with huge 7z files anymore.

misc:  reenabled detection of unneeded folders within rar/7z files with safe handling on delete
fixed: no more possible double file creations when using external packer's rename command
fixed: possible assertion when not using external packer's rename command
misc:  updated unrar dll

75
clrmame Discussion / 7z blockwise memory decompress
« on: 28 February 2014, 18:42 »
As you might notice from the amount of releases I'm pretty busy with real life.....and so looking at 7z is nearly impossible at the moment...

Looking at 7z currently means: trying to get the c++ part of the 7z SDK to work...the old routines use the C core of the SDK, which is limited when it comes to blockwise operations (everything is decompressed to memory/file in one go) and > 4GB support.

While I had no problem to use the general reading/extracting mechanisms of the C++ COM part I'm still looking at way to have a callback ready which is able to update calculated hash values or -most likely the same callback- decompress data blockwise to memory (for testing purposes)...

I might have overseen such a callback due to my lack of time.....but I only found some update callback which can e.g. be used to print out a progress percentage value...but not giving me access to a memory block/size (to update my hash calcs etc)...

So....if anyone knows where to find this...you're more than welcome...

76
clrmame Discussion / clrmamepro 4.012b released
« on: 05 February 2014, 20:06 »
4.012b

fixed: unneeded samples can cause crash
fixed: rebuilder fails on filenames containing special character '`' which is internally used
fixed: crash on illegal 7z file dates
fixed: case fix for rar/7z without using their rename operations removes file and leads to crash
misc:  updated to latest unrar dll
misc:  updated to latest ziparchive class

77
clrmame Discussion / clrmamepro 4.012a released
« on: 22 December 2013, 20:23 »
4.012a

fixed: rar processing freezes when handling multi volume rars
fixed: rar deletion failed due to some other multi volume handling (dll update)
misc:  changed default operation for "Edit Datfile..." from ShellExecute "edit" to "open"


merry xmas

78
clrmame Discussion / clrmamepro 4.012 released
« on: 08 December 2013, 20:44 »
Wow...another year comes to its end...and nearly no cmpro releases... Well..I'm still alive but budget and timewise I'm not that deep into MAME and CMPRO development anymore. Real life job, and way more important, family takes most of my time...which is actually great. Sorry for the users which sent in a request which didn't make it in yet...they are not forgotten though. Enjoy the rest of the year, have a great holiday season and look forward to a healthy 2014. Ah yeah...some end of year build


4.012

added: profiler tree option "Profile List Includes All Subfolder Entries"
       which shows you profiles on the selected plus all sublevels
added: cmpro.ini option "Adv_MinimizeCHDMan = on" to keep chdman windows minimized (not hidden)
misc: updated unrar.dll with the release of winrar5
fixed: zero padding in offlineList xml parser was not working correctly
fixed: little memleak when you drag'n drop profiles in profiler
misc: changed rar/7z rename operations a bit to made them more safe against possible external packer failures
misc: minor changes to disk name checks to avoid rare issues with identical hashes but different names within a parent/clone relationship (in full merge mode)

79
clrmame Discussion / OfflineList XML files
« on: 12 September 2013, 17:55 »
If you're interested in better OfflineList XML dat parsing (especially when it comes to padding numbers with zero), you might want to use this:

Thanks to Oxyandy for reporting the issue...


ah....fixed again....

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

don't forget to clean your cache

80
News & Communication / clrmamepro 4.011a released
« on: 20 August 2013, 20:49 »
4.011a

misc: supporting multiple device_ref entries (removed %i from rebuilder poststring variables though)
misc: replaced 7z case fix with exe rename when possible
misc: disabled obsolete archive folder check for external packers (since they might remove the folder and entries)

Pages: 1 2 3 [4] 5 6 7 8 9 10

Page created in 0.135 seconds with 19 queries.

anything