Converting backups to be used on new model dc

CptTarpals · #1 13-08-2001, 12:00

Ok, I have a new model dreamcast manufactored in november 2000 so I know it's not supposed to support cdrs. I tried to follow the directions below:
1.Rip the CD with DiscJuggler to a CDI file.
2.Go in to a DOS/Command Prompt and using CDIRip, rip the CDI file so that a .CUE and .BIN file are created.
3.You can delete the .CUE file. Download a free copy of ISOBuster from the net and extract the files to a directory from the .BIN file.
4.Using IPBIN4WIN, create an IP file which corresponds to the game. It normally needs to be pointing at the 1st_read.bin file, or perhaps a different file if it is a WinCE game. A WinCE game can be detecting by checking if it has a 'WinCE' directory on the CD. If so, make sure you take this in to account when creating the IP file.
5.Now you'll need a tool called 'mkisofs'. It is included in the selfboot toolkit. Create an ISO from the files you have extracted, and the IP.BIN in the root directory. Make sure you use an offset of 0,0 *NOT* 0,11700.
6.Then you'll need to use Xeal's amazing 'Bin2Boot' tool on the ISO, which creates a selfboot CDI which puts the game data BEFORE the audio boot data. A miracle. Now the game works. It's been tested on a real non-CDR boot DC (one of the first in the UK) and it works fine.
Copied and pasted from the Dreamcast Burning/Backup FAQ

I am able to get past step 3 but keep getting stuck after that on step 4. This is what i'm doing. I'm ripping the data from a backup cdr of selfbooting san francisco rush 2049 with dj 2.0 to get a cdi file. I then use cdirip to rip teh data to get a .cue, .iso, and a .wav file. i then use isobuster to extract all teh data. Then i get confused. When using ipbin4win, cant i use the same bin that was ripped from the cdr(ip.bin)? I did that and then ran mkisofs using example in the readme file. After taht is finished, i run bin2boot and it wont recognize the ip.bin file(i think. i did it last night and i cant remember exactly what it said).

Does anyone know what i'm doing wrong? Is it something i'm doing in the previous steps that I need to know about? Or does someone have a more detailed guide of this? Everything works fine in my older dc so i know the game is fine. I'm using an hp 8200 series with jinxter ghost driver and burns everygame just fine. I just want to get around this newer model thing. It's driving me crazy. Thanks

RedsunsFD · #2 13-08-2001, 13:55

I have try this tutorial too. The prob about it is, that the steps aren't detailed enough. But somehow I got the Ip.bin in the iso, but my dc still won't boot my games. And I don't really know what have done wrong. Hope someone out there can help us with this guide.

Wayne · #3 13-08-2001, 17:13

I don't see why you can't use the IP.BIN if one is already there. Just be sure you use BINHACK to patch the IP.BIN/1st_READ.BIN files to an offset of "0,0".

I've recreated selfboot discs from .CDI files I couldn't burn with Disc Juggler, and most of the time there's no IP.BIN available on the disc. When I have found there isn't an IP.BIN file, I was able to grab the blank IP.BIN from a package called "zerotools.zip". You can find zerotools on the DC CopyWorld website listed in the button above. I didn't make any changes to the IP.BIN other than to run BINHACK.

Also, instead of using Disc Juggler/CDIrip/Isobuster combination, why not just use ISOBUSTER to rip the disc from your drive (it works and actually defaults to your CD burner drive!). Actually, the only reason to actually RIP the files using ISOBUSTER is if there's audio files... The disc should read in your CDROM drive and you can just copy the entire disc's files & directories to your hard drive using Windows Explorer.

Just food for though.

CptTarpals · #4 14-08-2001, 07:15

In this case, there is a ip.bin file. Like I said it's for San Francisco Rush 2049 and does have audio track in it's first session, that's why it won't work in newer model so isobuster is needed.
After using binhack, don't you still need to use mkisofs?
Maybe all I need is teh command line to the mkisofs program. I think this is where i'm screwing up. This is what I used:
mkisofs -C 0,0 -V ECHELON -l -o data.iso data
I'll try again tonight and let you know what happens.
Thanks

RedsunsFD · #5 14-08-2001, 11:11

Wayne should we use binhack on IP.BIN AND 1ST-READ.BIN? Won't bin2boot do this already? I'm using the same command line for mkisofs like CptTarpals: is this command line ok?
Do you have tried the burning method with bin2boot CptTarpals mentioned above?

Wayne · #6 14-08-2001, 11:15

I personally would BINHACK anyway, although you may be right - BIN2BOOT probably will do it for you. I'd just do it myself just in case. Remember, when you run MKISOFS.EXE, you have to give it the "0,0" offset (prior to running BIN2BOOT). So if you have to give MKISOFS an offset, it makes sense that the files you're writing into the ISO should have their offsets changed to match.

CptTarpals · #7 14-08-2001, 11:41

I have not tried these methods yet since i'm still stuck at work but tonight is hopefully the night i get this working. I was also doing some mass searches and came across this posted by ss:
"this is the working, tested method [steps in above post] circulating right now. some people claim, that after step three, you can just go straight into CDRWIN and pick "build an iso image", then go straight to bin2boot - this in fact, does work...but some people have reported occasional problems with the latter method."
You may want to try this out too. I'm going to do both and see what i come across. Good Luck.

Wayne · #8 14-08-2001, 15:51

CDRWin doesn't work for me... Never has, and I'd imagine it never will (as I've given up on it and use alternative methods now). Fireburner works for me in place of CDRWin for burning .BIN/.CUE files.

CptTarpals · #9 14-08-2001, 20:18

Ok, I tried to use the binhack method and the cdrwin method and still got this when using bin2boot:

C:\Selfboot>bin2boot data.iso
bin2boot - makes selfboot cdi from bin
beta made by xeal - xeal.cjb.net

Name of bin file: data.iso
Mode 2 track
bin file size: 650168320
total sectors: 278325
big path table sector: 0
Finding the ip.bin...
A record for ip.bin could not be found

what is causing this?

Wayne · #10 14-08-2001, 22:29

Sorry, but I ran into this a few times myself and I resorted to building the self-boot disc myself when it occurred.

I wonder if someone has written a tutorial for the "DATA-data" type self-boot disc (as opposed to the "audio-DATA" disc). BTW: The CAP letters in the names above indicate the actual game's data track in the order.

RedsunsFD · #11 15-08-2001, 02:43

"A record for ip.bin could not be found": You will got this message if there isn't an IP.BIN file in your iso. Just use cdirip on the cdi image then use isofix on the new iso image.Then you will got three files. One of them is called bootfile.bin: Just rename this one to IP.BIN and you have the IP.BIN file for the game. Now include the IP.BIN file in the iso image and try bin2boot again. I tried this, but it don't work for me: It boots up to the license screen and then go to the screen with the 4 icons.
One word to the data/data image: would it work if I use cdirip on the cdi image. Then I would usually get an iso file and a *.wav file. Could I not just burn the *.wav file in mode 2 and then burn the iso image afterwards as session 2 to get a data/data game?
And Wayne how do you resorted the image to get bin2boot work properly?

Wayne · #12 15-08-2001, 03:23

I just discovered that the message you mention also appears sometimes when there is a valid IP.BIN in the file. There is a bug in the older version of BIN2BOOT (which I got from DCCOPYWORLD but is no longer there).

I downloaded a new copy from http://dcxeal.virtualave.net/b2b-cdda-b1.zip

This is apparently the latest version and it works on .BIN or .ISO files that the older version didn't. I just played around with creating a CRAZYTAXI.ISO file from the files on my game disc, then I used the older BIN2BOOT that I already had and got the same error. I used the new one I just downloaded and it worked. I burned a copy to a CDRW (I didn't test it on my DC, but I examined the file and disc structures).

I used the new BIN2BOOT on MrDriller (KAL-MRDR.BIN) and made a bootable disc that resembled in structure, the one I made of CrazyTaxi. I tested it successfully in my DC.

Mind you, my Dreamcast is the older variety, but I can vouch for the fact that this utility doesn't use a blank audio session before the data. It actually appears to burn the data to the first session and then burns an empty second session - only importing the directory from the first one. The results is that you have two sessions with the same files, although the second session is exactly 600KB in size.

Wayne · #13 15-08-2001, 03:37

By the way, RedSunFD, you misunderstood my use of the phrase "RESORTED TO BUILDING". I didn't mean "SORTED AGAIN", but rather "DECIDED TO".

That would give my previous sentence the following meaning:

"Sorry, but I ran into this a few times myself and I decided to build the self-boot disc myself when it occurred."

RedsunsFD · #14 15-08-2001, 08:02

Is the command line for mkisofs mentioned above right to create an iso?

Wayne · #15 15-08-2001, 12:51

That is correct, and the files you're writing to the ISO need to be in the DATA directory (thus the data at the end of the line), and it will create an ISO named DATA.ISO. You can change the "ECHELON" in the command line to whatever you want the label to read on the CD. Keep it uppercase, no spaces or punctuation and no more than 11 characters.

The -C 0,0 sets the offset to 0,0 so it'll ####t at the beginning of the disc.