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.
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
SMiTH
Super Sonic
Posts: 1518

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by SMiTH »

Tried many different ways to extract ip.bin from the miltemp bleem beta to no avail.

Tried running a vm of win2000 and early versions of nero to use the BURNMIL.TXT process to create a bleem disk. (almost got it)
Tried merging the audio session + data session from MILTEMP to create nrg, iso, cdi, etc. (NOPE!)

I will attach the miltemp folder again if anyone would like to give it a try.

The point is to build an iso of the files that were originally used by betatesters. (using the original method)

In doing so, the created miltemp iso will include the original ip.bin that can then be extracted.
Once extracted a file comparison of heartbreak diary ip.bin can be done.
This would document the exact hex data that was used to modify the ip.bin on each beta color and each color dreamcast consoles to allow beta testing on locked dreamcasts.
If this is 100% true then each color beta should show different hex data in each ip.bin.

Here are the instructions to create a bleem disk using the leaked files.
If some1 creates a disk using miltemp files correctly pls rip the disk with diskjuggler to a cdi.
Then each beta color folder can be done as well. (from the original leaked files)

**The versions of bleem beta that exist as selfboot and working found online do not use the original miltemp ip.bin
(they also used cracked 1BLEEM.BIN)
***A bleem disk created using the leaked files/miltemp should result in a non booting disk. (maybe not since i added cracked blue beta)
****This miltemp archive actually has files added to help some1 figure it out.
I think I added an audio file, bleem blue beta cracked and image.nrg from my attempt at creating disk.

Some1 can find the original miltemp in one of the posts in this thread.
It should be missing the audio wav, image.nrg, and will have no cracked beta 1bleem.bin
Any way to create a bleem.nrg using this method is still something useful.

Code: Select all

PREPARING TO BURN A DISC
------------------------
 1. Unzip Zip into "C:\MILTEMP\"
 2. Open Nero.
 3. Cancel all Nero windows.

BURNING THE AUDIO TRACK
-----------------------
 1. FILE | OPEN
 2. Change Directory to "C:\MILTEMP"
 3. Change File Type to "*.NRA"
 4. Select File called "AUDIO" (or "AUDIO.NRA")
 5. CD-RECORDER | CHOOSE RECORDER
 6. Select your CDROM Recorder and click OK
 7. FILE | WRITE CD
 8. Click the "WRITE" button.
 9. Allow write to complete and then "DISCARD" messages

CREATING THE DATA IMAGE
-----------------------
 1. CD-RECORDER | CHOOSE RECORDER
 2. Select Image Recorder, and click OK
 3. FILE | OPEN
 4. Make sure Directory is "C:\MILTEMP"
 5. Change File Type to "*.NRI"
 6. Select File called "ISO" (or "ISO.NRI")
 7. Click OK when Nero reports the files were found/refreshed
 8. FILE | WRITE CD
 9. Click the "WRITE" button, and an Image FileName box appears
10. Make sure Directory is "C:\MILTEMP"
11. Enter "IMAGE".NRG" in the Filename box, if not already set
12. Click "SAVE"
13. Allow write to complete and then "DISCARD" messages

BUILDING THE DATA IMAGE
-----------------------
 1. Open a DOS Window without closing Nero
 2. Change directory to "C:\MILTEMP\"
 3. Enter "BUILDNRG.BAT"
 4. Close DOS Window and return to Nero

BURNING THE DATA TRACK
----------------------
 1. CD-RECORDER | CHOOSE RECORDER
 2. Select your CD Burner and click OK
 3. FILE | BURN IMAGE
 4. Make sure Directory is "C:\MILTEMP"
 5. Select File called "BLEEM" (or "BLEEM.NRG")
 6. Click the "WRITE" button.
 7. Allow write to complete and then "DISCARD" messages

CLOSING NERO
------------
 1. Close Nero and do NOT save any changes when asked
Attachments
MILTEMP.rar
(1.07 MiB) Downloaded 61 times
Last edited by SMiTH on Sun Oct 15, 2023 10:34 pm, edited 2 times in total.

User avatar
MoeFoh
1300
Posts: 1384

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by MoeFoh »

Nevermind - the IP.BIN I was using was in raw 2352 byte format - meaning it had header & ecc data, so the comparison was in error.
Last edited by MoeFoh on Sun Oct 15, 2023 1:35 pm, edited 7 times in total.

SMiTH
Super Sonic
Posts: 1518

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by SMiTH »

MoeFoh wrote:It looks to me like IP.BIN is inside of ISO16.RAW. Extracted 32,768 bytes from this file and did a Compare by Content with Total Commander. It found 38 areas to be different than the DPS IP.BIN.
Yes, this is how I originally compared the files (*ISO16.RAW-ip.bin miltemp, ip.bin heartbreak) in a hex editor.
I copied each at same file size of an ip.bin in hex.. (at where they should start and end) then cut each file hex data and save them as ip.bin, then compared both of the files...If you see the size of iso16.raw is larger than a standard ip.bin.

iso16.raw is the ip.bin of the miltemp bleem but when using the batch file it cuts/splits part of this data when building the bleem disk.
This is the reason for creating an actual miltemp disk.
(getting the bleem ip.bin and not a hex data version that might not be correct due to the iso16.raw file size before a cut/split etc)
Last edited by SMiTH on Sat Oct 14, 2023 11:58 pm, edited 1 time in total.

User avatar
MoeFoh
1300
Posts: 1384

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by MoeFoh »

SMiTH wrote:
MoeFoh wrote:It looks to me like IP.BIN is inside of ISO16.RAW. Extracted 32,768 bytes from this file and did a Compare by Content with Total Commander. It found 38 areas to be different than the DPS IP.BIN.
Yes, this is how I originally compared the files (*ISO16.RAW-ip.bin miltemp, ip.bin heartbreak) in a hex editor.
I copied each at same file size of an ip.bin in hex and then compared.. (at where they should start and end)
If you see the size of iso16.raw is larger than a standard ip.bin.
iso16.raw is the ip.bin of the miltemp bleem but when using the batch file it cuts/splits part of this data when building the bleem disk.
This is the reason for creating an actual miltemp disk.
(getting the bleem ip.bin and not a hex data version that might not be correct due to the iso16.raw file size before a cut/split etc)
True, we will never know about 100% accuracy until we extract IP.BIN/ISO16.RAW from the original working CD.
Last edited by MoeFoh on Mon Oct 16, 2023 11:45 am, edited 4 times in total.

SMiTH
Super Sonic
Posts: 1518

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by SMiTH »

well, I have tried many times to create a true bleem.nrg using miltemp method.
I know some1 can figure it out.

as far as my issue with win2000 vm using older nero version 3020, the only real issue was aspi layer.
i'm sure if some1 can get the perfect setup to use older nero version and their optical drive then the miltemp method will work without an issue.

then each beta color could be created (bleem.nrg) and each beta color ip.bin could be extracted..then compared to heartbreak diary ip.bin
then document the exact hex data that was modified to lock each dreamcast color to each bleem beta color
:)

User avatar
MoeFoh
1300
Posts: 1384

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by MoeFoh »

SMiTH wrote:well, I have tried many times to create a true bleem.nrg using miltemp method.
I know some1 can figure it out.

as far as my issue with win2000 vm using older nero version 3020, the only real issue was aspi layer.
i'm sure if some1 can get the perfect setup to use older nero version and their optical drive then the miltemp method will work without an issue.

then each beta color could be created (bleem.nrg) and each beta color ip.bin could be extracted..then compared to heartbreak diary ip.bin
then document the exact hex data that was modified to lock each dreamcast color to each bleem beta color
:)
What do you mean by beta color, dreamcast color?

SMiTH
Super Sonic
Posts: 1518

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by SMiTH »

MoeFoh wrote:What do you mean by beta color, dreamcast color?
read through this thread from the first post on.
there is some tinfoil but alot of it is fact.
the story goes that each color bleem beta was locked to corresponding dreamcasts that had a color sticker on them. (a way to keep the betas from leaking and rendering them only useful on specific color dreamcast etc)
the idea is that the ip.bin of each bleem color was modified and so were each of the dreamcasts. (locking specific color beta to specific color dc)
i'm still 50/50 on the entire concept but have sorta given in to megavolt and darc's theory. or not a theory but a fact that I still speculate lol.
allegedly rand confirmed it, but in reality he did not say much and left it somewhat still unanswered.
so, here we are.

User avatar
MoeFoh
1300
Posts: 1384

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by MoeFoh »

See post #291 from darc.

After taking a second look, I'm highly suspicious the method described in post #282 of creating a bootable cd ever worked (at least with tools in 2023 - maybe it worked with a specific version of NERO way back in 2000). ISO16.RAW size should be a multiple of 2352 - it is not. It's missing the 1st 16 bytes of header data at the start. One would expect a size of 16 * 2352 = 36,632 from ISO16.RAW.
Last edited by MoeFoh on Mon Oct 16, 2023 9:18 pm, edited 5 times in total.

User avatar
MoeFoh
1300
Posts: 1384

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by MoeFoh »

Nothing notable in compares the IP.BIN of DPS, BLUE & YELLOW.
BLUE has a logo MR file inserted, so that block shows up as different.
Attachments
IP.BIN.7z
IP.BIN of DPS, BLUE & YELLOW
(10 KiB) Downloaded 60 times
Last edited by MoeFoh on Mon Oct 16, 2023 11:07 pm, edited 2 times in total.

SMiTH
Super Sonic
Posts: 1518

Re: Bleemcast conspiracy *disclaimer tin foil necessary*

Post by SMiTH »

MoeFoh wrote:After taking a second look, I'm highly suspicious the method described in post #282 of creating a bootable cd ever worked. ISO16.RAW size should be a multiple of 2352 - it is not. It's missing the 1st 16 bytes of header data at the start. One would expect a size of 16 * 2352 = 36,632 from ISO16.RAW.
So if the miltemp method never worked what does that even mean?
That was what the beta testers used to create the different color bleem beta disks.

I have been on this topic since 2019 but in reality it goes back further. (2008ish?)
And so far no1 has created a disk using the miltemp method.

Looking at the bleem rainbow books it appears only one ip.bin is used. <--
So then the different beta color ip.bin theory of locking to different color dreamcast consoles is bs.
LOL

Only other scenario is 1bleem.bin has data to lock to each console or its bs.
But, no1 has cracked them.
Well it was said all were cracked and all were the same.

So, why 20 years after the fact no1 has shown any proof of this?
Just a leaked "blue" and we have gone with the story since 2003.
Its hard to believe no1 since the original cracked beta leak has cracked each color.

The miltemp archive i posted earlier actually has files added to help some1 figure it out.
I think I added an audio file, bleem blue beta cracked and image.nrg from my attempt at creating a disk.
The audio file was from the echelon archive that was used originally for mil cd exploit to create dc isos.
I figure this is the same audio file rand would have used as well.

Some1 can find the original miltemp in one of the posts in this thread.
It should be missing the audio wav, image.nrg, and will have no cracked beta 1bleem.bin

If you modify the batch to keep files it adds 2 temp files which are what i assume is split from the ip.bin?
Maybe view hex data from the split files and find the same hex in ip.bin then remove those sections creates the proper ip.bin?
Or maybe those 2 temp files have other data needed to create a proper nrg file? because it does merge data as well.
Idk? some1 should take the time to figure wtf all of this means lol

Here is the rainbow book from an earlier post in this thread.
Attachments
Bleem Rainbow Books (US).zip
(1.55 MiB) Downloaded 62 times

  • Similar Topics
    Replies
    Views
    Last post