2961
clrmame Discussion / Re: warning about "Remove Matched Sourcefile" failures
« on: 18 May 2010, 17:52 »
I put it on my todo list
- 23 April 2024, 20:25
- Welcome, Guest
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.
2962
clrmame Discussion / clrmamepro 3.133b released
« on: 17 May 2010, 15:45 »
3.133b
added: support for mess software lists (either as hash/*.xml file or via -listsoftware output)
misc: don't show archive errors for no entries in rar part files (partxx.rar format only)
misc: 64bit version uses version64.ini and version.ini as fallback
misc: slight speedup for several routines
misc: showing chd region count in title when not enabling all
misc: trim filenames in dats and remove "." from end of folders and files in datfile
fixed: wrong "illegal download" message on clean install
fixed: rare wrong named chd stats count issue
added: support for mess software lists (either as hash/*.xml file or via -listsoftware output)
misc: don't show archive errors for no entries in rar part files (partxx.rar format only)
misc: 64bit version uses version64.ini and version.ini as fallback
misc: slight speedup for several routines
misc: showing chd region count in title when not enabling all
misc: trim filenames in dats and remove "." from end of folders and files in datfile
fixed: wrong "illegal download" message on clean install
fixed: rare wrong named chd stats count issue
2963
News & Communication / clrmamepro 3.133b released
« on: 17 May 2010, 15:45 »
3.133b
added: support for mess software lists (either as hash/*.xml file or via -listsoftware output)
misc: don't show archive errors for no entries in rar part files (partxx.rar format only)
misc: 64bit version uses version64.ini and version.ini as fallback
misc: slight speedup for several routines
misc: showing chd region count in title when not enabling all
misc: trim filenames in dats and remove "." from end of folders and files in datfile
fixed: wrong "illegal download" message on clean install
fixed: rare wrong named chd stats count
added: support for mess software lists (either as hash/*.xml file or via -listsoftware output)
misc: don't show archive errors for no entries in rar part files (partxx.rar format only)
misc: 64bit version uses version64.ini and version.ini as fallback
misc: slight speedup for several routines
misc: showing chd region count in title when not enabling all
misc: trim filenames in dats and remove "." from end of folders and files in datfile
fixed: wrong "illegal download" message on clean install
fixed: rare wrong named chd stats count
2964
clrmame Discussion / Re: Rename several roms in a folder to match names on a *.dat
« on: 13 May 2010, 13:21 »
profiler renamewizard lets you compare two dats and tells you what was renamed to what. you can export this list or can apply the changes on a third dat.
2965
clrmame Discussion / Re: Rollback problem - almost certainly user error
« on: 12 May 2010, 18:40 »
If you're using addpaths, don't forget to enable the "use addpath" option in the rebuilder.....
...or you rollback set did not contain anything which was matched against the 84 datfile.
...or you rollback set did not contain anything which was matched against the 84 datfile.
2966
clrmame Discussion / Re: Rollback problem - almost certainly user error
« on: 12 May 2010, 13:53 »
well, the purpose of rollback sets is to have only the files which were replaced/removed in later versions, not full sets.
shortcuts/symlinks ...erm...good question. Test it
. I'm using some very generic directory tree walk routine....no idea what the OS functions do for shortcuts etc....since shortcuts are pif files I'm assuming they are handled as files....
shortcuts/symlinks ...erm...good question. Test it
. I'm using some very generic directory tree walk routine....no idea what the OS functions do for shortcuts etc....since shortcuts are pif files I'm assuming they are handled as files....
2967
clrmame Discussion / Re: Rollback problem - almost certainly user error
« on: 12 May 2010, 10:07 »
Maybe some general things about the Rebuilder
Source Folder - cmpro scans this folder (and optionally subfolders) for valid files (either single file or file in archives....or file in archive in archive..or ...). This is done by a hash lookup against the loaded database. In case of a match, each instance will be generated in the destination folder, now using the correct names. Each instance means that if a file is used in various sets, each set is being generated (if not yet existing) and the file is being added.
Destination Folder - here the matched files are being re-generated with correct names.
You need various source folders?
Then you can either setup folders as 'AddPaths' in settings->addpaths and enable the "use addpath" option below the source folder edit box.
Or you can drag'n drop files, folders directly into the rebuilder window (by the way, drag'n drop also works in the scanner...which then internally runs the rebuilder).
You need various destination folders?
Ok, a bit more tricky, currently you can only use system-default-folders for this, i.e. you can split up sets by bios file usage.
Recompression should usually be turned off....a later run with batch tools to rezip files is a better approach...or drop them in my zipmax tool
Things which make rebuilding slow:
- Recompress enabled (speed killer)
- remove rebuilt source files (useful feature..but of course this is additional effort)
- an enabled Rebuilder Advanced->additionally test md5/sha1 (however this avoids rare crc32 hash conflicts)
- Advanced->backup replaced files
If you know what you're doing you can fiddle around with these features to get some speed up...
Source Folder - cmpro scans this folder (and optionally subfolders) for valid files (either single file or file in archives....or file in archive in archive..or ...). This is done by a hash lookup against the loaded database. In case of a match, each instance will be generated in the destination folder, now using the correct names. Each instance means that if a file is used in various sets, each set is being generated (if not yet existing) and the file is being added.
Destination Folder - here the matched files are being re-generated with correct names.
You need various source folders?
Then you can either setup folders as 'AddPaths' in settings->addpaths and enable the "use addpath" option below the source folder edit box.
Or you can drag'n drop files, folders directly into the rebuilder window (by the way, drag'n drop also works in the scanner...which then internally runs the rebuilder).
You need various destination folders?
Ok, a bit more tricky, currently you can only use system-default-folders for this, i.e. you can split up sets by bios file usage.
Recompression should usually be turned off....a later run with batch tools to rezip files is a better approach...or drop them in my zipmax tool
Things which make rebuilding slow:
- Recompress enabled (speed killer)
- remove rebuilt source files (useful feature..but of course this is additional effort)
- an enabled Rebuilder Advanced->additionally test md5/sha1 (however this avoids rare crc32 hash conflicts)
- Advanced->backup replaced files
If you know what you're doing you can fiddle around with these features to get some speed up...
2968
clrmame Discussion / Re: Rollback problem - almost certainly user error
« on: 12 May 2010, 09:23 »
- Load the .84 datfile in the profiler
- Setup a rompath to point to your future .84 files in Settings
- go to the rebuilder, the rebuilder destination should now show that .84 path....otherwise click on "use 1st rompath" button.
- disable recompress files
- disable remove rebuilt files
- select your prefered merge mode
- and finally drag'n drop your .137 folder and .84 rollback folder into the rebuilder window
(alternatively you can setup addpaths for the these 2 and enable "use addpaths" in the rebuilder.
Depending on your PC and especially HD power, it should create any valid file which is found in your new .84 set.....pretty fast...12 hours sounds way, way, way too long.
After the rebuild, you can use the scanner to see what's still missing.
Please differ:
84 folder as rompath - a new empty folder (or the folder with your old setup of .84)
.84 rollback folder - your described folder with the rollback files
.137 folder - your folder with the .137 collection
- Setup a rompath to point to your future .84 files in Settings
- go to the rebuilder, the rebuilder destination should now show that .84 path....otherwise click on "use 1st rompath" button.
- disable recompress files
- disable remove rebuilt files
- select your prefered merge mode
- and finally drag'n drop your .137 folder and .84 rollback folder into the rebuilder window
(alternatively you can setup addpaths for the these 2 and enable "use addpaths" in the rebuilder.
Depending on your PC and especially HD power, it should create any valid file which is found in your new .84 set.....pretty fast...12 hours sounds way, way, way too long.
After the rebuild, you can use the scanner to see what's still missing.
Please differ:
84 folder as rompath - a new empty folder (or the folder with your old setup of .84)
.84 rollback folder - your described folder with the rollback files
.137 folder - your folder with the .137 collection
2969
clrmame Discussion / Re: MESS and software lists
« on: 10 May 2010, 20:35 »
not fullly correct...at least for the cmpro part.
I've only added support to read MESS software list xml files or mess <system> -listsoftware output xmls like common datfiles.
So you can drag'ndrop/add/use such xmls in the profiler as you can do with any other dat...
...it won't auto-get all software lists from a mess binary....you will have one profile for your mess bios stuff and other profile(s) for software list(s)....
I've only added support to read MESS software list xml files or mess <system> -listsoftware output xmls like common datfiles.
So you can drag'ndrop/add/use such xmls in the profiler as you can do with any other dat...
...it won't auto-get all software lists from a mess binary....you will have one profile for your mess bios stuff and other profile(s) for software list(s)....
2970
clrmame Discussion / Re: clrmamepro & UTF-8
« on: 07 May 2010, 19:21 »
ok, the failures are based on the fact that kanjis/katas require some WideCharacter specific filesystem function calls to get the correct filename. The standard ones will convert them to "?" characters which are illegal....
Will check how much effort it is to change this throughout cmpro......I guess too much effort
Update: Yep...too much effort for the moment....sorry.
Will check how much effort it is to change this throughout cmpro......I guess too much effort
Update: Yep...too much effort for the moment....sorry.
2972
clrmame Discussion / Re: MESS and software lists
« on: 07 May 2010, 15:29 »
guess so....I will send you one when I'm home...
2973
clrmame Discussion / Re: clrmamepro & UTF-8
« on: 07 May 2010, 14:41 »
then I only have to generate japanese filenames on my Win7........erm...ok...how to do that...
...ok...found a way...let's test a bit :O)
...ok...found a way...let's test a bit :O)
2974
clrmame Discussion / Re: clrmamepro & UTF-8
« on: 07 May 2010, 09:21 »
hmm...ok..maybe I should try it with a real kanjis/katas containing xml....maybe you can provide me one?
2975
clrmame Discussion / Re: MESS and software lists
« on: 07 May 2010, 08:55 »
maybe I should send you a current build this evening before I release the next cmpro version....then you can recheck it a bit...
let me know your email address somehow...
let me know your email address somehow...
2976
clrmame Discussion / Re: MESS and software lists
« on: 07 May 2010, 08:37 »
yes, cloneof is being parsed and the setname which is listed there is the parent......works fine...at least with snes...which I've tested....
2977
clrmame Discussion / Re: clrmamepro & UTF-8
« on: 06 May 2010, 18:25 »
I did a quick test with a dat with utf8 encoding in the xml and the set:
<?xml version="1.0 encoding="utf-8"?>....<game name="- [MGT] Sam Coupé Disc Drive Interface"> where é translates correctly to é when loading.
It was parsed successfully and a demo file with "é" was created. Using dir2dat or setinfo's export option exports a datfile which encodes the é as é and loading this created dat shows correctly the é again...
...so...did I miss something here? Seems to work fine.....
<?xml version="1.0 encoding="utf-8"?>....<game name="- [MGT] Sam Coupé Disc Drive Interface"> where é translates correctly to é when loading.
It was parsed successfully and a demo file with "é" was created. Using dir2dat or setinfo's export option exports a datfile which encodes the é as é and loading this created dat shows correctly the é again...
...so...did I miss something here? Seems to work fine.....
2978
clrmame Discussion / Re: clrmamepro & UTF-8
« on: 06 May 2010, 10:52 »
well, I will check if I add an "utf8" encoding option to dir2dat...maybe one which you manually have to enable and then it gets right to the xml header....
...guess I have to convert the names as well then....as I said...I will do a little investigation on that...
...guess I have to convert the names as well then....as I said...I will do a little investigation on that...
2979
clrmame Discussion / Re: MESS and software lists
« on: 06 May 2010, 07:32 »
well, the flaw is that I only added reading of the software list xmls 
They are handled as any other datfile and you as an user have to care about how to setup rompaths.
If you now drop a snes.xml, it will show you a datfile in the profiler
name="snes" description="Nintendo SNES cartridges"
and it holds the single sets, 2020bb, 2020bbj, 96zenko etc....in this case these are 1-rom-sets.
I guess any further support beyond that is something for later releases....if at all..
They are handled as any other datfile and you as an user have to care about how to setup rompaths.If you now drop a snes.xml, it will show you a datfile in the profiler
name="snes" description="Nintendo SNES cartridges"
and it holds the single sets, 2020bb, 2020bbj, 96zenko etc....in this case these are 1-rom-sets.
I guess any further support beyond that is something for later releases....if at all..
2980
clrmame Discussion / Re: clrmamepro & UTF-8
« on: 06 May 2010, 07:14 »
utf8 support was added to the xml datfile parser only, i.e. when the xml file holds an encoding <?xml version="1.0" encoding="UTF-8"?> entry, then the names in the dat are correctly parsed.