976

(3,488 replies, posted in General discussion)

F1ReB4LL wrote:

Gap detection glitch (last track).

_disc.txt

========== TOC ==========
           :
     Audio Track 50, LBA   247692-  250338, Length     2647
     Audio Track 51, LBA   250339-  255212, Length     4874
                                            Total    255213
========== FULL TOC ==========
    Session 1,     Track 50, MSF 55:04:42 (LBA[247842, 0x3c822])
    Session 1,     Track 51, MSF 55:00:00 (LBA[247500, 0x3c6cc])

LBA of TOC is correct but LBA of FULL TOC is incorrect. I don't know why...

977

(3,488 replies, posted in General discussion)

Updated test version.
----

Logical Block Size: 1024

I had thought that "Logical Block Size" is fixed in 2048 byte. But Ecma-119 says below.

6.2.2 Logical Block
The Volume Space shall be organized into Logical Blocks. Each Logical Block shall consist of 2n+9 bytes,
where n equals 0 or a positive integer. The number of bytes in a Logical Block shall be referred to as the Logical
Block size which shall not be greater than the Logical Sector size.

That is, it is correct that "Logical Block Size" is 1024 byte and "Volume Space Size", "Location of Occurrence of Path Table" and "Location of Extent" is double size because "Logical Block Size" is half size.

http://redump.org/disc/43476/
File system doesn't corrupt, but CD-ROM that "Logical Block Size" isn't 2048 byte is perhaps rare or irregular. So, I think the OS that is newer than WinXP doesn't support it.

978

(3,488 replies, posted in General discussion)

F1ReB4LL wrote:

http://redump.org/disc/16920/ -- scrambled contents has the pre-last sector half-scrambled, half-descrambled and the last sector descrambled, so the descrambled dump should have the last sector scrambled and the pre-last sector inverted. It's a common Saturn mastering error. For some reason DIC leaves the last sector as is without scrambling it, that's not correct. And the earlier DIC versions work fine, I remember I've tested such discs, dumps were correct.

20170719 test
- changed: Directory record size from 8192 to 16384 (for some amiga CD)
- fixed: data sector is descrambled when sync and mode is valid and reverted sector


xTMODx wrote:
sarami wrote:

Is it really ISO9660 disc? If so, it is easily unbelievable that "Only" old Windows (3.1?, 95?, 98?, 2000? etc) can read it.

here are the dump files with reentrant's DIC  http://www107.zippyshare.com/v/xb6AmTRp/file.html i could open the disc on windows xp but not on windows 8.1 tested on 4 plextor drives

_volDesc.txt

========== LBA[000016, 0x00010]: Volume Descriptor ==========
                           Volume Descriptor Type: 1
                              Standard Identifier: CD001
                        Volume Descriptor Version: 1
                                System Identifier:                                 
                                Volume Identifier: MASTERQUIZ                      
                                Volume Space Size: 510448
                                  Volume Set Size: 1
                           Volume Sequence Number: 1
                               Logical Block Size: 1024
                                  Path Table Size: 116
             Location of Occurrence of Path Table: 36
    Location of Optional Occurrence of Path Table: 0
              Length of Directory Record: 34
        Extended Attribute Record Length: 0
                      Location of Extent: 40
                                          :

Correct size of "Volume Space Size" is perhaps 255384. "Location of Occurrence of Path Table" is perhaps 18. "Location of Extent" is perhaps 20. Other values may be corrupt.

If possible, I don't want to skip reading the path and directory table. These values are to fix manually in app. Of course, the image file isn't fixed.

979

(3,488 replies, posted in General discussion)

Only 3 sector? but clearly, 289 sectors are error if use 0xd8..

Track 3 is recognized as Audio mode in IsoBuster."
I guess the shift is caused by data > audio transition?

I don't know, but these sectors are clearly including the data sector. "00 ff ... ff 00" is sync, "69 b6 10" is the scrambled msf, "61" is the scrambled mode.

980

(3,488 replies, posted in General discussion)

xTMODx wrote:

i could open the disc on windows xp but not on windows 8.1 tested on 4 plextor drives

Weird.. if you can, please try on win7, win10, linux(ubuntu, fedora etc.)

Jackal wrote:

olofolleola4 is having some problems dumping a disc.

_mainError.txt

LBA[308560, 0x4b550]: Track[00]: Sync is invalid
========== LBA[308560, 0x4b550]: Main Channel ==========
              +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
      0(   0) 00 ff ff ff ff ff ff ff 00 ff ff ff ff ff ff ff
     10(  16) ff ff ff 00 69 b6 10 61 03 83 f4 cd bf 24 63 7a
              :
              :

The garbage byte (a part of the sync?) exists in first 8 byte of this sector. So, the offset is shifted by 8 byte... dic can't descramble these sector for this reason. Can you read these sector by the other tools (Isobuster, perfectrip clonecd etc.)?

Does this mean that if properly descrambled, the dump is correct and doesn't need any 0x55 fixes?

I don't know whether these sector are a mastering error, or a protect or not.

981

(3,488 replies, posted in General discussion)

Is it really ISO9660 disc? If so, it is easily unbelievable that "Only" old Windows (3.1?, 95?, 98?, 2000? etc) can read it.

982

(3,488 replies, posted in General discussion)

http://forum.redump.org/post/55106/#p55106
http://forum.redump.org/post/55327/#p55327
http://forum.redump.org/post/55479/#p55479

Attention
1. Before you report a bug, could you test the latest test version. Nevertheless a bug exists, could you upload all created file except bin, img and scm. And could you tell me the disc title ,region, barcode and ringcode.

Thanks several report, but I don't have these disc, so I can't test and fix them.

About PVD:
If it can't be read by IsoBuster, it is weird disc, otherwise dic's bug.

Yes. I'll add the total errors like edccchk in next version.

http://forum.redump.org/topic/16073/r09 … ification/
This disc will also show the errors are 3 in total.

984

(3,488 replies, posted in General discussion)

Confirmed.

The pre-last sector is erroneous. The last sector is reverted/scrambled.

Exactly, the last 4510 byte is reverted/scrambled. BTW, does reading error occur if isobuster reads these 2 sectors?

reentrant wrote:

It could this: http://redump.org/disc/42279/

Also Ring PROTECH cannot be dumped with Plextors.
1) Extract AUDIO using DIC.
2) Extract DATA using OptiARC.

This is the only solution...

Does this disc has "PROTECT.PRO" file? or found the string "Allocator" in bin file?


https://www.gamecopyworld.eu/games/pc_s … _old.shtml

Unreadable Errors
The topside of CD #1 has been "damaged", a ring (about 1 mm) is clearly visible at about 1/3 of the outside of the CD.

GameCopyWorld isn't using the word "Ring PROTECH". If this disc is really Ring PROTECH, GameCopyWorld will also use this word.
Protected disc list: http://www.cdmediaworld.com/hardware/cd … tech.shtml
This protect is also adopted in Japanese disc. http://www12.plala.or.jp/t2-bun/list5.html

It seems edccchk doesn't regard the zero sync data sector as error.

And please use the latest EccEdc.exe

http://redump.org/disc/43270/
Same disc?

988

(3,488 replies, posted in General discussion)

Please upload the scrambled and descrambled pre-last sector, and the scrambled and descrambled last sector.

989

(3,488 replies, posted in General discussion)

Please try the latest. Btw, does this occur in another tool?

990

(3,488 replies, posted in General discussion)

memo:
Protected game list
https://www.gamecopyworld.eu/games/gcw_index.shtml

search "unreadable errors"
https://gamecopyworld.eu/games/search_r … ;sa=Search

Der korsar
https://gamecopyworld.eu/games/pc_the_corsairs.shtml

Fort Boyard Millenium
not found

991

(3,488 replies, posted in General discussion)

DIC
*2017-07-02
- added: Reading TOC ATIP for CD-R, CD-RW
- added: Reading path table, directory record for DVD
- changed: Directory record size from 4096 to 8192
- changed: Some log message
- changed: Sector Outputted to log to IsoBuster-like sector
- fixed: Ripping range of SecuROM
- fixed: Reading path table record
- fixed: data sector is descrambled when sync and mode valid

EccEdc
*2017-07-02
fixed: forgot FLAG DCP

TODO:
http://forum.redump.org/topic/16073/r09 … ification/

usurper wrote:

Latest DIC version fail at dumping this disc.
Old DIC version is fine though. here you will find full logs of both dumps (old and current DIC version).

http://forum.redump.org/post/54685/#p54685

reentrant wrote:

Also I found one bug in CD-Text dumping. In function: SetAndOutputTocCDText -> strlen(pTmpText + uiIdx) crashes. iuIdx has some big value. This only happens with PX760. Other drive reads it correctly. Maybe before parsing those data structures subchannels should be corrected (packed mode read?).

Weird. Please fix if you can.

sarami wrote:

I checked under debugger that pDirRec[*nDirPosNum].uiDirNameLen = 0. It's an error during mastering phase?

Please see LBA 19 with IsoBuster and paste it in this thread.

Is this solved?

Jackal wrote:
usurper wrote:

Sarami, if you are looking for a challenging protection, get yorself this or this disc.

https://www.medimops.de/infogrames-der- … 6FS54.html
https://www.medimops.de/infogrames-der- … 6FS55.html

This one from the same publisher has the same protection:

https://www.medimops.de/vivendi-univers … edVeryGood

GameCopyWorld wrote:

The process took 18 hours to complete because about 35% of the CD contains unreadable errors!

What protection is this?

I bought this. This is surely VobProtectCD (wiggles.exe). But this disc is almost compressed by a specific archive (archive.bin). So this can't be also detected by ProtectionID, A-RAY scanner.
To detect:
1. decompress archive, but it's difficult.
2. read main channel and search the invalid sync ("00 FF 00 FF ...")

992

(3,488 replies, posted in General discussion)

sarami wrote:
ssjkakaroto wrote:

BTW can you modify the *_volDesc.txt log so that it also has the Primary Volume Descriptor (PVD) in the format that the "New Disc" form requires?

Adopted IsoBuster sector.
http://www.mediafire.com/file/eq80y20l9 … or_test.7z
See *_mainInfo.txt

Supported DVD too.

993

(3,488 replies, posted in General discussion)

MSF: 04:09:30 Q-Data: 410101 04:05:30 00 04:49:30 9b33  xor 8001 068d P2 xor 02 40
this one wasn't detected..

Fixed the range.

994

(3,488 replies, posted in General discussion)

I checked under debugger that pDirRec[*nDirPosNum].uiDirNameLen = 0. It's an error during mastering phase?

Please see LBA 19 with IsoBuster and paste it in this thread.

995

(3,488 replies, posted in General discussion)

Escaped 0 length.

        if (pDirRec[*nDirPosNum].uiDirNameLen > 0) {
                                   :
                                   :
        }
        else {
            OutputVolDescLogA(
                "\t     Length of Directory Identifier: %u\n", pDirRec[*nDirPosNum].uiDirNameLen);
            break;
        }

Is 0 correct value? I want to look the *mainInfo.txt and *volDesc.txt

996

(3,488 replies, posted in General discussion)

It applies to mode 1 and 2.

997

(3,488 replies, posted in General discussion)

Please upload *_volDesc.txt

Problem with disc: http://redump.org/disc/42666/
This is a clear case where 00:00:00 Track02 pregap causes audio data to be moved into the data track.
From previous discussion: http://forum.redump.org/topic/15992/abo … or-sector/
"If sync doesn't exist in the sector of mastering error, this sector shouldn't be descrambled. Because no sync = not a valid data sector."
However, DIC is descrambling these sectors. This is wrong.

Fixed: The data sector is descrambled when sync and mode is valid.

998

(3,488 replies, posted in General discussion)

reentrant wrote:

Sarami there's a small regression in latest version of DIC. When you specify /rc switch and no protection is detected a warning pops up with message /rc is ignored. For some discs (when protection cannot be detected) this is causing a regression and some sectors are not properly dumped. Please provide a way to override /rc so that it's always active.

What protection cannot be detected?

999

(3,488 replies, posted in General discussion)

darksabre76 wrote:

Hey again, I have a bit of an odd issue with a no-scratches OEM disc (IBM-PC). I've tried reattaching my drive multiple times and even tried ripping the disc with another program (which succeeded). Below is the error that it throws after it enumerates the tracks and checks the EXEs:

LBA[299337, 0x49149]: [F:ReadCDForVolumeDescriptor][L:1120]
    OpCode: 0xa8
    ScsiStatus: 0x02 = CHECK_CONDITION
    SenseData Key-Asc-Ascq: 03-02-82 = MEDIUM_ERROR - OTHER
lpCmd: a8, 00, 00, 04, 91, 49, 00, 00, 00, 01, 00, 00
dwBufSize: 2048

Other output files available if they're needed.

Updated test ver.

Rubberbandman wrote:

I don't see how that message with its broken English is in any way clear, especially since I gave it a number and it ignored it.

I'm not a native eng speaker. Please tell me the broken English you think.

1,000

(5 replies, posted in General discussion)

I created some images to test (8360, 8361, 8362 is mastering error sector).

Pattern 1 [8360:descramble, 8361:descramble, 8362:descramble]
Pattern 2 [8360:descramble, 8361:No descramble, 8362:No descramble]
Pattern 3 [8360:No descramble, 8361:descramble, 8362:No descramble]
Pattern 4 [8360:No descramble, 8361:No descramble, 8362:descramble]
Pattern 5 [8360:No descramble, 8361:descramble, 8362:descramble]
Pattern 6 [8360:descramble, 8361:No descramble, 8362:descramble]
Pattern 7 [8360:descramble, 8361:descramble, 8362:No descramble]
Pattern 8 [8360:No descramble, 8361:No descramble, 8362:No descramble]

Writing drive: PX-W4824A
Writing tool: Disc Mediator Kureha version 0.9.2 beta
Writing command: DAO RAW+96
Reading tool: DIC test version 20170518

Result:
Pattern 1 => 8360 is same, 8361 is different, 8362 is different
Pattern 2 => all matched
Pattern 3 => all matched
Pattern 4 => all matched
Pattern 5 => all matched
Pattern 6 => all matched
Pattern 7 => all matched
Pattern 8 => all matched

Conclusion:
I understood that it was incorrect to descramble all mastering error sectors. On the other hand, I felt that it wasn't necessary to descramble all mastering error sectors.