Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


1394 dead #2 The board supports network debugging,

matt_sykesmatt_sykes Member - All Emails Posts: 290
Have to say it works well, very quick.

How far back is network debugging supported, windows 8.1 isnt it? Better hang on to that old hardware that supports firewire if you ever need to debug windows 7 then!

Comments

  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,302
    I have definitely used 1394 with Windows 10 for both the host and target,
    not sure what happened in your environment. Maybe this:

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

    ?

    The only other time I've had problems is when I've had two 1394 controllers
    on the host (the 1394 debug driver will only bind to one of them).

    Network debug is indeed Win8+.

    -scott
    OSR
    @OSRDrivers

    wrote in message news:[email protected]

    Have to say it works well, very quick.

    How far back is network debugging supported, windows 8.1 isnt it? Better
    hang on to that old hardware that supports firewire if you ever need to
    debug windows 7 then!

    -scott
    OSR

  • matt_sykesmatt_sykes Member - All Emails Posts: 290
    Interesting, though the failure occured on win 10 IoT (Enterprise) build 14393 so not sure its relevant.

    However network debugging is an appreciable leap in performance over 1394, just a shame they didnt add it to the system config GUI, then it would have been obvious its suported.

    Thanks!
  • Jim_BushnellJim_Bushnell Member Posts: 2
    Be careful that one of the limits of network debugging (at least back when I tried it) was that you couldnt debug anything before the network stack was up. So if you are working on a driver that has stuff to do before the netowrk drivers are up, it won't work.
  • matt_sykesmatt_sykes Member - All Emails Posts: 290
    I am assuing this will be fixed in the future Jim? If MSFT are moving to network debugging as the only solution, and it seems ot be that way, then it is going to need to work properly.

    Perhaps in debug mode its got/going to have a different stack?
  • Wes_BarcalowWes_Barcalow Member - All Emails Posts: 4
    I am not familiar with the limitation of waiting for the network driver to start. I have been using network debugging going back to Win8 and its be started early enough to KdFile replace boot start drivers.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 15 Jun 2020 LIVE ONLINE
Writing WDF Drivers 22 June 2020 LIVE ONLINE
Internals & Software Drivers 28 Sept 2020 Dulles, VA