Jump to content

zman

Members+
  • Posts

    9
  • Joined

  • Last visited

zman's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Lucky me... I've figured it all out after about 25 coasters. First the only method which worked about a third of the time was discjuggler on one setting. mode1, offset 0, 2352, cdrom... With luck I got what seems like a 100% correct burn ratio now. I use Daemon tools to mount the image. Then Alcohol120% to burn the image. I do the "copy cd" instead of the "burn image" selection. As when I tried to directly burn an image using different and various burning programs nothing would work. So I realized the raw write issue would be in effect, which my cd burner seemingly did not support. I was wrong as often as I am. To confirm the cd raw write capabilities of my cd rom burner I used clone cd on an image. Clone cd of course reported that my cd rom burner did support raw write methods, as I suspect is neccessary with most of the Dreamcast disc images. So as usual clone cd would not burn the image due to the raw write issue I have. So this sucks... right.... In my darkest of hour and utilizing the mix mode method on nero (did not work) I went back to Daemon tools for help. I figured on giving it one more shot on cd to cd burning. As Raw DAO does not work on my burner, I new I had to use DAO/SAO as the default and hoped it worked. So I set up Alcohol120% and the lights went on in the refrigerator. I new the encoding information was contained in the header of an image. I.E. What was used and how the image flags where set. So I saw it with my own two eyes. Alcohol120% handled the raw write flag as long as I was copying the image as a fellow cd to cd copyier could. No more coasters and no more image to cd copy attempts. So to make this story end. Raw write images on my cd burner will only work if I copy those images from a virtual cd drive as a one to one cd copy. And now it works...
  2. My cd-r writer does not like the word raw, so I am unable to burn any image requiring the raw flag. I.E. raw-dao or raw-write. So is there a way to modify these images to work without using the raw data flag on burning.
  3. Hold up... Do not purchase a Dreamcast that is dated November or Newer...As Sega changed the bios in the November Models...Also you do not need the boot disk if you use the swap method. A little info beforhand saves on the trouble later...
  4. My steps I use to build a DC Selfboot Game image. Ideas and suggestions welcomed. 1) cdirip filename.cdi -iso 2) isofix TData02.iso (either 11700 or 11702 on rare cases it is something else. Check LBA in the first step.) 3) isobuster fixed.iso and extract data to directory. 4) Move "bootfile.bin" to that directory and rename "IP.BIN" 5) mkisofs -C 0,0 -V "GAME" -l -o GAME.ISO dir (dir is the directory of the extracted data) 6) bin2boot GAME.ISO 7) cdirip image.cdi -info to check and see all is good. (I want the data before the audio, because I have a December 2000 Dreamcast.) burn in discjuggler. ? on correct settings. That's were I'm at. Soon I shall succeed. I just need a little help, info, faq, walkthrough, knowledge, luck, or other to succeed at this.
  5. Well this is the steps I've taken. 1) Run cdirip utopia.cdi -iso (This rips the file to a raw iso and wav file. It also gives me the mode and LBA.) (For Utopia BootCD v1.2: Session 1 --> Audio/2352 size is 426kb and LBA is 0 Session 2 --> Mode2/2336 size is 1050kb and LBA is 11826 (not 11702 as direction indicate) 2) I use isofix on on TData02.iso. method: isofix TData02.iso 11826 (not 11702 as it says in the instructions) This makes "fixed.iso" for use with isobuster. 3) I use isobuster and rip out "0Load.bin" LBA 11850 2 MB 4) I Grab "bootfile.bin" and move it to "CDROM" directory where "0Load.bin" was riped to. Then I rename "bootfile.bin" to "IP.BIN" 5) I use mkisofs -C 0,0 -V "Utopia BootCD v1.2" -l -o BOOTCD.ISO dir (dir is where "CDROM" directory is located) 6) I use bin2boot on "BOOTCD.ISO" to make "image.cdi" 7) I confirm that the data is before the audio in "image.cdi" I do this by using cdirip image.cdi -info The info is: Track 1-->Mode2/2336 size 1064 kb LBA 0 Track 2-->Mode2/2336 size 302 kb LBA 12464 This shows that the larger data file is now first and the smaller audio file is second. The original Utopi.cdi is 4062 kb. My file image.cdi is 3801 kb. Then I burned the image.cdi with dicjuggler v3. I used: Mode: Mode2 (because that is what the image was formed as.) Block: 2336 (because that is what the image was formed as.) Offset: 0 (needs to be no matter what.) TOC: cdrom (the original method used on Utopia.) (This was an unsuccessful attempt.) So my questions are: 1) Alot of reports about raw write, however my CD burner supports it but does not deliver on that promise. 2) Alot of reports about Block: 2048 and Mode: 2 vs Mode: 1. What is the most successfully used Block size and Mode. 3) Alot of reports about TOC: cdrom vs TOC: CD DA. (CD DA is the audio format) So what's the best way for this. 4) This is what I would like, but I am unable to use raw write: Mode: Mode2 Block: 2048 Offset: 0 TOC: cdrom Click on raw write. These are some version I have seen. Mode: Mode1 Block: 2352 Offset: 0 TOC: cdrom Nothing Click on. Mode: Mode1 Block: 2048 Offset: 0 TOC: CD DA Click on raw write. So what's the best for a good burn. Also for such a small sized file for the Utopia BootCD, shall I dummy the disc to burn the data on the edge. Any info, suggestions or ideas will be welcomed.
  6. Well it's a new day with more knowledge, but unfortunatly no success. I found out why isobuster does not read the *.cdi file our TData02.iso file correctly. It has to do with the data track position on the image. The LBA number needs to correspond correctly to the data track. That is what isofix is for.
  7. Well I have a December 2000 model Dreamcast so I follow the instructions given on making a working DC cdr for these later Dreamcast. See this http://dreamlover.tecbox.com/ and look under the section "Newer Non MIL-CD DC's and Workaround." It's vague, but that is what I have to go on. I'm also looking to make the Utopia boot CD. I learnt about the Daemon Tools deal after I wrote the first stuff and that looks like it does the trick much better than isobuster. By the way I use all the current editions of all the programs mentioned in the the guides forums and or discussion. Unfortunately, I have more questions than answers so not everything given is as such as I am able to grasp the concept. Basically I'm lost... When I'm done and successfull at burning the Utopia boot CD and Games to run on My December 2000 Dreamcast. I plan to rewrite the manual on how it's done. Today, the concept looks easier using Nero and Alcohol120% and Daemon Tools then with isobuster and Discjuggler, but I'll find out in the end. First I need to succeed, and for that I need more specific answers. So any experience users Ideas are welcomed here, I give credit to all for there help. Thanks.
  8. Alright, part or all of my problem with burning a DC disc successfully lies in isobuster and figuring this program out. 1) To extract the files in a *.cdi , what settings in isobuster's options do I use for configuration. I.E. NFL2K1 - This *.cdi is read by isobuster and I can see and extract the files that are there. Tony Hawk PS2 - I am unable to see and extract the files that are there. What I can extract is a *.cue + *.bin or a raw *.bin image, but not the files in THPS2. What gives? This is the same for Silver and the Utopia Boot CD...NO files to be seen. My question here is why. Why can isobuster read NFL2K1 with no problems and not THPS2 or the Utopia boot Disc. Does it have to do with *.cdi version number. I.E. a *.cdi v2.0 or a *.cdi v3.0 converted disc. 2) I did a standard DC Discjuggler burn with Silver and my cdrom can read the cd after the burn. I did the same method with THPS2 and was unsuccessfull in my cd rom reading the disc afterwards. What's the difference? 3) The whole purpose is to convert games to a working non-mil cd format, so if you know someone who succesfully has done this send a transcript on how it was done. Thank you...
  9. What am I doing wrong? Instructions: Utopia Boot CD for NON MIL-CD DCs MUCH thanks to jc of dcwarez (and xeal, of course!) Download the cdrecord-tools, CDIRip, ISOFix, and Bin2Boot if you don't already have them. Get the *.CDI file for the Utopia BootCD. Extract the CDI, cdirip.exe, isofix, and bin2boot to a directory (ie, C:\JC_IS_COOL). Open a DOS/Command Prompt in said directory. Run the following commands: cdirip FILENAME.CDI /iso then do: isofix TData02.iso 11702 Extract the contents of the ISO using ISO Buster into a directory with the cdrecord-tools. Move the "bootfile.bin" from the directory where you were working with CDIRip to the Directory you extracted the contents of the fixed ISO. Make an ISO with the following command: mkisofs -C 0,0 -V "Utopia BootCD v1.1" -l -o BOOTCD.ISO DIR (where "DIR" is where you extracted your fixed ISO. Take the ISO that "mkisofs" produces and put it into the directory where you have Bin2Boot. Run the following command: bin2boot BOOTCD.ISO /nohack Burn image.cdi with DiscJuggler and enjoy it on your "copy-protected" Dreamcast. I end up with this at the end: "image.cdi" which contains two files --> BOOTFILE.BIN & Track01.bin I followed the instructions to the "T"... My Dreamcast is a December Model, so I'm using these instructions. Any info is helpfull as I can not find any more documentation on the subject. Such as what to set discjuggler to for the burn. I.E. what mode to use etc. Also I could use more descriptive instructions that others may have relating to the new model Dreamcast and successfully burning CD's. Alright things are not working. I'm trying Silver_Selfboot. The instruction say to use isobuster to extract files. The only file that extracts is Track 01.bin. Is this correct and what do I do with it. Padus Discjuggler does not work with my burner so I'm going to use Nero. I have no *.bin/*.cue and no *.wav files. Either I'm reading wrong or the Faq's are not descriptive. So I'm looking for some step by step instructions that explain how to burn an image. I have the silver_selfboot.nrg but where do I go from there.
×
×
  • Create New...