#1 Burning Software

I'm calling StarBurn_CdvdBurnerGrabber_TestUnitReady in a thread because it's extremely slow if the device isn't ready (20 seconds) which works fine except that I would like to be able to offer a "Cancel" button to the user.

I tried calling StarBurn_CdvdBurnerGrabber_Cancel in my UI (so not in the same thread that was calling StarBurn_CdvdBurnerGrabber_TestUnitReady) but that didn't seem to do anything.

Thanks!

There's no way to abort TestUnitReady(...) code however you have a choice of using TestUnitReadyEx(...) variant of the call. It has extra parameter - how many seconds to wait for combination "drive + disc" becoming ready.

If it would not be enough for you - we'll consider adding "abort" functionality to at least one of this API calls (they only "ping" device with 0x00 command in a loop so it's not a very big deal to do what you want).

Please let me know what do you think - which way would be preferred for you (we recommend startin from using Ex(...) variant of API call).

Is there a difference between calling TestUnitReadyEx(wait=20) and calling TestUnitReadyEx(wait=2) ten times? To put the question another way, are there drives that take 10 seconds to reply, so if I called TestUnitReadyEx(wait=2) ten times, I would always get EN_SCSI_CDB_FAILED, but if I called TestUnitReadyEx(wait=20) it would succeed?

So for me, if calling TestUnitReadyEx(wait=20) and calling TestUnitReadyEx(wait=2) ten times do exactly the same thing, I'm glad to do that; if not, some sort of Cancel would be helpful.

Thanks!

No difference! You can do what you've told!