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 - jclampy

Pages: [1]

clrmame Discussion / Roman quick question regarding "Support Inverted CRC32"

« on: 18 January 2013, 07:34 »

Hi Roman,

Do you know off the top of your head around what Mame/.Dat Version we would toggle from "Support Inverted CRC32" enabled to disabled?

Just a vague idea or perhaps some 'keywords' I should go and search for in the MAME previous release changelogs would be of help.

Thanks.

clrmame Discussion / My 'diff' .dats in Clrmamepro won't let me choose merge type. [solved]

« on: 13 January 2013, 09:47 »

Hi,

I have just noticed that whenever I make a 'diff' .dat using makediff.exe and then in Clrmamepro 'Scanner' or 'Rebuilder' I am forced to use 'non-merged' option. The other two choices are greyed out.

Is there no way I can unlock the other options when using a 'diff' .dat?
Was it only possible in older versions of Clrmamepro but not now?

I tried adding forcemerging="split" to the datfile header but no difference.
I have tried with 'diffs' .dats I have made of either new or old mame versions and no difference.

Thanks.

clrmame Discussion / Error loading profile with DOS Mame034 and Clrmamepro409a

« on: 12 January 2013, 13:27 »

Hi,

I am trying to create/load new profile with DOS Mame034 .exe and Clrmamepro v4.09a but a error message pops up when it is going to start creating a database;

I select mame.exe and make a description
I select OLD_MAME emulator setting and create profile
click [ok]

Under 'options' box I tick "Support Inverted CRC" and "Hide Common DatFile Errors"

I select the profile in the profiles window and click 'load/update' button
Message box appears saying to create database which I click [ok]

running: c:\mame034\mame.exe -listinfo

Then straight away error box appears:
Warning: Found an incomplete datfile or a bad exe-output!
Last correctly imported set:
name: none
description: none

Any ideas how to get it to work?

Could it be some old entries in the registry from previous clrmamepro usage?

Additional Info:
I downloaded mame034 binary from mamedev website.
Also tried old clrmamepro all the way back to 3108 and still same result.

Thanks.

clrmame Discussion / New user having difficulties using Clrmamepro. [Workable]

« on: 11 January 2013, 11:01 »

Hi everyone I am new user and having a few difficulties using Clrmamepro.

I use default settings.
When I first load a .dat file in Clrmamepro I select 'no to all' questions.
I compile romsets using split method.

Here is what I am trying to do:
01. Created folder for mame v0.034 romset.
02. Used mame v0.034 .dat from progettasnaps with Clrmamepro to compile romset.
03. Completed 'New Scan' and showed up 0 missing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
04. Created folder for 'difference of' mame v0.034 to v0.036 romsets.
05. Got mame v0.036 .dat from progettasnaps.
06. Used mamediff to create 'difference of' .dat between mame v0.034 to v0.036 .dat files.
07. Used newly created 'difference of' .dat with Clrmamepro to compile romset.
08. Completed 'New Scan' and showed up 0 missing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
09. Created folder for 'difference of' mame v0.034 to v0.036 to v0.037b5 romsets.
10. Got mame v0.037b5 .dat from progettasnaps.
11. Used mamediff to create 'difference of' .dat between mame v0.034 to v0.037b5 .dat files.
12. Used mamediff to create 'difference of' .dat between ['difference of' mame v0.034 to v0.036] and ['difference of' mame v0.034 to v0.037b5] .dat files.
13. Used newly created 'difference of' .dat with Clrmamepro to compile romset.
14. Completed 'New Scan' and showed up 0 missing.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15. Got mame v0.037b5 .dat from progettasnaps.
16. Completed 'New Scan' on *all three previously created folders at same time and results in a whole lot of problem messages popping up.

Is there a way to do the last part so that the problem messages don't pop up? I assume it starts throwing messages up while scanning the v0.034 folder even though it still has the other two (v0.036 and v0.037b5) folders to scan after.

Maybe I have to change some settings in Clrmamepro to reflect my use of multiple paths?

Also, am I using the best method for what I am trying to do above?

Thank you for all help/advice.

PS:
v0.034 is for PCMamev0.4a for PPC/WM
v0.036 is for PCMamev0.5wip for PPC/WM
v0.037b5 is for Mame4all and various iterations