#1 Burning Software

Hi,

a user reported that my app does not detect any drives when run using the Windows task scheduler, except when a user is logged on. Log is attached. Any possible causes? Intentional? Technically impossible?

Regards,
Florian

With SPTI if somebody else (other burning app for example) had opened device handle with "no share" option drive is not going to be visible to anybody else. We'll simply fail to get access to it with error 32 (sharing violation) or error 5 (access denied, exacty your case) during enumeration sequence. So use SPTD or don't complain: OS storage stack is designed this way: "winner-takes-all".

***

CStarBurn_ScsiTransportSPTI::CStarBurn_ScsiTransportSPTI(): EXITing with failure, status 5, message 'CStarBurn_ScsiTransportSPTI::CStarBurn_ScsiTransportSPTI(): CreateFile( '\\.\E:', 0xc0000000, 3, 0x00000000, 3, 0, 0x00000000 ) failed, status 5 ( 0x5 )'

***

//
// MessageId: ERROR_ACCESS_DENIED
//
// MessageText:
//
// Access is denied.
//
#define ERROR_ACCESS_DENIED 5L

And what if I have a problem with SPTD? Who bothers to help me in this case? No one replied on my issue regarding a simple problem with the silent setup, and that clearly arouses the impression that I'll have to spend even more time dealing with people in order to get my app running.

We'll do.