BIN instead of ISO. What differences?

[Prez]

Hi,

 

In which cases ImgBurn can suggest me to change an Image format? What differences between ISO and BIN files. Mode - Read. Source - DVD-R, burned from the dowloaded ISO. Capacity - approx 2,5 Gb.

 

Thanks in advance.

Edited July 8, 2010 by Prez

[LIGHTNING UK!]

Open ImgBurn in Read mode, copy + paste the disc info from the panel on the right please.

[Prez]

I see. Ok. But I have no that DVD right now. A bit later...

[Prez]

Ok. Here is it.

 

ASUS DVD-E616P 1.04 (ATA)

Current Profile: DVD-ROM

 

Disc Information:

Status: Complete

State of Last Session: Complete

Erasable: No

Sessions: 1

Sectors: 1 182 352

Size: 2 421 456 896 bytes

Time: 262:46:52 (MM:SS:FF)

 

TOC Information:

Session 1... (LBA: 0)

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

-> LeadOut (LBA: 1182352)

 

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

 

And screenshot.

 

Edited July 8, 2010 by Prez

[Prez]

A very strange. The same info and DVD but from the DVD-RW device:

 

ASUS DRW-1608P 1.57 (ATA)

Current Profile: DVD-ROM

 

Disc Information:

Status: Complete

State of Last Session: Complete

Erasable: No

Sessions: 1

Sectors: 1 182 352

Size: 2 421 456 896 bytes

Time: 262:46:52 (MM:SS:FF)

 

File System Information:

Sectors: 1 182 352

Size: 2 421 456 896 bytes

Time: 262:46:52 (MM:SS:FF)

 

TOC Information:

Session 1... (LBA: 0)

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

-> LeadOut (LBA: 1182352)

 

Track Information:

Session 1...

-> Track 01 (LTSA: 0, LTS: 1182352, LRA: 1182351)

 

Pre-recorded Information:

Manufacturer ID: MCC 03RG20

 

Recording Management Area Information:

ASUS DRW-1608P

 

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: 1 378 959

Last Physical Sector in Layer 0: 0

 

Screenshot:

 

 

As result ImgBurn has a problem with image creation in my DVD-ROM ASUS DVD-E616P 1.04. It was stop reading at the 78% completed. But Alcohol 120% have a full disk reading succefully at the same drive.

 

 

Edited July 8, 2010 by Prez

[LIGHTNING UK!]

I can't really see a problem with either of those.

 

Do you have an actual log of your attempting to read the disc? (in both drives)

[Prez]

I can't really see a problem with either of those.

Please look at the screenshots of ImgBurn. In the DVD-ROM it can't determine neither vol.label nor file system. But in the DVD-RW it can.

Do you have an actual log of your attempting to read the disc? (in both drives)

I can make it now. Please wait...

[LIGHTNING UK!]

Ah yes... I was looking at the disc info and trying to work out why it wanted to make a bin file.

 

It's probably just a case of the disc not being very readable in the drive.

 

The way to confirm that is to press F8 and enable I/O debug mode, THEN insert the disc and see what gets written in the log.

[Prez]

DVD-ROM.

 

Sorry, I forgot. ImgBurn stop reading at the 87% but not 78% . But I think it is not matter.

 

 

ImgBurn stop reading and say no words. I've been forced to click Cancel after the some time.

And this is not an Audio. It is a software DVD.

 

DVD-RW.

 

There is no problem.

 

Both logs are in the attachments.

ImgBurn_DVD_ROM.log

ImgBurn_DVD_RW.log

[Prez]

It's probably just a case of the disc not being very readable in the drive.

Unfortunately, no .

I took another my software DVD-R, insert it into a DVD-ROM and got the same situation (I mean in ImgBurn, of course. No label, No file system).

 

This DVD have a very good and full readable at the system explorer, or Total commander or Alcohol 120%. In the same drive (DVD-ROM).

 

The way to confirm that is to press F8 and enable I/O debug mode, THEN insert the disc and see what gets written in the log.

Thanks. I'll try this now.

Edited July 8, 2010 by Prez

[Prez]

A new log. Very interesting . Look at the line in log:

 

I 20:43:22 Reading(Read) Finished!

 

I got it at the 87% completed. Then the LED on my DVD-ROM is turned OFF and copying have been stopped. Then I click a Cancel.

ImgBurn.log

[LIGHTNING UK!]

I 20:38:02 [1:1:0] ASUS DVD-E616P 1.04 (G:) (ATA)

I 20:38:02 CDB: 51 00 00 00 00 00 00 00 20 00

I 20:38:02 CDB Interpretation: Read Disc Information

I 20:38:02 BUFFER: 00 20 0E 01 01 01 01 00 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

I 20:38:02 [1:1:0] ASUS DVD-E616P 1.04 (G:) (ATA)

I 20:38:02 CDB: 52 01 00 00 00 01 00 00 30 00

I 20:38:02 CDB Interpretation: Read Track Information

I 20:38:02 BUFFER: 00 22 01 01 00 00 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

 

Ok, this is the important stuff.

 

The response to the 'Read Track Information' command is useless and is what's causing the issue. It's just not MMC compliant and basically contains no valid data.

 

I can probably implement a workaround but it's not really my problem.

 

FYI, the DVDE616P2 with 1.08 firmware works fine.

[Prez]

Thanks. Some years ago I tried to upgrade a firmware for this drive but was can't. I don't remember what was a problem. BTW, this drive have a very good reading possibilities. I've a succesfully read in it a DVDs that have a lot of faults in the other drives.

[LIGHTNING UK!]

Ok, a workaround has now been implemented ready for 2.5.2.0.

[Prez]

Many many thank's . The last firmware that I have is 1.04. My drive is E616P and official firmware from the ASUS (for the E616, E616P1, E616P2 and E616P3) do not install because a drive names are mismatch. So your workaround would help me, I hope.

[LIGHTNING UK!]

I assumed yours was just a E616P1, even if it didn't actually have the '1' at the end of the identifier. Still, the newest for that is 1.04 and you're already on that.

[Prez]

Some years ago I have found an utility from Pioneer, that can loads an any bin firmware image to any version of drive. It has no any checks for compatibility. I can find it in my soft archives, but I'm a bit scared to use it .