|darc| wrote:What's tinfoil about it? I still have the uncracked, original rainbow files. There were five colors (blue, green, yellow, purple, and orange), so that's more than regions available. If these betas aren't locked to specific Dreamcasts, then what exactly are they locked to?
There is a theory that the bleem beta was intentionally leaked to test how good the encryption was at the time.
While I haven't done my own analysis of the bleemcast code that locks the software to the specific machines, it makes no sense that it would be used as test bait. Because the protection on the betas fundamentally has to be different than the protection on the discs, because they're protecting two completely different things.
The protection on the retail discs has to protect against people making duplicates of the discs. And it does that by using several techniques to ensure a PC drive can't read the discs, from bad sectors to sectors existing outside of the ToC range. And even if you successfully read and duplicated the software, the software also checked to make sure those same disc quirks were still there when executed, so when you burned the disc you needed to also replicate the same damaged structure, which was damn near impossible. So the only solution is to crack the executable. The current bleemcast! burnable image is a mix-and-match of both. It cracks out the check for damaged sectors past the ToC but retains special data existing in the pregap where data isn't supposed to be. GDEMU doesn't support this, for example, which is why that image doesn't work on GDEMU.
But the protection on the beta has to protect against a completely different problem: it absolutely needs to be easily burnable so that testers can make their own copies, so the protection used here is absolutely fundamentally different than the copy protection used in the final. It needs to be as copyable as possible but only run for specific people (i.e. the testers).
So if the retail version needs protection that runs for everybody but isn't able to be copied, how would the bleem guys benefit from leaking a copy with the exact opposite type of protection: one that is able to be easily copied but doesn't run for everybody?
SMiTH wrote:To see how quickly the public could crack the files. After all it was found that all five colors (blue, green, yellow, purple, and orange) were the same beta. Some claim the differences with the betas might be the region code?
As far as the regions:
REGION 1 -- USA, Canada.
REGION 2 -- Japan, Europe, South Africa, Middle East, Greenland.
REGION 3 -- S.Korea, Taiwan, Hong Kong, Parts of South East Asia.
REGION 4 -- Australia, New Zealand, Latin America (including Mexico)
REGION 5 -- Eastern Europe, Russia, India, Africa.
This isn't how the Dreamcast markets were even aligned, and Sega themselves only had 3 regions for the Dreamcast. Dreamcast had 3 main regions:
REGION 0 (J): Japan, Taiwan, Philippines
REGION 1 (U): USA, Canada
REGION 2 (E): Europe
Stuff like Hong Kong Dreamcasts ended up getting put into region 0, countries like Brazil got put in with region 1, and Australia and other PAL countries were grouped in with region 2. The groups you speculate don't make any sense? Why would Japan and Europe be grouped together, but Taiwan/HK are separate from Japan? Some of these countries didn't even have Dreamcast markets at all... ?
But... even if this were how the Dreamcasts were aligned, what is the point of assigning different colors to different region systems or locking the builds to regions? No indie software for the Dreamcast has ever had different builds for different region Dreamcasts, because why would they?
The actual myth makes far more sense than your theory: They made the software check for a console modification, and if the modification wasn't present, it refused to run; and only authorized people were given consoles with that modification. And to add a digital trail, the modifications were slightly different so if someone was losing or sharing their discs they'd know who was being loose with the software. So of course when all of the protections were stripped off the builds were the same. They were always supposed to be. Why would they have 1 person test different builds? One person can't test everything alone. You need a lot of people testing one single consistent build.
This would be really easy to do because the Dreamcast has flash memory. Just put the strings "BLUE," "PURPLE," etc. in an obscure location in the flash memory where it won't be overwritten and check for that. They could even put it in the read-only portion of memory with a simple hardware modification so it would take a hardware mod to duplicate the security token on other people's Dreamcasts.
This is a perfectly reasonable and normal thing for a company like bleem to do. Again, I ask, what is tinfoil about this? bleem! did hardware work on the Dreamcast, too--after all, they were at one point exploring the feasibility of doing an N64 emulator instead of PSX by using a cartridge adapter that connected to the G2 bus (modem) slot. So I'm sure they were more familiar with how easy it'd be to modify the console in certain ways than even official third party developers did.
Besides, the theory that bleemcast was intentionally leaked doesn't really agree with my opinion of the personality of Rand Linden. Rand and I were both staff members at DCEmulation in the early 00s and I spoke to him on the #dcemulation IRC quite a few times back in the day. One of the bleem testers, Dave Hojak, was also on DCEmulation staff as GhosT^x0, and I knew him very, very well (but haven't spoken to him in over 15 years unfortunately). He was extremely
protective of his code and hated pirates. I distinctly recall all of this vividly because I own DCEmulation now and his opinions highly influenced how we chose to approach moderating the DCEmulation boards. The #1 criticism of DCEmulation was that we never allowed even the discussion of anything bordering piracy on our boards and the #1 reason we did that was because no one dared alienate Rand, who had a strong personality of standing up for his convictions on this issue.
I just couldn't fathom Rand taking the risk of putting his code out there on purpose. Especially when after bleem! had gone under and they no longer had a financial interest in its sales, Rod Maher and Rand Linden posted on DCEmulation expressing regret that the beta making the rounds was extremely early and misrepresented the work they put into the emulator afterwards and that they were very disappointed in the person who leaked the builds because the company was so small and tight knit (thread here
I think people just like to come up with theories and gossip about bleem! because it's just one of those things that has had an extreme following. People saw bleem! as rebels in defense of a dying Sega. Rand even had a cult of personality on DCEmulation known as the Randites.
OGDCFAN99 wrote:I am surprised at how much he remembers about DC hardware and software development compared to a lot of other developer interviews. Not to mention how competent he was in that he found a bug in the Power VR rendering methods! He would be extremely valuable to the Indy scene if he wanted to and if someone could make that happen.
bleemcast! was written entirely in SH4 assembly language. With that level of talent, he would practically be a God in the Dreamcast indie programming community.
Of course he'd never say that... he's religious (or was, don't know if he still is) and doesn't believe in saying the Lord's name (using "G-d" instead).