1

(1,162 replies, posted in General discussion)

/c2 is only for cd mode. Audio mode is simple burst read mode without rereadings.

2

(1,162 replies, posted in General discussion)

My usual one. 8x read speed because my PX-755SA won't read faster than that. It's stucked forever at 8x read speed. For other drives, 24x read speed is the optimal one in my humble opinion.

discimagecreator.exe cd g: discimagecreator 08 /c2 2000 8192 08

3

(1,162 replies, posted in General discussion)

Still?

4

(1,162 replies, posted in General discussion)

Simply, via rereading lots of times the bad sectors until being lucky and get a reread without C2 errors for any bad sector. Not always possible, though.

If the disc to dump is really in awful condition (label side heavily scratched, corroded by long exposition to water, disc edge bad sealed and metallic layer is corroded by oxygen...), no matter how much you reread the problematic sectors, data returned will be always bad and therefore unrecoverable. Miracles don't exist.

5

(4 replies, posted in General discussion)

Thanks for the post #258. Clear as black on white and properly written (for both meaning and grammar), at least the part related directly to this project.

Thanks!

7

(1,162 replies, posted in General discussion)

Only example I have physically (or at least I am aware of that) with that kind of "colission" is track 35 of /disc/29188/. A MCN frame appears in the track 34 - index 01 / track 35 - index 00 transition.

http://i.imgur.com/Kp1FVBw.png

That MCN frame belongs to previous track, pregap is 00:02:02 (Sony style) and, at least this one, was ripped finely by DIC without doing anything special. I didn't specify any /m parameter even if back then was already encoded.

Proof:
https://www.mediafire.com/?3z1r6o4yxe9d7om

8

(1,162 replies, posted in General discussion)

Sure:

http://redump.org/disc/30958/
http://redump.org/disc/32498/
http://redump.org/disc/32560/

These discs sometimes contain a MCN frame in certain audio tracks transitions, where there are no indexes 00 and whatnot in these audio-audio transitions. Those frames belong logically to the next track, as dicted by the TOC.

Certain buggy app (well, not optimized to dump game discs with audio tracks) used in the past (EAC) treated these things as artificial indexes 00, especially when combined with TOC versus subcode desyncs.

Can someone translate the little japanese part of this bonus .txt file included in the Racingroovy game? It was originally a Shift-JIS .txt which I converted to UTF-8 (I hope that properly), and deleted the last byte, 0x1A, end of file if I understand correctly.

http://pastebin.com/sckPBfaa

Line:
#    ソフトに含まれるプログラム等著作物を無断で解析することを禁止します    #

Original one:

https://www.mediafire.com/?31677ab7a0hrd5l

10

(1,162 replies, posted in General discussion)

Tested:

http://www.mediafire.com/?6w3noqvyw4glvit

11

(1,162 replies, posted in General discussion)

Observe this carefully in the sample you have posted. If you compare R-W data extracted via these two modes, they look different.

====== Check SubP to W, OperationCode: 0xbe, Subcode: 1(=Raw) ======
Sub Channel LBA 0
      +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B
    P ff ff ff ff ff ff ff ff ff ff ff ff
    Q 41 01 01 00 00 00 00 00 02 00 28 32
    R 00 00 00 00 00 00 00 00 00 00 00 00
    S 00 00 00 00 00 00 00 00 00 00 00 03
    T 00 00 00 00 00 00 00 00 00 00 00 02
    U 00 00 00 00 00 00 00 00 00 00 00 00
    V 00 00 00 00 00 00 00 00 00 00 00 00
    W 00 00 00 00 00 00 00 00 00 00 00 02

====== Check SubP to W, OperationCode: 0xd8, Subcode: 0x08(=Raw) ======
Sub Channel LBA 0
      +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B
    P ff ff ff ff ff ff ff ff ff ff ff ff
    Q 41 01 01 00 00 00 00 00 02 00 28 32
    R 00 00 00 00 00 00 00 00 00 00 00 01
    S 00 00 00 00 00 00 00 00 00 00 00 03
    T 00 00 00 00 00 00 00 00 00 00 00 02
    U 00 00 00 00 00 00 00 00 00 00 00 00
    V 00 00 00 00 00 00 00 00 00 00 00 03
    W 00 00 00 00 00 00 00 00 00 00 00 00


Two samples I have prepared for you:

http://www.mediafire.com/?lhad50oqouoznsv

C2 + Raw sub 96 extracted via certain method via D8 command, and the same thing via BE command, audio trap disc (so subcodes will be always properly aligned in the BE mode, especially true for certain buggy drives which lose the sync in the data-audio [or viceversa] transitions) method. Both look at first sight more or less identical. They contain lots of random errors, as expected for a subcode extracted without any class of rereadings/cleanings and whatnot, though.

I am wondering if this pattern could be predictable. And the reason of its existence: intentional, an accidental mastering artifact...?

12

(1,162 replies, posted in General discussion)

Is the offset correction applied for the C2 pointers as well? Perhaps this has something to do with the recent bug I discovered, C2 file was bigger than expected.

13

(1,162 replies, posted in General discussion)

EAC's developer should know something, because EAC has D8 support for these vintage SCSI CD-ROM readers, for C2 pointers and for FUA (-usefua parameter, and you have to configure drive as non-caching one).

And:

SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    379/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    380/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    381/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    382/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    383/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    384/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    385/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    386/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    387/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    388/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    389/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    390/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    391/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Creating img(LBA)    392/ 69300[F:ReadCDForFlushingDriveCache][L:516] OperationCode: 0xd8

So that only normal 0xA8 command is valid for FUA, and you cannot use this one for extracting data sectors in scrambled form.

14

(1,162 replies, posted in General discussion)

sarami wrote:

If so, I can code it but I can't test. Because I don't have already WinXP sad

Code it, I have damaged discs likely recoverable via many rereads and the SysInternals' Desktops (so processes which will take a lot of time won't mess my main desktop and distract me) to test the FUA function.

15

(1,162 replies, posted in General discussion)

Final test would be running DIC from an elevated command prompt line in these OS with UAC. I don't think that SPTI has changed so much in order to disable the D8h(FUA) command.

16

(1,162 replies, posted in General discussion)

Latest unlocked firmware installed:

1_08Xrpc1.bin
CRC32: f5f14e42
MD5: e60760ed1f36ec457df4d833b1e6e06b
SHA-1: 6e920618c5aa242e1df7b2f9bdce13d177601577

Windows Server 2003 Ent. SP2, account with admin privileges and absolutely no 3rd filter drivers installed and no virtual drives, as said before, in my main OS this trash is banned. Sticked into the drive a conventional CDDA.

C:\>cachex.exe -i g:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on G is  PLEXTOR  DVDR   PX-755A   1.08

[+] Buffer size: 2048 kB, read cache is enabled
[+] Supported read commands: BEh A8h(FUA) 28h(FUA) D4h(FUA) D5h(FUA) D8h(FUA)

C:\>

17

(1,162 replies, posted in General discussion)

Every real Plextor drive I own supports D8h (FUA).

http://forum.redump.org/post/45164/#p45164

18

(1,162 replies, posted in General discussion)

Solved X-File?

One thing... why don't implement an ultra-secure mode?

"ultrasecure n" Where n would be the number of read passes.

Idea is basically this one:

-Read multiple times the disc, as defined by n. I mean read the entire disc from AMSF 00:02:00 until the last pre-lead-out sector, and then read it another time, same method. Not to read n times 24 sectors (or whatever number of sectors read by DIC in a read command), the next 24 sectors n times and so on.

-If dumps of multiple passes do match and there are no C2 errors, create the final dump as usual.

-If they missmatch and at least one of them contains C2 errors, then cross/combine the C2 errors reported by the n passes and reread the questionable sectors until they can be recovered or limit of rereads for individual sectors is exhausted.

19

(1,162 replies, posted in General discussion)

PX-708UF, 'nuff said... ATAPI to USB bridge chip cannot pass properly certain low level commands for sure. At least my external PX-W4824TU supports these things properly, ATAPI to USB bridge chip is NEC, as far I remember, supposedly the best ones. Perhaps for the PX-708UF drive Plextor decided to implement a cheaper brand and thus support for certain low level commands isn't 100% OK.

20

(1,162 replies, posted in General discussion)

Man, you have a X-File...

Even the older PX-W4824TA/TU drive can support that. More or less supports the same functions than Premium / Premium II and authentic PX-7xx drives, except Gigarec, that piece of pure trash named Silent Mode (due to this my PX-755SA won't read any pressed CD at 24x or higher speeds, 8x is the maximum speed), PowerRec and quality scans. Hide CD-R media, force single session mode and SpeedRead are available for any real Plextor drive I own.

Installed software which installs filter drives? My system is completely clean, absolutely 0 3rd party filter drivers and 0 drivers for virtual drives. And will stay that way.

===============================================
Filter Driver Load Order - ImgBurn v2.5.8.0
===============================================

Upper Device Filter:  redbook
 Upper Class Filter:  [None Found]
             Device:  CD/DVD-ROM Device
Lower Device Filter:  imapi

        Filter Name:  redbook
          File Name:  C:\WINDOWS\system32\DRIVERS\redbook.sys
       File Version:  5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
   File Description:  Redbook Audio Filter Driver
       Product Name:  Microsoft® Windows® Operating System
    Product Version:  5.2.3790.3959
       Company Name:  Microsoft Corporation
          Copyright:  © Microsoft Corporation. All rights reserved.

        Filter Name:  imapi
          File Name:  C:\WINDOWS\system32\DRIVERS\imapi.sys
       File Version:  5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
   File Description:  IMAPI Kernel Driver
       Product Name:  Microsoft® Windows® Operating System
    Product Version:  5.2.3790.3959
       Company Name:  Microsoft Corporation
          Copyright:  © Microsoft Corporation. All rights reserved.

A parameter in order to avoid DIC controlling this feature is needed, I guess.

Just determinate the first sector which belongs to the HFS/HFS+ file system according to the info shown by IsoBuster, via hovering the cursor over the icon of that file system. Without paying the license won't allow you that you can go directly to that sector via right click and Sector Viewer, but you can always do the same thing for the ISO9660 file system and then go manually to the previously determinated sector.

The previous example:

http://i.imgur.com/vYMPPL5.png

A hybrid with ISO9660+Joliet and HFS+:

29413

http://i.imgur.com/SRDESqx.png

http://i.imgur.com/uIT60Ow.png

http://i.imgur.com/ahedWBO.png

Zeroed backup and checked timestamps means 01/01/1904 00:00:00 (GMT).

22

(1,162 replies, posted in General discussion)

SpeedRead is supported even by my old PX-W4824TA drive. So go figure any +30 drive. Sounds to filter drives (CloneCD, Alcohol 120%, just to mention a few of them) or virtual drives (especially the ones based on the damn sptd.sys driver) preventing that command for being supported correctly. Due to this kind of things and bad experiences in the past, in my main OS installed in the SSD drive it's completely forbidden the installation of this pure trash. If I need this software (very sporadically) I prefer to clone the SSD drive into a VelociRaptor, disable physically the SSD, boot from the VelociRaptor, install that software, do whatever is needed, deattach the VelociRaptor and now boot from my SSD.

That... or perhaps an elevated command prompt is needed for this kind of low level commands.

============

So in fact... are there a raw mode and a packed mode for D8 read command? Interesting.

Can you choose freely the subcode extracting mode for D8 without depending on the C2 pointers? Does D8 read command plus 08 mode for subcodes the trick?

It seems that for extracting C2 pointers in D8 mode, full subs are needed yes or yes. And I understand from your post that for extracting raw subcodes in D8 mode, C2 pointers are needed yes or yes. Well, that makes sense, because I rip with C2 pointers and DIC reports raw mode like the one used. MrX_Cuci rips without C2 pointers (maybe because it's a SafeDisc CD?) and selected mode is the packed according to the output. If so, description of the CDB used?

23

(1,162 replies, posted in General discussion)

Why subcodes of those discs are extracted in packed mode? Mine are extracted in raw mode, always. And what interface are you using to attach that drive? Internal ATAPI channel? Internal SATA channel? ATAPI/SATA to USB 2.0?

Another yet disc with those damn R-W subs, uploaded the logs and whatnot plus a raw subcode now properly extracted by my Plextor drive without cleaning anything.

https://www.mediafire.com/?nldg07nlloooent

D:\Redump\Dumps\Krazy Ivan (Japan)\discimagecreator>discimagecreator.exe cd g: discimagecreator 08 /c2 2000 8192 08
OS
        Windows Server 2003 Enterprise Edition Service Pack 2 32bit
AppVersion
        x86, AnsiBuild, Jul 22 2014 21:56:08
CurrentDir
        D:\Redump\Dumps\Krazy Ivan (Japan)\discimagecreator
InputPath
         path: discimagecreator
        drive:
          dir:
        fname: discimagecreator
          ext:
Start: 2014-07-24(Thu) 00:06:44
Checking reading lead-out
Creating bin from 306893 to 306894 (LBA) 306894
Reading lead-out: OK
Allocating memory for C2 error: 8192/8192
Operation Code: 0xd8, Sub Code: Raw
Creating img(LBA) 306893/306892
C2 error didn't exist
Copying .scm to .img
Descrambling data sector of img(LBA) 144878/144878
Checking ecc/edc LBA 306892/306892
User data vs. ecc/edc doesn't match num: 1
        Sector: 144878,

User data vs. ecc/edc match, except edc doesn't exist to a sector: 20330
Creating bin, cue, ccd(Track) 13/13
Free memory for C2 error: 8192/8192
Calculating hash: discimagecreator (Track 01).bin
Calculating hash: discimagecreator (Track 02).bin
Calculating hash: discimagecreator (Track 03).bin
Calculating hash: discimagecreator (Track 04).bin
Calculating hash: discimagecreator (Track 05).bin
Calculating hash: discimagecreator (Track 06).bin
Calculating hash: discimagecreator (Track 07).bin
Calculating hash: discimagecreator (Track 08).bin
Calculating hash: discimagecreator (Track 09).bin
Calculating hash: discimagecreator (Track 10).bin
Calculating hash: discimagecreator (Track 11).bin
Calculating hash: discimagecreator (Track 12).bin
Calculating hash: discimagecreator (Track 13).bin
Calculating hash: discimagecreator.img

End: 2014-07-24(Thu) 00:16:03

By the way, possible texts you could enhance, so that they sound more natural:

Sub Code ---> Subcode reading mode
C2 error didn't exist ---> No C2 errors
Operation Code ---> Read command
Allocating memory for C2 error ---> Allocating memory for C2 errors
Creating img(LBA) --->Creating img (LBA)
Checking ecc/edc ---> Checking data sectors
User data vs. ecc/edc doesn't match num: ---> Number of sector(s) where user data doesn't match the expected ECC/EDC
User data vs. ecc/edc match, except edc doesn't exist to a sector ---> Number of sector(s) where while user data does match the expected ECC/EDC there is no EDC
Creating bin, cue, ccd(Track) --> Creating bin, cue and ccd (Track)
Free memory for C2 error ---> Freeing allocated memory for C2 errors

29149

Sector 21, more or less the same timestamps as defined by the ISO9660's PVD.

http://i.imgur.com/Ps3LV0V.png

http://i.imgur.com/1CzkbTk.png

Implementing this new field is up to iR0b0t, though.

  1. No ISO9660 file system, no PVD to provide, simple as that.

  2. CDmage was developed when Messalina was still alive, it's an old, uncomfortable and buggy app. Cannot open images with a non-standard (for him, of course) file system. You'd better to run another EDC/ECC checker, an one completely file system agnostic.
    edccchk-v1.25-win32.zip
    chkraw0.14.zip (rename lang(en).ini to lang.ini and delete lang(fr).ini).

  3. Possible emulators of Classis Mac OS: Mini vMac, PearPC and BasiliskII.