Search options (Page 11 of 30)

Now we're seeing a new size... 34138929152

logs: https://drive.google.com/file/d/1CqmRbl … sp=sharing

well i've got over a dozen of these things. is there anyone we can ask? should i buy another drive model to test with?

With LITE ON iHBS112-04 2 drive:

Somewhere around here: Creating iso(LBA) 16833824/23652352
the slowdown occurs, it becomes very slow...

https://drive.google.com/file/d/1aNOKPS … sp=sharing

1. DIC and PS3 OEM drive          => 48440016896
2. DIC and other drive                => fails (goes super slow towards the end)
3. Isobuster and PS3 OEM drive => 48440016896
4. Isobuster and other drive       => 34138947584 (size of data on disc)

Would love to mail you one of these...

Data size on finder level is about what isobuster dumps (34,138,947,584 bytes). I presume this means it has to be overdumping?

I'm going to dump with the same PS3 OEM drive with isobuster and see what happens.

The previous resurface might need to be carefully smoothed out. Very doable with care. dangerboy (Game-Rave) resurfaced a few of his ultra-rare discs from super scratched to safety with a cheapy at home one, so i'm sure a decent resurfacer would do a great job on some light scratches.

Someone will give a better explanation, but I know some other drives CAN dump CD-roms with DIC, I think its discs with positive offsets. Why can't these discs that dump successfully with other drive models be added to redump? Or can they? Not sure we've had that conversation yet.

Despite the improvement I'm still getting overdumps on some discs.

CD-R overdump: https://drive.google.com/file/d/1eTf-J5 … sp=sharing
DVD-R overdump: https://drive.google.com/file/d/1EXNDBR … sp=sharing

When dumping a press kit CD-R, it crashes converting from img to bin: https://drive.google.com/file/d/1JOaw_r … sp=sharing

edcchk shows the .img has 0 errors.

isobuster is dumping the disc with consistent hashes, different than dic's .img hashes.

Still getting overdumps: https://drive.google.com/file/d/12nwgBR … sp=sharing

DIC is over-dumping a DVD-R.

DIC logs: https://drive.google.com/file/d/15PsgjX … sp=sharing

I dumped twice with IsoBuster and once with IMG Burn to get the same hashes / size: 3.27 GB (3,515,416,576 bytes)

Here's IMG Burn analysis:

PLEXTOR DVDR   PX-755A 1.08 (USB)
Current Profile: DVD-R

Disc Information:
Status: Complete
Erasable: No
Sessions: 1
Sectors: 1,716,512
Size: 3,515,416,576 bytes
Time: 381:28:62 (MM:SS:FF)
Supported Write Speeds: 6x, 8x, 12x, 16x

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 1716511)
-> LeadOut  (LBA: 1716512)

Pre-recorded Information:
Manufacturer ID: TTH02

Recording Management Area Information:
PIONEER DVD-RW DVR-118L DVD-RW DVR-118L

Physical Format Information (Last Recorded):
Book Type: DVD-R
Part Version: 5
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 1,913,119
Last Physical Sector in Layer 0: 0

Performance (Write Speed):
Descriptor 1...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 8,310 KB/s (6x)
Descriptor 2...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 11,080 KB/s (8x)
Descriptor 3...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 16,620 KB/s (12x)
Descriptor 4...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 1716511 (0x001A311F)
-> RS: 16,620 KB/s (12x) - WS: 22,160 KB/s (16x)

Issues properly dumping *-Rs seems to be a recurring theme with dic that's never been completely fixed over the years. Most discs do not have issues, but throughout the years, issues have arisen from dumping *-Rs in dic that work in IsoBuster properly.