Coaster burning Nemo R1 with ImgBurn v1.1

[Amit]

Hi,

I tried to burn Finding Nemo R1 NTSC (ripped using DVD Dec v3.5.4) on a Verbatim DVD+R DL at 2.4x speed using BenQ 1620 with the latest firmware and all I got was a $5 coaster.

Here's the log of the burn process


I 22:21:24 ImgBurn Version 1.1.0.0 started!
I 22:21:24 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 22:21:24 Initialising SPTI...
I 22:21:24 Searching for SCSI / ATAPI devices...
I 22:21:34 Found 1 CD-RW, 1 DVD-ROM and 1 DVD±RW!
I 22:22:36 Operation Started!
I 22:22:36 Source File: F:\Finding Nemo.MDS
I 22:22:36 Source File Sectors: 4,013,234 (MODE1/2048)
I 22:22:36 Source File Size: 8,219,103,232 bytes
I 22:22:36 Destination Device: [0:1:0] BENQ DVD DD DW1620 B7W9 (G:) (ATA)
I 22:22:36 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x)
I 22:22:37 Destination Media Sectors: 4,173,824
I 22:22:37 Write Mode: DVD
I 22:22:37 Write Type: DAO
I 22:22:37 Write Speed: 2.4x
I 22:22:37 Link Size: Auto
I 22:22:37 Test Mode: No
I 22:22:37 BURN-Proof: Enabled
I 22:22:37 Optimal L0 Data Zone Capacity: 2,034,304
I 22:22:37 Optimal L0 Data Zone Method: Copied From Original Disc
I 22:22:37 Filling Buffer...
I 22:22:38 Writing LeadIn...
I 22:22:47 Writing Image...
I 22:22:47 Writing Layer 0... (LBA: 0 - 2034303)
W 22:22:52 Failed to Write Sectors 7136 - 7167 - Write Error
W 22:22:52 Retrying (1 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (2 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (3 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (4 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (5 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (6 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (7 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (8 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (9 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (10 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (11 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (12 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (13 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (14 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (15 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (16 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (17 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (18 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (19 of 20)...
W 22:22:52 Retry Failed - Invalid Address For Write
W 22:22:52 Retrying (20 of 20)...
W 22:22:52 Retry Failed! - Invalid Address For Write
W 22:23:13 Retrying (21)...
W 22:23:13 Retry Failed! - Invalid Address For Write
W 22:23:14 Retrying (22)...
W 22:23:14 Retry Failed! - Invalid Address For Write
W 22:23:16 Retrying (23)...
W 22:23:16 Retry Failed! - Invalid Address For Write
W 22:23:19 Retrying (24)...
W 22:23:19 Retry Failed! - Invalid Address For Write
W 22:23:20 Retrying (25)...
W 22:23:20 Retry Failed! - Invalid Address For Write
W 22:23:21 Retrying (26)...
W 22:23:21 Retry Failed! - Invalid Address For Write
W 22:23:22 Retrying (27)...
W 22:23:22 Retry Failed! - Invalid Address For Write
W 22:23:22 Retrying (28)...
W 22:23:22 Retry Failed! - Invalid Address For Write
W 22:23:24 Retrying (29)...
W 22:23:24 Retry Failed! - Invalid Address For Write
W 22:23:25 Retrying (30)...
W 22:23:25 Retry Failed! - Invalid Address For Write
W 22:23:25 Retrying (31)...
W 22:23:25 Retry Failed! - Invalid Address For Write
W 22:23:26 Retrying (32)...
W 22:23:26 Retry Failed! - Invalid Address For Write
E 22:23:39 Failed to Write Sectors 7136 - 7167 - Write Error
I 22:23:39 Synchronising Cache...
I 22:23:40 Closing Track...
I 22:23:45 Finalising Disc...
E 23:08:24 Failed to Write Image!
E 23:08:24 Operation Failed! - Duration: 00:45:47
I 23:08:24 Average Write Rate: 274 KB/s (0.2x) - Maximum Write Rate: 3,081 KB/s (2.2x)

Here's the information about the burner and media

BENQ DVD DD DW1620 B7W9 (ATA)
Current Profile: DVD+R DL

Disc Information:
Status: Complete
Erasable: No
Sessions: 1
Sectors: 4,068,608
Size: 8,332,509,184 bytes
Time: 904:10:08 (MM:SS:FF)

DVD±R DL Boundary Information:
L0 Data Zone Capacity: 2,034,304
Changeable: No

Physical Format Information (ADIP):
Disc ID: MKM-001-00
Book Type: DVD+R DL
Part Version: 1
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 2
Track Path: Opposite Track Path (OTP)
Linear Density: 0.293 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 16,580,607
Last Physical Sector in Layer 0: 2,283,519

Physical Format Information (Last Recorded):
Disc ID: MKM-001-00
Book Type: DVD-ROM
Part Version: 1
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 2
Track Path: Opposite Track Path (OTP)
Linear Density: 0.293 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 203,439
Last Physical Sector in Layer 0: 2,230,912

Layer Information:
Layer 0 Sectors: 2,034,305 (50%)
Layer 1 Sectors: 2,034,303 (50%)


-Amit

[LIGHTNING UK!]

It's helpful if you actually ask something in your post - otherwise, what sort of answer are you expecting?!

The error is pretty clear:

W 22:22:52 Failed to Write Sectors 7136 - 7167 - Write Error

So your drive failed to write those sectors on the disc and the reason it gave (all be it a pretty generic one) was 'Write Error'.

Maybe it was a duff disc or perhaps a spek of dirt caused the problem.

[Amit]

@LIGHTNING UK!,

I was expecting to find out from you if this error will occur again, if I try another disc? Will this kind of error be reported if I tried the TEST mode instead of WRITE/BURN mode? Also I wanted to know, if the error happened because there was a problem with the ISO image? A write error means the program failed to write but I am not sure whether it was not able to read the ISO image properly or it means error writing physically on the disc?

Lastly when burning an image with ImgBurn, which results in better image ; choosing the MDS file; OR choosing the ISO file?

Thanks in advance for replying to this post.

-Amit

[LIGHTNING UK!]

Well obviously your drive should never fail to burn a disc. Of course that's just in an ideal world.

I (or my software) has no control over if it will fail on a second attempt or not - and so I will not say either way. It's up to you if you want to risk another $5 or not.

Let just get something clear though, the drive is failing to write, not the program. The software is only as good as the drive / media / firmware combination.

The actual image file you're burning has no effect on the burn or the likelyhood of it failing.

Using the MDS is better for double layer burns as it should contain the original layer break position - which can then be duplicated onto your DVD+R DL discs.
ImgBurn is pretty good at getting this info from the IFO files though, so even without it, you stand a pretty good chance of getting an identical copy.

Basically, it's just easier to always select the MDS file - just to be on the safe side.

[Amit]

@LIGHTNING UK!,

Thanks for your reply. I thing you forgot to reply was whether the TEST mode would have pointed an error like this (this way I could possible save a disc before its corrupted by a bad burn)? i.e. if I check both TEST and WRITE option and choose an MDS file to burn on DVD+R DL disc, will this kind of error be detected during the TEST mode and the burn process will be canceled because of an error?

One thing I noticed was that when the error occured (which happened in very quickly as the burn process started) I got the option to retry or cancel. I clicked the retry option couple of times but I kept on getting the same error. Fianlly I clicked cancel and the error went away but the programe kept on writing something to the disc as if it just skipped writing those sectors. It took about an error for the program to finish the burn (I was burning at 2.4x as that's the fastest my burner supports). Wouldn't it be nice to give the user an option to stop the rest of the burning or continue burning by skipping the error? This is just a request to save time when in future this kind of error happens for anyone out there.

-Amit

[LIGHTNING UK!]

Test mode on DVD+R (DL) is a BenQ specific feature.

The DVD+R standard does not allow for such a thing.

I cannot comment on how well it works, I've not used it enough.

I can't see how performing a test can find problems with media. After all, the drive isn't actually burning. I just see it as testing that the program logic is correct and that your hdd can keep up with the requested burn speed - and that's not really very important now that we have burnproof type technology.

Don't confuse ImgBurn with Nero. Ticking 'Test Mode' doesn't mean it will write after the test. Test mode is test mode. Untick it and it will actually burn.

Once you cancel a burn, the program stops attemping to write data to the disc. Period. You cannot ignore write errors.

The delay you're experiencing is from the program / drive performing the end of burn functions. i.e. sync cache, close track/session/disc etc. This is clearly shown in the log and in the status bar.

These operations are performed internally by the drive once the initial command has been issued by the software. It's basically a clean up process and once I consider important in that is stops the drive getting confused about what it's doing!

How long they take to complete depends on the drive and how it's manufacturer deals with them. They probably took longer on your machine because the drive was having trouble writing to the media.

btw, your drive says it can burn that verbitim media at 4x. Just look at the 'supported write speeds' info.

[Amit]

@LIGHTNING UK!,

Thanks for your input. I tried another disc to rule out any bad media problem and I was able to burn a perfect copy using ImgBurn v1.1.

NOTE: I did not try the TEST burn yet.

Thanks for all your help.

-Amit