ASUS and LG Drive Audio Tracks / Positive Offset Testing

In the other thread I described what was the problem with ASUS drives (problems with locating data offset in cache). If this is handled correctly the dumps should be safe.

Problem = data in cache can sometimes be shifted by 1 (or more?) sectors. It's mandatory to parse cache data (subs) to locate correct offset instead of blindly assuming the offset.

Looks random and happens from time to time like 1/15

> if it occurs so rare, then if dump 2 times and the two dumps match it should be correct dump.

IIRC I had never 2 consecutive bad dumps with ASUS. But it's just a probability - if something might happen it will happen

I believe that is the bug in Plextor firmware, already discussed many times, I believe the first time reported and confirmed as such, was in the following series of posts:

http://forum.redump.org/post/91255/#p91255

So far it was reported only for PX-755/760 and other Plextor DVD drives like PX-716/712 were reported as fine, but maybe the Premium has such (or similar) bug as well. BTW, I found even earlier discussion of such problem:

http://forum.redump.org/post/72520/#p72520

where @sarami suggested to rule out DiscImageCreator bug to use combination of cdtoimg.exe (d8 hacked) and descramble using Descramble_CDDA.exe:

http://forum.redump.org/post/72549/#p72549

actually, my BW-16D1HT (and it's brand new, no any wear) is terrible reader when it comes to real tough C1/C2 errors. I think so, because on Cactus protected discs - those are intentionally pressed at the factory with incredible amounts of C1/C2 errors - on one early version of the protection, DicsImageCreator counted about 8000 C2 errors alone:

http://forum.redump.org/topic/39461/how … ular-lbas/

and BW-16D1HT cannot even touch them:

http://forum.redump.org/post/94578/#p94578

to be honest only drives (at least that I own) that can do it are PX-5224 and surprisingly NEC ND-3530A (later NEC like ND-4550A failed very badly on my tests and ND-3520A fails as well. so, it's really possible ND-3530A and potentially the model after it - ND-3540A are the only working one. Those are actually the last NEC, the next ND-4550A is Sony-NEC on the label).

as far as I know there was at least one batch of PX-716, especially those used in USB enclosures, that had some issue with the laser on CDs and eventually they stop reading CDs altogether even after very light use. also, at the end of the post here:

http://forum.redump.org/post/95189/#p95189

I documented how PX-5224 that was reporting hundreds of C2 errors on the same discs after some more hours of use started to work, i.e. probably the laser "wake up" from the use instead die.

totally agree, as newbie here, recently I bought 708A, 712A and 716A : all of them are with dead laser in different stages, i.e. 708A and 712A the laser is completely dead (it cannot read neither CD, nor DVD, actually 712A was able only once to read one particular CD, but obviously the laser is very very weak) and 716A cannot read CDs, still good for DVDs (but that's more or less useless).

However, at least for 708A and 712A there are replacement lasers available from China - in 1 month or so I will be be able to give feedback and tell if the replacement laser is as good as original, i.e. if they can read my favorite test CDs - those with Cactus protection, i.e. many C1/C2 errors pressed at factory.

So, bottom line, I wouldn't recommend buying 716A at all - as there are no replacement lasers for them. Currently, BW-16D1HT beats PX755/760 in most cases, because of the aforementioned in previous posts firmware bug. So, I guess, only safe bet are 708A and 712A, but if you're willing to replace the laser plus for me it is still an open question if the replacement laser is as good as the original. I ordered mine, but shipping from China takes forever...

Also, Plextor PX-5224 I bought has a fault:

http://forum.redump.org/post/94515/#p94515

luckily I found way to workaround its fault, but not how to fix it. So, at least for me, so far it turned it's kind of impossible to find second hand Plextor that in 2021 is actually still in fully working order.

No problem, I will do that and report back.

Thanks. If data-shifted is really random, it will occur someday... btw, what drive and os do you use? Jackal reported that it occurred by ASUS (What ASUS?) and linux (What distribution?) http://forum.redump.org/post/93955/#p93955

Tell me the drive name and firmware before a flash, plz.

I've been doing experiments in switching between using my Plextors and my WH14NS40 crossflashed to a BW-16D1HT for various rips. One thing that periodically comes up is the inability for the BW-16D1HT drive to dump some discs due to a "this drive can't read into lead out" message from DIC. I thought the /mr switch was meant to resolve this error by reading into the lead out by reading from the cache? However, for this zero offset disc I just recently tried to dump, even /mr wouldn't allow the disc to be dumped due to the "can't read into lead out" error.

Is there some other steps I'm supposed to be doing to dump such discs?

I've had that happen before, but I also see this from some discs, where it doesn't even go through the process of trying to get a different buffer size:

.\Programs\Creator\DiscImageCreator.exe cd F "ISO\test\test.bin" 8 /c2 5000 /ns /sf /mr
AppVersion
        x86, AnsiBuild, 20210701T212154
/c2 val2 was omitted. set [0]
/sf val was omitted. set [60]
/mr val was omitted. set [50]
CurrentDirectory
        D:\mpf
WorkingPath
         Argument: ISO\test\test.bin
         FullPath: D:\mpf\ISO\test\test.bin
            Drive: D:
        Directory: \mpf\ISO\test\
         Filename: test
        Extension: .bin
StartTime: 2021-11-17T14:47:00-0600
Set the drive speed: 1411KB/sec
This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 0]
This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 1]
This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 2]
This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 1, SubCode: 4]
LBA[001686, 0x00696]: [F:ReadCDForCheckingReadInOut][L:801]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 04, 00, 00, 06, 96, 00, 00, 01, f8, 00, 00
dwBufSize: 2352
This drive can't read the lead-out
EndTime: 2021-11-17T14:47:01-0600

I wonder if it's 0 offset discs that do it? I wish I had been keeping a list of which ones do it, but I haven't, so I can't easily go back and check. I know this one is 0 offset according to the Plextor, though, so there's at least one 0 offset disc that does it.

Edit: It looks like it's a problem with the firmware I'm using. I updated to 3.10 a while back after a Sarami mentioned ripping with that version and I was trying to troubleshoot a disc that wouldn't dump. Looking at the DIC source code, though, it only flags drives running 3.00 and 3.02 as capable of reading the leadout via 0xF1. I'll probably just downgrade my drive back to 3.02, as I'd rather not modify DIC.

Edit2: I haven't tried the 0 offset disc again, but it looks like /mr works again after the downgrade.