Bleemcast conspiracy *disclaimer tin foil necessary*

General Dreamcast discussion applies here. Before posting here please check the other forums in the Dreamcast section to see if your topic would fit better in those categories.

Moderator: mazonemayu

Forum rules
Please check the other forums in the Dreamcast section before posting here to see if your topic would fit better in those categories. Example: A new game/homebrew release would go in the New Releases/Homebrew/Emulation section: http://dreamcast-talk.com/forum/viewforum.php?f=5 or if you're having an issue with getting your Dreamcast to work or a game to boot it would go in the Support section: http://dreamcast-talk.com/forum/viewforum.php?f=42
User avatar
SMiTH
Feet of Fury
Posts: 569

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post#61 » Sun Nov 17, 2019 5:31 pm

i wish darc would respond to what i posted here:

viewtopic.php?f=2&t=12161&start=40#p122520

i would add that i still think the leak was intentional, and the 5 color dc story is starting to seem more like bullshit once again.
:)
Image

User avatar
SMiTH
Feet of Fury
Posts: 569

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post#62 » Mon Nov 18, 2019 4:45 pm

megavolt85 wrote:dreamshell can read/write raw dump vmu


can someone test a bleemcast save with dreamshell?
Image

User avatar
SMiTH
Feet of Fury
Posts: 569

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post#63 » Wed Dec 04, 2019 12:05 am

I compared the original ip.bin's from the bleem betas (ALL COLORS) to the ip.bin from the cracked bleem beta.
There are many differences in the hex code between the two ip.bin's
But, I think that I might have found the custom code that was used to lock the dreamcast to a specific beta?
I could be wrong here...

Using a dummy file to write to and then modifying the script from the leaked beta to not delete files after creating the .nrg, results in a temp file that is usually split data of the ip.bin.
Instead it writes the hex code to the dummy file, and this same hex code is found in the original bleem beta ip.bin and not in the modified ip.bin from the cracked beta.
maybe?
:)

The file size of the original bleem beta ip.bin is 37,376 bytes.
The file size of the cracked bleem beta ip.bin is 32,768 bytes.
This means that there is custom code added.
The original ip.bin's are the same for each color beta.

Here is the custom hex code that I think is added to the ip.bin to lock the beta to a specific dreamcast..
This hex chain repeats 5 times.
Image

I attached the bleem beta ip.bin's
The archive contains the original ip.bin from the beta and the modified ip.bin from the cracked beta.
Attachments
b!c beta ip.bins.rar
(19.61 KiB) Downloaded 4 times
Image

User avatar
megavolt85
BFG-10K
Posts: 213

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post#64 » Wed Dec 04, 2019 10:45 am

SMiTH wrote:The file size of the original bleem beta ip.bin is 37,376 bytes.


You have a damaged IP.BIN
IP.BIN these are the first 16 sectors of the session
16*2048=32768
Cannot be different

User avatar
SMiTH
Feet of Fury
Posts: 569

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post#65 » Wed Dec 04, 2019 5:14 pm

megavolt85 wrote:You have a damaged IP.BIN
IP.BIN these are the first 16 sectors of the session
16*2048=32768
Cannot be different


So this means that the extra code is a red herring.
I tested the original ip.bin and it never worked.
Image

  • Similar Topics
    Replies
    Views
    Last post

Return to “Lounge”

Who is online

Users browsing this forum: No registered users