Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All Threads*Show in Threaded Mode


SubjectIssue with CHDs and split sets new Reply to this message
Posted byuTaR
Posted on01/01/08 10:51 AM



Hi

I have a bit of an issue with having to double up CHDs when using split sets. For example with Mame 122u2 Clrmamepro complains that 949jab02.chd is not in the directory "gtfrk3ma" however the chd is in the parent directory "gtfrk3m" and Mame runs both without complaining about any missing CHDs.

I thought that the idea of split sets (as oppose to non-merged sets) was that the clone sets only had to contain any different / additional roms, and as such I'm not sure why Clrmamepro is complaining. Or is my understanding incorrect?


Thanks


Utar









SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byRoman
Posted on01/04/08 06:20 AM



> I thought that the idea of split sets (as oppose to non-merged sets) was that
> the clone sets only had to contain any different / additional roms, and as such


yep...correct...but maybe the chd belongs to the clone and not to the parent. I'm currently on holiday, I will check the chd in question on sunday. But I'm sure if cmpro tells you it's not correctly placed, it's not correctly placed 8)


Roman Scherzer



SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byuTaR
Posted on01/04/08 01:53 PM



> yep...correct...but maybe the chd belongs to the clone and not to the parent.
> I'm currently on holiday, I will check the chd in question on sunday. But I'm
> sure if cmpro tells you it's not correctly placed, it's not correctly placed 8)
>
>
> Roman Scherzer

Thanks for the reply Roman

949jab02.chd is required by both the parent and clone sets, I have double checked this by moving the file out of the parent directory. Anyway if it was just a clone chd and not a parent chd Clrmamepro would move the unrequired copy to the backup folder!

There are other examples too of the samething happening, I have had to make copies of parent chds for clone directories in the past.

Hope you had a good holiday by the way!







SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byjmac1718
Posted on01/04/08 07:02 PM



> > yep...correct...but maybe the chd belongs to the clone and not to the parent.
> > I'm currently on holiday, I will check the chd in question on sunday. But I'm
> > sure if cmpro tells you it's not correctly placed, it's not correctly placed
> 8)
> >
> >
> > Roman Scherzer
>
> Thanks for the reply Roman
>
> 949jab02.chd is required by both the parent and clone sets, I have double
> checked this by moving the file out of the parent directory. Anyway if it was
> just a clone chd and not a parent chd Clrmamepro would move the unrequired copy
> to the backup folder!
>
> There are other examples too of the samething happening, I have had to make
> copies of parent chds for clone directories in the past.
>
> Hope you had a good holiday by the way!
>
I concur, I am having a similar issue. Thought it was a bug with 122u2, but the same issue exists when auditing 122u3.


SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byRoman
Posted on01/06/08 07:54 AM



I'm back from holiday and haven't checked u2 or u3 yet. Will have a look at everthing today...


Roman Scherzer



SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byRoman
Posted on01/06/08 10:56 AM



ok...found the problem. Will release a new version later today.


Roman Scherzer



SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byuTaR
Posted on01/06/08 03:06 PM



> ok...found the problem. Will release a new version later today.
>
>
> Roman Scherzer
>

Thanks Roman, the new version is working great.

On another matter is there any chance I can make a request?

It would be good if you could drag and drop new chd files into clrmame as with zip files, so that clrmame could automatically create a new directory and copy the chd file. It's not a bit deal having to do this manually, I just thought it may be helpful for releases where lots of new chds are added.


Regards








SubjectRe: Issue with CHDs and split sets Reply to this message
Posted byRoman
Posted on01/06/08 03:15 PM



drag'n drop in the scanner internally uses the rebuilder. Since the rebuilder doesn't rebuild chds at the moment (no big deal to add that though) it don't work with chds.

What you still can do: move your (maybe even wrongly named) chd in any rompath (not in a subfolder) and scan. Cmpro detects it as wrong placed and automatically puts it in the correct place (incl. creating a subfolder for it etc..etc..)


Roman Scherzer



SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byuTaR
Posted on01/06/08 03:20 PM




> What you still can do: move your (maybe even wrongly named) chd in any rompath
> (not in a subfolder) and scan. Cmpro detects it as wrong placed and
> automatically puts it in the correct place (incl. creating a subfolder for it
> etc..etc..)
>
>
> Roman Scherzer

Good idea, I hadn't thought of that.

In future I will just copy chds to the backup folder. Will Clrmame then move the chd, or create a copy and leave the original in the backup folder?






SubjectRe: Issue with CHDs and split sets new Reply to this message
Posted byRoman
Posted on01/06/08 03:52 PM



I said rompath, not backup folder... a missing chd won't be picked up from backup (roms are picked up though). Simply copy a new chd to one of your rompaths before scanning (iirc chd + name + unneeded + fix has to be on)


Roman Scherzer



View All Threads*Show in Threaded Mode