Home Page Forums MAME MAME MESS Dumping Project ?

Oh, so the carts are the same? Was it overdumped or something?

Hard to say, because of missing hardware and can not test in practice. For the rest, I have not the technical knowledge.

In my dump, one byte was wrong and some bytes to reach 16Kb at the end was missing.

anna wu: its more likely that your dump was right for the one byte. which byte was it and what value should it have been/was it?

LN

0x48 to 0x23 at address 0x2000 changed
The missing bytes was filled with FFFF until 0x3FFF

As i wrote to anna:

with 0x23:

9fff 22 " inx d
a000 23 # dcx d
a001 24,25,26 $%& lxi d,2625h
a004 27,28 '( gti a,28h
a006 29 ) ldax b
a007 2a * ldax d

with 0x48:

9fff 22 " inx d
a000 48,24 H$ di
a002 25,26,27 %&' gtiw v.26h,27h
a005 28,29 () ldaw v.29h
a007 2a * ldax d

would be odd to have a "disable interrupt" out of the blue.
also 0x48 is also the first byte of the file (0x0000, mapped at 0x8000), so there
could have been a fluke in capture in the higher address lines.

(LN ill PM you soon)

Hi

Ive updated my procedure to dump the BIOS with more details and example code to decompress/checksum the results :

http://ploguechipsounds.blogspot.com/2009/07/rom-trojaning-super-cassette-vision.html (near the end)

Some new info contained in the readme.txt:

Epoch NTSC (jp) configuration (as the Japanese team provided)

CPU uPD7801G 4.0 MHz
VDC EPOCH TV-1 14.31818 MHz
SOUND UPD1771C 6.0 MHz
BIOS md5 (unknown)

***********

Yeno (PAL) configuration (im the owner)

CPU uPD7801G 3.78 MHz
VDC EPOCH TV-1A 13.4 MHz
SOUND UPD1771C 6.0 MHz
BIOS MD5: 635a978fd40db9a18ee44eff449fc126

It would be nice to have confirmation of the MD5 of my dump, especially since there are good chances PAL/NTSC bioses may differ.

Thanks again for your help, David.

Could you supply sha1 and crc hashes as well? Makes it easier to verify

no prob.

PAL SCV BIOS.ROM :
MD5 : 635a978fd40db9a18ee44eff449fc126
SHA1 : 6e89d1227581c76441a53d605f9e324185f1da33
CRC32 : 7ac06182

great, thanks.