#1 Burning Software

In "X", when I have a CD in the drive that cannot be detected for one reason or another, after a very long time...IMO...the application continues. I'm assuming this is some type of timeout function on CD detection. I'm wondering/hoping if you can make this timeout setting programmable because I would like to make it shorter.

If it hangs inside Win32 API call (like CreateFile) - we cannot.

Sorry, I don't/barely understand your response, and I don't think you fully understood my issue. When I have a bad CD and/or drive, after getting the drive object, my app is stalling on setting the drive for the grabber and burner and getting the discinfo. Is that a timeout feature you set up or is windows controlling that? Is there a way to change the timeout?
NOTE: When I say bad CD, I simply mean the drive is not reading it because the CD can be read elsewhere and it doesn't have any scratches on it.

Again, if the drive hangs during burner creation object (CreateFile hangs b/c of the broken TOC or partially readable media) we can do nothing to unblock the command.

I theory we can export command executions timeout to you. But it will bring more problems then real use.