Defrag Tools: #27 - WinDbg - Configure Kernel Debugging

The Discussion

• 

  Great show.
  btw as a little tid-bit of info... IEEE1394/FireWire is actually the first form of serialized SCSI. Thus why it has channels 0..63 - it's the number of SCSI id's/slots on a SCSI bus. The electrical transport specifications of 1394 has seen been obsoleted when connecting to hard drives. SAS (Serial Attached SCSI) Hard Drives now use the Nexus electrical standard - which is everywhere - GigE, PCIe, HDMI, SATA, SAS. The 1394 protocol lives on today in the SAS communciation protocol.
  

• 

  Brownie points to the first person who can tell me why my modem.sys breakpoint didn't get hit! I went back and watched the show later and figured out my mistake.

• 

  Really like the whole series. This episode was good because the few times I've had to do this it was a bit of a pain so I'm glad this was covered.

  Serial Tablet Larry? That's some solid hardware; just keeps on ticking.

• 

  @ChadBeeder Re-watched that part a few times. At first I though you had left that breakpoint disabled but that doesn't seem to be the case. Perhaps the modem wasn't powered on in the first place and that function is never called?

  Anyway I'll be checking back to see if someone figures it out.

• 

  Even I couldn't work it out - I guessed the same as you, that it was a disabled breakpoint or it wasn't powered on. Chad said he'd  answer it on the episode we tape tomorrow, and air on Monday.

• 

  Liked the show. Really nice. 

  I watch the part where the breakpoint was set on modem!ModemPower twice. My guess is the breakpoint needed to be on a different function? modem!PowerPnP? Maybe?

• 

  @FFE: You got it! I set the breakpoint on the dispatch routine for IRP_MJ_POWER (modem!ModemPower), then disabled the modem in device manager, which would result in, not a power IRP, but a Plug and Play IRP (IRP_MJ_PNP).

  I should have set the breakpoint on modem!ModemPnP instead of modem!ModemPower.

• 

  Crispin Glover?

• 

  Enabling Debug mode causes Windows to hang if no Debugger is connected

  http://support.microsoft.com/kb/2816225/en-us

• 

  thank you

• 

  great page thank you

• 

  Windbg support USB 3.0 debug, it is a very good news.
  
  But my PC donot have USB 3.0 interface so I have to buy the related device and USB 3.0 debug cable ,it looks good for me ,and it is very faster than COM debug.I share the details
  
  USB3.0 debug cable (www.ebay.com/itm/402650436755)
  PCIE to USB3.0 debug device: (www.ebay.com/itm/402677745334)
  
  Good luck for you!