OK, got an E-mail from Slysoft:
================================================================================================================
Dear Lance Summers,
Thank you for your e-mail.
If you are referring to blank media, AnyDVD is not involved at all in the burning process. It stays inactive when a blank disc is inserted.
Best regards,
Chris Gonzales
--
SlySoft Forum
http://forum.slysoft.com/
================================================================================================================
So you can see, the moderator did not fully read this thread. The problem is when a NON-Blank DVD is inserted and AnyDVD kicks in.
Which means the developers are not looking at the ERROR handling path of AnyDVD.
My own analysis (as shown above) points to the fact that the DVD drive generates a Disk-Changed error when a NON-Blank is inserted
that is no longer handled by Microsoft (with the removal of their DVD Player Support). Why this is an error I have no idea.
This Disk-Changed error is therefore passed to any utility that is in the drive handling chain (In this case, only AnyDVD is listed:
See Previous post). And since AnyDVD is not handling that error either, the drive reacts to the Disk-Changed error by ejecting the disk.
Another posibility is that this is a problem with the particular DVD drive??? One that is generating the error to begin with.
I will swap out the drive for an LG Blu-Ray drive to see if the same things happen.
Or maybe one of the updates to windows 10 will solve this problem, I don't know but since the problem is sporatic (not 100% of the time),
it is unlikely that my issue will be resolved any time soon.
I will post my results with the DVD drive swap. Lance