Burning Images |
Nero, Nero, Nero - everyone uses Nero! You can use other programs to burn images with, but if you need detailed instructions on how to do so then you're on your own. Now you're either going to have an .ISO or .GCM image you'll be burning. If you're image is named .GCM rename it to .ISO (yes, that was painful wasn't it!) ![]() Select the image file you wish to burn and then pick "Open". ![]() If you get the below message you're going to have to try to "FIX" the image file. Please skip down to Fixing The Image for more info on this. If you don't get this error go to the next step. ![]() Now you'll be presented with the final screen. Pick "Disc at Once", make sure the "Finalize CD" option is either checked out greyed out, pick a burning speed depending on what you've figured out works best for you (see the DRE Guide) and then click "BURN". ![]() If you're using a slower computer you can opt to turn off the "Buffer Underrun Protection" (if Nero will let you) which might increase your chances of having the disc boot, but if you chose to do this make sure no other programs are running (AIM, MSN, IE, FireFox, etc) and don't touch the computer until it is done burning. ![]() If you get this error message, “The entered block size does not correspond to the image length. The block size may be wrong. Do you want to correct or ignore the problem?” it means that the ISO is corrupt. If you receive this error message in CloneDVD, CloneCD, Alcohol 120%, Record Now MAX or any other software at that fact you should try loading it into Nero before burning (even if your burner isn’t supported by Nero). You do this because the programs listed above "will always complain about the block size". So if Nero doesn’t complain then simply ignore the warning in the above programs and burn anyway. Some people like to "wipe" their images which is removing the unused data from the end of them for whatever purpose. A program named FSTFIX will rebuild the image and add back the removed space so you can burn it. Note that the image itself could also be not dumped correctly or just plain damaged and then you'll out of luck. An easy way to tell if your image is wiped is to check it's filesize. If the image isn't exactly "1,459,978,240 bytes" then it has been wiped, underdumped and/or curroupted. To fix the image with FSTFIX go to our downloads section, grab "Loony Cube's Wiped GCM Fixer/FSTFIX v1.5f", extract it to the directory that contains the image and then run it via the command line interface as shown in the example below.
|