Jump to content

iso burn fails across multiple drives with multiple media


drolenc
 Share

Recommended Posts

I am using ImgBurn 2.3.2.0 and am having consistent failures burning iso images created by DVDShrink... I have tried this with different types of media and on different drives, all with no luck. My drives are both on latest firmware. The kicker is that these same files consistently burn successfully with other burning programs like Roxio Easy CD Creator. This leads me to believe that this may be an ImgBurn bug. I have included 3 logs for your viewing pleasure.

 

This one is from my Sony DVD burner using media type #1:

 

I 08:42:52 ImgBurn Version 2.3.2.0 started!

I 08:42:52 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4)

I 08:42:52 Total Physical Memory: 523,760 KB - Available: 265,676 KB

I 08:42:52 Initialising SPTI...

I 08:42:52 Searching for SCSI / ATAPI devices...

I 08:42:52 Found 2 DVD?RWs!

I 08:43:25 Operation Started!

I 08:43:25 Source File: G:\SS_1.ISO

I 08:43:25 Source File Sectors: 2,285,867 (MODE1/2048)

I 08:43:25 Source File Size: 4,681,455,616 bytes

I 08:43:25 Source File Volume Identifier: SS

I 08:43:25 Source File Implementation Identifier: DVD Shrink

I 08:43:25 Source File File System(s): ISO9660, UDF (1.02)

I 08:43:25 Destination Device: [0:1:0] TDK DVDRW0404N 1.0C (D:) (ATA)

I 08:43:25 Destination Media Type: DVD-R (Disc ID: MCC 02RG20) (Speeds: 2x, 4x)

I 08:43:25 Destination Media Sectors: 2,297,888

I 08:43:25 Write Mode: DVD

I 08:43:25 Write Type: DAO

I 08:43:25 Write Speed: MAX

I 08:43:25 Link Size: Auto

I 08:43:25 Test Mode: No

I 08:43:25 BURN-Proof: Enabled

I 08:43:26 Filling Buffer... (20 MB)

I 08:43:27 Writing LeadIn...

I 08:43:59 Writing Image... (LBA: 0 - 2285866)

W 08:47:11 Failed to Write Sectors 6624 - 6655 - Cannot Write Medium - Incompatible Format

W 08:47:11 Retrying (1 of 20)...

W 08:47:11 Retry Failed - Cannot Write Medium - Incompatible Format

...

W 08:47:11 Retrying (20 of 20)...

W 08:47:11 Retry Failed - Cannot Write Medium - Incompatible Format

E 08:47:19 Failed to Write Sectors 6624 - 6655 - Cannot Write Medium - Incompatible Format

I 08:47:19 Synchronising Cache...

E 08:47:20 Failed to Write Image!

E 08:47:20 Operation Failed! - Duration: 00:03:55

I 08:47:20 Average Write Rate: 66 KB/s (0.0x) - Maximum Write Rate: 66 KB/s (0.0x)

 

This one is from my TDK DVD burner using media type #1:

 

I 08:53:21 ImgBurn Version 2.3.2.0 started!

I 08:53:21 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4)

I 08:53:21 Total Physical Memory: 523,760 KB - Available: 261,416 KB

I 08:53:21 Initialising SPTI...

I 08:53:21 Searching for SCSI / ATAPI devices...

I 08:53:21 Found 2 DVD?RWs!

I 08:54:22 Operation Started!

I 08:54:22 Source File: G:\SS_1.ISO

I 08:54:22 Source File Sectors: 2,285,867 (MODE1/2048)

I 08:54:22 Source File Size: 4,681,455,616 bytes

I 08:54:22 Source File Volume Identifier: SS

I 08:54:22 Source File Implementation Identifier: DVD Shrink

I 08:54:22 Source File File System(s): ISO9660, UDF (1.02)

I 08:54:23 Destination Device: [0:1:0] TDK DVDRW0404N 1.0C (D:) (ATA)

I 08:54:23 Destination Media Type: DVD-R (Disc ID: MCC 02RG20) (Speeds: 2x, 4x)

I 08:54:23 Destination Media Sectors: 2,297,888

I 08:54:23 Write Mode: DVD

I 08:54:23 Write Type: DAO

I 08:54:23 Write Speed: MAX

I 08:54:23 Link Size: Auto

I 08:54:23 Test Mode: No

I 08:54:23 BURN-Proof: Enabled

I 08:54:23 Filling Buffer... (20 MB)

I 08:54:23 Writing LeadIn...

W 08:58:07 Failed to Write Sectors 32 - 63 - Cannot Write Medium - Incompatible Format

W 08:58:07 Retrying (1 of 20)...

...

W 08:58:07 Retrying (20 of 20)...

W 08:58:07 Retry Failed - Cannot Write Medium - Incompatible Format

E 08:58:09 Failed to Write Sectors 32 - 63 - Cannot Write Medium - Incompatible Format

I 08:58:09 Synchronising Cache...

E 08:58:10 Failed to Write Image!

E 08:58:10 Operation Failed! - Duration: 00:03:47

I 08:58:10 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)

 

This one is from my Sony DVD burner using media type #2:

 

I 08:48:41 ImgBurn Version 2.3.2.0 started!

I 08:48:41 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4)

I 08:48:41 Total Physical Memory: 523,760 KB - Available: 263,028 KB

I 08:48:41 Initialising SPTI...

I 08:48:41 Searching for SCSI / ATAPI devices...

I 08:48:52 Found 2 DVD?RWs!

I 08:49:03 Operation Started!

I 08:49:03 Source File: G:\SS_1.ISO

I 08:49:03 Source File Sectors: 2,285,867 (MODE1/2048)

I 08:49:03 Source File Size: 4,681,455,616 bytes

I 08:49:03 Source File Volume Identifier: SS

I 08:49:03 Source File Implementation Identifier: DVD Shrink

I 08:49:03 Source File File System(s): ISO9660, UDF (1.02)

I 08:49:03 Destination Device: [1:0:0] SONY DVD RW DRU-710A BYX5 (E:) (ATA)

I 08:49:03 Destination Media Type: DVD-R (Disc ID: SONY16D1) (Speeds: 4x, 6x, 8x)

I 08:49:03 Destination Media Sectors: 2,297,888

I 08:49:03 Write Mode: DVD

I 08:49:03 Write Type: DAO

I 08:49:03 Write Speed: MAX

I 08:49:03 Link Size: Auto

I 08:49:03 Test Mode: No

I 08:49:03 BURN-Proof: Enabled

I 08:49:03 Filling Buffer... (20 MB)

I 08:49:04 Writing LeadIn...

I 08:50:21 Writing Image... (LBA: 0 - 2285866)

W 08:52:25 Failed to Write Sectors 1056 - 1087 - Cannot Write Medium - Incompatible Format

W 08:52:25 Retrying (1 of 20)...

...

W 08:52:25 Retrying (20 of 20)...

W 08:52:25 Retry Failed - Cannot Write Medium - Incompatible Format

E 08:52:27 Failed to Write Sectors 1056 - 1087 - Cannot Write Medium - Incompatible Format

I 08:52:27 Synchronising Cache...

E 08:52:28 Failed to Write Image!

E 08:52:28 Operation Failed! - Duration: 00:03:24

I 08:52:28 Average Write Rate: 16 KB/s (0.0x) - Maximum Write Rate: 16 KB/s (0.0x)

 

Again, these consistently fail with ImgBurn, and succeed with Roxio. Any help would be aprreciated. I have searched the forums for similar problems but have always come up with people blaming the media. I would concur given the error message, but why would Roxio succeed then? The burnt discs always seem to end at about the same location, no matter the image file (i.e. if I physically look at the disks the burnt part looks to be about the same across the failures)

Link to comment
Share on other sites

  • 2 weeks later...

Your Sony drive does not like that media. The TDK writer likes them even less.

 

Those drives are surely getting on a bit.

 

Maybe time to buy a newer model or look for some decent 4x media.

 

 

Would still be worth looking into dma issues though. Eg removing the controller as per the FAQ

Link to comment
Share on other sites

And they are not all failing at the exact same spot from your log:

 

W 08:47:11 Failed to Write Sectors 6624 - 6655 - Cannot Write Medium - Incompatible Format

W 08:58:07 Failed to Write Sectors 32 - 63 - Cannot Write Medium - Incompatible Format

W 08:52:25 Failed to Write Sectors 1056 - 1087 - Cannot Write Medium - Incompatible Format

 

I would concur that your drive and that media is not a happy combination.

Link to comment
Share on other sites

  • 2 weeks later...

Did you catch that this works with Roxio consistently? My DMA is on, and I am using 2 different batches of media. I have a really hard time blaming the media or the drives on this one, since simply using a different software program succeeds every time.

 

 

Welcome to ImgBurn Forum

 

You might have a bad batch of disks. Try burning slower. Is your DMA on?

 

Regards

Edited by drolenc
Link to comment
Share on other sites

use that then and whilst your at it buy some better/ newer drives

 

 

Did you catch that this works with Roxio consistently? My DMA is on, and I am using 2 different batches of media. I have a really hard time blaming the media or the drives on this one, since simply using a different software program succeeds every time.

 

 

you answer yourself so you have solved it.

Link to comment
Share on other sites

If I wanted to use Roxio, I would not be posting here in the interest of fixing the bug for the benefit of the community. If someone is willing to entrust me with the ImgBurn source code, I could fix it, but it is likely that will not happen. The fact that Roxio does work with these exact drives and the exact media with which I am having problems using ImgBurn does seem to place the problem clearly with something ImgBurn is doing or not doing. It is easy to read logs and say that it is a media problem or that my drives don't like the media. If that were true Roxio would fail as well. Software burning apps can't fix crappy media or media and drive incompatability, so please stop blaming the media. I will try toggling DMA this evening to see if that's causing an issue, but I will be very disappointed if it is.

 

use that then and whilst your at it buy some better/ newer drives

 

 

Did you catch that this works with Roxio consistently? My DMA is on, and I am using 2 different batches of media. I have a really hard time blaming the media or the drives on this one, since simply using a different software program succeeds every time.

 

 

you answer yourself so you have solved it.

Edited by drolenc
Link to comment
Share on other sites

It's the drive that's erroring out here, just remember that.

 

Drives have bugs too, ImgBurn might just be doing something that causes it to rise to the surface.

 

All the software is doing for the entire burn is sending data, repeating the 'Write (10)' command over and over again.

 

There is no reason for it to fail, it just is and it's out of my hands.

 

Also, Roxio might not be using DAO for burning, it might be using the Packet / Incremental write type. Try switching to use that instead. Again, there's no reason for that to work either really but firmware bugs could mean that it does.

Link to comment
Share on other sites

I understand that drives can have problems too, but it is unlikely that the same problem would persist across 2 drives by different manufacturers with different firmware. I have gone through the trouble of trying to isolate the problem logically, to see if anyone had any ideas. As a developer I know all of the layers involved, and have isolated it to ImgBurn. Not necessarily the app itself, but perhaps something it is doing or not doing that may be causing this behavior. Surely you can see that the likelihood of it being a media or drive problem is slim, given that I have tested using 2 different drives with 2 different media types with the only difference being the burning software. Roxio does use DAO, and has never failed in my tests. In my opinion, that largely eliminates the OS, drive, firmware and media from the suspect list. I do realize that it may be something that ImgBurn does that Roxio doesn't do that is the root of the problem. That problem would likely be in the OS layer if it's not in ImgBurn. It doesn't make sense that it would be a firmware bug in the drive, unless TDK and Sony share code and have been equally lazy in fixing their stuff. Even if the problem is the OS, it should still be hunted down (for selfish reasons :thumbup:) I will give your suggestion a try for the incremental/packet write and report my findings. Do you have any more ideas that I could try?

 

Thanks

 

 

It's the drive that's erroring out here, just remember that.

 

Drives have bugs too, ImgBurn might just be doing something that causes it to rise to the surface.

 

All the software is doing for the entire burn is sending data, repeating the 'Write (10)' command over and over again.

 

There is no reason for it to fail, it just is and it's out of my hands.

 

Also, Roxio might not be using DAO for burning, it might be using the Packet / Incremental write type. Try switching to use that instead. Again, there's no reason for that to work either really but firmware bugs could mean that it does.

Edited by drolenc
Link to comment
Share on other sites

It looks like changing the write type to incremental allowed me to successfully write images using both drives and both media types. That seems to indicate that there is a problem in the DAO code path.

Link to comment
Share on other sites

No, there's a problem with your drive! (or somewhere else in the system)

 

The difference between Packet mode and DAO is simply a flag (a few bits in a byte) for the 'set write parameters' command.

 

Other than that they're pretty much identical.

 

Again, once the write has started, the 'Write (10)' command is just repeated over and over again (that's the same for packet / dao - they use the exact same lines of code within ImgBurn). That is the ONLY code running when your drive is erroring out - and it's only erroring out when the drive is supposed to be writing DAO style.

 

I'm not messing you about here, if I thought for 1 second that something was wrong, I'd look into it and fix it. Seeing as how it works perfectly for all 6 of the drives I have in my PC (not to mention all those used by the beta team), and under every OS starting with Windows 95, I have to conclude that the issue is with your setup. Sorry.

Link to comment
Share on other sites

Thanks for all your help. It may very well be something with my setup, I was simply stating that with my setup there is a problem in the DAO code path (it doesn't work!) I am just giving you a data point. There may be something there or not. It may just be something bad in the OS. I just think that the chances of it being something with the drives or OS is possible, but not probable, since it is unlikely that the same problem exists with 2 drives by different manufacturers and DAO works using another popular burning software. I assume Roxio should do the same sort of things you are doing for DAO, since it is fundementally just a bunch of writes and setup ioctls. Their's works, yours doesn't. That would certainly annoy me and grab my attention as an application developer! Could it be something stupid like a write buffer size choice for the writes? Or alignment of the buffer? Could it be something about the ISO image created by DVDShrink? Are there any other subtle differences between DAO and incremental that may be causing this? I really like ImgBurn due to its rich feature set and am very pleased to have it working using incremental writes.

 

 

No, there's a problem with your drive! (or somewhere else in the system)

 

The difference between Packet mode and DAO is simply a flag (a few bits in a byte) for the 'set write parameters' command.

 

Other than that they're pretty much identical.

 

Again, once the write has started, the 'Write (10)' command is just repeated over and over again (that's the same for packet / dao - they use the exact same lines of code within ImgBurn). That is the ONLY code running when your drive is erroring out - and it's only erroring out when the drive is supposed to be writing DAO style.

 

I'm not messing you about here, if I thought for 1 second that something was wrong, I'd look into it and fix it. Seeing as how it works perfectly for all 6 of the drives I have in my PC (not to mention all those used by the beta team), and under every OS starting with Windows 95, I have to conclude that the issue is with your setup. Sorry.

Link to comment
Share on other sites

I don't let it not working on 1 PC bother me, no.

 

If it didn't work on my machines, fair enough, I'd look into it.

 

You have the option to play around with buffer sizes, transfer lengths, different I/O interfaces etc within the settings. Be my guest and have a mess around.

 

Do you actually know for certain that Roxio isn't also using the Incremental Write type?! Just because the log says it is doesn't mean it's telling the truth. You'd need to snoop on the I/O to know for sure.

Link to comment
Share on other sites

I've just taken a look at the 'RecordNow' program that's part of Roxio v9.

 

CMD	55 10 00 00  00 00 00 00  3c 00		MODE SELECT
OUT	00 3a 41 00  00 00 00 00  05 32 60 05  08 10 00 00  00 00 00 00  00 10 00 96  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

 

the 05 32 is the start of the 'Write Parameters' mode page I mentioned earlier.

 

The 3rd byte (60) is the one that specifies the 'Write Type' - well, the first 4 bits of it are.

 

As the first 4 bits of 0x60 are 0x00, that means the Write Type is being set to 0x00 - and 0x00 = Packet / Incremental.

 

So it would appear we have our answer.

 

Packet / Incremental works in ImgBurn and it's what Roxio appears to default to.

 

This can all be found / checked in the MMC specs from www.t10.org

Link to comment
Share on other sites

As the first 4 bits of 0x60 are 0x00, that means the Write Type is being set to 0x00 - and 0x00 = Packet / Incremental.

Erm, LUK : just seeking to understand here : to my big-endian brain 0x60 = bin(0110 0000) ..... is there a little-endian thing going on here, or something ? :unsure:

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

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