476

(3,538 replies, posted in General discussion)

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- added: If valid extension was omitted, ".bin" is set to path automatically.

477

(3,538 replies, posted in General discussion)

antimatter wrote:

New _subinfo.txt log:

Weird... 11 sectors (-1, 5000, 6404, 7373, 7613, 9628, 9986, 10837, 12164, 14344, 14419) have correct RMSF and AMSF. Is this other securom version? I don't know.
The mode of the last 4th sector is changed. If this disc is securom, it's correct.

LBA[334159, 0x5194f], MSF[74:17:34], mode 1
LBA[334160, 0x51950], MSF[74:17:35], mode 1
LBA[334161, 0x51951], MSF[74:17:36], mode 2 form 1, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[00]), [3](SubMode[00]), Form 1, [4](CodingInfo[00])
LBA[334162, 0x51952], MSF[74:17:37], mode 1
LBA[334163, 0x51953], MSF[74:17:38], mode 1
LBA[334164, 0x51954], MSF[74:17:39], mode 1

478

(3,538 replies, posted in General discussion)

F1ReB4LL wrote:

if the current sector is EAN/ISRC, the next sector's Q-channel has its index changed to 01, but the next sector's P-channel is padded with 0x00, then the current EAN/ISRC sector does not belong to pregap, but belongs to the track's index 01 (because the first sector of the 01 index should have its P-channel padded with 0xFF). Even if you take the 1st indexes from TOC, this check is still important for the TOC/cue desync detection.

Changed it to your logic. http://www.mediafire.com/file/eq80y20l9 … st.7z/file

antimatter wrote:

Burnout find no protection but ProtectionID & Alcohol 120 find it has SecuROM.

Added log to _subinfo.txt. If there is random error(s) in LBA -1 sector, it's difficult to detect.

479

(3,538 replies, posted in General discussion)

F1ReB4LL wrote:

when the EAN or ISRC sector is detected and its P-channel is 0x00, you need to check the next sector's P and Q channels: if the Q-channel's track number is increased and the P-channel is filled with 0xFF, then the EAN/ISRC sector belongs to the next track.

Coded. http://www.mediafire.com/file/eq80y20l9 … st.7z/file
I checked it by Cosmic Fantasy 3. If this code is no problem, I'll remove /m flag.

>superg
This has been written to KnownIssue.txt as "Extension problem" since several years ago.
If you want to escape this problem without new coding, you should specify the extension.

480

(3,538 replies, posted in General discussion)

zcal wrote:

I get the below errors in Linux

Try to use su or sudo.

481

(3,538 replies, posted in General discussion)

pool7 wrote:

Now the swap command worked and started dumping; however at one point DIC crashed.

No scrambled data. Perhaps PX-760A doesn't support swap trick.

pool7 wrote:

Here's sector 16 from IsoBuster, both RAW and non-RAW:

volume space size is 0x265b. It's 9819 sectors. 9819 * 2048 = 20109312 bytes.

It's easy to use volume space size instead of TOC, but I'm not sure volume space size is correct disc size.

482

(3,538 replies, posted in General discussion)

pool7 wrote:

When trying to run the swap command, I get invalid argument:

D:\apps\redump\dic_test_20191227>DiscImageCreator.exe swap H foo.bin

Missing the drive speed.

----
As user7 says, if your disc have a fake TOC, I want to know the volume space size. Please upload 16th sector using Isobuster.

483

(3,538 replies, posted in General discussion)

user7 wrote:

the LG has a different write offset value.

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: parse driveOffset.txt

484

(3,538 replies, posted in General discussion)

pool7 wrote:

One thing I noticed when checking IsoBuster: the files in the disc are 19.1MB; however if I check the properties of the CD/Session/Track, IsoBuster says the disc size is 921.290.752 bytes (449.849 blocks).

Yes. TOC says the last sector is 449.849.

========== TOC ==========
      Data Track  1, LBA        0 -   449848, Length   449849
                                              Total    449849
pool7 wrote:

I tried entering 449849 in the Sector View window, and it did the same noise as when trying to dump with DIC(however I'm not sure if that's the number I should have entered), then showed this error:
Device reported Error code : 03/02/8D

Perhaps it needs swap trick. See wiki https://github.com/saramibreak/DiscImageCreator/wiki "Dumping Guide for CD with swap"
At least, kreon drive supports it.

485

(3,538 replies, posted in General discussion)

pool7 wrote:

Trying to dump a PS1 Unlicensed disc (Breaker Pro); tried with both stable and latest test version (20191227):
The drive makes some funny noises a couple of times, then it errors out.

Please check if the sector view of isobuster can read the last sector.

486

(3,538 replies, posted in General discussion)

user7 wrote:

Having trouble dumping one particular Action Replay PS2 disc.

There is a incorrect directory length.

              Length of Directory Record: 52
        Extended Attribute Record Length: 0
                      Location of Extent: 15479
                             Data Length: 2288
                 Recording Date and Time: 2003-05-12 16:01:11 +00:00
                              File Flags: 2 (Visible, Directory, Disassociated, File hasn't record format,Owner/Group ID hasn't,Final Directory Record)
                          File Unit Size: 0
                     Interleave Gap Size: 0
                  Volume Sequence Number: 1
               Length of File Identifier: 4
                         File Identifier: FONT

Data Length should be 2048. 2288 is an internal error. I can't fix it now.

user7 wrote:

Another one, this is a PC press kit CD-Rom (not CD-R).

I always say about c2 error.
1. use "/c2 4096", not "/c2 20".
2. resurface the disc.
3. change the disc if possible.
4. change the drive.

487

(3,538 replies, posted in General discussion)

Enker wrote:

The latest DIC versions are underdumping UDF-only Xbox One discs.

20191227 233113 http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: detecting 2nd Anchor Volume Descriptor Pointer

488

(3,538 replies, posted in General discussion)

user7 wrote:

Sarami, i'm continuing to test dic with ps4 kiosk discs. this one was dumped with the latest stable, does it look good to you? https://drive.google.com/file/d/1bqYwos … sp=sharing

here's redump's non-matching entry for reference http://redump.org/disc/62879/

Uploaded test version 20191227 233113
- fixed: detecting 2nd Anchor Volume Descriptor Pointer

489

(3,538 replies, posted in General discussion)

https://github.com/saramibreak/DiscImag … r/releases
*2019-12-23
- added: output cue file if 2nd language code of CDTEXT exists
- changed: ISRC position of cue file
- fixed: fail to XBOX/XBOX 360 dumping from 2019-11-16
- fixed: main channel buffering (ROM^2 Karaoke Volume 5 [PCE])
- improved: UDF logging => support detecting the size of DVD-RE, BD-R, BD-RE

490

(3,538 replies, posted in General discussion)

fuzzball wrote:

Which is correct?

Perhaps it's IsoBuster.

fuzzball wrote:

dic: doesn't match db (1 error)

No C2 error, no sub error. I have no idea about it.

491

(3,538 replies, posted in General discussion)

LoStraniero91 wrote:

Still doesn't work

Fixed UDF http://www.mediafire.com/file/eq80y20l9 … st.7z/file

492

(3,538 replies, posted in General discussion)

LoStraniero91 wrote:

Xbox 360 DVD dumping is broken

Fixed http://www.mediafire.com/file/eq80y20l9 … st.7z/file

xTMODx wrote:

Track 3 didnt start dumping
Track 4 didnt start dumping
Track 5 didnt start dumping

Weird. TOC is hacked? I don't know...

493

(3,538 replies, posted in General discussion)

xTMODx wrote:

when i try dump only track 1 with isobuster it stops at sector 97208 (93%) with Error: 03/11/05

Then, do you dump only track 2, 3, 4 and 5 by Isobuster?

494

(3,538 replies, posted in General discussion)

xTMODx wrote:

Disc has 5 tracks and also a ring on the data side, isobuster dump takes very long dont know if i have to cancel this

According to the log, LBA 115010 is not a data sector. Do you dump only track 1 by Isobuster?

495

(3,538 replies, posted in General discussion)

xTMODx wrote:

i have a problem dumping a disc it stop with this error

Try other app (isobuster, clonecd, etc.)

496

(3,538 replies, posted in General discussion)

http://www.mediafire.com/file/eq80y20l9 … st.7z/file

iR0b0t wrote:

sarami, could you please change the order of cuesheet tags:

- fixed: cuesheet order

sarami wrote:

One problem exists. Cue format handles only 1 language code. DIC outputs one-byte-character language.

- added: output the 2nd language code of CDTEXT to _alt.cue

497

(3,538 replies, posted in General discussion)

sarami wrote:
iR0b0t wrote:

sarami, could you please change the order of cuesheet tags:

OK, but I want to know too the cuesheet of Isobuster and CloneCD.

Isobuster uses cdt and doesn't use TITLE, PERFORMER, etc.
CloneCD doesn't use cdt and TITLE, PERFORMER, etc.

I'll change the order of cuesheet tags in the near future.

user7 wrote:

So dic dump is confirmed good?

I think so.

498

(3,538 replies, posted in General discussion)

F1ReB4LL wrote:

https://mega.nz/#!a9pDAK6R!lic1WG0clvNK … VWKbX13RpQ

    TITLE "Track 1 (CD Text in Japanese only)"
    PERFORMER "Artist CD Text in Japanese only"

Are these strings really encoded as CD Text? Not replaced by DIC?

Reference https://www.gnu.org/software/libcdio/cd … ormat.html
There are 2 language codes in this disc.

This is the raw format written in ccd (If you see readable format, see _disc.txt)

[CDText]
Entries=21
Entry 0=80 00 00 80 00 00 82 63 82 62 00 00 00 00 00 00
Entry 1=81 00 01 80 00 00 82 63 82 92 82 81 82 8d 82 81
Entry 2=81 01 02 85 82 62 82 63 00 00 00 00 00 00 00 00
Entry 3=8f 00 03 80 00 01 01 00 01 02 00 00 00 00 00 00
Entry 4=8f 01 04 80 00 00 00 00 00 00 00 03 05 0e 00 00
Entry 5=8f 02 05 80 00 00 00 00 69 09 00 00 00 00 00 00
Entry 6=80 00 00 10 54 69 74 6c 65 20 43 44 20 54 65 78
Entry 7=80 00 01 1c 74 20 69 6e 20 4a 61 70 61 6e 65 73
Entry 8=80 00 02 1f 65 20 6f 6e 6c 79 00 54 72 61 63 6b
Entry 9=80 01 03 15 20 31 20 28 43 44 20 54 65 78 74 20
Entry 10=80 01 04 1f 69 6e 20 4a 61 70 61 6e 65 73 65 20
Entry 11=80 01 05 1f 6f 6e 6c 79 29 00 00 00 00 00 00 00
Entry 12=81 00 06 10 41 72 74 69 73 74 20 43 44 20 54 65
Entry 13=81 00 07 1c 78 74 20 69 6e 20 4a 61 70 61 6e 65
Entry 14=81 00 08 1f 73 65 20 6f 6e 6c 79 00 41 72 74 69
Entry 15=81 01 09 14 73 74 20 43 44 20 54 65 78 74 20 69
Entry 16=81 01 0a 1f 6e 20 4a 61 70 61 6e 65 73 65 20 6f
Entry 17=81 01 0b 1f 6e 6c 79 00 00 00 00 00 00 00 00 00
Entry 18=8f 00 0c 10 80 01 01 00 06 06 00 00 00 00 00 00
Entry 19=8f 01 0d 10 00 00 00 00 00 00 00 03 05 0e 00 00
Entry 20=8f 02 0e 10 00 00 00 00 69 09 00 00 00 00 00 00

From Entry 0 to 5 are 1st language code.
[Entry 0]
1st byte shows Album.
5th byte is 0 => Album Name is null.
From 7th to 10th are "82 63 82 62". => Song Name is "DC"

[Entry 1, 2]
1st byte shows Performer.
5th byte is 0 => Album Performer is null.
From 7th to 16th of entry 1 are "82 63 82 92 82 81 82 8d 82 81" => "Drama"
From 5th to 8th of entry 2 are "82 62 82 63" => "CD"
  => These are concatenated as "DramaCD"


From Entry 6 to 20 are 2nd language code.
[Entry 6, 7, 8]
1st byte shows Album.
From 5th to 16th of entry 6 are "54 69 74 6c 65 20 43 44 20 54 65 78" => "Title CD Tex"
From 5th to 16th of entry 7 are "74 20 69 6e 20 4a 61 70 61 6e 65 73" => "t in Japanes"
From 5th to 10th of entry 8 are "65 20 6f 6e 6c 79"                   => "e only"
  => These are concatenated as "Title CD Text in Japanese only"

[Entry 8, 9, 10, 11]
From 12th to 16th of entry 8 are "54 72 61 63 6b" => "Track"
From 5th to 16th of entry 9 are "20 31 20 28 43 44 20 54 65 78 74 20" => " 1 (CD Text "
From 5th to 16th of entry 10 are "69 6e 20 4a 61 70 61 6e 65 73 65 20" => "in Japanese "
From 5th to 9th of entry 11 are "6f 6e 6c 79 29" => "only)"
  => These are concatenated as "Track 1 (CD Text in Japanese only)"

[Entry 12, 13, 14]
1st byte shows Performer.
From 5th to 16th of entry 12 are "41 72 74 69 73 74 20 43 44 20 54 65" => "Artist CD Te"
From 5th to 16th of entry 13 are "78 74 20 69 6e 20 4a 61 70 61 6e 65" => "xt in Japane"
From 5th to 11th of entry 14 are "73 65 20 6f 6e 6c 79" => "se only"
  => These are concatenated as "Artist CD Text in Japanese only"

[Entry 14, 15, 16, 17]
From 13th to 16th of entry 14 are "41 72 74 69" => "Arti"
From 5th to 16th of entry 15 are "73 74 20 43 44 20 54 65 78 74 20 69" => "st CD Text i"
From 5th to 16th of entry 16 are "73 65 20 6f 6e 6c 79 00 41 72 74 69" => "n Japanese o"
From 5th to 7th of entry 17 are "6e 6c 79" => "nly"
  => These are concatenated as "Artist CD Text in Japanese only"


One problem exists. Cue format handles only 1 language code. DIC outputs one-byte-character language.

499

(3,538 replies, posted in General discussion)

user7 wrote:

Here are the final bytes from the DIC dump https://mega.nz/#!cvAHDYJZ!2ofFgyO2YJOh … ToQR34tBKQ

This is certain "Anchor Volume Descriptor Pointer". This is the last sector.

500

(3,538 replies, posted in General discussion)

There are 2 types in your bd-r dumps.

1. Only ISO9660 --- PS4 IDU 2015 Summer Refresh Standard
2. Only UDF --- ps4 idu 2018 summer refresh gamestop, 2019 Summer Refresh - Game 89

1 uses "Volume Space Size". If the last sector is all zero, it's no problem. Perhaps DIC and Isobuster match.
2 uses "Anchor Volume Descriptor Pointer". This sector is non-zero. Isobuster overdumps by 16 sectors? I'm not sure yet.

If you have ISO9660 + UDF hybrid bd-r, please upload logs and tell me the last sector.