The call StartService() fails when the driver is located in a shared
network drive or have a network drive mapped to a drive letter.

As an example, the DDK's sample exe for CANCEL and EVENT have this
issue. I can run them OK within my local drive, but when I place them
in a network shared drive (mapped to Z: drive), the call to
StartService() returns ERROR_PATH_NOT_FOUND. I called
QueryServiceStatusEx() and ControlService() with
SERVICE_CONTROL_INTERROGATE, and dwCurrentState always shows
ADS_SERVICE_STOPPED and not ADS_SERVICE_START_PENDING.

Can anyone help?

RE: Loading a driver from a mapped drive fails by pavel_a

pavel_a
Tue Nov 22 21:13:03 CST 2005

"nws_reader@yahoo.com" wrote:
> The call StartService() fails when the driver is located in a shared
> network drive or have a network drive mapped to a drive letter.

This is _by design_ so no help needed; all works as it should.
The driver loader runs under LocalSystem account, which has no access to
network.

--PA

> As an example, the DDK's sample exe for CANCEL and EVENT have this
> issue. I can run them OK within my local drive, but when I place them
> in a network shared drive (mapped to Z: drive), the call to
> StartService() returns ERROR_PATH_NOT_FOUND. I called
> QueryServiceStatusEx() and ControlService() with
> SERVICE_CONTROL_INTERROGATE, and dwCurrentState always shows
> ADS_SERVICE_STOPPED and not ADS_SERVICE_START_PENDING.
>
> Can anyone help?
>
>