CiroConsentino |
Frontend freak!
|
|
|
Reged: 09/21/03
|
Posts: 6211
|
Loc: Alien from Terra Prime... and Brazil
|
|
Send PM
|
|
|
Commodore 128 (PAL)... not clone of Commodore 128 (NTSC) ?
#341326 - 06/11/15 03:35 AM
|
|
|
I was browsing MESS machines and found several clones for Commodore 128 (NTSC) (name c128 driver c128.c). Shouldn't Commodore 128 (PAL) (name c128p driver c128.c) be a clone of c128 ?
|
Ciro Alfredo Consentino
home: http://emuloader.mameworld.info
e-mail: [email protected]
|
|
Tafoid |
I keep on testing.. testing.. testing... into the future!
|
|
|
Reged: 04/19/06
|
Posts: 3137
|
Loc: USA
|
|
Send PM
|
|
|
Re: Commodore 128 (PAL)... not clone of Commodore 128 (NTSC) ?
[Re: CiroConsentino]
#341359 - 06/12/15 01:20 AM
|
|
|
> I was browsing MESS machines and found several clones for Commodore 128 (NTSC) (name > c128 driver c128.c). > Shouldn't Commodore 128 (PAL) (name c128p driver c128.c) be a clone of c128 ?
Only the driver author can answer that. It has been that way for over 2.5 years and does allow for each set to have a 'romset.zip'. If it were a clone of c128, c128p would not show up on the internal UI because there would be no c128p romset (in split merge mode, a .zip for each set and it's unique roms), since all the parts of the c128/c128p are the same and therefore making the cloneset redundant.
Should it be changed? I dunno. Refer to my first statement
|
|
|