Home Page Forums MAME MAME SVN builds - new driver flood

With the backwards compatibility of the Japanese Master System, should the .sg extension be added to load those games? SG-1000 Bank Panic works fine under smsj (just renamed to .sms for now).

The ace files are snapshots, but they have always been implemented using a cartslot. Why, I do not know. That's just another thing that needs to be fixed.

The cassette loading is not working yet, probably because of some small emulation issue. The .tap file decoding is working because I see the header being read in, but for some reason the bios code doesn't see the end of the header block.

Thanks for checking the driver.

Thank you for your answer.
I read already, that the cassette loading is not working yet.
My problem is, if i load a cartridge/snapshot, I am not able to use the keyboard.

SG-1000 does not have a BIOS. Othello Multivision on the other hand has a built-in Othello cartridge.

Thank you for the info. Now it is clear for me.

omv : omvbios.bin (8192 bytes) - NO GOOD DUMP KNOWN
romset omv [sg1000] is best available

The external Othello cartridge has a different size (32768 bytes).

r3272
[JUPITER] Some tape loading fixes.

Not know the actual tape loading status.
If i try to load a tape file (.wav) as example moonbuggy.wav
I get a error.

LOAD moonbuggy g

load moonbuggy
Dict: moonbuggy ERROR 10

With other tape games I get the same error.

Some tap (.wav) files will not recognized.
Example: Acevaders

Error when loading the image: Unspecified error

With EightyOne emu I can load these games.

I have tried the acevaders tap file, that loaded something into memory. Looking at the wav files, they seem to be in a format which the MESS core doesn't understand (yet). A clearer error message would have been nice, I know.

SVN revision 3273

Correct : 617
Incorrect : 11
Total : 628

I have a question to the Mess -verifyroms

vip : chip8.bin (512 bytes) - INCORRECT CHECKSUM:
EXPECTED: CRC(438ec5d5) SHA1(8aa634c239004ff041c9adbf9144bd315ab5fc77)
FOUND: CRC(5e035c8e)
romset vip is bad

mekd2 : jbug.rom (1024 bytes) - INCORRECT CHECKSUM:
EXPECTED: CRC(a2a56502) SHA1(60b6e48f35fe4899e29166641bac3e81e3b9d220)
FOUND: CRC(5ed08792)
romset mekd2 is bad

cybikov1: cyrom112.bin (32768 bytes) - INCORRECT CHECKSUM:
EXPECTED: CRC(9e1f1a0f) SHA1(6fc08de6b2c67d884ec78f748e4a4bad27ee8045)
FOUND: CRC(268da7bf)
romset cybikov1 is bad

cybikoxt: cyrom150.bin (32768 bytes) - INCORRECT CHECKSUM:
EXPECTED: CRC(18b9b21f) SHA1(28868d6174eb198a6cec6c3c70b6e494517229b9)
FOUND: CRC(268da7bf)
romset cybikoxt [cybikov1] is bad

comx35p : 80.column.card.u3 (2048 bytes) - INCORRECT LENGTH: 17 bytes
comx35p : mc6845.font.u (2048 bytes) - NO GOOD DUMP KNOWN
romset comx35p is bad
comx35n : 80.column.card.u3 (2048 bytes) - INCORRECT LENGTH: 17 bytes
comx35n : mc6845.font.u (2048 bytes) - NO GOOD DUMP KNOWN
romset comx35n [comx35p] is bad

newbrain: cop420.419 (1024 bytes) - INCORRECT LENGTH: 8192 bytes
newbrain: 8248r7.453 (4096 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset newbrain is bad

newbraim: cop420.419 (1024 bytes) - INCORRECT LENGTH: 8192 bytes
newbraim: 8248r7.453 (4096 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset newbraim is bad

newbraia: cop420.419 (1024 bytes) - INCORRECT LENGTH: 8192 bytes
newbraia: 8248r7.453 (4096 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset newbraia [newbrain] is bad

newbraiv: cop420.419 (1024 bytes) - INCORRECT LENGTH: 8192 bytes
newbraiv: 8248r7.453 (4096 bytes) - NOT FOUND - NO GOOD DUMP KNOWN
romset newbraiv [newbrain] is bad

If for these drivers no (good) dumps exist, is it no better to show as best available rom sets ?

SVN revision 3273

VIC 20/1001
Not have problems to load PAL/NTSC cartridges.
Also no more have multisession problems. But not sure, maybe i mistake it with other Commodore drivers.

C16/Plus4
The cartridge Jack Attack.bin is not working.

Plus4
On C16 emu i can load and start the Jack Attack snapshot file (.prg)
On Plus 4 i can load but not start the same file.

CBM30xx/40xx/80xx
Some drivers are marked as working on GUI. But during the initializing these drivers freeze.

All those -verifyroms errors indicate that you need different files. You're right that the NO GOOD DUMP KNOWN stuff is not a problem, but you'll notice that each of those sets also has an INCORRECT LENGTH error on a different file - that's why it's saying they're bad.