751

(3,497 replies, posted in General discussion)

Thanks. download link is same.
- fixed: disc speed changing doesn't work for linux.
- fixed: increased memory allocation for double pointer (subchannel, cd-text)
- deleted: some warning when used Wextra

F1ReB4LL wrote:

Does DIC also support RCE (Regional Code Enhancement) discs?

Perhaps no. At least, dic can't detect all DVD protection (RCE, Sony ARccOS, UOP, Disney X-Project DRM, Cinavia Protection etc.) except css/cppm/cprm. ARccOS adopts bad sectors, others I don't know the detail.

752

(3,497 replies, posted in General discussion)

Uploaded test version.
win: http://www.mediafire.com/file/eq80y20l9 … st.7z/file
linux: http://www.mediafire.com/file/uw3e03kdk … t.tar/file

iR0b0t wrote:

And in addition to that check mode 0x00 according to Ecma-130.

Added.

Jackal wrote:

If there's a sector inside a data track that has a different format, so non-data, different mode or other yellow book violation, then it should be regarded as an error imo for the error count, even if ECC/EDC matches.

All set to error.

753

(3,497 replies, posted in General discussion)

iR0b0t wrote:

If sector mode is not 0x00 or 0x01 or 0x02 then treat it as error.

OK, but is this error, not warning? As you know, CDmage doesn't distinguish between error and warning.

And...

CDmage B5 1.02.1 error report for image "FATAL.cue"
Track #| Sector|Sync|Header|Subheader|EDC|Intermediate|ECC P|ECC Q|Severity|Content of sector
      1| 63.502| Yes|  Yes |   No    |No |    N/A     | No  | No  |Low     |unused/empty
      1| 63.503| Yes|  Yes |   No    |No |    N/A     | No  | No  |Low     |unused/empty
Total error count:2


EdcEcc error count:
[INFO] Number of sector(s) where EDC doesn't exist: 2
[INFO] Number of sector(s) where sync(0x00 - 0x0c) is zero: 2
    Sector: 63352, 63353, 
Total errors: 0
Total warnings: 2

Are all 2352 bytes zero sectors error or warning or no error?


More...
4th sector from last of SecuROM changes the mode from 1 to 2 intentionally for the purpose of protect.
Is this error or warning?

754

(3,497 replies, posted in General discussion)

microsoft wrote:

RegionManagementInformation

Indicates in which regions of the world the disc can be played. Each bit represents one of eight regions. If a bit is set, the disc cannot be played in the corresponding region. If a bit is not set, the disc can be played in the corresponding region.

I fixed it in 7/26.

e.g. dvd-video

========== CopyrightInformation ==========
        CopyrightProtectionType: CSS/CPPM
    RegionManagementInformation: 2

e.g. xbox360

========== CopyrightInformation ==========
        CopyrightProtectionType: No
    RegionManagementInformation: 1 2 3 4 5 6 8

iR0b0t wrote:
sarami wrote:

If incorrect 16th byte should be an error, CDmage is correct. If not so, DIC is correct.

We should check CD specifications. If this byte is specified to be either 0x01 or 0x02 and nothing else then it should be treated as an error, otherwise maybe make it a warning.

Ecma-130 defines 0x00, 0x01 and 0x02. I knew 0x00 for the first time.
https://imgur.com/a/97uUzeX

755

(3,497 replies, posted in General discussion)

Jackal wrote:

I assumed they are lead-out sectors?

But subchannel of these sectors points data, not lead-out.
edcchk doesn't see the subchannel, so it can't recognize data or audio or lead-in/out correctly.

330553 sector is apparently a bad sector, bad edc/ecc.
330550, 330551 and 330552 are sectors edc/ecc is no problem.

iR0b0t wrote:

CDmage does too much checks, different subheaders should not be flagged as an error.

edcchk cannot differentiate between data and audio sectors if you scan the whole image containing audio tracks, and if i remember correctly it treats empty data sectors as non-data, which would be incorrect, because it has to be an error.

I think so, too.

A problem is 16th byte (mode).

CDmage recognizes these 3 sectors as error data sector because 16th byte is not 0x01 or 0x02.
edccchk doesn't recognize these 3 sectors as data sector because 16th byte is not 0x01 or 0x02.
DIC recognizes these 3 sectors as non-error data sector because edc/ecc is no problem.


edccchk is clearly incorrect because these 3 sectors are data sector.

If incorrect 16th byte should be an error, CDmage is correct. If not so, DIC is correct.

iR0b0t wrote:

If warnings reflect different or wrong subheaders only (i cannot think of any other case right now) then we can have an additional note about warnings in database.

It's easy to understand if 'error counts' of redump'org db counts only bad edc/ecc.

756

(3,497 replies, posted in General discussion)

Jackal wrote:

There are lead-out sectors inside the data track.

What evidence let it say to you?

757

(3,497 replies, posted in General discussion)

ajshell1 wrote:

No. I won't do that.

Ok. Then, you need to get a no-damaged disc because I don't know if 288 bits error is really intentional c2.

315213 and 315214 sectors are all zero. Is this audio silence? Perhaps admin or moderator can judge it.


xTMODx wrote:

also a lot of older PC Games coverdiscs have 4 non data sectors for example PC Games 1/97 https://www35.zippyshare.com/v/7diPaxz0/file.html

Same as http://forum.redump.org/post/63108/#p63108

CDmage looks the invalid mode sector on error data sector. In this case, this disc has 4 errors.
edcchk looks the invalid mode sector on non-data sector. In this case, this disc has 0 error.
DIC looks the invalid mode sector on non-error data sector and incomplete data sector on error data sector. In this case, this disc has 1 error.

Which is correct? Perhaps admin or moderator can judge it.

758

(32 replies, posted in General discussion)

Or you can use "xboxswap" command of DIC.

### Dumping Guide for XBOX/XBOX360 (XGD2)/XBOX360 (XGD3) on genaral drive
 Prepare DVD-DL or create the DVD+R DL trap disc in advance.  

#### How to prepare
 You need a pressed DVD-DL disc with around 8.5GB data on it
 
 XBOX: Layerbreak larger than 1913776 and the exact size needed (in sectors) is (your_disc_layerbreak - 1913776) * 2 + 3820880

#### How to create
 XBOX: DVD (Length is 3820880 or larger, Layerbreak is 1913776 or larger)

1. Create image file of the above DVD using dumping tool (e.g. isobuster)
2. Run [ImgBurn](http://www.imgburn.com/)
3. Setting LayerBreak manually (L0 sector num is about a half size of DVD length)  
   e.g. If DVD length is 3900304, L0 sector num is about 1950160
4. Before burn the image file, you need to confirm the size is correct  
   e.g. (1950160 - 1913776) * 2 + 3820880 = 3893648 => 3893648 is smaller than 3900304, so the DVD+R DL this image is burnt can dump a XBOX disc
5. Burn image file to DVD+R DL

#### Dump the disc
1. Insert the DVD-DL or DVD+R DL trap disc to a general DVD drive.
2. Run below. (stop spinning disc)  
   DiscImageCreator.exe stop [DriveLetter]
3. Use a pin to press the escape eject button, so the tray will eject (or remove
   the drive cover).
4. Insert the XBOX disc and run below. (close the drive tray)  
   DiscImageCreator.exe close [DriveLetter]  
   (or gently push the tray back or put the drive cover back on).
5. Run below.  
   e.g. Dead or Alive 3 http://redump.org/disc/27157/  
   DiscImageCreator.exe xboxswap [DriveLetter] foo.iso 12 292756 467910 686060 830074 999794 1212958 1579164 1719138 2010470 2372562 2527492 2682830 2915560 3065604 3219138 3455656  

759

(3,497 replies, posted in General discussion)

It needs other logs.

760

(3,497 replies, posted in General discussion)

Updated makefile. Please pull the test branch.

If I remember rightly, some Sega Saturn discs (perhaps +588/+1176 offsets?) have duplicate sector in the pregap of track 1.
Or some FM Towns discs are same. http://forum.redump.org/topic/16418/add … new-dumps/
These pattern can't recognize at 0xbe (non-plextor drive) ripping. Is TeamEurope disc similar pattern? I don't know now... It needs to dump by other drive and other disc.

As a result, you maybe are right. But you shouldn't have fixed it without consultation and discussion, should you?
At least, I think you shouldn't add the disc which is suspicious of the error in the db directly, for reliable db.

762

(3,497 replies, posted in General discussion)

http://forum.redump.org/post/58182/#p58182
"312" sectors are intentional c2 errors, but I don't know all intentional errors are 312.
At least please check rereading at 10000 times.

discimagecreator cd f Startopia (USA) 32 /c2 10000 /d8 /sf 

763

(3,497 replies, posted in General discussion)

Jackal wrote:

Another issue where DIC gives 3 errors (2 discs give the same dump), but a CloneCD dump from non-plextor drive gives 0 errors.

https://www12.zippyshare.com/v/xttyLELo/file.html

Can you check what's wrong?

mainError

0900 : 7D A4 4D 62 45 A3 B0 63  20 29 7D 4A 9B E6 87 CC   }.MbE..c )}J....
0910 : 98 12 82 C1 B0 21 D7 BB  00 FF FF FF FF FF FF FF   .....!..........
0920 : FF FF FF 00 08 95 16 61  00 9B D5 CB A3 0A E1 A3   .......a........
LBA[041491, 0x0a213]: Track[01]: Invalid sync. Skip descrambling
========== LBA[041491, 0x0a213]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : AA 83 EC 83 12 E2 67 09  6A 0A 88 8C 8A 20 2E 86   ......g    j.... ..
0010 : 23 01 3D AF 2F 45 EF 35  73 52 F8 2F 48 0D 05 18   #.=./E.5sR./H...

Sync exists, but it's slided behind 24 bytes. Perhaps drive's cache is broken (or firmware/drive/dic bugs?). It maybe is fixed if rereading (but it's not supported yet in this case).

764

(3,497 replies, posted in General discussion)

xTMODx wrote:

I have only edcchk 1.11 here the result

I understood CDmage looked invalid mode sector on error sector and edcchk didn't look it on non error sector.

reentrant wrote:

"Always descramble sectors of data track"

to:

"Descramble sector of data track if there's a proper sync and mode"

No, to be exact...

"Descramble sector of data track if there's a proper sync and mode"

to:

"Always descramble sectors of data track"

to:

"Descramble sector of data track if there's a proper sync and reserved (only mode 1)"
reentrant wrote:

Q CRC value from the file       : 3B01
Computed Q CRC value            : F730

3B01 XORed with 0x8001 is BB01, not F730. So perhaps this sector also has random errors in RMSF or AMSF or CRC.
There are huge suberror in this disc, so it needs to be dumped by other good-condition disc.

ajshell1 wrote:

I've had a problem with some PC games with SafeDisc.

Plz upload the log of latest version.


F1ReB4LL wrote:

Does the c2 feature work properly?

I say yes if the drive reports c2 errors properly.

765

(3,497 replies, posted in General discussion)

How about edccchk v1.26?

766

(3,497 replies, posted in General discussion)

xTMODx wrote:

DiscImageCreator_20160805_dump.7z

EdcEcc.txt says

LBA[305469, 0x4a93d], This sector is audio or scrambled data or corrupt data
LBA[305470, 0x4a93e], This sector is audio or scrambled data or corrupt data
LBA[305471, 0x4a93f], This sector is audio or scrambled data or corrupt data
LBA[305472, 0x4a940], This sector is audio or scrambled data or corrupt data
User data vs. ecc/edc match all
xTMODx wrote:

DiscImageCreator_20180901_dump.7z

LBA[305469, 0x4a93d], MSF[67:54:69], mode 1
LBA[305470, 0x4a93e], MSF[67:54:70], mode 1
LBA[305471, 0x4a93f], MSF[67:54:71], mode 1
LBA[305472, 0x4a940], MSF[66:d4:72], unknown mode: a1
[ERROR] Number of sector(s) where mode(0x0f) is unknown: 1
    Sector: 305472, 

mainError.txt

LBA[305469, 0x4a93d]: Track[01]: Invalid mode. 
========== LBA[305469, 0x4a93d]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 69 81   ............f.i.
LBA[305470, 0x4a93e]: Track[01]: Invalid mode. 
========== LBA[305470, 0x4a93e]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 70 A1   ............f.p.
LBA[305471, 0x4a93f]: Track[01]: Invalid mode. 
========== LBA[305471, 0x4a93f]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 71 A1   ............f.q.
LBA[305472, 0x4a940]: Track[01]: Invalid mode. Invalid reserved byte. Skip descrambling
========== LBA[305472, 0x4a940]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 72 A1   ............f.r.
0010 : 00 28 00 1E 80 08 60 06  A8 02 FE 81 80 60 60 28   .(....`......``(
0020 : 28 1E 9E 88 68 66 AE AA  FC 7F 01 E0 00 48 00 36   (...hf.......H.6
0030 : 80 16 E0 0E C8 04 56 83  7E E1 E0 48 48 36 B6 96   ......V.~..HH6..
0040 : F6 EE C6 CC 52 D5 FD 9F  01 A8 00 7E 80 20 60 18   ....R......~. `.
0050 : 28 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   (...............
0060 : 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
0070 : 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................

Normal scrambled mode is '0x61' (mode 1 disc) or '0x62' (mode 2 disc). But these sectors are irregular (0x81, 0xA1). Old DIC doesn't descramble these sectors that irregular scrambled mode has.
DIC of 2017-2018 descrambles these. But 305472 sector is incomplete as data sector. This is a mastering error. So, latest DIC perserves this sector as is.

F1ReB4LL wrote:

Does the c2 feature work properly?

I see it later.

767

(3,497 replies, posted in General discussion)

https://github.com/saramibreak/DiscImag … r/releases
*2018-09-01
- added: Drive speed of bd and xbox. (If you don't use this, please specify 0)
- changed: No output XGD3 SSv1
- improved: Security Sector log of XBOX (added timestamp etc.)

768

(3,497 replies, posted in General discussion)

Could you upload the dumping log files of XGD3 (Battlefield 3 (Disc 1) (Multiplayer/Co-Op)) and the SSv2 using XBC and ABGX360 if you still have it?

769

(3,497 replies, posted in General discussion)

user7 wrote:

Xbox One and PS4 discs no longer have the layerbreak info in _disc.txt

I don't know yet how to get the L0, L1 length and layerbreak of BD.

Jackal wrote:

it would be better to disable the SS.BIN output?

It's possible. Btw, please tell me the differences of SS and SSv1 and SSv2. I don't understand yet why there's no point in adding SSv1 info for these discs.

It seems ss_sector_range.exe (1.0d-alpha) supports "XGD3 SSv1" and "XGD3 AP25". What is AP25?

            if(filled == false)
            {
                 //Fix XGD3 SSv1 ss.bin
                 m_buf[552] = 1;   // 0x01
                 m_buf[553] = 0;   // 0x00

                 m_buf[561] = 91;  // 0x5B
                 m_buf[562] = 0;   // 0x00

                 m_buf[570] = 181; // 0xB5
                 m_buf[571] = 0;   // 0x00

                 m_buf[579] = 15;  // 0x0F
                 m_buf[580] = 1;   // 0x01
            }
            else
            {
                 //Fix XGD3 AP25 ss.bin
                 m_buf[72]  = 1;   // 0x01
                 m_buf[73]  = 0;   // 0x00
                 m_buf[75]  = 1;   // 0x01
                 m_buf[76]  = 0;   // 0x00

                 m_buf[81]  = 91;  // 0x5B
                 m_buf[82]  = 0;   // 0x00
                 m_buf[84]  = 91;  // 0x5B
                 m_buf[85]  = 0;   // 0x00

                 m_buf[90]  = 181; // 0xB5
                 m_buf[91]  = 0;   // 0x00
                 m_buf[93]  = 181; // 0xB5
                 m_buf[94]  = 0;   // 0x00

                 m_buf[99]  = 15;  // 0x0F
                 m_buf[100] = 1;   // 0x01
                 m_buf[102] = 15;  // 0x0F
                 m_buf[103] = 1;   // 0x01
            }

770

(3,497 replies, posted in General discussion)

Uploaded as releases https://github.com/saramibreak/DiscImag … r/releases

*2018-07-26
- added: CSS authentication
          => CSS.exe is needed. Please download and put exe into Release_ANSI directory of DIC.
             https://github.com/saramibreak/CSS/releases
- added: Linux build
- fixed: Reading directory record of GD-ROM
- fixed: /s option (/s 0 and /c2 can't use together)
- fixed: Disc log of DVD (Region)

*2018-08-12
- added: xboxswap, xgd2swap, xgd3swap command
- added: Reading param.sfo
- added: makefile for linux
- improved: Reading sub-channel (create QGenSector from QNextSector - 1 and QPrevSector + 1)
- fixed: _splitpath for linux (added null checking)

*2018-08-28
- added: Support XGD3 dumping on kreon drive
- fixed: Rereading of SecuROM/Libcrypt
- deleted: some warning

771

(3,497 replies, posted in General discussion)

changed: how to detect SecuROM Type 4 (11 errors version) http://www.mediafire.com/file/eq80y20l9 … st.7z/file

772

(15 replies, posted in General discussion)

fuzzball wrote:

おとうさん (お父さん) = otōsan = otoosan
おおかみ (大神/狼) = ōkami = ookami

F1ReB4LL wrote:

But as far as I understand, No-Intro uses "Ou" for these with the exception for things like "ōkami", which transcription isn't "オーカミ", but "オオカミ".

http://www.mext.go.jp/b_menu/hakusho/nc … 01001.html

6  次のような語は,オ列の仮名に「お」を添えて書く。

例  おおかみ  おおせ(仰)  おおやけ(公)  こおり(氷・郡△)  こおろぎ  ほお(頬*・朴△)  ほおずき  ほのお(炎)  とお(十)

いきどおる(憤)  おおう(覆)  こおる(凍)  しおおせる  とおる(通)  とどこおる(滞)  もよおす(催)

いとおしい  おおい(多)  おおきい(大)  とおい(遠)  おおむね  おおよそ

これらは,歴史的仮名遣いでオ列の仮名に「ほ」又は「を」が続くものであって,オ列の長音として発音されるか,オ・オ,コ・オのように発音されるかにかかわらず,オ列の仮名に「お」を添えて書くものである。
(5)  オ列の長音

オ列の仮名に「う」を添える。

例  おとうさん  とうだい(灯台)

わこうど(若人)  おうむ

かおう(買)  あそぼう(遊)  おはよう(早)

おうぎ(扇)  ほうる(抛*)  とう(塔)

よいでしょう  はっぴょう(発表)

きょう(今日)  ちょうちょう(蝶*々)

That is to say, otōsan is otousan, ōkami is ookami.

773

(3,497 replies, posted in General discussion)

Refixed: rereading about SecuROM/Libcrypt http://www.mediafire.com/file/eq80y20l9 … st.7z/file

774

(3,497 replies, posted in General discussion)

fixed: Do not reread in SecuROM/Libcrypt sectors range http://www.mediafire.com/file/eq80y20l9 … st.7z/file

775

(3,497 replies, posted in General discussion)

added: XGD3 dumping on kreon drive. http://www.mediafire.com/file/eq80y20l9 … st.7z/file
----

ajshell1 wrote:

what happened to the /r command?

Not be supported /r on the cd command.

andoryuu3 wrote:

At the time of ripping, I did not see any errors in the command line output.

Unfortunately, I can't understand why your halo2 can't be dumped because mainError.txt is empty and no-error in the command line.