Re: firewire + windbg == unstable?

WINDBG
1

Hi,
When restarting WinDbg fails because the firewire driver isn’t very happy I
have found a way of solving the problem every time on my system :

  1. Close Windbg
  2. Open device manager
  3. Select View->Show hidden devices
  4. Find the 1394 ARP Client Protocol
  5. Right hand mouse click on the device and select 'Scan for hardware
    changes;
  6. Start WinDbg again

Hope this helps.

Yours
Roger

Roger Coote,
Senior Design Engineer
PowerVR Technologies, A Division of Imagination Technologies Ltd
Home Park Estate, Kings Langley, Hertfordshire, WD4 8LZ, UK
phone :+44 (1923) 260511 fax :+44 (1923) 268969
direct :+44 (1923) 277274
mailto:xxxxx@powervr.com www.powervr.com

-----Original Message-----
From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
Sent: 30 November 2001 11:30
To: Kernel Debugging Interest List
Subject: [windbg] Re: firewire + windbg == unstable?

This is a know problem with the 1394 debugger wire protocol, and it
unfortunately requires OS changes to fix. The fix is
available in Windows
.NET BETA 3 and will be in Windows XP SP1.

-Andre

You are currently subscribed to windbg as: xxxxx@videologic.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Thanks for the suggestion… I’ve actually ditched firewire for the time
being. It was a pain in the ass to try and work around all the little
quirks, so I’ve gone back to serial… much slower when loading a driver
with .kdfiles, but I don’t have to worry about restarting the debugger
if I try and step through code too fast, reload all symbols at once, or
any of a number of other things that seemed to freak out the 1394
protocol… serial may be slow, but at least its stable…
so now my firewire cards can just collect dust until sp1 comes out…

sean

Roger Coote wrote:

Hi,
When restarting WinDbg fails because the firewire driver isn’t very happy I
have found a way of solving the problem every time on my system :

  1. Close Windbg
  2. Open device manager
  3. Select View->Show hidden devices
  4. Find the 1394 ARP Client Protocol
  5. Right hand mouse click on the device and select 'Scan for hardware
    changes;
  6. Start WinDbg again

Hope this helps.

Yours
Roger

Roger Coote,
Senior Design Engineer
PowerVR Technologies, A Division of Imagination Technologies Ltd
Home Park Estate, Kings Langley, Hertfordshire, WD4 8LZ, UK
phone :+44 (1923) 260511 fax :+44 (1923) 268969
direct :+44 (1923) 277274
mailto:xxxxx@powervr.com www.powervr.com

>-----Original Message-----
>From: xxxxx@microsoft.com [mailto:xxxxx@microsoft.com]
>Sent: 30 November 2001 11:30
>To: Kernel Debugging Interest List
>Subject: [windbg] Re: firewire + windbg == unstable?
>
>
>This is a know problem with the 1394 debugger wire protocol, and it
>unfortunately requires OS changes to fix. The fix is
>available in Windows
>.NET BETA 3 and will be in Windows XP SP1.
>
>-Andre
>
>—
>You are currently subscribed to windbg as: xxxxx@videologic.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

You are currently subscribed to windbg as: xxxxx@stg.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com