226

(3,488 replies, posted in General discussion)

Another one, this is a PC press kit CD-Rom (not CD-R).

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

It dumps consistently in Iso Buster (even on different drives).
But it gets C2 errors in dic and scm from different dumps dont match - I've tested with an old a new dic version, logs included.

The disc has a few scratches, nothing major.

FYI ImgBurn is dumping with different hashes each time, but not throwing any errors.

227

(3,488 replies, posted in General discussion)

Having trouble dumping one particular Action Replay PS2 disc.

It gets stuck here: "Reading DirectoryRecord    1/   2"

Here's logs for attempting to dump on two different drives: https://drive.google.com/file/d/1uMk7G3 … sp=sharing

I've dumped a ton of PS2 action replay discs and it is the first time i've had this error. For what its worth, I tried dumping this the past few months on older builds of DIC and same result.

228

(3,488 replies, posted in General discussion)

Sarami, i'm continuing to test dic with ps4 kiosk discs. this one was dumped with the latest stable, does it look good to you? https://drive.google.com/file/d/1bqYwos … sp=sharing

here's redump's non-matching entry for reference http://redump.org/disc/62879/

Hi, after dumping a handful of discs and submitting them properly, you should be granted Dumper status.

Since its easier to provide feedback on forum submissions, the mods want to know you got the hang of dumping/submitting before granting you Dumper status to submit via New Disc Form.

230

(3,488 replies, posted in General discussion)

sarami wrote:

This is certain "Anchor Volume Descriptor Pointer". This is the last sector.

So dic dump is confirmed good? If so I will submit a fix. Thanks.

231

(3,488 replies, posted in General discussion)

Regarding the dic logs for the disc we're discussing: https://drive.google.com/file/d/1oq0uz4 … xyYF5/view

>If you have ISO9660 + UDF hybrid bd-r, please upload logs and tell me the last sector.

Both dic and isobuster dumps end in 0's

Here are the final bytes from the DIC dump https://mega.nz/#!cvAHDYJZ!2ofFgyO2YJOh … ToQR34tBKQ


Thanks smile

232

(3,488 replies, posted in General discussion)

sarami wrote:

Are there some 0's in your dump?

Yes, both dic and isobuster. isobuster has additional 0's though.

233

(3,488 replies, posted in General discussion)

Even in the dic dump there are some 0's at the end. Isobusters just go for longer.

Submit the dic dump?

234

(3,488 replies, posted in General discussion)

The additional sectors are just 0's.

235

(3,488 replies, posted in General discussion)

How do I extract certain sectors? Thanks.

236

(3,488 replies, posted in General discussion)

Sorry, I got confused. This is the entry for the isobuster dump: http://redump.org/disc/64427/

Size is much closer.

If you believe the dic dump is correct, I will ask Enker to update.

237

(3,488 replies, posted in General discussion)

Sure, I understand that, but that's about 10GB of unused data in the disc image. Does that seem right?

238

(3,488 replies, posted in General discussion)

I have redumped yet another one, https://drive.google.com/file/d/1oq0uz4 … sp=sharing

iso size is full disc, but data should only be about 34gb

239

(3,488 replies, posted in General discussion)

sarami wrote:

Yes. How about Isobuster size?

Size / hash matches isobuster and dic dump.

240

(3,488 replies, posted in General discussion)

Thanks, both drives dumped the same. Looks good to you? https://drive.google.com/file/d/1t2EOdj … sp=sharing

241

(3,488 replies, posted in General discussion)

I tried with another one, I left it dumping on my PS3 OEM drive (logs here): https://drive.google.com/file/d/1bZMna_ … sp=sharing
It wrote out the full disc size, even though data only took up 32 gb or so.

Not sure how long this ^ took, but when I came home and tried dumping on my LG, the dump slowed way down after the data area (32 GB or so) and I canceled the dump: https://drive.google.com/file/d/10oD7w2 … sp=sharing

242

(3,488 replies, posted in General discussion)

sarami, good sign. my ps3 OEM drive dumps with the same results: https://drive.google.com/file/d/1fVoJi3 … sp=sharing

Thank you! I will submit these results.

How do you check UDF version of the disc? I'd like to make sure all my other PS4 kiosk BD-Rs are UDF 2.50, thanks.

243

(3,488 replies, posted in General discussion)

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

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

244

(3,488 replies, posted in General discussion)

Thank you, I've redumped with updated firmware and new DIC as well as IsoBuster https://drive.google.com/file/d/15PSYB6 … sp=sharing

dic size: 34,139,484,160 bytes
isobuster: 34,138,947,584 bytes (same size as before)

245

(3,488 replies, posted in General discussion)

sarami wrote:

I don't know now.

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?

246

(3,488 replies, posted in General discussion)

sarami wrote:

I can't fix this problem now. By the way, how about other BD-R?

Same way. which size is correct? 33gb or 45gb? i can do more tests if necessary.

247

(3,488 replies, posted in General discussion)

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

248

(3,488 replies, posted in General discussion)

sarami wrote:
user7 wrote:

2. DIC and other drive                => fails (goes super slow towards the end)

Are there logs?.

Yes, but i canceled so they're incomplete: https://drive.google.com/file/d/14gLO6N … sp=sharing

Dumping slows WAAAAAY down.

249

(3,488 replies, posted in General discussion)

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...

250

(3,488 replies, posted in General discussion)

I redumped the PS4 kiosk disc BD-R with the PS3 OEM drive this time and got size "48440016896". This number seems to be the ENTIRE size of the blu-ray disc, including where data isn't written. Can this be right? Shouldn't the dump end where the data ends?

The lite-on blu-ray dump isobuster iso matches the data size without padding (34,138,947,584 bytes). I'm inclined to believe this is correct.

Is there a definite answer?