And again...... I use both drives at the same time...... both are on the same IDE channel and I have made well over 1000 quality burns.
Chances are you are not burning on the fly. Clonedvd2, Shrink, etc., write to the hard drive first (unless you choose "write existing data" in Clonedvd2--but most people don't do this)--and then from the hard drive to your burner. When you're burning on the fly, you don't write everything to the hard drive first. If you're not burning on the fly, this issue is unlikely to affect you--much.
Write at 8x or higher while burning on the fly with the reader on the same ide channel as the writer; the buffer underrun protection of the writer will be engaged every 5-10 seconds. This tends to produce pretty bad quality scans, even if the burn is successful.
Yes
........every home built or store bought PC that I have ever seen is setup with both optical units on the same IDE channel
Not Falcon Northwest . . .
My parents were at one point living in the U.S. and were inquiring about who I thought were good system builders (they didn't mind paying the premium for a well built system with good parts, and I didn't want to have to ship and deal with out of country warranty issues). Falcon called them prior to building their system, and mentioned this exact issue on the Asus m/b they were using at the time (and recommended a good add-on board). My parents called me to ask if the person at Falcon was correct, and I said he was. The person who called them was a very smart system builder.
One simply should not put the destination and source device on the same ide channel--unless there is no other choice (and then you have to start compromising)
Edit: This really is, this time, my last post in this thread (unless something like spam or other moderator type stuff needs my attention here).