What's new
By:

Puzzle Bobble MVS sound issue

Retro Mecano

Retro Mecano

Enthusiast
Joined
Dec 10, 2024
Messages
83
Reaction score
92
Location
Tunisia
Hi,

I had a Puzzle Bobble cartridge lying around at the bottom of a box, and I wanted to play a game. It worked fine, except for a few tracks that had a heavy, really unpleasant crackling sound.
I did the basics (cleaning, suspect soldering), but nothing. So I moved on to reading the maskroms (P, V, and M), and they were all fine, according to the Mame ROMs. I pushed it even further by changing the NeoPCM and the LS139. Still nothing.

I happened to get my hands on another Puzzle Bobble cartridge, and, surprise, it was exactly the same sound glitch! So I immediately suspected my slot. I put in 6 other games (MS1, 2, 3, Streethoop, Sh.Troopers, Samurai 4), and they all worked perfectly.

So what's this all about? PS: The audio glitch is exactly the same as the one in this video:

View: https://youtu.be/HFt3c4hbBwA
 
What the crc of your M1 ?
Maybe the problem is finding the correct bootleg audio, a lot of version on the web.
Now the prog board have some patch modified to work with dip 40 eprom so you have to find the correct romset according with the M1.

this is the audio of bootleg version:
View attachment 185125
according with mame db
<dataarea name="ymsnd:adpcma" size="0x380000">
<!-- 0x000000-0x1fffff empty -->
<rom name="u8" offset="0x200000" size="0x100000" crc="0840cbc4" sha1="1adbd7aef44fa80832f63dfb8efdf69fd7256a57" />
<rom name="u9" offset="0x300000" size="0x080000" crc="0a548948" sha1="e1e4afd17811cb60401c14fbcf0465035165f4fb" />
</dataarea>
Click to expand...
You missing half v1 since its 1Mb ?
It have also offset of 2MB maybe its not working as V1 and V2, maybe its not correct romset.
 
Last edited:
maybe this is the correct romset ?
the only one with v1 and v2 of 512k

pbobblenba "Puzzle Bobble (set 3)(Neo-Geo) (bootleg)"

1742084956381.png
 
pierpa86 said:
maybe this is the correct romset ?
the only one with v1 and v2 of 512k

pbobblenba "Puzzle Bobble (set 3)(Neo-Geo) (bootleg)"

1742084956381.png
Click to expand...
I have recheked in Arcadefraidi V3 and M1 and EP1, against original roms, and they are matching the CRC.
 
pbobblenba set is known as a bad dump of pbobblenb

As you can see in comparison picture below, V1 EPROM on your bootleg needs to be populate with 1MB of data (on pbobblenba 083b.v1 + 083b.v2 = d96-01.v3 [pbobblenb] or u8 [pbobblenb]) and V2 EPROM with 512 KB of data (d96-05.v4 for pbobblen and u9 for pbobblenb [same data])

ep7G6tI.png


To resume EPROMS on your bootleg has to be :
EPROM.V1 crc 0840cbc4 size 1 048 576 bytes
EPROM.V2 crc 0a548948 size 524 288 bytes

Not sure of it because i can test in real hardware but can solve sound glitch.

Best regards
 

Attachments

JacKc said:
pbobblenba set is known as a bad dump of pbobblenb

As you can see in comparison picture below, V1 EPROM on your bootleg needs to be populate with 1MB of data (on pbobblenba 083b.v1 + 083b.v2 = d96-01.v3 [pbobblenb] or u8 [pbobblenb]) and V2 EPROM with 512 KB of data (d96-05.v4 for pbobblen and u9 for pbobblenb [same data])

ep7G6tI.png


To resume EPROMS on your bootleg has to be :
EPROM.V1 crc 0840cbc4 size 1 048 576 bytes
EPROM.V2 crc 0a548948 size 524 288 bytes

Not sure of it because i can test in real hardware but can solve sound glitch.

Best regards
Click to expand...
it's not that easy i think, because the prog board has been modified on some tracks to accept the 500k v roms, so maybe the tracks need to be corrected first.
and you need also at least one 27c160 as v1.
 
Indeed...According to Retro Mecano's video, it seems this is this bootleg :

https://www.mvs-scans.com/images/c/c1/Bust_a_move_bootleg2_b1_front.jpg
File:Bust_a_move_bootleg2_b1_front.jpg

V1 and V2 on NEO-MVS PROG G-2 are on TC574200D-150 (4 MEGA BIT (262,144 WORD x 16BIT 524,288 WORD x 8 Bit / CMOS U.V. ERASABLE AND ELECTRICALLY PROGRAMMABLE READ ONLY MEMORY).

So bootlegeers probably only use data from d96-01-V3 (size 1MB) from original pbobblen set which has been splitted into 512 KB part to be fit on V1 and V2. The result is missing data from d96-05.v4 which maybe can explain unpleasant crackling sound and maybe missing tracks.

It would be interesting to have V1 and V2 dump from Retro Mecano Puzzle Bobble bootleg to see how look like datas.
 
JacKc said:
Indeed...According to Retro Mecano's video, it seems this is this bootleg :

https://www.mvs-scans.com/images/c/c1/Bust_a_move_bootleg2_b1_front.jpg
File:Bust_a_move_bootleg2_b1_front.jpg

V1 and V2 on NEO-MVS PROG G-2 are on TC574200D-150 (4 MEGA BIT (262,144 WORD x 16BIT 524,288 WORD x 8 Bit / CMOS U.V. ERASABLE AND ELECTRICALLY PROGRAMMABLE READ ONLY MEMORY).

So bootlegeers probably only use data from d96-01-V3 (size 1MB) from original pbobblen set which has been splitted into 512 KB part to be fit on V1 and V2. The result is missing data from d96-05.v4 which maybe can explain unpleasant crackling sound and maybe missing tracks.

It would be interesting to have V1 and V2 dump from Retro Mecano Puzzle Bobble bootleg to see how look like datas.
Click to expand...
Actually this is the set that i have used to write the V1, V2 and M eproms.

The CRCs are matching those you have mentionned.

I have even tried another PROG board. Exactly same issue.

Switched PCM chip, LS139, same thing..
20250319_171916.jpg
 
JacKc said:
Indeed...According to Retro Mecano's video, it seems this is this bootleg :

https://www.mvs-scans.com/images/c/c1/Bust_a_move_bootleg2_b1_front.jpg
File:Bust_a_move_bootleg2_b1_front.jpg

V1 and V2 on NEO-MVS PROG G-2 are on TC574200D-150 (4 MEGA BIT (262,144 WORD x 16BIT 524,288 WORD x 8 Bit / CMOS U.V. ERASABLE AND ELECTRICALLY PROGRAMMABLE READ ONLY MEMORY).

So bootlegeers probably only use data from d96-01-V3 (size 1MB) from original pbobblen set which has been splitted into 512 KB part to be fit on V1 and V2. The result is missing data from d96-05.v4 which maybe can explain unpleasant crackling sound and maybe missing tracks.

It would be interesting to have V1 and V2 dump from Retro Mecano Puzzle Bobble bootleg to see how look like datas.
Click to expand...
Update,

I moved the whole P znd V roms to a test Progbk1 board i have, it made the same issue, but after moving the jumpers a little bit, it finally worked!

Now i have to figure out what is wrong with my Progtop board, as the jumpers configuration is exactly matching the mvs-scan layout.

Coud it be that the LS139 is responsible?
 
You must log in or register to reply here.
Back
Top