Major Burning Problems- Burn Won't Start, And Creator 2009 Doesn't Recognize Disc In Optical Drive.

[phxskyguy]

Over the last several years I've burned dozens of DVD-R discs using EMC-7. For my recent project of a vacation, I've completed my editing, made my movie and created my DVD which successfully burned as an ISO file all using EMC7. When I tried to burn the ISO file to disc, the Disc Copier program wouldn't recognize the blank DVD-R in the drive. It did only on 3 attempts out of about 50. On those 3 attempts the table of contents was written and then it would stop; showing an error and canceling the operation. I checked my firmware and drivers and everything is current. Finding that WMP 10 and IE7 cause problems with EMC7 I removed them from my computer, but was unable to get WMP9 as it's no longer available. Thinking technology has surpassed my ability to use EMC7, I went out and got Creator 2009. It installed with some difficulty, but was fixed with an update. My ISO file is still ready to be burned but the same thing happens with Creator 2009- When I use the Video Copy Control everything gets set up and then Creator won't recognize the blank DVD-R in the drive. I've been at it for 2 days and am at my wit's end. I'm considering going out to replace my optical drive. I've tried as many "fix solutions" as I've been able according to what's posted in this forum. Is my drive just too tired? All the firmware and drivers are current. When the disc is inserted, the drive indicator light will shine for 10-20 seconds then go out. It never spins up ready to burn and the highlight buttons to "burn" on the Program don't highlight leaving me unable to burn my project. What's even more confusing is that the optical drive (Sony RW DRU 530A) will burn a CD with no problem as well as read discs and install software from discs with no problem at all. Now what? Time for a new DVD-Drive? Just spent a bunch on Creator 2009. I'm using Windows XP on a 6 year old computer (HP) but it's been updated with additional RAM, video card and additional hard drive. Speed is a little slow these days at 1 Ghz but it should do the trick. Any suggestions would really help. I need to make 5 of these DVD's and wanted them done yesterday! Since both EMC-7 and Creator 2009 are not recognizing the blank discs in my drive I'm thinking the problem to fixed is the same regardless of the program I use. But what exactly is the problem?

[Brendon]

You're welcome.

You're welcome.

You're Welcome.

 

Brendon

[Brendon]

Phxskyguy,

 

When you put a blank disc into a burner a program [firmware] in the burner spins the disc up and tries to read it. Once it recognizes the disc, the drive "comes ready" and signals the computer that it's ready to go.

 

If something is wrong with the drive - dirty lens, insensitive photodiode, ageing electronics with values drifting out of spec, mechanical wear or failure - then the drive can't recognize that there's a blank disc in there, and can't "come ready".

 

If the drive doesn't show ready, then there's no way for the software to know that there's a blank disc in position and nothing is going to happen.

 

There are two optical systems in a DVD burner. One for CDs and one for DVDs. It is rare for both systems to drop out simultaneously as the drive reaches end-of-life, so it is common at that point to still be able to burn CDs when DVDs aren't working or vice-versa.

 

I think this is what has happened with your drive, and I think it has reached the point where it is just too tired. That would explain all the behaviour you've described.

 

New drives are inexpensive at the moment, and Cdanteek was talking of one available from NewEgg for only about $22 I think. And it is a very good model with excellent reviews. I can't find that post at the moment, but he could point you in the right direction. I'll ask him.

 

 

 

 

[phxskyguy]

Phxskyguy,

 

When you put a blank disc into a burner a program [firmware] in the burner spins the disc up and tries to read it. Once it recognizes the disc, the drive "comes ready" and signals the computer that it's ready to go.

 

If something is wrong with the drive - dirty lens, insensitive photodiode, ageing electronics with values drifting out of spec, mechanical wear or failure - then the drive can't recognize that there's a blank disc in there, and can't "come ready".

 

If the drive doesn't show ready, then there's no way for the software to know that there's a blank disc in position and nothing is going to happen.

 

There are two optical systems in a DVD burner. One for CDs and one for DVDs. It is rare for both systems to drop out simultaneously as the drive reaches end-of-life, so it is common at that point to still be able to burn CDs when DVDs aren't working or vice-versa.

 

I think this is what has happened with your drive, and I think it has reached the point where it is just too tired. That would explain all the behaviour you've described.

 

New drives are inexpensive at the moment, and Cdanteek was talking of one available from NewEgg for only about $22 I think. And it is a very good model with excellent reviews. I can't find that post at the moment, but he could point you in the right direction. I'll ask him.

Thanks for that. I suspected that may be the case but wasn't sure. The last batch of DVD's I made 14 months ago started with the same issue but then- whamo!-- they burned with no propblem. I'll replace the drive, keep my fingers crossed and see what happens.

[Brendon]

You could try a lens cleaner first in case there is grunge on the objective lens, but they have mixed results. Good luck with that.

 

I checked with Cdanteek, but he pointed out that the new drive I mentioned has a SATA interface, and with a 6 yr old computer at 1 GHz you'd be needing an IDE burner. Still, it's a buyer's market at the moment and drives are cheap.

 

Regards,

Brendon

[phxskyguy]

Got a new burner, installed it and it worked like a charm (sort of). DVD looks great but the audio is about a 1/2 second ahead of the video. I'll see if I can find a solution for that. The major problem has been fixed. Thanks!