Stephen Tjasink - *boblbobl - 4,225,730

Discussion of playback questions / problems. Any recording where people have playback problems should appear here.

Moderator: Chad

Post Reply
User avatar
Barthax
MARP Seer
MARP Seer
Posts: 691
Joined: Fri Sep 27, 2002 1:13 pm
Contact:

Stephen Tjasink - *boblbobl - 4,225,730

Post by Barthax » Fri Nov 28, 2014 6:43 am

http://replay.marpirc.net/inp/4/9/d/sjt ... mame30.zip
http://replay.marpirc.net/r/*boblbobl
Fails to insert a coin in MAME 0.30 (requires boblbobl extracted content). With MAME 0.31 it de-syncs around 70K and gets 73050 in the end.

User avatar
Barthax
MARP Seer
MARP Seer
Posts: 691
Joined: Fri Sep 27, 2002 1:13 pm
Contact:

Re: Stephen Tjasink - *boblbobl - 4,225,730

Post by Barthax » Mon Jan 05, 2015 7:05 am

Got playback functioning in MAME 0.30 with the "-playback inp\<file>" foible. Unfortunately, playback only works to 57410 with or without sound. MAME32 0.30 has no playback/record facility.

User avatar
Chad
Tournament Coordinator
Posts: 4463
Joined: Tue Mar 05, 2002 3:15 pm
Location: calif

Re: Stephen Tjasink - *boblbobl - 4,225,730

Post by Chad » Tue Jan 06, 2015 2:24 am

I get the same 57410 result. However when attempting to playback with new roms I got a warning that my BB3 rom should be crc=9202336e. After making the BOBLBOBL folder and copying the new roms in, in I don't get the mame30 failure and crc warning, but in reality my rom is from m33b6 and my only available BB3 rom is seemingly incorrect (crc=01f81936) though mame30 does not audit crc values. I think as long as the rom file names match mame30 doesn't complain if the crc is wrong. So, I have a theory the playback problem here may be due to incorrect roms. I do not have the mame30 version of boblbobl.zip with BB3 crc=9202336e to truly verify playback, so I can't confirm this does not playback.
-skito

User avatar
Barthax
MARP Seer
MARP Seer
Posts: 691
Joined: Fri Sep 27, 2002 1:13 pm
Contact:

Re: Stephen Tjasink - *boblbobl - 4,225,730

Post by Barthax » Tue Jan 06, 2015 6:03 am

Chad wrote:I get the same 57410 result. However when attempting to playback with new roms I got a warning that my BB3 rom should be crc=9202336e. After making the BOBLBOBL folder and copying the new roms in, in I don't get the mame30 failure and crc warning, but in reality my rom is from m33b6 and my only available BB3 rom is seemingly incorrect (crc=01f81936) though mame30 does not audit crc values. I think as long as the rom file names match mame30 doesn't complain if the crc is wrong. So, I have a theory the playback problem here may be due to incorrect roms. I do not have the mame30 version of boblbobl.zip with BB3 crc=9202336e to truly verify playback, so I can't confirm this does not playback.
Hmmm... I've been relying on the EgoElf MAME 0.30 DAT file which lists bb3 as 0x01f81936 CRC. I've got ClrMAMEPro hunting through my ROMs for a 0x9202336e. I'm not finding this CRC mentioned on a Google search - there's usually hints of people hunting for a non-existant ROM at least with a CRC search or a MAME source page buried somewhere. I'll download the MAME 0.30 source to have a hunt through also.

[Edit:]
Sure enough:
ROM_START( boblbobl_rom )
ROM_REGION(0x1c000) /* 64k+64k for the first CPU */
ROM_LOAD( "bb3", 0x00000, 0x8000, 0x9202336e )

Hmmm... a lot of CRCs were inverted back then if they were incorrect, so that'd be a 0x6dfdcc91 potential too. I don't seem to have either if they existed in the wild. :(

BeeJay
MARPaltunnel Wrists
MARPaltunnel Wrists
Posts: 583
Joined: Fri Jun 17, 2005 1:40 am

Re: Stephen Tjasink - *boblbobl - 4,225,730

Post by BeeJay » Thu Jan 08, 2015 6:51 am

Dang it all. It was only just a couple of months back that I had a big clean-out of old CDRs and threw out one that had a Mame030B roms label on it. :(

Post Reply