I/O device error, then works like normal

[Anesred]

I burned a few audio CD's, and everytime I was making a new .cue file, the first time burning the file I was getting an I/O device error, which ruined a perfectly good disk. When I put another disk in, it worked like normal. Any idea why is it happening?

[LIGHTNING UK!]

If it was perfectly good, your drive wouldn't have errored out

 

If you post the log from that burn session, we'll be able to tell you more.

[RobRoy]

If it was perfectly good, your drive wouldn't have errored out

 

If you post the log from that burn session, we'll be able to tell you more.

Seems like that's your answer for everything.   It's never the application.   Bare in mind, you haven't updated the application in over 3 years!  So don't you think it's possible that your code may need a bit of tweaking?

[LIGHTNING UK!]

Yes, it pretty much is my answer for everything... and 99% of the time, it's the correct answer.

 

Optical drives conform to a standard. That standard hasn't changed and therefore programs don't need to either.

 

The program actually does very little beside just send the data to the drive. All the technical stuff is done by the drive and its firmware. If it can't write to a certain bit (sector or whatever) on the disc, that's totally out of my hands. It's a hardware (be it the drive or the media) issue.

 

If you'd like me to take a look at the log for your specific case, I'm happy to do so.