Can a Dreamcast GD Burner work if it is connected to a PC instead of a Dreamcast Dev unit. If not, can it be connected to a PC to read data?
I posted this ages ago in another thread... Burning a Disk with a GD-Writer Connected to a P.C When you want to burn GD-ROMs for in-house use by members of a development team, you can connect one or more GD-writers to a PC and then follow these steps: 1) Create an emulation project and test it using GDWorkshop (see "A Final Check") 2) In GDWorkshop, choose "Save CRI Script?" from the File menu. Note: If you aren't certain at this point that you have everything set up correctly, you can test your setup by executing the crfdc.exe command with the options "wenv=test lang=e -wm=imagefile -bld-scrfile" (where scrfile is the CRI script) before you perform Step 3. 3) Open the "\Utl\Dev\CDCraft" directory and execute the crfdc.exe command with the options "lang=e -bld-scrfile" (where scrfile is the CRI script). This operation will generate a disk image file.Transfer the disk image file to any number of PCs connected to GD-Writers. (When making this connection, make sure that the SCSI ID is not 0. 4) To burn a disk, execute the crfdc.exe command with the options "lang=e -wm=imagefile -bld-scrfile." (These options are the same as those used in Step 3, with the -wm=imagefile option added.) Note: If you wish, you can use the -num=n option to repeat the burn process. Currently, however, you can use only one GD-Writer per PC. Generating an Uncompressed File The procedure described above generates a compressed image file. CDCraft creates a compact image file because it knows the disk is to be padded, but it doesn't put the actual filler data in the file. To generate an uncompressed image file that is suitable for submission to Sega for pressing, you must create a full 1GB image file. To do this, add the "-benv-imf1" option to the "-bld=scrfile" command mentioned in Step 3 of "Burning a Disk with GD-Writers Connected to PCs" in this document. In addition to creating a full image, you will also need to generate a text-format TOC file that Sega can use to verify the contents of your GD-ROM. To create a TOC file, run CDCraft with the option "-tck=myimagefile." Hope this helps. ...In other words you don't have to connect it to a Dev Kit if you don't want to!
Well after nearly a 5 month hibernation of my GD-Writer, my Adaptec 2940 Ultra SCSI card has come in :redface:. Whenever I boot my PC, right after the BIOS comes a screen displaying something like: ==================== SCSI Found - SEGA GD-R... 1997... No SCSI Boot Found... SCSI is not set on BIOS... ==================== I've installed the Katana SDK (Release 9) on my Windows 98SE, Windows 2000 Professional, and Windows XP Professional partitions, and I can't seem to get it to read on my computer. I have updated all of the OSs with the latest ASPI. On all of the Windows OSs, I get this box whenever I attempt to run GDWorkshop: When I updated the ASPI drivers on Windows XP and rebooted, a small box appeared displaying: Your new hardware is ready... (something along those lines). I don't know if the Dial is set to the wrong number on the back of the GD-Writer, or if I need a SCSI terminator. I'm in a real fuss now since I thought I had everything ready, since I don't have an actual Dev Box OH:, and the SCSI cable is way too short, like 1 foot long.
Don't quote me on this as it's been a good year or 2 since I tried, but even if you have the SDK installed and the GD Writer plugged in, GD Workshop still won't do sod all without a devbox But when you do get a devbox you can either choose to leave it on the PC or plug it into the devbox
Well that's just wonderful! I guess that's what happens when I get a GD-Writer before getting the actual unit itself! Wasn't there also something about it not being able to read GD-ROMs but GD-Rs only?
you can use the writer with CIM utility or CDcraft,but since i haven't a writer and haven't tried it please do not ask how.Just givin' a hint
It can't natively read GD-R too it only writes to it You joined after I broke my GD Writer, but I found some switches that allowed you to set it to read GD-R too - the only hitch being you literally need to dismantle the whole drive assembly as they're buried deep - just taking the cover off will get you nowhere
So is there some chance I might end up killing the unit in the process? I have a rare GD that I want to at least be able to pull up and back up on my PC before something catastrophic happens to it. I don't necessarily "have" to be able to burn to GD-Rs... at least not yet...
Best off using a DC + Coders Cable/BBA to rip it if that's the plan It's not worth taking it apart to play with the switches though, I did it and then it was £220 down the toilet.
Thanks, it looks like my best bet for the meanwhile is to use a DC coder's cable instead. Thanks a lot for your help LeGIt & oldengineer! :nod:
The "BIOS not found!" message is nothing to worry about. What happens is, during boot, if the SCSI controller finds a drive that is bootable, it loads a TSR to allow the device to be read via BIOS calls. This is only to boot it.