2861
clrmame Discussion / clrmamepro 3.135c released
« on: 01 September 2010, 20:01 »
3.135c
fixed: dupes check was still broken
fixed: dupes check was still broken
- 07 May 2024, 09:55
- 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.
2862
News & Communication / clrmamepro 3.135c released
« on: 01 September 2010, 20:01 »
3.135c
fixed: dupes check was still broken
fixed: dupes check was still broken
2864
clrmame Discussion / clrmamepro 3.135b released
« on: 31 August 2010, 20:49 »
3.135b
fixed: rare wrong "no or corrupt chd header/sectormap" message
fixed: wrong dupe check when clones does have chd(s) while parent doesn't
fixed: wrong "wrong case" message when using the move set to correct sysdefpath option
fixed: rare wrong "no or corrupt chd header/sectormap" message
fixed: wrong dupe check when clones does have chd(s) while parent doesn't
fixed: wrong "wrong case" message when using the move set to correct sysdefpath option
2865
News & Communication / clrmamepro 3.135b released
« on: 31 August 2010, 20:49 »
3.135b
fixed: rare wrong "no or corrupt chd header/sectormap" message
fixed: wrong dupe check when clones does have chd(s) while parent doesn't
fixed: wrong "wrong case" message when using the move set to correct sysdefpath option
fixed: rare wrong "no or corrupt chd header/sectormap" message
fixed: wrong dupe check when clones does have chd(s) while parent doesn't
fixed: wrong "wrong case" message when using the move set to correct sysdefpath option
2866
clrmame Discussion / Re: Problem with 3.135a
« on: 31 August 2010, 18:22 »
could be .... I will check this
2867
clrmame Discussion / Re: Problem with 3.135a
« on: 31 August 2010, 14:14 »
hmm....could be a problem with the dupes check (disable it if you like in scanner advanced).
It should only alert you if:
- the set does not have chds and you got more than one instance (archive or folder) of it
- the set does have chds and you got more than two instances of it
wonder why it gives an alert for you.....
It should only alert you if:
- the set does not have chds and you got more than one instance (archive or folder) of it
- the set does have chds and you got more than two instances of it
wonder why it gives an alert for you.....
2868
clrmame Discussion / clrmamepro 3.135a released
« on: 30 August 2010, 21:32 »
3.135a
fixed: wrong warning about bios storage method in rebuilder when no bios sets are available
fixed: wrong "error while reading" warning during scan
misc: double setnames/descriptions are now renamed in any case during parsing dat
fixed: wrong warning about bios storage method in rebuilder when no bios sets are available
fixed: wrong "error while reading" warning during scan
misc: double setnames/descriptions are now renamed in any case during parsing dat
2869
News & Communication / clrmamepro 3.135a released
« on: 30 August 2010, 21:32 »
3.135a
fixed: wrong warning about bios storage method in rebuilder when no bios sets are available
fixed: wrong "error while reading" warning during scan
misc: double setnames/descriptions are now renamed in any case during parsing dat
fixed: wrong warning about bios storage method in rebuilder when no bios sets are available
fixed: wrong "error while reading" warning during scan
misc: double setnames/descriptions are now renamed in any case during parsing dat
2870
clrmame Discussion / Re: clrmame 3.135 keeps asking to fix neogeo bios set
« on: 30 August 2010, 21:10 »
ah ok...you didn't let cmpro import the 2nd instance of neogeo with a changed name....will change this for the next version so that double entries are forced to get renamed during parsing the dat.
2871
clrmame Discussion / Re: Error while reading:
« on: 30 August 2010, 20:53 »
should be fixed for next release
2872
clrmame Discussion / Re: new error, re: bios
« on: 30 August 2010, 20:25 »
ok, fixed for next release
2873
clrmame Discussion / Re: clrmame 3.135 keeps asking to fix neogeo bios set
« on: 30 August 2010, 20:17 »
hmm..interesting....
2874
clrmame Discussion / Re: clrmame 3.135 keeps asking to fix neogeo bios set
« on: 30 August 2010, 17:59 »
Thanks.
However I don't get any error.
The datfile holds the neogeo set twice...which is a bit dumb but cmpro imports it then as neogeo and neogeo_0.
I've zipped up your neogeo folder and the first scan only complains about missing files in neogeo_0. So fix-missing fixes them fine and that's all. New 'new scans' don't popup any message.
So....maybe you should
a) send me your original zipfile (maybe it's corrupt).
b) send me cmpro.ini plus the belonging .cmp file (settings folder) to that datfile
c) what does cmpro ask you in detail? What does it want to fix?
However I don't get any error.
The datfile holds the neogeo set twice...which is a bit dumb but cmpro imports it then as neogeo and neogeo_0.
I've zipped up your neogeo folder and the first scan only complains about missing files in neogeo_0. So fix-missing fixes them fine and that's all. New 'new scans' don't popup any message.
So....maybe you should
a) send me your original zipfile (maybe it's corrupt).
b) send me cmpro.ini plus the belonging .cmp file (settings folder) to that datfile
c) what does cmpro ask you in detail? What does it want to fix?
2875
clrmame Discussion / Re: clrmame 3.135 keeps asking to fix neogeo bios set
« on: 30 August 2010, 07:15 »
Can you send me the set and the used datfile?
2876
clrmame Discussion / Re: Error while reading:
« on: 30 August 2010, 07:14 »
A little bit more details are needed.
For example...
which dat are you using...what are the exact error messages in which files....how to do store your sets...
Since you're running it on Ubuntu, maybe you have to setup access rights correctly.
Send me the used datfile, the belonging *.cmp file (in cmpro's settings folder) for the used profile and cmpro.ini.
And maybe make some screenshots showing your folder with the files and the error message...
For example...
which dat are you using...what are the exact error messages in which files....how to do store your sets...
Since you're running it on Ubuntu, maybe you have to setup access rights correctly.
Send me the used datfile, the belonging *.cmp file (in cmpro's settings folder) for the used profile and cmpro.ini.
And maybe make some screenshots showing your folder with the files and the error message...
2877
clrmame Discussion / Re: new error, re: bios
« on: 29 August 2010, 06:48 »
yeah it's a rebuilder only warning. could be that if no bios are used both options are disanled and greyed out... hehe... ignore it for now.. will be fixed soon.
2878
clrmame Discussion / Re: new error, re: bios
« on: 28 August 2010, 09:16 »
it's only a warning which pops up when scanner and rebuilder bios set options differ (allow sep. bios and separate bios files). so check if they differ ( actually they are the negative form of each other. so enable the one and disable the other or vice versa). should work no matter if bios sets are used at all.
2879
clrmame Discussion / Re: [request]can i set different fix option to different rompath?
« on: 28 August 2010, 05:49 »
no. but why dont you use a diff-dat which only holds the differences between mame and mame plus? should be an easy task for logiqx' mamediff tool.
2880
clrmame Discussion / Re: clrmamepro 3.135 released
« on: 25 August 2010, 15:13 »
yeah....somethings for you in there...