Jump to content
Sign in to follow this  
Peter HB

CD Size Error

Recommended Posts

Using ImgBurn 2.5.1.0 with Windows 7 Home Premium (64 bit) to burn an ISO file, the operation fails because of incorrectly sensed disk capacity, details pasted below. NB Windows CD Burner burns the ISO correctly.

 

Optiarc DVD RW AD-7200A 1.06 (ATA)

Current Profile: CD-R

 

Disc Information:

Status: Empty

State of Last Session: Empty

Erasable: No

Free Sectors: 250,320

Free Space: 512,655,360 bytes

Free Time: 55:39:45 (MM:SS:FF)

Next Writable Address: 0

Supported Write Speeds: 8x, 16x, 24x, 32x, 40x, 48x

 

ATIP Information:

Disc ID: 97m34s23f

Manufacturer: Mitsubishi Chemical Corp.

Start Time of LeadIn: 97m34s23f

Last Possible Start Time of LeadOut: 79m59s73f

 

Performance (Write Speed):

Descriptor 1...

-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 359848 (0x00057DA8)

-> RS: 1,764 KB/s (10x) - WS: 1,411 KB/s (8x)

Descriptor 2...

-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 359848 (0x00057DA8)

-> RS: 3,528 KB/s (20x) - WS: 2,822 KB/s (16x)

Descriptor 3...

-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 359848 (0x00057DA8)

-> RS: 7,056 KB/s (40x) - WS: 4,234 KB/s (24x)

Descriptor 4...

-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 359848 (0x00057DA8)

-> RS: 7,056 KB/s (40x) - WS: 5,645 KB/s (32x)

Descriptor 5...

-> B0: 0x03, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 359848 (0x00057DA8)

-> RS: 7,056 KB/s (40x) - WS: 7,056 KB/s (40x)

Descriptor 6...

-> B0: 0x03, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 359848 (0x00057DA8)

-> RS: 8,467 KB/s (48x) - WS: 8,467 KB/s (48x)

 

 

Peter HB

Share this post


Link to post
Share on other sites

If it fails, post the log too.

Log files attached. The problem appears to be Win 7 related, as I re-ran the ISO burn attempt on an old Win2K machine with an identical drive (and firmware revision) and the correct CD size was detected, as evidenced in "Win2K_disk-info.txt".

 

Also I re-ran the test against another DVD-RW drive (Sony AW-G170A 1.71) in my Win 7 machine and it failed in a similar manner.

 

Anything further I can add, or do please ask.

 

Peter HB

Win2K_ImgBurn.log

Win2K_Disk-info.txt

Win7_ImgBurn.log

Share this post


Link to post
Share on other sites

I was hoping for a log of something actually failing :)

 

At the moment, the worst thing I can see happening is that the program would say your image is too big to fit on the disc and you'd have to just tell it to continue anyway.

 

Do please try again once you've done the 1.09 firmware update.

 

The values displayed within the program are what the drive has reported so there's nothing I can do about it. If you've got some rogue driver installed that's messing with the info before it reaches ImgBurn then that's out of my hands too. The OS makes no difference to the program, an MMC command is an MMC command, it doesn't matter which OS it's issued under.

 

Your two drives are very similar (Optiarc 7170 and a 7200) so it wouldn't be unheard of for them to share an issue.

Share this post


Link to post
Share on other sites

I was hoping for a log of something actually failing :)

 

At the moment, the worst thing I can see happening is that the program would say your image is too big to fit on the disc and you'd have to just tell it to continue anyway.

 

Do please try again once you've done the 1.09 firmware update.

 

The values displayed within the program are what the drive has reported so there's nothing I can do about it. If you've got some rogue driver installed that's messing with the info before it reaches ImgBurn then that's out of my hands too. The OS makes no difference to the program, an MMC command is an MMC command, it doesn't matter which OS it's issued under.

 

Your two drives are very similar (Optiarc 7170 and a 7200) so it wouldn't be unheard of for them to share an issue.

OK I performed the firmware update and still obtain the same symptoms, but I accepted your suggestion to proceed with the burn and it went to a successful completion (log attached). I accept your word that the problem is 'upstream' of ImgBurn, but I can't see the drive reporting an incorrect value, more likely it is a Redmond introduced error somewhere in the software stack through which you gain drive access? If it was the drive then I would expect similar symptoms from the identical drive in my Win2K machine, given that they were purchased at the same time from the same source.

 

Anyway the problem doesn't stop me burning ISOs so I'm happy to let this go unless you have an interest in tracking the source of the bug. If you do I'm at your disposal as a test bed.

 

Many thanks for your help.

 

Peter HB

Win7_ImgBurn(2).log

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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