I don’t use Windows 8.1 for development normally but my customer is. We are trying to use Windbg over 1394, and get the weird situation of if we have the standard 1394 driver enabled the debuggers 1394 driver shows up disabled, BUT IF WE DISABLE THE STANDARD 1394 DRIVER, THE DEUBGGER 1394 DRIVER DISAPPEARS FROM THE DEVICE MANAGER. Under either scenario, 1394 in Windbg complains it can’t find the device?
Has anyone seen this behavior, and know how to fix it? My client foolishly bought systems that do not offer drivers for Win7 so are stuck.
Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
The 1394 debug device is a child of the 1394 controller, so it would make
sense for it to go away if the controller is disabled. What error do you get
when you try to open WinDbg?
-scott
OSR
@OSRDrivers
“Don Burn” wrote in message news:xxxxx@windbg…
I don’t use Windows 8.1 for development normally but my customer is. We are
trying to use Windbg over 1394, and get the weird situation of if we have
the standard 1394 driver enabled the debuggers 1394 driver shows up
disabled, BUT IF WE DISABLE THE STANDARD 1394 DRIVER, THE DEUBGGER 1394
DRIVER DISAPPEARS FROM THE DEVICE MANAGER. Under either scenario, 1394 in
Windbg complains it can’t find the device?
Has anyone seen this behavior, and know how to fix it? My client foolishly
bought systems that do not offer drivers for Win7 so are stuck.
Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com