Self Boot Burning Tutorial

Make sure you download this kit, for you need it to use the tutorial.(This tutorial assumes you already know how to unzip files and other basic windows functions, if you cannot do basic windows functions do not even attempt trying to use this tutorial)
mexboot.zip (447 KB)

***Important***
If you run into errors while attempting this tutorial, read the notes section at the end for some possible solutions.

Step.1 - Get your SCSI ID
From a DOS prompt, in your selfboot directory, type the following command.

cdrecord -scanbus

Cdrecord will give you a list of all attached devices that it can identify. Locate your CD-Burner on this list. Write down the 3 numbers it gives you.
For example, if your CD burner is at 0,1,0 write those numbers down, just like that.
(See notes if you have problems here)
From now on, these numbers will be used where ever you see the command: "-dev=x,x,x" where x,x,x are your device's SCSI ID numbers.

Step.2 - Burn the First Session
From a DOS prompt, in your selfboot directory, type the following command.

cdrecord -dev=x,x,x -multi -audio audio.raw

When CD Record finishes it's task, you will have successfully burned the first session and first audio track

Step.3 - Getting Multi Session off-set numbers
From a DOS prompt, in your selfboot directory, make sure your CD-R is still in the drive an type the following command.

cdrecord -dev=x,x,x -msinfo

When CD Record finishes it's task, it will print on the screen two numbers. a Zero, and most likely either the numbers 11700 or 11702 which are the most common off set numbers for a CD-R with nothing but 4 seconds of blank audio on it (which is exactly what the first session is)
(see notes if you have read the general tutorial on making "disk warning" audio tracks)
When you have the numbers on screen, write them down. The first one will always be 0, but the second one can vary depending on your burner, and the length of the audio track burned in session 1. These numbers will be referred to from now on as "x,y" and will be used in the burning on the second session, and possibly the creation of the selfbooting image. Keep this in mind.

Step.4 - Setting up the files
From Windows, create a sub-directory (folder) inside your selfboot directory. Name this sub-directory "data". In this new directory, copy ALL the files needed for the program you are trying to make self booting. Make sure you have ALL your roms in the directory . The top level (i.e. the root of "data") should contain a file called ip.bin, and . You need to move your IP.BIN file from your data folder into your main directory. You do NOT want the IP.BIN in your "data" directory. The top level (i.e. the root of "data") should contain a file called ip.bin, and (see notes section if you don't see either ip.bin or ) If you have both of these files, MOVE (not copy) them one level up (i.e. into your selfboot directory). after this is done, move on to step 5.

Step.5 - Hacking the boot-up files
From a DOS prompt, in your selfboot directory, type the following command.

binhack

the program will run, and it will ask you for the name of the executeable. When it does, type in " ". it will then ask you for the name of the boot sector. When it does this, type "ip.bin". If Binhack detects a non-WinCE executable, it will ask you for your msinfo, or Off set number. If it does, type in ONLY the SECOND number. So, if your off set numbers were 0,11702 , you would only type "11702" here. Also, if Binhack DOES detect a WinCE executable, it will print a message to that effect, and it will not ask you for your msinfo numbers.
(if you are having trouble with this step, see the notes section)

Step.6 - Creating the Selfbooting Image
From a DOS prompt, in your selfboot directory, type the following command.

mkisofs -C x,y -V label -l -o data.iso data

Make sure that in the command, you substitute in your off set numbers instead of x,y and instead of the word "label" you type a label that you desire, just make sure it's 8 characters or under.

After the program is done, you will have a new file in your selfboot director called "data.iso"

Step.7 - Injecting the boot sector
From a DOS prompt, in your selfboot directory, type the following command.

ipins

The ip inserting program will run, and it will ask you for the name of the boot sector. You will type "IP.BIN". it will then ask you for the name of the ISO image. You will type "data.iso". After the program completes (doesn't take very long) you will be ready for the final step.

Step.8 - Buring the second session
From a DOS prompt, in your selfboot directory, type the following command.

cdrecord -dev=x,x,x -xa1 data.iso

after the program completes (this will take several minutes) you should have a self-booting DC CD-R of . Eject the disk when finished, and try it in your Dreamcast. Have fun!! Note: This last step does not work for a lot of people, you can also use CDR Win to burn the iso, just burn the iso in regular Mode 1.

***Notes section***

Before working with the Self-Boot kit tools, if you have windows 2000 I recommend download the ASPI Layer Fixer if you have any problems with even starting the first steps. Be sure

***Burner Compatibility:
Self-Booting Disks can be made on the vast majority of new burners, and alot of not-so-new ones as well. Unfortunately, the CAN NOT be made on ALL burners. Specifically ones that can not burn under 302 sectors. To make a selfbooting disk for DC, you MUST be able to burn a sector size of 300. If you attempt to make a Disk self boot for your Dreamcast, and when you try to burn the second session, CD-Record gives you an error stating it can't open a new session, you most likely have one of those burners that doesn't support under 302 sectors.

***CD Record issues:
In some instances, Trying to run the -scanbus command from CD Record will halt the use of any SCSI compliant drives and sometimes lock up your system, preventing it from shutting down properly. If this happens to you, you need to find an updated ASPI driver. They are freely available on the Web. Also, try using the "update driver" option from the device manager of any CD Burner you are trying to use, and re-install it from it's original disks. Sometimes you may need to do both. As long as you can get teh SCSI ID for the device you are tyring to burn with, you will be fine. If after re-installing your drivers, CD shows the SCSI ID of your burner, but then hangs up again on another device. Write down the SCSI ID anyway, and re boot. You do not need to run the -scanbus command again, as long as you have the ONE device you wish to use configured probperly, any other incompatible drives are irrelevant to the self-booting process.

***"Disk Warning" tracks:
If you ahve read my general self booting guide and are attempting to burn your own "disk warning" track instead of the 4 seconds of silence, do NOT forget that you will get a different off set number from 11700 or 11702 when you run CD Record with the "-msinfo" command.

***Binhack problems:
If you can not get the binhack program to work, you most likely have not copied your and IP.BIN files correctly. Make sur ethat both of those exist in the SAME directory (folder) as the Binhack.exe program.