Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All Threads*Show in Threaded Mode


SubjectWould it be possible ... new Reply to this message
Posted byRetroLover
Posted on07/15/05 01:48 PM



to change cmpro in that way, that if you load a profile for MESS, the warnings of not importable sets, like e.g. a2600 are not displayed.

In the meantime 24 sets are BIOS-less and so you have to click or press 24 times OK to get further or did I do something wrong?

Kind Regards,
RetroLover



SubjectFurthermore ... new Reply to this message
Posted byRetroLover
Posted on07/15/05 02:01 PM



Since all BIOS-less sets don't get imported, this results in further 17 warnings, that parentfolders don't exist and that the parent/clone relationship will be removed.

Is that somehow changeable to a more convenient method, without the warnings?

Best regards,
RetroLover



SubjectAnd another one ... new Reply to this message
Posted byRetroLover
Posted on07/15/05 03:21 PM



Please read this:

http://www.bannister.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=7&t=002584

Please tell me what you think about the whole thread here and at emuverse?

Regards,
RetroLover



SubjectRe: Would it be possible ... Reply to this message
Posted byRoman
Posted on07/18/05 02:05 AM



> to change cmpro in that way, that if you load a profile for MESS, the warnings
> of not importable sets, like e.g. a2600 are not displayed.

Profiler->Settings->Datfile Errors->Hide Common


Roman Scherzer



SubjectRe: Furthermore ... new Reply to this message
Posted byRoman
Posted on07/18/05 02:06 AM



> Is that somehow changeable to a more convenient method, without the warnings?

Profiler->Settings->Datfile Errors->Hide Common


Roman Scherzer



SubjectRe: And another one ... new Reply to this message
Posted byRoman
Posted on07/18/05 02:08 AM



> Please read this:
>
> http://www.bannister.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=7&t=002584
>
> Please tell me what you think about the whole thread here and at emuverse?
>
> Regards,
> RetroLover
>



Yawn...We got this discussion since 1997....both parties are right...if the name matches the one on the PCB, it should be used. If that means that you got different roms with equal names within a parent/clone relationship, well...clrmamepro will 'fix' that for you anyway...


Roman Scherzer



SubjectRe: Would it be possible ... new Reply to this message
Posted byRetroLover
Posted on07/18/05 06:56 AM



OK!

Regards,
RetroLover



SubjectRe: Furthermore ... new Reply to this message
Posted byRetroLover
Posted on07/18/05 06:57 AM



OK!

Regards,
RetroLover



SubjectRe: And another one ... new Reply to this message
Posted byRetroLover
Posted on07/18/05 06:58 AM



> > Please read this:
> >
> > http://www.bannister.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=7&t=002584
> >
> > Please tell me what you think about the whole thread here and at emuverse?
> >
> > Regards,
> > RetroLover
> >
>
>
>
> Yawn...We got this discussion since 1997....both parties are right...if the name
> matches the one on the PCB, it should be used. If that means that you got
> different roms with equal names within a parent/clone relationship,
> well...clrmamepro will 'fix' that for you anyway...
>
>
> Roman Scherzer
>

Yes it does fix it but it results in a non-merged set apple2c3, doesn't it?

Regards,
RetroLover



SubjectRe: And another one ... new Reply to this message
Posted byRoman
Posted on07/18/05 07:08 AM



> Yes it does fix it but it results in a non-merged set apple2c3, doesn't it?


It will remove parent/clone relationships, yes. Otherwise you'd kill files if you keep them fully merged. No way around it (well..unless a romrename is done).


Roman Scherzer



View All Threads*Show in Threaded Mode