Dont apologise. I have been on to Maunder for a while to create a kernel forum. :) First, eliminate the warnings. Tfhis is the kernel here, we accept nothing but 100% perfection. :) (And seriously, I mean that. It is either 100% or it is crap. Nothing in betweem.) So, ewhen the inf checks out OK and rins you need to check the services key to make sure the driver is there. If not, the inf failed in some way. Look at setupapi.log file, it will tell you about inf based installs. If the services entry is there, we need to look at signing, turn off driver signing checking, else the system wont load it. Slight aside here, drivier signing checking on 64 Vista+. Originally you couldnt load unsigned drivers, then the driver dev world got pissed of with MS, and they changed it, but you have to be booted in debug mode (last I heard, but it is possible they changed it on later OSs. Check on google). It coule be your driver is loading, but failing driver entry. So, after it loads (supposedly), do a sc query and see if it says running. If not, it is time to hook up windbg and set a breakpiont on your driver driverentry. bp !driverentry Load it, and it should break. (set the symbols up.) Then you can see if it is failing in driverentry. If it suceeds driverentry, your driver IS running. If your service entry is there, but driverentry isnt getting hit, then you need to make sure it is compiled properly, it needs a check sum, so make sure you use the ddk build utility. Yep, its PITA, but thats why I get paid so damn much! :)
============================== Nothing to say.