Jump to content

Recommended Posts

Posted

Hello.

 

On one of my PC, when i chose to make an iso in ISO Read mode, i've got only a file of 2Ko.

DVD-Rom is a Plextor PX-116A3 (firmware 1.01 modified RCP-1).

Posted

Post a log. You are probably looking at the MDS file, which is small. The ISO should be in the location in Tools --> Settings --> File Locations --> Image Files

 

Regards

Posted

Hello.

 

Thanks, but i'm not stupid enough to mistake the MDS file for the iso file !!!!!!

And BTW, the MDS file is around 4Ko, not 2Ko.

 

Otherwise, here several tests. Everything is explained in the readme file.

Logs_Files.rar

Posted
I 11:02:06 Reading Session 1 of 1... (1 Track, LBA: 0 - 0)

I 11:02:06 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 0)

I 11:02:06 Operation Successfully Completed! - Duration: 00:00:00

 

Your drive appears to be reporting bad TOC info.

 

Copy + paste the disc info from the panel on the right when in read mode with the plextor active and that disc in the drive.

Posted
Thanks, but i'm not stupid enough to mistake the MDS file for the iso file !!!!!!

Never said you were. And gee, thanks for the info on the MDS's filesize. I'll just retire to the corner while all the smarty pants on the net teach me what it's all about.

 

Regards

Posted

Here the panel :

 

PLEXTOR DVD-ROM PX-116A3 1.01 (ATA)

Current Profile: DVD-ROM

 

Disc Information:

Status: Complete

Erasable: No

Sessions: 1

Sectors: 2 294 097

Size: 4 698 310 656 bytes

Time: 509:49:72 (MM:SS:FF)

 

TOC Information:

Session 1...

-> Track 01 (Mode 1, LBA: 0)

 

Track Information:

Session 1...

-> Track 01 (LTSA: 0, TS: 2294096, LRA: 2294096)

 

Physical Format Information (Last Recorded):

Disc ID: 0@P-!-00

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: 2 495 103

Last Physical Sector in Layer 0: 0

 

 

For more information :

Problem is not specific to that disc, and not specific to recorded DVDs, it occurs on all DVDs.

Problem is specific to ImgBurn, no problem with clonecd or Nero.

 

Don't realy sure, but maybe the post may put be back to bug repport ???

Posted

This is what it should look like:

 

TOC Information:

Session 1... (LBA: 0)

-> Track 01 (Mode 1, LBA: 0 - 2297887)

-> LeadOut (LBA: 2297888)

 

Your drive isn't reporting the leadout address, or if it is, it's doing it differently to every other drive I've ever come across.

 

Now I need you to do the following:

 

Eject the disc

Load the program and switch to Read mode.

Press F8.

Insert the disc.

 

Wait until is says 'Ready' in the status bar and then press F8 again.

 

Save the log to a file and attach it in your next post.

 

Thanks :)

Posted

They're totally different.

 

DVD Decrypter didn't have to deal with multiple tracks etc and just went on the capacity. ImgBurn uses TOC info so it knows where tracks/sessions start and end.

Posted

Yours...

 

I 19:25:22 [0:0:0] PLEXTOR DVD-ROM PX-116A3 1.01 (M:) (ATA)

I 19:25:22 CDB: 43 00 00 00 00 00 01 10 00 00

I 19:25:22 CDB Interpretation: Read TOC/PMA/ATIP - Formatted TOC

I 19:25:22 BUFFER: 00 0A 01 01 00 14 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

 

A normal drive...

 

I 19:07:31 [6:0:0] ATAPI DVD A DH20A3P XY13 (R:) (SCSI)

I 19:07:31 CDB: 43 00 00 00 00 00 00 10 00 00

I 19:07:31 CDB Interpretation: Read TOC/PMA/ATIP - Formatted TOC

I 19:07:31 BUFFER: 00 12 01 01 00 14 01 00 00 00 00 00 00 14 AA 00 00 23 10 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

 

Your plextor just isn't returning any leadout info (that's the 'AA' bit in the buffer).

 

I can probably work around it but really this is a firmware bug - or some filter driver corrupting things.

Posted

Ok, I've implemented a workaround for when drives only report 1 descriptor in the TOC info (i.e. the leadout is missing). It'll fabricate it based on the value returned by the 'Read Capacity' command.

 

ie. the command that gives you this info:

 

Sectors: 2 294 097

Size: 4 698 310 656 bytes

Time: 509:49:72 (MM:SS:FF)

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.