|
Something funky with ClrMamePro?
#302331 - 01/11/13 03:53 AM
|
|
|
Does anyone know, off the top of their head; is there a version of ClrMamePro which, from 'then onwards' does not work properly with a few files from around ancient 0.35 to 0.38 MAME versions?
Edit:
Ok, found that if there *is* something that changed it happened with version 4.01, I haven't finished my investigation, but here is the changelog if it helps jog anyones memory:
4.01
added: Font selector (popupmenu->View->Select Font) for scanner tree and setinfo tree/list
added: profiler option to support inverted crc32 for baddumps method (default = off)
fixed: missing device path/system initialization randomly keeps devices unchecked
fixed: circular renames inside zips don't work
fixed: saving/loading of standard/mech/device path clones names when only 1 is setup
misc: limit list of not setup sysdefpaths to avoid too big prompt
misc: don't allow profiler reset on exe based dat
removed: setinformation title flyover (obsolete and flickers)
Edited by jclampy (01/11/13 05:05 AM)
|
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|
|
|
Re: Something funky with ClrMamePro?
[Re: jclampy]
#302338 - 01/11/13 08:19 AM
|
|
|
What makes you think that it does not work?
MAME is only used to get the xml (or in that old case listinfo) data from. So the only thing you have to care about is to use "OLD_MAME" as Emulator setting in the profiler create option.
|
|
|
|
Re: Something funky with ClrMamePro?
[Re: Roman]
#302340 - 01/11/13 09:03 AM
|
|
|
I am not making new profile as I am using .dat files from progettosnaps.
Problem is I get the odd rom that the newer versions of clrmamepro skips past and reports 'missing'.
I use older versions of Clrmamepro and the roms are not skipped and added to archives.
It is only the odd few roms, but the difference is having a complete set at the end.
I suspect the roms were known as 'bad dumps' later on in Mame's life and the newer versions of Clrmamepro are not adding them to the archives where the older versions of Clrmamepro would.
I can confirm that Clrmamepro v4.00b (and probably all older versions before) will add these roms to the archives.
Clrmamepro v4.01 and all modern versions since will not add these roms to archives therefore causing 'missing roms'.
|
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|
|
|
Re: Something funky with ClrMamePro?
[Re: jclampy]
#302343 - 01/11/13 10:25 AM
|
|
|
added: profiler option to support inverted crc32 for baddumps method (default = off)
you need to turn that on
Very old MAME versions used to mark baddumps not with a flag but with an inverted crc32.
|
|
|
|
Re: Something funky with ClrMamePro?
[Re: Roman]
#302344 - 01/11/13 10:45 AM
|
|
|
Ok, thank you for your help in clearing that up for me and also for developing Clrmamepro.
By the way, what is the *correct* method for auditing roms?
If I use a Mame .dat in Clrmamepro and compile a full set with none missing, is that enough?
Or should I run an audit with DOS Mame afterwards? I assume that when talking around the years 1998 to 2001 that it was ok to audit with Mame32 as well?
I have run a verifyroms with both the DOS and Mame32 variants of versions 0.036 and 0.037b5 of their respective sets and come up with various messages.
As far as I know the 'No good dump known' can be ignored in this instance.
Same with 'Not found - no good dump known' and 'Rom needs redump' as well.
The "INCORRECT CHECKSUM" and "INCORRECT LENGTH" messages have got me worried though. I think somebody mentioned there is a valid reasoning for some of those and I am not sure if there is anything a user can do or should do to rectify them.
Also it lists most romsets as 'Best known' but some are listed as 'bad'. At the bottom of the report; 2240 romsets found, 2200 were OK.
Mame32 will show less roms 'available' than 'all games'.
Is this 'normal' and what is classified as a 'full set'?
Or is something not 'right' because remember that clrmamepro compiled the set with 'none missing' and didn't mention any errors from what I noticed.
|
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|
|
|
Re: Something funky with ClrMamePro?
[Re: jclampy]
#302345 - 01/11/13 11:28 AM
|
|
|
If (after a new scan) the cmpro scan results tree doesn't list anything (and you got all check options and all sets/systems/devices/bios) enabled, you're done.
|
|
|
|
Re: Something funky with ClrMamePro?
[Re: Roman]
#302346 - 01/11/13 11:32 AM
|
|
|
I think the issues I am having is because I am trying to split the romsets over multiple paths.
For example one folder for 0.034 and then one for changes to 0.036 and then one for changes to 0.037b5
Although everything may 'look ok to my eyes' with this setup, I have the feeling that Mame (maybe because older versions) and Clrmamepro are not handling the multiple paths to well. I think this could be causing the 'audits' to get messed up.
Is there a 'proper' way to do this or should I not use multiple paths when auditing? I'm starting to think I shouldn't use multiple paths at all.
|
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|
|
|
Re: Something funky with ClrMamePro?
[Re: Roman]
#302347 - 01/11/13 11:47 AM
|
|
|
Quote:
> If (after a new scan) the cmpro scan results tree doesn't list anything (and you got
> all check options and all sets/systems/devices/bios) enabled, you're done.
Ok, I just ran "New Scan's" of the .dat file's for each of the three individual folder's from my previous message and all Clrmamepro "New Scan's" came up clean.
If I try to run a FULL v0.037b5 .dat on all three folder's at same time then I get errors.
Is there a way to setup Clrmamepro to 'scan' these multiple paths without throwing up errors?
|
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|
|
|
Re: Something funky with ClrMamePro?
[Re: jclampy]
#302348 - 01/11/13 11:48 AM
|
|
|
I've got them split up by systems, devices and mechanical...so I end up with something around 70 rompaths...no problem. (Maybe the rompath entries in mame.ini get too long then..but who cares  )
|
|
|
|
Re: Something funky with ClrMamePro?
[Re: jclampy]
#302349 - 01/11/13 11:57 AM
|
|
|
This is not the cmpro forum. If you got questions, please raise them there.
You only need to setup your rompaths in settings and let the scan run. It tells you what is wrong with your files.
|
|
|
|
Re: Something funky with ClrMamePro?
[Re: Roman]
#302350 - 01/11/13 11:57 AM
|
|
|
Ok, so you are able to run one .dat file to scan all folders at same time or do can you only use individual .dat file's to scan each folder individually?
Thanks.
|
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|
|
|
Re: Something funky with ClrMamePro?
[Re: Roman]
#302351 - 01/11/13 12:00 PM
|
|
|
Quote:
> This is not the cmpro forum. If you got questions, please raise them there.
> You only need to setup your rompaths in settings and let the scan run. It tells you
> what is wrong with your files.
Sorry, where is that forum?
Ok, found it. I am not a member there, so if you want I will go there or you could answer my previous question if you want to?
Thanks for your help.
|
Read about my latest custom HLSL setup here;
http://gamingnos.blogspot.com/
|
|
|
Re: Something funky with ClrMamePro?
[Re: jclampy]
#302352 - 01/11/13 12:01 PM
|
|
|
|
|
|
Re: Something funky with ClrMamePro?
[Re: Roman]
#302353 - 01/11/13 12:04 PM
|
|
|
|
|
Index 
Threaded 
Something funky with ClrMamePro?
Reply
[Re: 
)
