GD-ROM Dumping Guide
From Redump Wiki
(→Method 2: DiscImageCreator) |
(→Submitting your Dump Info) |
||
(45 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
- | '''GD-Rom''' and '''GD-R''' dumping guide. | + | '''GD-Rom''' (pressed) and '''GD-R''' (recordable) dumping guide. |
- | Note: Some GD- | + | Note: Some GD-ROMs may NOT dump with these method, and require a TOSEC-style SD Card dump for the HD Area which then has to be "fixed" to meet redump spec. If the game is a single track in the HD Area, then the TOSEC-style dump will be equal a redump dump for HD Area, LD Area still needs Plextor dumping. See [[GD-ROM SD Card Dumping Guide]]. |
- | ==What are | + | ==What are GD Discs?== |
- | GDs (Gigadiscs) are the type of [[wikipedia:Optical disc|optical media]] used by the [[wikipedia:Dreamcast|Sega Dreamcast]] as well as the [https://segaretro.org/Sega_NAOMI Sega NAOMI], [https://segaretro.org/Sega_NAOMI_2 Sega NAOMI 2], [https://segaretro.org/Sega_Chihiro Sega Chihiro] and [https://segaretro.org/Triforce Triforce] arcade systems. | + | GDs (Gigadiscs) are the type of [[wikipedia:Optical disc|optical media]] used by the [[wikipedia:Dreamcast|Sega Dreamcast]] as well as the [https://segaretro.org/Sega_NAOMI Sega NAOMI], [https://segaretro.org/Sega_NAOMI_2 Sega NAOMI 2], [https://segaretro.org/Sega_Chihiro Sega Chihiro], and [https://segaretro.org/Triforce Triforce] arcade systems. |
The disc contains two distinct areas, a Low Density (LD) Area and a High Density (HD) Area, physically separated by a ring. To get a good dump, you need to extract both Areas from the disc. | The disc contains two distinct areas, a Low Density (LD) Area and a High Density (HD) Area, physically separated by a ring. To get a good dump, you need to extract both Areas from the disc. | ||
Line 12: | Line 12: | ||
* Windows PC | * Windows PC | ||
- | * [[ | + | * [[Optical Disc Drive Compatibility#GD-ROM|Recommended Optical Disc Drives]] (see also: [[Optical Disc Drive Compatibility for GD-ROM and GD-R Dumping]]) |
- | * [https://github.com/SabreTools/MPF/releases MPF application] (includes DiscImageCreator) | + | * [https://github.com/SabreTools/MPF/releases MPF application] (includes Redumper and DiscImageCreator) |
* [https://archive.org/download/dcdumper-ice-startstop/DCDumper_ice_startstop.zip DCDumper, ice, startstop applications] | * [https://archive.org/download/dcdumper-ice-startstop/DCDumper_ice_startstop.zip DCDumper, ice, startstop applications] | ||
* [[Audio Trap Disc]] | * [[Audio Trap Disc]] | ||
==Dumping the LD Area== | ==Dumping the LD Area== | ||
- | The LD Area should be dumped with using the [[Disc Dumping Guide (MPF)]] with a [[ | + | The LD Area should be dumped with using the [[Disc Dumping Guide (MPF)]] with a [[Optical_Disc_Drive_Compatibility#CD-ROM_.2F_CD-Audio|CD-ROM compatible drive]]. |
- | The LD Area is a standard CD- | + | The LD Area is formatted like a standard CD-ROM so the CD-ROM profile should be selected in MPF. |
==Dumping the HD Area== | ==Dumping the HD Area== | ||
- | To dump the HD Area of the GD- | + | Dumping the HD Area can take over an hour sometimes, and your drive may make scary noises. |
+ | To dump the HD Area of the GD-ROM, a Swap Disc technique is used. | ||
There are two ways to do the Swap Disc technique: | There are two ways to do the Swap Disc technique: | ||
- | * '''Prepare a Drive for Top Removal''' [https:// | + | * '''Prepare a Drive for Top Removal''' [https://youtu.be/RfCc7nsTUoo as seen in this video tutorial]. Afterwards, set the top back onto the drive with screws removed, this allows for easy top removal. Make sure your drive lid is replaced perfectly, putting your drive lid on unevenly can lead to the dump failing partially into the dumping process. |
- | * '''Pin Eject''' | + | * '''Pin Eject''': Push the tray back into the drive quickly so the spindle will catch. |
- | + | ===Method 1: DCDumper (Preferred for GD-ROM Dumping)=== | |
- | + | A video tutorial for this dumping method can be seen [https://youtu.be/N3wPQOqHJr8 here]. | |
- | + | ||
- | + | This method is the more reliable method for dumping GD-ROMs because: | |
- | + | * The recommended TSST drives read GD-ROMs best, and do not support /c2 error correction. | |
- | * Insert the Audio Trap Disc to an HD Area [[ | + | * DCDumper dumps disc segments multiple times and compares hashes for QC, it does not rely on /c2 error correction. |
+ | |||
+ | Dumping: | ||
+ | * Insert the Audio Trap Disc to an HD Area [[Optical_Disc_Drive_Compatibility#GD-ROM|compatible drive]]. | ||
* In command line, '''cd''' (change directory) to the "DCDumper_ice_startstop" folder. | * In command line, '''cd''' (change directory) to the "DCDumper_ice_startstop" folder. | ||
* Run '''startstop [DriveLetter] 1''' | * Run '''startstop [DriveLetter] 1''' | ||
* Remove the top off the drive. | * Remove the top off the drive. | ||
- | * Insert the GD- | + | * Insert the GD-ROM and put the drive top back on. |
* Run '''dcdumper [DriveLetter] -c446261 -df -ft -t0 -p20''' | * Run '''dcdumper [DriveLetter] -c446261 -df -ft -t0 -p20''' | ||
* It will take several "PASS"es to get all matches, this is fine. If you need to stop (sometimes there is no progress for 30mins) and restart the dumping process, it will continue where it left off - so don't delete progress if you have to stop it. | * It will take several "PASS"es to get all matches, this is fine. If you need to stop (sometimes there is no progress for 30mins) and restart the dumping process, it will continue where it left off - so don't delete progress if you have to stop it. | ||
Line 45: | Line 48: | ||
If dcdumper fails to run with an error complaining about MSVCP100.DLL being missing, install the Microsoft Visual C++ 2010 Redistributable Package (x86) to fix this issue. | If dcdumper fails to run with an error complaining about MSVCP100.DLL being missing, install the Microsoft Visual C++ 2010 Redistributable Package (x86) to fix this issue. | ||
- | ===Method 2: DiscImageCreator=== | + | ===Method 2: DiscImageCreator (Preferred for GD-R Dumping)=== |
- | + | This method is more reliable for GD-Rs because: | |
- | * Insert the Audio Trap Disc to an HD Area [[ | + | * GD-Rs do not read on the TSST drives that work so well with GD-ROMs. |
+ | * c2 error re-reading is very useful. Since DiscImageCreator can use /c2 error correction, dumping with a compatible Plextor model is preferred. | ||
+ | |||
+ | Dumping: | ||
+ | * Insert the Audio Trap Disc to an HD Area [[Optical_Disc_Drive_Compatibility#GD-ROM|compatible drive]] | ||
* In command line, '''cd''' (change directory) to the folder containing "DiscImageCreator.exe" | * In command line, '''cd''' (change directory) to the folder containing "DiscImageCreator.exe" | ||
* Run '''DiscImageCreator.exe stop [DriveLetter]''' | * Run '''DiscImageCreator.exe stop [DriveLetter]''' | ||
* Remove the top off the drive | * Remove the top off the drive | ||
* Insert the GD disc and run: '''DiscImageCreator.exe close [DriveLetter]''' | * Insert the GD disc and run: '''DiscImageCreator.exe close [DriveLetter]''' | ||
- | * Then run the dumping command: '''DiscImageCreator.exe gd [DriveLetter] foo.bin [DriveSpeed(0-72)] /c2''' (Note #1: " /c2" is only for use with compatible Plextors. Note #2: Adding the command "/be pack" may | + | * Then run the dumping command: '''DiscImageCreator.exe gd [DriveLetter] foo.bin [DriveSpeed(0-72)] /c2''' (Note #1: " /c2" is only for use with compatible Plextors. Note #2: Adding the command "/be pack" may[http://forum.redump.org/post/105799/#p105799] be helpful when dumping GD-Rs.) |
* Dump multiple times until you get an error-free dump (check the Command Prompt output after DiscImageCreator finishes dumping) | * Dump multiple times until you get an error-free dump (check the Command Prompt output after DiscImageCreator finishes dumping) | ||
- | ==Submitting your | + | Note for GD-R dumping: |
- | Here | + | * 1x, 4x, 8x read speeds can be helpful or even necessary when dumping GD-Rs. Try starting with 8x, if one of those speeds doesn't work then try another. |
+ | * If you have issues where the drive locks up partway through, disabling cache flushes helps: '''DiscImageCreator.exe gd [DriveLetter] foo.bin 8 /c2 /f 600000''' | ||
+ | |||
+ | ==Submitting your Dump Info== | ||
+ | Here are example submissions: [http://forum.redump.org/topic/45492/addeddc-nfl-2k1-usa/] [http://forum.redump.org/post/105798/#p105798] | ||
+ | |||
+ | '''Note:''' [https://github.com/SabreTools/MPF/ MPF.Check] (UI or CLI) supports DCDumper logs. This greatly speeds up gathering submission info. | ||
We'll presume you've used Disc Image Creator for you dump in both LD and HD Areas. | We'll presume you've used Disc Image Creator for you dump in both LD and HD Areas. | ||
Line 63: | Line 76: | ||
* "DAT" | * "DAT" | ||
* "Cuesheet". When combining Cuesheet data for LD and HD Areas, paste "REM SINGLE-DENSITY AREA" at the top of the cuesheet, and "REM HIGH-DENSITY AREA" in a new line after the LD Area cuesheet into, then finally the HD Area cuesheet text. | * "Cuesheet". When combining Cuesheet data for LD and HD Areas, paste "REM SINGLE-DENSITY AREA" at the top of the cuesheet, and "REM HIGH-DENSITY AREA" in a new line after the LD Area cuesheet into, then finally the HD Area cuesheet text. | ||
- | * "Write Offset" | + | * "Write Offset". For determining write offset for HD Area of a DCDumper + ice.exe dump, open the .txt file output by Ice: |
+ | ** Combined offset = Disc offset + Drive offset | ||
+ | ** Kreon drives used for DC dumping have a +6 offset | ||
+ | ** Calculation for Disc Offset: [Example Combined Offset of +30] - [(Any Kreon Model) Drive Offset of +6] = [Disc Offset of +24] | ||
+ | ** Offsets for GD-ROMs are formatted in entries as follows: [LD Area disc offset]|[HD Area disc offset] | ||
Fill in Ring Code data and any relevant Comments. Post on the Redump "New Dumps" subforum. | Fill in Ring Code data and any relevant Comments. Post on the Redump "New Dumps" subforum. | ||
[[Category:Dumping Guides]] | [[Category:Dumping Guides]] |
Latest revision as of 04:15, 11 June 2024
GD-Rom (pressed) and GD-R (recordable) dumping guide.
Note: Some GD-ROMs may NOT dump with these method, and require a TOSEC-style SD Card dump for the HD Area which then has to be "fixed" to meet redump spec. If the game is a single track in the HD Area, then the TOSEC-style dump will be equal a redump dump for HD Area, LD Area still needs Plextor dumping. See GD-ROM SD Card Dumping Guide.
Contents |
What are GD Discs?
GDs (Gigadiscs) are the type of optical media used by the Sega Dreamcast as well as the Sega NAOMI, Sega NAOMI 2, Sega Chihiro, and Triforce arcade systems.
The disc contains two distinct areas, a Low Density (LD) Area and a High Density (HD) Area, physically separated by a ring. To get a good dump, you need to extract both Areas from the disc.
Tools
First you need to make sure you have the necessary equipment. To dump a GD you need:
- Windows PC
- Recommended Optical Disc Drives (see also: Optical Disc Drive Compatibility for GD-ROM and GD-R Dumping)
- MPF application (includes Redumper and DiscImageCreator)
- DCDumper, ice, startstop applications
- Audio Trap Disc
Dumping the LD Area
The LD Area should be dumped with using the Disc Dumping Guide (MPF) with a CD-ROM compatible drive.
The LD Area is formatted like a standard CD-ROM so the CD-ROM profile should be selected in MPF.
Dumping the HD Area
Dumping the HD Area can take over an hour sometimes, and your drive may make scary noises. To dump the HD Area of the GD-ROM, a Swap Disc technique is used. There are two ways to do the Swap Disc technique:
- Prepare a Drive for Top Removal as seen in this video tutorial. Afterwards, set the top back onto the drive with screws removed, this allows for easy top removal. Make sure your drive lid is replaced perfectly, putting your drive lid on unevenly can lead to the dump failing partially into the dumping process.
- Pin Eject: Push the tray back into the drive quickly so the spindle will catch.
Method 1: DCDumper (Preferred for GD-ROM Dumping)
A video tutorial for this dumping method can be seen here.
This method is the more reliable method for dumping GD-ROMs because:
- The recommended TSST drives read GD-ROMs best, and do not support /c2 error correction.
- DCDumper dumps disc segments multiple times and compares hashes for QC, it does not rely on /c2 error correction.
Dumping:
- Insert the Audio Trap Disc to an HD Area compatible drive.
- In command line, cd (change directory) to the "DCDumper_ice_startstop" folder.
- Run startstop [DriveLetter] 1
- Remove the top off the drive.
- Insert the GD-ROM and put the drive top back on.
- Run dcdumper [DriveLetter] -c446261 -df -ft -t0 -p20
- It will take several "PASS"es to get all matches, this is fine. If you need to stop (sometimes there is no progress for 30mins) and restart the dumping process, it will continue where it left off - so don't delete progress if you have to stop it.
- When the HD Area dump completes, you'll convert it to it's final form. Run ice.exe dense.bin 44990 > gamename.txt This will produce a bunch of files starting with "Track 03" and going as high as however many tracks were on the HD section of the disc (as little as 1, as many as 98).
If dcdumper fails to run with an error complaining about MSVCP100.DLL being missing, install the Microsoft Visual C++ 2010 Redistributable Package (x86) to fix this issue.
Method 2: DiscImageCreator (Preferred for GD-R Dumping)
This method is more reliable for GD-Rs because:
- GD-Rs do not read on the TSST drives that work so well with GD-ROMs.
- c2 error re-reading is very useful. Since DiscImageCreator can use /c2 error correction, dumping with a compatible Plextor model is preferred.
Dumping:
- Insert the Audio Trap Disc to an HD Area compatible drive
- In command line, cd (change directory) to the folder containing "DiscImageCreator.exe"
- Run DiscImageCreator.exe stop [DriveLetter]
- Remove the top off the drive
- Insert the GD disc and run: DiscImageCreator.exe close [DriveLetter]
- Then run the dumping command: DiscImageCreator.exe gd [DriveLetter] foo.bin [DriveSpeed(0-72)] /c2 (Note #1: " /c2" is only for use with compatible Plextors. Note #2: Adding the command "/be pack" may[1] be helpful when dumping GD-Rs.)
- Dump multiple times until you get an error-free dump (check the Command Prompt output after DiscImageCreator finishes dumping)
Note for GD-R dumping:
- 1x, 4x, 8x read speeds can be helpful or even necessary when dumping GD-Rs. Try starting with 8x, if one of those speeds doesn't work then try another.
- If you have issues where the drive locks up partway through, disabling cache flushes helps: DiscImageCreator.exe gd [DriveLetter] foo.bin 8 /c2 /f 600000
Submitting your Dump Info
Here are example submissions: [2] [3]
Note: MPF.Check (UI or CLI) supports DCDumper logs. This greatly speeds up gathering submission info.
We'll presume you've used Disc Image Creator for you dump in both LD and HD Areas.
Open your "!submissionInfo.txt" file from both your LD and HD Area dump. Copy in the additional track information from your HD Area !submissionInfo.txt file into your LD Area !submissionInfo.txt file in three sections:
- "DAT"
- "Cuesheet". When combining Cuesheet data for LD and HD Areas, paste "REM SINGLE-DENSITY AREA" at the top of the cuesheet, and "REM HIGH-DENSITY AREA" in a new line after the LD Area cuesheet into, then finally the HD Area cuesheet text.
- "Write Offset". For determining write offset for HD Area of a DCDumper + ice.exe dump, open the .txt file output by Ice:
- Combined offset = Disc offset + Drive offset
- Kreon drives used for DC dumping have a +6 offset
- Calculation for Disc Offset: [Example Combined Offset of +30] - [(Any Kreon Model) Drive Offset of +6] = [Disc Offset of +24]
- Offsets for GD-ROMs are formatted in entries as follows: [LD Area disc offset]|[HD Area disc offset]
Fill in Ring Code data and any relevant Comments. Post on the Redump "New Dumps" subforum.