ImgBurn errors - Any help appreciated

vbimport

#1

Hello. I’ve burned many DVDs using my Acer laptop and never had a problem, no matter what media brand I picked. Now, when using my Acer Aspire 6920 running Vista Home Premium 64 bit with SP2, I am not able to burn onto any discs, including the TDK SL I’m trying right now. Detail is below. If anyone has suggestions, I’m listening. THANK YOU!

ImgBurn
I/O Error!

Device: [1:0:0] Slimtype DVD A DS8A1P CA14 (F:) (ATA)

ScsiStatus: 0x02
Interpretation: Check Condition

CDB: 2A 00 00 00 00 00 00 00 20 00
Interpretation: Write (10) - Sectors: 0 - 31

Sense Area: 70 00 05 00 00 00 00 0A 00 00 00 00 27 00 00 00 00 00
Interpretation: Write Protected

ImgBurn Log:
I 16:01:50 ImgBurn Version 2.5.1.0 started!
I 16:01:50 Microsoft Windows Vista Home Premium x64 Edition (6.0, Build 6002 : Service Pack 2)
I 16:01:50 Total Physical Memory: 4,183,548 KB - Available: 1,487,000 KB
W 16:01:50 Drive H:\ (FAT32) does not support single files > 4 GB in size.
I 16:01:50 Initialising SPTI…
I 16:01:50 Searching for SCSI / ATAPI devices…
I 16:01:50 -> Drive 1 - Info: Slimtype DVD A DS8A1P CA14 (F:) (ATA)
I 16:01:50 Found 1 DVD±RW/RAM!
I 16:02:36 Operation Started!
I 16:02:36 Source File: E:\DVD_Image.iso
I 16:02:36 Source File Sectors: 1,488,535 (MODE1/2048)
I 16:02:36 Source File Size: 3,048,519,680 bytes
I 16:02:36 Source File Volume Identifier: DVD
I 16:02:36 Source File Volume Set Identifier: 4BA6EE9F00000231
I 16:02:36 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR © 1993 E.YOUNGDALE © 1997 J.PEARSON/J.SCHILLING
I 16:02:36 Source File Implementation Identifier: mkisofs
I 16:02:36 Source File File System(s): ISO9660, UDF (1.02)
I 16:02:36 Destination Device: [1:0:0] Slimtype DVD A DS8A1P CA14 (F:) (ATA)
I 16:02:36 Destination Media Type: DVD+R (Disc ID: RITEK-F16-01) (Speeds: 2.4x)
I 16:02:36 Destination Media Sectors: 2,295,104
I 16:02:36 Write Mode: DVD
I 16:02:36 Write Type: DAO
I 16:02:36 Write Speed: MAX
I 16:02:36 DVD+R Reserve Track: No
I 16:02:36 Link Size: Auto
I 16:02:36 Lock Volume: Yes
I 16:02:36 Test Mode: No
I 16:02:36 OPC: No
I 16:02:36 BURN-Proof: Enabled
I 16:02:36 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x)
I 16:02:36 Book Type Setting: N/A
I 16:02:36 Advanced Settings - Force HT: N/A, Online HT: N/A, OverSpeed: N/A, SmartBurn: Yes
I 16:02:36 Filling Buffer… (40 MB)
I 16:02:38 Writing LeadIn…
W 16:02:38 Failed to Write Sectors 0 - 31 - Reason: Write Protected
W 16:02:38 Retrying (1 of 20)…
W 16:02:38 Retry Failed - Reason: Write Protected
W 16:02:38 Retrying (2 of 20)…
W 16:02:38 Retry Failed - Reason: Write Protected
W 16:02:38 Retrying (3 of 20)…
W 16:02:38 Retry Failed - Reason: Write Protected
W 16:02:38 Retrying (4 of 20)…
W 16:02:38 Retry Failed - Reason: Write Protected
W 16:02:38 Retrying (5 of 20)…
W 16:02:38 Retry Failed - Reason: Write Protected
W 16:02:38 Retrying (6 of 20)…
W 16:02:38 Retry Failed - Reason: Write Protected
W 16:02:38 Retrying (7 of 20)…
W 16:02:38 Retry Failed - Reason: Write Protected
W 16:02:38 Retrying (8 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (9 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (10 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (11 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (12 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (13 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (14 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (15 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (16 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (17 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (18 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (19 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
W 16:02:39 Retrying (20 of 20)…
W 16:02:39 Retry Failed - Reason: Write Protected
E 16:06:16 Failed to Write Sectors 0 - 31 - Reason: Write Protected
I 16:06:16 Synchronising Cache…
W 16:06:19 User opted to skip the ‘Close Track/Session/Disc’ functions.
E 16:06:19 Failed to Write Image!
E 16:06:19 Operation Failed! - Duration: 00:03:43
I 16:06:19 Average Write Rate: N/A - Maximum Write Rate: N/A


#2

Your drive doesn’t support these disks. This is a mismatch between drive/current firmware and the Ritek-F16 disks you are trying to burn.

I suggest buying Verbatim 16x disks and burning at 6x if that is allowed in ImgBurn. When buying Verbatim these days, it is best to get the ones with AZO on the label…I don’t trust the newer “Life Series” yet, since they are simply CMC Magnetics disks.

An alternative media that should work very well is Taiyo Yuden 8x +R disks found online at sites like rima.com and supermediastore.com
A third choice would be Sony disks found locally.


#3

[QUOTE=Kerry56;2523244]Your drive doesn’t support these disks. This is a mismatch between drive/current firmware and the Ritek-F16 disks you are trying to burn.

I suggest buying Verbatim 16x disks and burning at 6x if that is allowed in ImgBurn. When buying Verbatim these days, it is best to get the ones with AZO on the label…I don’t trust the newer “Life Series” yet, since they are simply CMC Magnetics disks.

An alternative media that should work very well is Taiyo Yuden 8x +R disks found online at sites like rima.com and supermediastore.com
A third choice would be Sony disks found locally.[/QUOTE]

Thanks for the input. I’ll give these discs away and buy the ones you recommended. However, I have a follow-up question: why would a drive reject a certain brand? I’ve used many different brands before and never had a problem. Now two different brands are doing this to me. My drive is supposed to support any -R or +R discs and these are TDK DVD+Rs, so why would there be a problem?


#4

All dvd drives have a list of known disk types and individual manufacturer identification codes (mid codes). This list is contained in the firmware of the drive and tells it what kind of disk it is looking at…a cd vs a DVD-R vs a DVD+RW…etc. The firmware also gives the drive a specific burning strategy that is appropriate for each individual mid code. So, the way it burns a Verbatim MCC004 mid code may be quite different from a Taiyo Yuden 000T02 mid code.

The problems begin when the drive does not recognize the disks properly. New mid codes appear over time, and if they are not included in the firmware of the drive, it will revert to a generic burning strategy that might produce poor results, or may not burn at all. Manufacturers are not particularly good about sending out new firmware for older drives, so after a couple of years you probably won’t see new firmware for any drive you buy (there are a few exceptions).

TDK has been going downhill for quite some time, and they have been purchasing poor to medium grade dvds to sell under their label. These that are failing in your drive are made by the Ritek Corp, which is one of the two largest manufacturers of blank media in the world. They are also one of my least favorites for blank dvds. Their cds are quite good.

Hope that answers the question you had.

If the drive will not burn Verbatim 16x at a moderate speed, or Sony brand dvds, then suspicion starts to fall on the drive itself failing.