Use my old tool for this:
http://forum.redump.org/topic/18980/dum … g-protech/
OptiARC seems to give the best results for RingProtech...
You are not logged in. Please login or register.
Redump Forum → Posts by reentrant
Use my old tool for this:
http://forum.redump.org/topic/18980/dum … g-protech/
OptiARC seems to give the best results for RingProtech...
Redump already modifies data by not using rawdump
The best way to preserve the disc is to scan it with microsocope. Period
Yep, one in cue field and copied to comments iirc. Was adding it few days ago...
I have submitted one multi session coverdisk (Max Kids 2/2009)...
Dump with /ms flag is the same as old dump. There's an additional info printed:
Creating .scm (LBA) 120757/353286 Lead-out length of 1st session: 6750
Creating .scm (LBA) 120762/353286 End of readable sector
Sleep 20000 msec
Lead-in length of 2nd session: 4500
Creating .scm (LBA) 125407/353286 Pregap length of 1st track of 2nd session: 150
Creating .scm (LBA) 353286/353286
No C2 errors
REM SESSION 01
FILE "Max_Kids_2_2009 (Track 1).bin" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00
REM LEAD-OUT 01:30:00
REM SESSION 02
REM LEAD-IN 01:00:00
REM PREGAP 00:02:00
FILE "Max_Kids_2_2009 (Track 2).bin" BINARY
TRACK 02 MODE2/2352
INDEX 01 00:00:00
Have you considered adding automatically /ms flag when disc is multisession?
sarami, have you looked more closely at multisession issue I reported few days ago? Sth doesn't look right there...
Nexy: VS 2015
I have some multisession discs and I wanted to check those. I don't understand one thing. I made a DIC dump few months ago and got:
========== FULL TOC ==========
FirstCompleteSession: 1
LastCompleteSession: 2
Session 1, Ctl 0, Adr 1, Point 0xa0, FirstTrack 1, Format: CD-DA or CD-ROM
Session 1, Ctl 0, Adr 1, Point 0xa1, LastTrack 1
Session 1, Ctl 0, Adr 1, Point 0xa2, Lead-out, MSF 25:22:08 (LBA[114158, 0x1bdee])
Session 1, Ctl 0, Adr 1, Point 0x01, Track 1, MSF 00:02:00 (LBA[000150, 0x00096])
Session 1, Ctl 0, Adr 5, Point 0xb0, NextSession, MSF 27:52:08 (LBA[125408, 0x1e9e0])
Outermost Lead-out of the disc, MSF 78:32:36 (LBA[353436, 0x5649c])
Num of pointers in Mode 5, 02
Session 1, Ctl 0, Adr 5, Point 0xc0, Optimum recording power, 00
First Lead-in of the disc, MSF 95:00:00 (LBA[427500, 0x685ec])
Session 2, Ctl 4, Adr 1, Point 0xa0, FirstTrack 2, Format: CD-ROM-XA
Session 2, Ctl 4, Adr 1, Point 0xa1, LastTrack 2
Session 2, Ctl 4, Adr 1, Point 0xa2, Lead-out, MSF 78:32:36 (LBA[353436, 0x5649c])
Session 2, Ctl 4, Adr 1, Point 0x02, Track 2, MSF 27:54:08 (LBA[125558, 0x1ea76])
========== OpCode[0xd8]: SubCode[8]: Track[01]: Check CD + G ==========
<rom name="Max_Kids_2_2009 (Track 1).bin" size="268146816" crc="d9189fa7" md5="384c32d53e044f977495d82e9a3230dc" sha1="d4cefd6d597221813663c784b2cbe5fe79e32013" />
<rom name="Max_Kids_2_2009 (Track 2).bin" size="535969056" crc="72a7f75c" md5="e2c0fd53846c600c740c458faf567e9a" sha1="7e21e6515863c0acc380411753049a42abec1070" />
Now I redumped the disc with newest DIC from git and got:
========== FULL TOC ==========
FirstCompleteSession: 1
LastCompleteSession: 2
Session 1, Ctl 0, Adr 1, Point 0xa0, FirstTrack 1, Format: CD-DA or CD-ROM
Session 1, Ctl 0, Adr 1, Point 0xa1, LastTrack 1
Session 1, Ctl 0, Adr 1, Point 0xa2, Lead-out, AMSF 25:22:08 (LBA[114008, 0x1bd58])
Session 1, Ctl 0, Adr 1, Point 0x01, Track 1, AMSF 00:02:00 (LBA[000000, 0000000])
Session 1, Ctl 0, Adr 5, Point 0xb0, NextSession, AMSF 27:52:08 (LBA[125258, 0x1e94a])
Outermost Lead-out of the disc, AMSF 78:32:36 (LBA[353286, 0x56406])
Num of pointers in Mode 5, 02
Session 1, Ctl 0, Adr 5, Point 0xc0, Optimum recording power, 00
First Lead-in of the disc, AMSF 95:00:00 (LBA[427350, 0x68556])
Session 2, Ctl 4, Adr 1, Point 0xa0, FirstTrack 2, Format: CD-ROM-XA
Session 2, Ctl 4, Adr 1, Point 0xa1, LastTrack 2
Session 2, Ctl 4, Adr 1, Point 0xa2, Lead-out, AMSF 78:32:36 (LBA[353286, 0x56406])
Session 2, Ctl 4, Adr 1, Point 0x02, Track 2, AMSF 27:54:08 (LBA[125408, 0x1e9e0])
========== OpCode[0xd8]: SubCode[8]: Track[01]: Check CD + G ==========
<rom name="Max_Kids_2_2009 (Track 1).bin" size="268499616" crc="b67cbbb8" md5="38c83f38723a04a7aaa9588b63ae5912" sha1="6ce9fa394be0b87f1d2e862794b0a0bf1e480c0b" />
<rom name="Max_Kids_2_2009 (Track 2).bin" size="535969056" crc="72a7f75c" md5="e2c0fd53846c600c740c458faf567e9a" sha1="7e21e6515863c0acc380411753049a42abec1070" />
First track in 2nd dump is bigger by 150 sectors, is it expected that old vs new dumps are different?
New Cue:
REM SESSION 01
FILE "Max_Kids_2_2009 (Track 1).bin" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00
REM LEAD-OUT 00:00:00
REM SESSION 02
REM LEAD-IN 00:00:00
REM PREGAP 00:00:00
FILE "Max_Kids_2_2009 (Track 2).bin" BINARY
TRACK 02 MODE2/2352
INDEX 01 00:00:00
Old Cue:
FILE "Max_Kids_2_2009 (Track 1).bin" BINARY
REM SESSION 01
TRACK 01 AUDIO
INDEX 01 00:00:00
FILE "Max_Kids_2_2009 (Track 2).bin" BINARY
REM LEAD-OUT 25:20:08
REM SESSION 02
TRACK 02 MODE2/2352
INDEX 01 00:00:00
Mr Nexy: Problem with Plextor and 8x:
http://forum.redump.org/topic/13211/fir … or-drives/
"P.S.: If you own a Plextor drive which features the silent mode (for example: Premium, Premium 2 and PX-7xx drives [for this serie only the true ones, not the rebadged ones]), NEVER enable the silent mode. This funcion is somewhat buggy, and after of that your drive maybe remains stucked forever at 8x read speed for CD, even if you disable that mode."
All my drives are stucked at 8x. Shit happens?
My Px760 starts reading DVDs when I disassemble it and clean the lens. As always is stops doing so after few weeks...
I have problems with safedisc 2.9 discs sometimes, it seems they have some type of weak sectors towards the end of the disc. They get no C2 errors, but get EDC/ECC errors after descramble and I have to manually redump those sectors many times in iso buster after performing a seek to 150 to get a good dump of them.
So far two discs have this problem, disc 3 of original Splinter Cell version, and Need for Speed Hot Pursuit. I wonder if anyone else has encountered this?
CSS seems OK now for the discs I tested.
If RapidCRC is not present with test version, hashes are not calculated. Maybe forget I suggested this as the tool has no command line version.
Can you remove the 4 spaces from produced dat files , I have to manually remove them always when submitting dump hashes.
I used to have problems with this disc. I think it uses weak sectors too. I had to manually zero out scm file in some places and then descramble manually to get correct data...
+1
It slows the process a lot also on my PC.
An attempt to dump DPM data from SecuROM DVD has been documented here: http://forum.redump.org/topic/17084/ana … l-120-dpm/
I tried going back, going forward, flushing cache, but it's all in vain...
Oh that's quite bad. Maybe eject + load (like hard reset) will make it work?
What happens when crc is 0 - some data is invalid?
When subQ crc is 0 DIC stops. When I retried it worked. Is is possible to add some more complex restart logic? If crc is 0 go back 100 sectors and retry reading? This crc 0 thing looks quite random...
Some of the dumps are here: http://forum.redump.org/topic/16655/ibm … to-redump/
TRUSTEDME + HARD groups. These are the suspicious ones that were picked up last time...
Descramble algorithm: https://github.com/saramibreak/DiscImag … output.cpp
Line 1699
It's very complex...
reentrant wrote:You don't have access to low level read commands that return DVD correction codes.
You do - http://forum.redump.org/topic/3808/raw- … iscussion/
I meant something like that: https://debugmo.de/2007/07/read-your-dvds-the-raw-way/
Don't forget that even if you succeed at dumping few more sectors you'd still get unverified data. You don't have access to low level read commands that return DVD correction codes.
In CD terms it's like you would be trying to read more sectors from unreabable range but in 2048 mode. Your drive firmware tries to correct all mastering errors + data tracks defects which are in turn "masked" by ECC/EDC.
How can you be sure that the data you read is the data on the disc? Without correction codes it's not deterministic to dump such sectors.
Do you expect that people should rerip all those 2400 discs?
Maybe another dat should be created solely for those SS ranges (similar to DMI, PFI dats)?
I have DVD9 disc and DIC reports following data:
========== SectorLength ==========
LayerZeroSector: 2010896 (0x1eaf10)
========== PhysicalFormatInformation ==========
BookVersion: 1
BookType: DVD-ROM
MinimumRate: 10.08 Mbps
DiskSize: 120mm
LayerType: Layer contains embossed data
TrackPath: Parallel Track Path
NumberOfLayers: Double Layer
TrackDensity: 0.74â╩m/track
LinearDensity: 0.293â╩m/bit
StartingDataSector: 196608 (0x30000)
EndDataSector: 1730300 (0x1a66fc)
EndLayerZeroSector: 0 (0)
BCAFlag: No
MediaSpecific:
========== SectorLength ==========
LayerZeroSector: 1533693 (0x1766fd)
LayerAllSector : 3544589 (0x36160d)
Why LayerZeroSector is different in both cases?
Hi sarami. I have a safedisc protected disc and I want to report some weird info. Below is a list of C2 error counters from protected range:
240
264
288
312
Each of these vary by 24. I can confirm that this is correct info.
nightson: https://club.myce.com/t/difference-betw … eed/176851
Read about Plextor SpeedRead. But keep in mind that PlexTools is a true devil and better don't install it or your drive would go to shit...
So if data / track hashes stay the same, what's the problem with emu devs, can't they just generate the cues internally on the fly?
Wow, I forgot about this topic
If you're using version from 23th reply in this thread specify cue path as last argument!
This example shows the power of DIC + Plextor drives
Redump Forum → Posts by reentrant
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.