Here are dumping methods for Nintendo Gamecube / Wii optical discs according to Redump.org quality standards.

Before dumping anything take care about infos you need to submit:

1. Checksum (crc32, md5, sha1, ed2k): use Hashcalc (mirror) to get these infos quickly

2. Image size: it must be always as follows:

- Gamecube: 1.459.978.240 bytes (712.880 sectors)
- Wii: 4.699.979.776 bytes (2.294.912 sectors)
- Wii DL: 8.511.160.320 bytes (4.155.840 sectors)

3. Disc ID / Serial: DL-DOL-Gxxx-yyy for Gamecube and RVL-Rxxx-yyy for Wii, the one written on upper side of disc (if you cannot read it find the right light angle).

4. Ring Code: you can find it on bottom side on disc in the inner inside ring (if you cannot read it find the right light angle). If you cannot read Ring Code at all, please post Barcode instead.

5. Region: Japan, Europe, USA, France, Germany, Spain, Italy, Australia, etc. (if not sure check yyy of Serial).

6. Version: open your dumped image with HxD (or another Hex editor) and look at offset 0x07:

http://www.rocknroms.net/gcdump/images/header.png

if value is 0x00 => v1.00 ; if value is 0x01 => v1.01 ; if value is 0x02 => v1.02 and so on.

Version can be also retrieved via Ring Code. Take for example this "1080° Avalanche (E)" GC ring code

"IFPI LQ11 103J3008 DOL-GTEP-0-00 JPN S0"

or Wii "2K Sports: NBA 2K10"

"IFPI LL89 E09J1512 RVL-R76E-0A-0 USA M1S7"

the bold numbers are the same as the hex value:

For GC: if value is -00 => v1.00 ; if value is -01 => v1.01 ; if value is -02 => v1.02 and so on.
For Wii: if value is -0 => v1.00 ; if value is -1 => v1.01 ; if value is -2 => v1.02 and so on.

Please take care to check Version with the standard Hex viewer method because numbers in GC/Wii ring codes are smaller than any other media around and it's so easy to write down the wrong number or letter.

7. Edition: Original, Player's Choice, Bundle, Promo, Demo etc.

8. Languages: English, Japanese, French, Spanish, German, Italian and so on

- Some games have language selection at game loading or inside game options.

- Some games have language detection by bios configuration, change it to see if the game has more languages.

- Please take care that if a game has for example "En,Fr" as spoken languages and "En,Fr,De,Sp,It" as subtitles, it's better to submit "En,Fr" as languages and add subtitles languages in the notes (if you use wip form).

9. Tools used to dump your disc (see below).

Notes:

1. Optional infos are ---> Dol-MD5 (only for Gamecube use dolmd to get checksum - mirror), Barcode.

2. Header is not required and it has no reason to be archived because every usefull data is still avaible (unless Streaming that is not archived and it has to be clearified). Header can be necessary for alternative dumps when it's the only info to identify a dump.

3. Please post also Layer Break for Dual Layer Wii discs.

4. Gamecube/Wii discs has no clear EXE date. The date you find in Gamecube images header is not an EXE date as we mean; that date is probably the EXE date of boot application which is common to many games, like autoexec for old dos games (if you play something around with some vintage cpu like MSX you'll know better what I mean).

Here is a sample template anyone can use to post needed infos:

Title:
Region:
Languages:
Serial:
Ring Code:
Version:
Edition:
Image Size:
CRC32:
MD5:
SHA-1:
ed2k:


DUMPING METHODS

----------------------------------------------------------------------
DUMPING disc from your PC
----------------------------------------------------------------------

You need one of the following LG DVD drives:

LG-8164B
LG-8163B
LG-8162B
LG-8161B

A. Dumping with Rawdump (mirror - you may need to install .NET framework 2.0)

http://www.rocknroms.net/gcdump/images/rawdump.png

Simply insert disc in your LG drive, check "Dual Layer" box if disc is dual layer and click "Start Dump".

It will take around 45min for Gamecube and 2h 30min for Wii, when the dump is finished a popup will show.

B. Dumping with Friidump (mirror - this package contain a batch file to automate the process, edit it if needed)

Use the batch file in the archive (edit it if needed, I have set it to typical drive D:) or start a command prompt, move to friidump directory and type:

friidump -d D: -a

If your LG drive letter is different, type the right letter instead of D

Let program dump disc, it will take a little more than Rawdump.

----------------------------------------------------------------------
DUMPING disc from your softmodded Wii to SD card
----------------------------------------------------------------------

1. Softmod your Wii with one of the guides around (gbatemp or wiihacks websites for example and take care not to brick it with stupid IOS or Sysmenu patches).

Tools needed: SD card (8GB is best choise) + Superdump + IOS249 (cIOS38) v1.3b

2. Copy the content of this package (mirror) to your SD card, it contains Superdump v.1.2 and v1.3, cIOS38 v1.3b and cIOS uninstaller.

3. If you have cIOS v1.4 or v1.5 uninstall it with the unistaller and then install v1.3b to have a clean system. Don't use IOS249 v1.4 or v1.5 because it has a bug which cannot read last sector of first layer of Wii dvds (not confirmed: please beware some modchips cannot retrieve right dumps of Wii dvds even with v1.3b or lower)

4. Insert your disc and your SD card in your Wii, lauch HBC (HomeBrew Channel) and load Superdump. The screen will switch to a command line with the following options to choose with your Wiimote:

B  = changes DVD type (Gamecube, Wii Single Layer, Wii Double Layer).

1  = changes image chunks size

2 = changes #n of chunks to dump *

A = starts dumping

* please remember to move to next chunk -- 0,1,2 -- after you dump first one otherwise you'll continue to dump the same chunk. Gamecube discs can be dumped in one chunk, Wii games have to be dumped at least in 2 chunks because a chunk cannot be bigger than 3GB because of FAT limitation.

It will take around 10min for GC and 30min for Wii discs, if you got "error reading sector data" message your dump is wrong (last sector, or more for DL discs, has not been dumped. See above).

5. Once you have dumped one chunk (if you have a 8GB SD or bigger you can wait and dump all the chunks), move it on your PC and delete it from SD. Remount SD in your Wii, dump next chunk and repeat the process untill you have finished.

6. Once finished you'll have all your chunks on PC (Ex: RZDJ01_0.bin, RZDJ01_1.bin, etc. if dumped with Superdump 1.3, 1.bin,2.bin, etc. if dumped with Superdump 1.2) and you have to join them to a single file; to do this simply open a command promp and join files with copy command *:

copy /b RZDJ01_0.bin+RZDJ01_1.bin RZDJ01.bin

or

copy /b 1.bin+2.bin dump.bin

Notes:

1. Superdump v1.3 has a problem with multiple disc Gamecube games, you have to dump and move to PC the first disc dump before dumping the second disc because of same name in the header. To avoid this loss of time dump first disc with v1.3 and second disc with v1.2 (this is mainly why I put both apps in the package).

2. * If you have problems with copy command you can join chunks with HxD: on menu select "Extras ---> File tools ---> Concatenate...". On the new window open all chunk files, order them right and save the joined file as output with your preferred name in your preferred directory.

3. Don't dump anything via wifi tools becuase it's confirmed it will return a bad dump!!!

----------------------------------------------------------------------
DUMPING GC disc from your Gamecube
----------------------------------------------------------------------

...to do (see here)

Zipfile with dat is created on the fly (please correct me if I'm wrong) and probably now it's too big to be handled by DB?

Do you invert cdtools sector views while posting? I ask because the different one above is LG and bot plextor are the same.

F1ReB4LL wrote:

Companies aren't so stupid, if there's a checksum - there are releases somewhere, that's why MAME follows the "3 years" rule and excludes single games by request. Hosting .torrent files is also legal (theoretically), but many trackers are being constantly sued (even MiniNova, which isn't even a tracker). I don't see a reason to be so brave, we should have some caution to prevent the possible unpleasant consequences.

Mame is not a DB, it's a software which emulates copyrighted games so they can have problems (in reality they will have any problem if they are smart, people who normally sued torrents sites and so on are people who has nothing to do with big companies. They are only intermediary that wants to make money and act like nazi, most of times they send their shit emails without even saying who they are. They simply are considered too much and they act on fear). Normally big companies are more interested in region bypass or hardware hacking, normally real piracy is only a great deal for console producers (more piracy more console sales).
No-intro releases dats for GBA and NDS the same day a game is on shelf and I never hear they were sued or else.

105

(13 replies, posted in General discussion)

I was thinking that entry was bad since the day it was added. Simply a suspect I have, probably dumped with bad tools.

If you haven't subtracted anything yet:

A) +8 (combined read offset => drive read offset + disc write offset)

B) +2 ==> +8 - (+6) = +2 (disc write offset)

Feltzkrone wrote:

I already came over a CD (Al Unser, Jr. Arcade Racing) where a wrong bit is in subchannel data in one sector which is read as it is regardless what drive I used - meaning it really is on CD and not just a random error dropped in by the drive. I guess 1:1 preservation (which is aimed at redump.org AFAIK) should preserve this wrong bit, too. What's your opinion on this?

Data is on CD only if it's in disc sector viewer. If the disc has some signs or scrathes and the drive is not good you will get errors, so if you cannot dump properly a disc, there's nothing to preserve.
If this error is something really on CD and if we are talking about PC stuff it could be some kind of protection so it has to be dumped differently.

Feltzkrone wrote:

or maybe start all over again as Rockrnoms doesn't find it easy to read

I think it's quite complicated to understand for most of people, moreover take a look at the forums also for reMove tool, you can find it in quite every forum faq by me. It can be more useful while moving sectors.
It will be great if you can code a tool that will avoid all those exceptions and that can handle them in a while.

109

(2 replies, posted in General discussion)

It was already discussed in the past, it's not quite safe to add DVD dumps which cannot have a real comfirmation / disc infos.
IMO it could be discussed if those dumps are verifications, but also this is not safe.

Your explanation is quite confusing, sorry. Moreover we have some other tools that can simplify the job.
Also about point 5, if you are referring to 2 tracks disc (1 data 1 audio) you don't have to do all this job to get real pregap.
I'll test what you say on point 5 as soon as possible to fit it in exceptions.

Obviously it's better to update guide before translating.

112

(27 replies, posted in General discussion)

I don't assume anything, I'm complete sure as I recovered those sectors (not my dumps) this way (scrambled and unscrambled) and because those are empty sectors that are always the same in the same position.

And I repeat those sector are not garbage, garbage is something else: wrong offset detection or bytes added by firmware or program, bytes not present on CD.

Your method is only good for converting the random dumps to match our dats

What's the difference if they match? I don't say to do this when you like but after analysing subs... if subs say something, is this wrong now?
I only say: TEST WHAT I SAID instead of assuming it's wrong because you assume wrongly that empty data sectors are something different. If I got 99 matches on 100 this is not assuming, but it's a proof where you have the remaining one (see Sakura Tsushin) as exception. We have a lot of exceptions in DB so please don't tell me that an exception doesn't make a rule because we can close DB as everything could be wrong.

Moreover I never said I want to submit dumps this way, mine was an analisys about something; did you read somewhere I wanted to add discs dumped this way?

I find this solution not only for recovering dumps around but also because as you should remember I have problems dumping Gunbird with cdtoimg

Please, don't ever generate any data, every byte should be read from CD

It's better also not to repeat this everytime you want something to match your thoughs because again we can close DB as everything could be wrong (psx, safedisc, all dvds, 2 tracks discs, etc.).

113

(27 replies, posted in General discussion)

This http://redump.org/disc/8047/ is the only exception, the other one is the same of my examples, that is not garbage unless it has wrong offset.

About the other point you don't fix anything, simply speed up the process importing the same sectors from an empty image without redumping it with cdtoimg or trap disc. There's nothing to fix or modify, disc has always the same structure, if it's mode1 for example, all empty sectors will have the same header at same position for any disc with mode1 form unless toc is fake. The sector I write above is the first empty sector of any image, it's always the same in any disc if this sector is empty. So if you know with sub analisys that n sector or sectors have to be scrambled you can simply take these from an empty image (same position, same format) and unscramble them with descramble_cdda. If they don't have to be scrambled they are simply ready as they are.

PS: About your PCE assertions above, today we have probably something more to check real gaps, I'll report something as soon as I have time to take a look.

114

(27 replies, posted in General discussion)

What are you talking about? Did you understand or not?
Empty data sectors has nothing corrupt, they are simply empty with headers

The following is simply an empty mode1 sector and not garbage:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  00 FF FF FF FF FF FF FF FF FF FF 00 00 02 00 01  .ÿÿÿÿÿÿÿÿÿÿ.....
00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000020  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000040  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000050  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000060  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000070  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000080  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000090  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000000A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000000B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000000C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000000D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000000E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000000F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000100  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000110  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000120  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000130  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000140  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000150  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000160  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000170  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000180  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000190  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000001A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000001B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000001C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000001D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000001E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000001F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000200  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000210  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000220  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000230  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000240  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000250  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000260  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000270  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000280  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000290  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000002A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000002B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000002C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000002D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000002E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000002F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000300  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000310  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000320  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000330  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000340  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000350  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000360  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000370  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000380  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000390  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000003A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000003B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000003C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000003D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000003E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000003F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000400  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000410  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000420  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000430  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000440  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000450  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000460  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000470  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000480  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000490  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000004A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000004B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000004C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000004D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000004E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000004F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000500  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000510  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000520  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000530  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000540  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000550  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000560  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000570  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000580  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000590  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000005A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000005B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000005C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000005D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000005E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000005F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000600  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000610  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000620  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000630  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000640  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000650  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000660  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000670  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000680  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000690  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000006A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000006B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000006C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000006D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000006E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000006F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000700  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000710  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000720  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000730  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000740  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000750  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000760  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000770  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000780  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000790  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000007A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000007B0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000007C0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000007D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000007E0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000007F0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000800  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000810  C5 13 68 2B 00 00 00 00 00 00 00 00 00 F7 00 F5  Å.h+.........÷.õ
00000820  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000830  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000840  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000850  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000860  00 00 00 00 00 00 52 35 B8 7D 00 00 00 00 00 00  ......R5¸}......
00000870  00 00 00 F5 00 F4 00 00 00 00 00 00 00 00 00 00  ...õ.ô..........
00000880  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000890  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000008A0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
000008B0  00 00 00 00 00 00 00 00 00 00 00 00 97 26 D0 56  ............—&ÐV
000008C0  00 00 00 00 00 00 00 00 00 41 00 00 00 00 00 00  .........A......
000008D0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 2D 17  ..............-.
000008E0  2E 1B B1 48 B2 44 00 00 00 00 00 00 00 00 00 00  ..±H²D..........
000008F0  00 00 00 00 00 00 00 65 00 C2 00 E6 00 43 00 00  .......e.Â.æ.C..
00000900  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000910  00 00 45 3C 53 75 33 2B 25 62 00 00 00 00 00 00  ..E<Su3+%b......
00000920  00 00 00 00 00 00 00 00 00 00 00 90 00 C1 00 12  .............Á..

a) Plextor, cdtoimg and chopfile or b) Swap trick, CD tool and chopfile

Don't you have to rescrambling something in both situations? Or not? don't you have to use descramble_CDDA or something similar?
I repeat again THOSE SECTORS ARE EMPTY and so they are always the same if they take sector count and mode (the only exception can be fake TOC discs, but I don't see any in DB, did you?).

And I repeat again descrambled data can be wrong ok, if so you can use sector from an empty mode1/2 track to fix it (or simply use this track to create scrambled sectors). And there's no garbage at the end on data track, those are empty dta sectors (you want to call them descrambled audio pregap? Wel is the same thing because this audio is 0x00 and when descrambled you will get empty data sectors like the one above, no garbage this is simply header on 0x00).

115

(27 replies, posted in General discussion)

F1ReB4LL wrote:

I repeat, any drive descrambles everything in datatrack automatically, including the next audio gap, because it "belongs" to the same datatrack (drive splits tracks by TOC and TOC contains LBAs of all the 01 indexes, 00 index belongs to the previous track, according to this logic), d8 edition of cdtoimg is a must.

I didn's say anything different. We are talking of audio gap and if we have a bad mastering situation (this gap attached to the end of "track 01" has any garbage due to offset correction, the sectors are simply saved as data <---> they are 0x00 audio descrambled to data format so simply empty sectors with mode1/2 headers).
If you have to move sectors as audio, simply use the operation I said above to unscramble sectors (I did this operation to retrieve most of SS dumps if I got right offset correction).

116

(20 replies, posted in General discussion)

Yes, 2.74 confirmed without any oddities in sub, so it's quite sure that it was a problem of other drives of yours.
Also write offset is right 8 - 30 = -22

As sub has no problem both perfectrip and EAC should detect right pregap 2.74 with PX-716A.

117

(27 replies, posted in General discussion)

F1ReB4LL wrote:
Rocknroms wrote:

F1ReB4LL, if it's confirmed that there are data sectors in pregap we can simply take them from Isobuster dumping the data track as always and then use remove instead of resize:

Any drive manages the 1st gap as a part of data track, if there are any scrambled sectors - they will be descrambled. Also don't forget, that you can't get a complete gap in isobuster dump of the first track - with positive combined offset there's always a garbage between the data and audio sectors and, as a result, the very end of the gap is cut.

If you save track or segment with isobuster (or if you take it from bin-cue) there's no garbage inside pregap. Garbage is only present in sector view on real CD (or you can get it with wrong offset dumping audio), it is not dumped otherwise you'll have to move also data offset like we do with audio.
It could be that IB put garbage in pregap of track02 (dumping track01) simply because it cannot handle well scrambled sectors, otherwise for example every SS disc with data+data would be wrong (I always got same result perfectrip=isobuster after moving sectors and they are all disc with positive offset).

By the way my point is always valid, you can use also my tools used to fix DC pregaps, simply find sector count, save and unscramble (all those sectors we are talking about are simply empty data sector with data only headers and thse are always the same if you get the correct data mode).
Moreover you can get all pregap in data mode in IB, sector count it's not cut as it is between low and high density on GDIs.

118

(27 replies, posted in General discussion)

Feltzkrone wrote:

And whatever the right choice on this question is: How can we represent the sector mode switch at relative -02.00 in Q subchannel with CUE sheet syntax properly? At least I don't find a way to do this. Isn't it that when CUE sheet denotes Audio sectors the subchannel will be (re)generated accordingly, i.e. the 75 data sectors in Track 2 will be marked with Q-CONTROL 0 (Audio) instead of 4 (Data)? So how can the CD properly be preserved using CUE/BIN then?

You cannot represent sectors i CUE correctly at all. This matter was discussed in the past with Fireball, I had the same thoughts of yours but then I change my mind because we cannot fix arbitrary something reported in subcode unless we have a clear reply from someone who mastered those discs. To explain better, if those discs were badly mastered (as it is) we cannot fix them otherwise we have no real preservetion. Eventually it could be discussed again once we have more hints.
Moreover redump is not a DB for burning/pirating/etc., but for preserving data. Those sectors can be switched in any moment, at least we have preserved all data like reported in subcodes.

It would be nice if a guide for exactly that situation (pregap consists of both data and audio sectors) with explanation of technical background could be added somewhere by a person who really understands it.

I'm working on something also because we have no scambling/descrambling faq unless themabus faq on pce discs.

ssjkakaroto wrote:

@whoever added my dump: I think you should leave the comment about the scrambled data in the track 2 pregap.

Can you repost comment you add about un/scrambled sector (I dont understand if is one sector or one second) and someone will add it back.

EDIT: I have to understand too why someone removes comments in PC section when they are necessary. I have already asked it in the past...

119

(27 replies, posted in General discussion)

F1ReB4LL, if it's confirmed that there are data sectors in pregap we can simply take them from Isobuster dumping the data track as always and then use remove instead of resize:

remove -size=225sec "track 01.bin" pregap.bin

then cut the lenght of data sectors, example if it's 1 sector:

remove -direction=left -size=1sec data_scrambled.bin pregap.bin

then use Descramble_CDDA (if there's no link around I'll upload it again) to descramble this data.
At last when you have the descrambled sector, like in the example, you have simply to remove first sector of track02 and exchange it with the new descrambled one.
I think it's more speedy and I can confirm you got same result as I recover some of your dumps when I got also right offset.

120

(20 replies, posted in General discussion)

Yes, if real pregap is right you have to take offset you'll find at 2.00 but pregap will be 3.00 (it's better to use d8 command to avoid errors) and as you said

In this case we have a pregap of 03.00 consisting of 01.00 of Mode 1 sectors and 02.00 of Audio sectors.

121

(20 replies, posted in General discussion)

It was an example, obviously you cannot determine pregap on audio sectors, but reverse sentence is possible: offset on 2.74 but pregap on 2.00 --> this will take 74 sectors of audio to data track and they have to take audio mode so you have to move 74sec of 0x00 without changing mode (I know it's weird, but if there's a mastering error that report this we have to save it as it is unless someone who mastered disc will prove the correct one).

Sorry but data you reported doesn't seem scrambled bytes but offset correction garbage. I repeat it's better to wait also Fireball sentence or at least a sub with real plextor.
With a d8 command compatible drive you can also dump disc with cdtoimg (http://vigi.dremora.com/cdtoimg.rar), it will dump all disc in scramble format so you can get the real lenght of track01-02.

122

(20 replies, posted in General discussion)

About TOC, ok if it's imgburn so gaps for other tracks is right, by the way it's a wrong toc as it appends gaps to previous track.
I don't know if it's good to change options found by EAC.
As I said it's better to wait what plextor will say also because it can be that offset correction is on 2.00 but pregap is 2.74, so you will have to dump disc with offset taken by d8 command but with pregap from sub (in this situation as those sectors are audio you'll have to descramble 0.74 sectors because they cannot be only 0x00). If the opposite you'll have to take the reverse and scramble. I hope I explained well the matter.

123

(20 replies, posted in General discussion)

With CDTool I am unable to read LBA 41734 to 41957

This is the main problem with cdtool because it feels those sectors with errors (sometimes is also impossible to understand mode of those sectors), instead of cloncd which tries something.
By the way after you said this it's better to wait to verify a real plextor sub even if it's not a final sentence.

The TOC you reported (from cdtool?) clearly said pregap is 2.00

This a log from your plextor/lg1 I got, simply add 150 for track01 pregap and you got same result for track01 (so your toc says pregap for track02 is 2.00 and not 2.74, but it seems your toc gives also 2.00 pregap for all other tracks losing one sector at the end, so it's quite wrong):

Track   Mode       Flags   Start               Length
-----------------------------------------------------------------
01      UNKNOWN    6       00:00:00 (     0)   09:17:33 ( 41808)
02      UNKNOWN    2       09:17:33 ( 41808)   06:17:07 ( 28282)
03      UNKNOWN    2       15:34:40 ( 70090)   05:40:50 ( 25550)
04      UNKNOWN    2       21:15:15 ( 95640)   05:42:00 ( 25650)
05      UNKNOWN    2       26:57:15 (121290)   07:51:67 ( 35392)
06      UNKNOWN    2       34:49:07 (156682)   03:47:12 ( 17037)
07      UNKNOWN    2       38:36:19 (173719)   04:54:63 ( 22113)
08      UNKNOWN    2       43:31:07 (195832)   04:47:66 ( 21591)
09      UNKNOWN    2       48:18:73 (217423)   05:34:19 ( 25069)
10      UNKNOWN    2       53:53:17 (242492)   05:01:52 ( 22627)
Leadout                    58:54:69 (265119)

Yes, to look at sectors I used Subcode analyzer, to get pregaps I used a beta tool that I don't know if can be shared.

124

(20 replies, posted in General discussion)

I took a look at your subs.

LG1 and plextor reports 2.00 and LG2 reports 2.74.
It seems to me that there's something on sector 41735 (CD is unprotected? No securom?) as it change to Q-Control=0x02 and Q-TNO=0x02 (track number). Then LG1 and plextor come back to Q-Control=0x06 and Q-TNO=0x01 indeed LG2 stands on 0x02 for both. It's not an EAN sector as Q-Address=0x01, so I cannot say at 100% which is right but I will bid on 2.00 instead of 2.74 because in the past subs with double sector count entries (0x73 is repeated - sector 41735-41736) are wrong and is a problem normally found with cdtool / perfectrip ccd and so on.

I hope Fireball will take a look at those subs too so we can find a final solution.

PS: your plextor is a real one? I understood you cannot use d8 command,  but if your drive is a real plextor it works (it will be better because in a disc like this you can get wrong offset with normal method / sector count).

125

(20 replies, posted in General discussion)

No problem, if you can please post them on mediafire.com

PS: ops, I see you used sector viewer, so this data is on real cd if I understand well? If yes this double sector has to be dumped as it is but has nothing to do with gap lenght. Let's see the subs and I will try to give a better explanation, unless it's a new exception never found here until today.