#DCRES COMPLETE PACK SOFTWARE#
#DCRES COMPLETE PACK ISO#

#DCRES COMPLETE PACK SOFTWARE#

'Some rare, late-model US Dreamcasts and some special edition Japanese Dreamcasts are crippled and have the code for booting MIL-CDs removed from their BIOS, meaning that there is no way to play backups or unofficial software on the system without some sort of hardware modification (or an as-of-yet undiscovered additional backdoor). The only advantage on using 45000 LBA is making hacking easier. So putting the second session near the not-streaming files would make the reader move less. The reason is that I found that some games made the reader go back to the start of second session, even if there was no data there. The most recent releases had the second session starting as far as I could, sometimes after dummy data or streaming data. Some Dreamcasts don't play audio/data 11702, which is what the DCRes releases are. This mimics the LBA of the original GD-ROM and is generally a more reliable selfboot format. Oh, one other thing we've got on DCRes 45000 data/data format. MD5SUM WILL BE DIFFERENT BECAUSE I DOWNSAMPLED THE VIDEO MYSELF.Īs a last point, please check the binary diffs of GDI's main binary and my release's: I don't keep oRARs anymore, so if someone could md5sum Kalisto's ST_ROLL.SFD please post here. If a video has a bitrate too high, reading speed at the inner part of the disc is not enough for the streaming, and video will keep freezing. ST_ROLL.SFD was NOT downsampled for 75min CD-R! It was downsampled so it could be played in the inner part of the disc! As a rule of thumb, all streamingĭata goes in the beggining of the disc, so data that actually impacts on loading time goes to the end of the disc. 52ce6194cbc50eea7098830415512a0c */ST_ROLL.SFDĪll videos except ST_ROLL.SFD are equal, so CRCs MATCHES WITH CRCs OF SCENE RELEASE BECAUSE THEY ARE THE SAME FILES OF GDI! The result for most games was great, and much better than the releases of the time.įacts presented, I would like to show you some comments I found (from other forums!), and some proofs that they are lies.Ĭode: Select all $ md5sum gdifiles/* | sed 's/gdifiles//' > /tmp/1.txt md5sum myfiles/* | sed 's/myfiles//' > /tmp/2.txt diff /tmp/1.txt /tmp/2.txt I encoded things with the highest quality I could, reverse engineered game formats, wrote tools, optimized file order the most I could (many hours, hundreds of CD-Rs.). DCRES work was not a simple applying dummy files in games.I have neither the knowledge, nor the patience to do that. I never hacked binaries and protections in the assembly level, AND NEVER CLAIMED TO HAVE DONE IT. Use of other groups' releases binaries, and in these cases THE GROUPS WERE CREDITED IN THE README FILE.Binary comparisson of other groups' releases, and in these cases THE GROUPS WERE CREDITED IN THE README FILE.Simple search/replace hacking of binaries (e.g.: changing sample rate of raw music files).

#DCRES COMPLETE PACK ISO#

Hex edit ISO to change size of protection files.Hacking recipes for known protections found on the internet.ALL the game hacking in my releases were done using one or more of these:.Of course there is a chance I forgot to mention someone by mistake, but I doubt it. I NEVER USED WORK FROM OTHERS WITHOUT MENTIONING IT IN THE README FILE.I found comments of different people saying that I copied work from others and did not give credit, and that's a lie.īefore answering to that, I would like to present some facts: Also, I found references of DCRES in several forums with different languages, and that's very satisfying. The complete pack I released before 'quitting' are still available in several places, and this is awesome. After all these years of the 'end' of DCRES project, I tried googling DCRES and got good and bad findings.įirst the good ones.

Dcres complete pack