Search options (Page 8 of 14)

sarami will you put this link in your first post so people can easily find the runtimes they need.

http://www.microsoft.com/en-us/download … x?id=40784

Why did you change the command line syntax, I can't get it to work at all anymore it just spits out your "usage" help.

How about an example of a command line too, because this "help" is unclear.

DiscImageCreator.exe cd d: Track01 DriveSpeed 8: /c2 256 256 8

or

DiscImageCreator.exe d: Track01 8: /c2 256 256 8

don't work

Here's the profile I use.

[CloneCD ReadPrefs]
ReadSubData=1
ReadSubAudio=1
RegenerateData=0
AbortOnReadError=0
FastErrorSkip=1
IntelligentBadSectorScan=1
SectorSkip=1
ReadSpeedData=8
ReadSpeedAudio=8
NoErrorReport=0
FirstSessionOnly=0
AudioQuality=3
[CloneCD WritePrefs]
DontRepairSubchannelData=1
AlwaysCloseLastSession=0
AmplifyWeak=2
WriteSpeed=0
[CloneCD DefaultReadPrefs]
ReadSubData=0
ReadSubAudio=0
RegenerateData=0
AbortOnReadError=0
FastErrorSkip=2
IntelligentBadSectorScan=1
SectorSkip=100
ReadSpeedData=0
ReadSpeedAudio=0
NoErrorReport=1
FirstSessionOnly=0
AudioQuality=0
[CloneCD DefaultWritePrefs]
DontRepairSubchannelData=1
AlwaysCloseLastSession=0
AmplifyWeak=2
WriteSpeed=0
[Common]
ImageIndex=5
NoDelete=1
[Caption]
DE=Geschütztes PC Spiel
EL=ÐñïóôáôåõìÝíï CD Ðáé÷íéäéïý

It doesn't matter what disc it is, it always outputs the same thing in DIC.

Mode0 = audio lead in
Mode1 = Mode 1 data
Mode2 = Mode 2 data

And no it doesn't put the catalog when you have Read Audio Subchannels, as this is already contained in the sub channels.
What version of CloneCD do you have? I am using 5.3.1.4 , which is the last one.

I don't know what PreGapSubC means exactly to CloneCD, but it seems to always set it to 1. Perhaps it tells the write routine to reconstruct the TOC subchannels based on the ccd indexes.

If the cable works and the enclosure doesn't, then it's obviously an issue with the enclosure and not the fault of DIC or windows.

ok but I had like 5GB free memory at the time... weird =]

F1ReB4LL what disc is that? You know there can be no C2 error but still be intentional header/EDC/ECC errors right? (some psx disc for example with last sector of data track)...

Anyways, better make it so DIC can handle absolute worst case scenario for errors, I guess with some GC disc this is gonna be like 450000-500000 sectors? Maybe you should go back to using files for C2 to avoid excessive ram allocation, or make it sliding window.

Disc I have was having > 80000 error (worst case test).

Someone reported that multiple data tracks weren't dumping proper... seems to work fine for me (D!Zone 3).

Are there hard coded fixes for certain discs in the code? Somebody said there was. I hope you didn't do that, if there is please remove such things and implement proper fixes for them. We do have a couple of other coders you could talk to.

7th guest was fine

SecuROM (and probably Tages/Starforce) is pretty simple in that it uses twin sector's, aka duplicate sectors. The protection checks for these sectors using seeking techniques. We are unsure if it actually checks for the existence of the sectors, or creates a signature based on seek times. But I suppose that is not important, dumping the sectors is what is important here. Since plextor seems to be able to do so with D8, it's possible you may be able to develop a way to dump these discs reliably.

SafeDisc/SmartE/LaserLOK all use intentional C2 error, like Cactus Data Shield. No need to really worry about these ones, as it is not possible to read the data with any standard drive.

Sarami, you need to buy some SecuROM protected discs. Dumps are completely inconsistent... BUT this is not an entirely bad thing... apparently you stumbled on a way to dump the twin sectors (this is a good thing) if it can be made consistent it will be great. Both me and MrTikki have run across this now and we discussed it on IRC for awhile today.

On the bad side, all SecuROM dumps are bad an need redone.

F1ReB4LL's idea is to read the disc linear in both directions , 0-end and end-0 to try and capture all twin sectors. But for some reason DIC reads the twin sectors at random.

Also, can you add a switch to save the unsplit scrambled dump from being deleted.

Also, error is "Unable to Access Device" happens randomly, I don't know what causes it. Other tools don't have this problem.

cachex mem test for fun.

Installed Software

Alcohol 120% 2.0.2 Build 3931
CloneCD v5.3.1.4
DVD Decrypter
EAC .99 PreBeta 5
ISOBuster v3.1
Nero Burning Rom v10 (nerocheck.exe removed)
Nero DiscSpeed 11
OptiDriveControl 1.51
UltraISO Premium v9.51

SPTD Layer v1.81

cachex.exe -i -p -c -r 0xd8 -n 20 d:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on D is  PLEXTOR  CD-R   PX-W5224A 1.04

[+] Buffer size: 2048 kB, read cache is enabled
[+] Supported read commands: BEh D8h
[+] Plextor flush command: accepted
[+] Plextor flush tests: 20/20
[+] Testing cache line size:
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors

cachex.exe -i -p -c -r 0xd8 -n 20 e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is  PLEXTOR  DVDR   PX-760A   1.07

[+] Buffer size: 2048 kB, read cache is enabled
[+] Supported read commands: BEh D8h
[+] Plextor flush command: accepted
[+] Plextor flush tests: 20/20
[+] Testing cache line size:
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors

The error checking F1REB4LL suggested still isn't working as described by him.

dic should continue to next sector on c2 error, after full disc is read then errors should be corrected by using c2 file. Error correction should be in this manner...

read c2 file
on sector error reread sector
if no error fix sector in image and mark c2 fixed
else next error sector
continue until all read error fixed or retries exhausted

this way disc does not get damaged further by heat from laser reading same area repeatedly. additionally buffer gets flushed for sure.

also agree, please restore verbose sector error and retry

If you add hashing, I would prefer that they can be outputted in clrmame format for using in the newdisc menu.

I think that F1REB4LL's suggestion of error correction be used so we can be sure that the cache is defeated on re-read.

:EDIT:

Got testing results back from other person with different HW revision 5224a.

DIC w/C2 is now functioning properly with his drive. =]

No, I didn't use the new version of DIC to dump that, I used the last one. So not with C2. Also it was the older dump I made of the OEM version.

Very strange that it happened at all and didn't give any error. There was subcode desync in the log however, maybe that was the reason.

I will do it again and see if that same bug occurs again. If it does, I will compress it all and upload it somewhere for you to look at.

A friend of mine with Plextor PX-W5224A, has problem with his drive reporting tons of C2 error. It has same firmware as mine and same hardware revision. Dumps are OK though... very strange! EAC does not report C2 error when ripping audio.

Can you scan the .exe itself and give me the version number.