Dear Community,
I have tried to install a homemade KMDF Driver for an USB device on a virtual PC (XP Mode for WIN7) and it failed with code 39. Then I installed WDK7.1 + KMDF1.0 which I used previously to compile this driver on a native XP PC successfully and compiled this driver now directly in the XP mode (also successfully). Then I reinstalled the driver ? surprisingly with success. However after restarting the XP mode the driver failed to load again with code 39. The USB driver contains some kdprintf messages which I could follow using debugview ? obviously the driver does not even starting. I would be very happy if anyone could help.
Best Regards,
Matthias
On Feb 15, 2015, at 10:23 AM, xxxxx@alumni.tu-berlin.de wrote:
I have tried to install a homemade KMDF Driver for an USB device on a virtual PC (XP Mode for WIN7) and it failed with code 39. Then I installed WDK7.1 + KMDF1.0 which I used previously to compile this driver on a native XP PC successfully and compiled this driver now directly in the XP mode (also successfully). Then I reinstalled the driver ? surprisingly with success. However after restarting the XP mode the driver failed to load again with code 39. The USB driver contains some kdprintf messages which I could follow using debugview ? obviously the driver does not even starting. I would be very happy if anyone could help.
Are you building a 32-bit driver or a 64-bit driver? Remember, even if your Win 7 is 64-bit, you’ll need to install a 32-bit driver in your XP mode. Are you signing the driver? Are you quite sure you are installing the driver into the XP VM’s disk?
—
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Dear Tim,
thank you very much for responding. To my knowledge the XP Mode is a 32 bit platform. The WIN7 os is a 64bit one. I have compiled the homebuild USB device driver using the WDK7.1 checked build environment which I combined as mentioned with the KMDF1.0 framework. Everything is installed on the virtual disk of the XP mode. As mentioned the driver was successfully installed and tested on a native WinXp sp3 pc.
As mentioned there?re must be an option to get this driver operating because it succeeded for one time in the said XP mode. However after restarting the XP Mode the USB device was detected as an unknown one and the os asked for installing the driver. As mentioned this resulted in code 39. I also tried to completely remove this driver (also in the registry) however after reinstalling there was again code 39.
Other examples selected from the WDK are working successfully in the same XP mode ? however those are not installed using the WDF co-installer dll. Maybe the XP mode is not useful for developing or testing KMDF drivers.
Best Regards,
Matthias
On Feb 15, 2015, at 2:41 PM, xxxxx@alumni.tu-berlin.de wrote:
thank you very much for responding. To my knowledge the XP Mode is a 32 bit platform. The WIN7 os is a 64bit one.
Yes, that’s why I was trying to ask what target you were building.
I have compiled the homebuild USB device driver using the WDK7.1 checked build environment which I combined as mentioned with the KMDF1.0 framework.
Saying “WDK 7.1 checked build environment” isn’t meaningful. You are using the WDK 7.1, OK, but are you using the “XP 32-bit checked build environment”? Remember that you can’t build with the Win 7 build environment and load it on XP, and you can’t build for 64-bit and load it on XP.
Other examples selected from the WDK are working successfully in the same XP mode ? however those are not installed using the WDF co-installer dll.
Another common mistake is to try to use the checked version of the co-installers. Those are only intended for use if you have the checked build of the operating system, which almost no one does. You want the regular build of the co-installers.
Is there anything useful in setupapi.log?
Maybe the XP mode is not useful for developing or testing KMDF drivers.
It is extremely useful. I’ve even run my streaming video capture drivers in the XP mode.
—
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
I restored the XP mode from the system restore point where the driver was installed successfully one- time only and now it is working so far. However this is unsatisfactory. I doubt the coinstaller somehow collides with the integrative features of the XP mode.
Best Regards,
Matthias