1394 on Win10

WINDBG
1

Setting up to use 1394 with WinDbg does not seem to work any more I have in the past used :

bcdedit /dbgsettings 1394 CHANNEL:43
bcdedit /set testsigning on
bcdedit /debug on

Which worked after the reboot.

Have things changed?

Larry C

2

1394 debugging has been removed from Windows, focus is switching over to
network debugging. You will eventually need to get the 1394 bits from the
SDK, current workaround is to find them elsewhere:

https://blogs.msdn.microsoft.com/windbg/2016/08/11/kd-1394-work-around/

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@windbg…

Setting up to use 1394 with WinDbg does not seem to work any more I have in
the past used :

bcdedit /dbgsettings 1394 CHANNEL:43
bcdedit /set testsigning on
bcdedit /debug on

Which worked after the reboot.

Have things changed?

Larry C

3

I am debugging network drivers, so how does one debug a network driver using a network connection?

Thanks for the link.

Larry C

4

You can use KDNET over a different network card to debug your network driver.

5

Aluhrs is right:

A network card is much easier to obtain and much cheaper than any other card.

Yes, you can use a secondary NIC card. If multiple network cards are available, the PCI bus “parameters” of the one used for debugging must be passed to bcdedit upon configuring the target for debugging.


…
5. If there is more than one network adapter in the target computer, use Device Manager to determine the PCI bus, device, and function numbers for the adapter you want to use for debugging. Then in an elevated Command Prompt window, enter the following command, where b, d, and f are the bus number, device number, and function number of the adapter:

bcdedit /set “{dbgsettings}” busparams b.d.f

6. Reboot the target computer.

https://msdn.microsoft.com/en-us/library/windows/hardware/hh439346(v=vs.85).aspx