I just got an error report from a tester for a very weird problem which I don’t really understand. I have an NDIS IM driver on Windows XP, based on the Passthrough example. I am able to replicate the problem in that if I install it through the normal means through the properties of a network connection, selecting to install a service, I subsequently lose the ability to burn CDs! I went through the System Events log, and what I find is that despite being set to Manual start, the IMAPI CD-Burning COM Service starts up when I reboot a system. However, when I install the NDIS IM, I see the following messages in the System log:
“The IMAPI CD-Burning COM Service service was successfully sent a start control.”
“The IMAPI CD-Burning COM Service service entered the running state.”
“The IMAPI CD-Burning COM Service service entered the stopped state.”
(and it is the only service of all the services which seem to be restarted by the installation which subsequently shuts down).
I’m not very experienced with the overall functioning of the Service Control Manager, so is there anyone who could explain where I go from here to get more verbose information about who’s sending the signals to start and stop this manual start service and/or thoughts on why this service won’t restart.
Much appreciated,
Jonas Sulk
MS LVP
I should maybe say too that whatever the problem is, it seems to be persistent in that if I reboot the machine, I still see that sequence of messages ending with the IMAPI service being stopped.
Jonas Sulk
MS LVP
What’s your driver and its service name? Does it collide with IMAPI service name?
It’s still just called Passthru.sys and service name of “Passthru Driver”
The other reason I was wondering if there was somewhere more verbose than the Event Log that I could start digging into is because I noticed that even if I manually start the IMAPI CD Burning Service after the fact, I still can’t burn disks. Although now I’m wondering whether it’s really necessary.
After doing some more tests (just using win XP’s built in CD burning, but on a SP2 partition because I’ve magically permanently prevented myself from being able to burn on my SP3 partition apparently), I found that it seems like on a system which is working, even the IMAPI service gets started when Windows gets ready to burn, and then stopped when it’s done burning. So I’m not sure if the start state of IMAPI is sufficiently indicative of the cause of the inability to burn.
One thing I did notice by booting to the working SP2 partition though is that on a system which can’t burn, if I insert a disk when it’s saying it can’t find a disk to burn to, nothing happens. On a working system, when I insert the disk, the mouse cursor gets a little CD icon on it while it seems to be recognizing that there’s a disk there, before it actually starts the burn. I know that’s not much additional useful information :-[
Jonas Sulk
MS LVP