Home DVD copying error

[ClayinCA]

I've been having problems making duplicates of some homemade DVDs. (The DVDs I'm trying to copy are not professional discs, but ones I've recorded myself on my Panasonic from old home movies - no copyright infringement here.) Anyway, I've been using DVDShrink to burn the discs, and I've never had a problem with it until recently, when it's consistently stopped working once it gets to the point in the process when it starts burning the disc. I'm not sure if it's a problem with my external DVD writer (I have a Pacific Digital 16X external) or with the software.

Here is the full error message I get:

Windows XP 5.1
IA32
WinAspi: -
ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.56, size=163910 bytes, created 4/2/2003 8:13:44 AM
Nero API version: 6.0.0.0
Using interface version: 6.0.0.0
Installed in: C:\Program Files\Ahead\Nero\
Application: ahead\Nero - Burning Rom
Recorder: <TOSHIBA CD/DVDW SD-R5372>Version: TU53 - HA 2 TA 3 - 6.0.0.0
Adapter driver: <> HA 2
Drive buffer : 2048kB
Bus Type : via Inquiry data (1) -> ATAPI, detected: ?
Connected to MMC as unknown drive with class-nr : 1
Drive is autodetected - recorder class: Std. MMC recorder

=== Scsi-Device-Map ===
DiskPeripheral : ST380011A atapi Port 0 ID 0 DMA: On
CdRomPeripheral : PHILIPS DVD8421 atapi Port 1 ID 0 DMA: On
=======================

AutoRun : 1
Excluded drive IDs:
CmdQueuing : 1
CmdNotification: 2
WriteBufferSize: 73400320 (0) Byte
ShowDrvBufStat : 0
EraseSpeed : 0
BUFE : 0
Physical memory : 503MB (515568kB)
Free physical memory: 162MB (166472kB)
Memory in use : 67 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

17.8.2006
NeroAPI
10:04:36 PM #1 Phase 111 File APIProgress.cpp, Line 232
DVD-Video files sorted

10:04:37 PM #2 Text 0 File Reader.cpp, Line 118
Reader running

10:04:37 PM #3 Text 0 File Writer.cpp, Line 127
Writer TOSHIBA CD/DVDW SD-R5372 running

10:04:37 PM #4 ISO9660GEN -11 File geniso.cpp, Line 3814
First writeable address = 0 (0x00000000)

10:04:37 PM #5 ISO9660GEN -11 File geniso.cpp, Line 3814
First writeable address = 0 (0x00000000)

10:04:37 PM #6 Text 0 File Burncd.cpp, Line 3081
Turn on Disc-At-Once, using DVD media

10:04:37 PM #7 Text 0 File DlgWaitCD.cpp, Line 224
Last possible write address on media: 2298495 (510:46.45)
Last address to be written: 2286143 (508:01.68)

10:04:37 PM #8 Text 0 File DlgWaitCD.cpp, Line 229
Write in overburning mode: FALSE

10:04:37 PM #9 Text 0 File DlgWaitCD.cpp, Line 1688
Recorder: TOSHIBA CD/DVDW SD-R5372, Media type: DVD-R
Disc Manufacturer: SONY16 - D1
Disc Application Code: 64, Disc Physical Code: 193

10:04:37 PM #10 Text 0 File ThreadedTransferInterface.cpp, Line 757
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (CTransferItem)
2 indices, index0 (150) not provided
original CD pos #0 + 2286144 (2286144) = #2286144/508:1.69
relocatable, CD pos for caching/writing not required/required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2286144 blocks [TOSHIBA CD/DVDW SD-R5372]
--------------------------------------------------------------

10:04:37 PM #11 Text 0 File Burncd.cpp, Line 3318
Recorder and media-info

=======================

Burning to TOSHIBA CD/DVDW SD-R5372 on a DVD-R media

10:04:37 PM #12 Text 0 File ThreadedTransferInterface.cpp, Line 910
Prepare recorder TOSHIBA CD/DVDW SD-R5372 for write in cue-sheet-DAO
DAO infos:
==========
MCN:
TOCTYPE: 0x0 Session Closed, CD fixated
Tracks 1 to 1:
TRM_DATA_MODE1, 2048/0x0, ISRC "", FilePos 0 307200 387362816

10:04:38 PM #13 Phase 24 File APIProgress.cpp, Line 232
Caching of files started

10:04:38 PM #14 Phase 25 File APIProgress.cpp, Line 232
Caching of files completed

10:04:38 PM #15 Phase 36 File APIProgress.cpp, Line 232
Burn process started at 16.1x (22,218 KB/s)

10:04:38 PM #16 Text 0 File ThreadedTransferInterface.cpp, Line 2104
Verifying CD position of item 0 (relocatable, CD pos, no patch infos, orig at #0): write at #0

10:04:38 PM #17 Text 0 File DVDR.cpp, Line 1407
Recording mode: Sequential Recording Mode

10:04:38 PM #18 Text 0 File Mmc.cpp, Line 18119
Set BUFE: supported -> ON

10:04:38 PM #19 Text 0 File DVDR.cpp, Line 1522
Start write address at LBA 0
DVD high compatibility mode: Yes

10:04:38 PM #20 Text 0 File Cdrdrv.cpp, Line 7827
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-R (2), Part Version: 5
Disc Size: 120 mm, Maximum Rate: 10.08 Mbps (2 h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 30000 h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Media Specific:
60 00 10 20 30 40 50 00 - 00 00 21 00 00 00 00 00 `...0@P...!.....
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 ................

10:05:07 PM #21 SCSI -1135 File Cdrdrv.cpp, Line 1361
SCSI Exec, HA 2, TA 3, LUN 0, buffer 0x01520000
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x03 (KEY_MEDIUM_ERROR)
Sense Code: 0x0C
Sense Qual: 0x00
CDB Data: 0x2A 0x00 0x00 0x00 0x07 0x80 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0A
0x00 0x00 0x00 0x00 0x0C 0x00

10:05:07 PM #22 CDR -1135 File Writer.cpp, Line 335
Write error

10:05:07 PM #23 Text 0 File ThreadedTransfer.cpp, Line 227
all writers idle, stopping conversion

10:05:07 PM #24 Text 0 File ThreadedTransfer.cpp, Line 221
conversion idle, stopping reader

10:05:08 PM #25 Phase 38 File APIProgress.cpp, Line 232
Burn process failed at 16.1x (22,218 KB/s)


Existing drivers:
File 'Drivers\CDRALW2K.SYS': Ver=7.0.0.162 , size=24576 bytes, created 1/27/2004 2:32:00 PM
File 'Drivers\PXHELP20.SYS': Ver=2.02.72a, size=20368 bytes, created 4/22/2004 9:02:00 AM (Prassi/Veritas driver for win 2K)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

Does anybody have any words of advice for me? Is this software or hardware? Am I sunk?

[hech54]

I would try DVDDecrypter.
ISO Read mode
ISO Write Mode

[redwudz]

I see this 'KEY_MEDIUM_ERROR' which seems to point to the media, or the burner not accepting the media.

First try different DVD media. It doesn't appear to be a software error. It could be a problem with the burner, but the media is a lot easier to change.

Last thing to try if all else fails is to clean the laser lens, though that's not usually the error you would get.

[VegasBud]

ClayinCA,

redwudz is right. Your burner doesn't seem to like the media you're using. Did you recently change to a different type of blank disks (at about the time you started having problems)? If so, you can go back to the previous disks you were using.

Your firmware is also not the most recent. If you installed the latest version, maybe your burner would work with this media. It may have said Pacific Digital on the box, but Nero says the drive is a Toshiba SD-R5372. The updated firmware for that burner is available here.

If you haven't recently changed to a different media manufacturer, your drive may be failing. The atapi error code you're getting (030C00) is caused by:
1) Not in DMA mode.
Nero says the drive is in DMA, and even if Nero was wrong, a PIO mode burn failure wouldn' be at the very start of the burn.
2) Media problem.
Discussed above.
3) Drive problem.

[ClayinCA]

Vegasbud,

I don't *think* it can be the media - I've tried both Sony and Verbatim discs, both of which have worked in the past on this drive, and the current batch of Sonys worked for awhile and then started giving me trouble.

I actually hope it turns out to be the firmware - thanks for posting that link! - as it seems this will be the easiest problem to rectify.

Do you recommend trying to clean the laser lens, as redwudz suggested? I've always been a little hesitant to do that, as I've been told that most of the lens cleaners commerically available are not good for the burners.

Thanks again for all the help - I'm woefully undereducated in these things, and I need all the help I can get!

[redwudz]

and the current batch of Sonys worked for awhile and then started giving me trouble.

That doesn't seem to point to a firmware problem. Upgrading firmware comes with some risk of destroying your drive if you use the wrong upgrade file. And it may void your warranty if not a factory version. Not a big problem, but you need to be aware. But if there is a newer factory firmware upgrade, give it a try.

Most upgrades have to do with being able to use different or newer media or making the drive region free or similar. They are not really to fix problems with media that worked before and doesn't work now.

Media can change from batch to batch, sometimes even within the batch you are using. This is a good reason to stick with good brands. The name on the media is not always the manufacturer of the media. The media code will tell you who really made it. It's always better to try different brands of media first if you have a burning problem. Once you find what works well for you, stick with it.

Your problem sounds like a media or burner problem. You can purchase a cleaner disc and try that. DVD drives rarely need cleaning unless you are in a dusty environment or there is a lot of smoke in the air.

If all the above fails, consider replacing the burner.

[VegasBud]

ClayinCA,

More good advice from redwudz (and once again before me). I'm starting to feel like a backup singer.

hech54's suggestion to try different burning software is worth a shot, except I would recommend the new version of ImgBurn instead of DvdDecrypter. It's the latest version of the same burning engine. Since the log you provided shows that you're using -R media, you can even make it a "Test Mode" burn, and not risk making another coaster (just don't try a "Test Mode" burn with +R media). It doesn't cost you anything to give it a try, and would rule out a software problem being the source of the trouble. In case you're interested, in another thread redwudz gave this link to a version of DvdShrink that uses ImgBurn for the burning, instead of the NeroAPI.

Assuming changing software didn't help, if two different brands of media that you've previously had success with aren't working anymore, it's looking more and more like your burner is dying/dead. Since the link I gave you is to the latest version of the manufacturer's firmware, and you're running out of options, you might as well try the firmware update (just to be sure), but redwudz is right that firmware doesn't appear to be your problem.

Do you recommend trying to clean the laser lens, as redwudz suggested?

I've never personally had any success with that, but what the heck, if nothing else has fixed the problem, you're about one step away from shopping for a new drive anyways.

[ClayinCA]

Thanks a lot, guys. I am starting to think it probably is the drive, as I've also tried burning data discs on it, with similar problems. As a last ditch effort, I think I will try downloading the firmware forwhich Vegasbud provided the link, but I do have one last stupid question: if downloading the firmware doesn't do me any good, is there any danger of having it actually mess things up for me in the future (say, if I do have to replace the burner)?

Thanks again for all your help, guys - I really appreciate it!

[VegasBud]

...if downloading the firmware doesn't do me any good, is there any danger of having it actually mess things up for me in the future (say, if I do have to replace the burner)?

The only possible danger is to the drive itself, and since it's an official manufacturer upgrade, even that danger is negligible. The only way you could damage the drive with an official firmware update is if there was a power failure during the installation of the new firmware.

The new firmware resides in and only affects the drive, not the computer, so it will have no effect on a replacement drive.