I am seeing some odd behavior when trying to install the WDK 1394 sample on a
Win7 machine. I am very new to WDK development, so bear with me if I've made
some noobish mistake. :-)
Following the instructions from the 1394 sample installation notes (from WDK
7000.0; v1.9) , I built the sample and loaded it onto the test machine (dev
machine is 32-bit XP, test machine is 32-bit Win7). When I run the sample
and Add a Virtual Device, I do not see the expected Found New Hardware popup.
I hear a sound as if a new device is connected and can see an 'Unknown
Device' in Device Manager, but it appears it never installs properly; it does
appear to uninstall when I select Remove Virtual Device from the sample app.
Manually trying to install the driver for the unknown device from Device
Manager causes a BSOD.
This behavior can be replicated using older WDM 1394 samples as well (WDK
6001.18001 and WDK 6001.18002). On a hunch, I built the 1394 sample on the
XP machine from the Win7 build environment (I know this is not recommended; I
was starting to try anything that I could think of by this point) and
experienced the same behavior, with the exception that the Unknown Device in
the Device Manager was properly titled WDF 1394 Hybrid Virtual Device.
What is going wrong here? The app executable is in the same folder as the
..inf, .sys, and .dll files that are built from the WDK sample; the older WDM
sample being used is manually installed before running the sample, according
to the installation notes for that version of the sample. All of the samples
run correctly on the dev machine and non-Win7 machines. Are there still
problems with running the samples alongside the new 1394 drivers in Win7?
Any help would be appreciated.
Devan
|
Similar Threads
Linear Mode
