I can delete both the “1394 Debugger Device” and the “VIA 1394 OHCI
Compliant Host Controller” from Device Manager, reboot, and then run
WinDBG again to trigger reinstallation of the “1394 Debugger Device” (by
selecting Kernel Debug, 1394, Channel 42).
However, the installation (of the debug device) fails. There is nothing
in setupact.log; the only thing that changes (in C:\Windows) is
WindowsUpdate.log (it appears that Automatic Update ran to check for new
updates).
If I reboot the machine, the “1394 Debugger Device” comes up
yellow-banged, and it shows Code 39 in the Properties (from Device
Manager). “C:\Windows\System32\drivers\1394kdbg.sys” is present, so
something got installed.
I tried re-running “C:\Program Files (x86)\Windows
Kits\8.1\Debuggers\Redist\X64 Debuggers And Tools-x64_en-us.msi”, and
then going through the whole process again (delete devices, reboot, run
Windbg, select kernel debug, 1394, channel 42), but same result.
I am completely at a loss as to what might be going wrong, or even what
to try next. Any and all suggestions welcome.
–mkj
On 11/6/2013 5:06 PM, Michael Jones wrote:
I’ve spent all day trying to get WinDbg set up to use 1394. I’ve done
this in the past many times without any trouble; but I’m getting nowhere
this time. This is just the host side; I haven’t even gotten to the
target yet.
I’m running Win7 64-bit; I installed the latest WinDbg from the online
SDK installer (that’s the only thing from the SDK I installed). Next, I
ran WinDbg (X64) as Administrator, selected File | Kernel Debug… |
1394, and entered channel 42.
When I click OK, it tries to install the 1394 debug driver; but after
spinning awhile, it fails. I tried deleting the device and installing
again; no luck. Then I tried deleting the 1394 controller, rebooting,
and reinstalling; it did the same thing (tried to install the debug
driver, then failed).
I tried updating the driver through driver manager by pointing it at the
one under C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\1394 but
it just tells me the latest driver is already installed.
I must be making some obvious mistake, but I am just not seeing it. Any
suggestions?
TIA,
– mkj
//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________
–
“I can answer any question, so long as you agree that
‘I don’t know’ is an answer.”
– Isaac Asimov
//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________