I have two XP test machines that I have updated to SP1. Both
machines were very happy campers with Firewire debugging back to my XP
development system before applying the SP1. Neither machine is happy now.
WinDbg sits forever here:
Microsoft (R) Windows Debugger Version 6.2.0013.1
Copyright (c) Microsoft Corporation. All rights reserved.
Using 1394 for debugging
Opened \.\DBG1394_CHANNEL44
Waiting to reconnect…
I can hear “doinks” on the development system’s speakers when the
Firewire cable is attached or detached from the target, so I know that the
connection is physically good. I have disabled the 1394 network
connections. I have disabled the network adapter on the target and on the
host. I have changed the channel to 44, having previously used channel 1
for many many months. I have disabled USB legacy support. Nothing has
helped.
Well, not quite nothing. Uninstalling SP1 makes it work again :-0
Does anyone have the magic recipe for making Firewire debugging work
with SP1.
Chris Myers
“Chris Myers” wrote in message news:xxxxx@ntdev…
>
> I have two XP test machines that I have updated to SP1. Both
> machines were very happy campers with Firewire debugging back to my XP
> development system before applying the SP1. Neither machine is happy now.
> WinDbg sits forever here:
>
> Microsoft (R) Windows Debugger Version 6.2.0013.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Using 1394 for debugging
> Opened \.\DBG1394_CHANNEL44
> Waiting to reconnect…
>
> I can hear “doinks” on the development system’s speakers when the
> Firewire cable is attached or detached from the target, so I know that the
> connection is physically good. I have disabled the 1394 network
> connections. I have disabled the network adapter on the target and on the
> host. I have changed the channel to 44, having previously used channel 1
> for many many months. I have disabled USB legacy support. Nothing has
> helped.
>
> Well, not quite nothing. Uninstalling SP1 makes it work again :-0
>
> Does anyone have the magic recipe for making Firewire debugging work
> with SP1.
This would probably be better asked on the windbg list. If you hurry
over there now, you’ll find Garry Little with a fist-full of hair in
one hand and a mangled Firewire cable in the other …
On your HOST, try:
set _NT_DEBUG_1394_SYMLINK=instance
and then start windbg.
“Chris Myers” wrote in message news:xxxxx@ntdev…
> I have two XP test machines that I have updated to SP1. Both
> machines were very happy campers with Firewire debugging back to my XP
> development system before applying the SP1. Neither machine is happy now.
> WinDbg sits forever here:
>
> Microsoft (R) Windows Debugger Version 6.2.0013.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Using 1394 for debugging
> Opened \.\DBG1394_CHANNEL44
> Waiting to reconnect…
>
> I can hear “doinks” on the development system’s speakers when the
> Firewire cable is attached or detached from the target, so I know that the
> connection is physically good. I have disabled the 1394 network
> connections. I have disabled the network adapter on the target and on the
> host. I have changed the channel to 44, having previously used channel 1
> for many many months. I have disabled USB legacy support. Nothing has
> helped.
>
> Well, not quite nothing. Uninstalling SP1 makes it work again :-0
>
> Does anyone have the magic recipe for making Firewire debugging work
> with SP1.
>
> Chris Myers
>
That did the trick. Thanks!
Chris Myers
-----Original Message-----
From: Ivan Bublikov [mailto:xxxxx@yahoo.com]
Sent: Sunday, October 05, 2003 9:48 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: WinDbg 1394 broken by XP SP1
On your HOST, try:
set _NT_DEBUG_1394_SYMLINK=instance
and then start windbg.
“Chris Myers” wrote in message
news:xxxxx@ntdev…
> I have two XP test machines that I have updated to SP1. Both machines
> were very happy campers with Firewire debugging back to my XP
> development system before applying the SP1. Neither machine is happy
> now. WinDbg sits forever here:
>
> Microsoft (R) Windows Debugger Version 6.2.0013.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Using 1394 for debugging
> Opened \.\DBG1394_CHANNEL44
> Waiting to reconnect…
>
> I can hear “doinks” on the development system’s speakers when the
> Firewire cable is attached or detached from the target, so I know that
> the connection is physically good. I have disabled the 1394 network
> connections. I have disabled the network adapter on the target and on
> the host. I have changed the channel to 44, having previously used
> channel 1 for many many months. I have disabled USB legacy support.
> Nothing has helped.
>
> Well, not quite nothing. Uninstalling SP1 makes it work again :-0
>
> Does anyone have the magic recipe for making Firewire debugging work
> with SP1.
>
> Chris Myers
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@quatech.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
RE: [ntdev] Re: WinDbg 1394 broken by XP SP1Not for me. The 1394 debug interface is still dead as a door nail and useless. Following this e-mail’s advice I set the following environment variables: _NT_DEBUG_BUS to 1394 and _NT_DEBUG_1394_SYMLINK to “channel”. I also tried “instance”. It still no worky.
Oh … target and host are both XP SP1a.
–
Gary G. Little
Seagate Technologies, LLC
“Chris Myers” wrote in message news:xxxxx@ntdev…
That did the trick. Thanks!
Chris Myers
>-----Original Message-----
>From: Ivan Bublikov [mailto:xxxxx@yahoo.com]
>Sent: Sunday, October 05, 2003 9:48 AM
>To: Windows System Software Devs Interest List
>Subject: [ntdev] Re: WinDbg 1394 broken by XP SP1
>
>
>On your HOST, try:
>
>set _NT_DEBUG_1394_SYMLINK=instance
>
>and then start windbg.
>
>
>“Chris Myers” wrote in message
news:xxxxx@ntdev…
> I have two XP test machines that I have updated to SP1. Both machines
> were very happy campers with Firewire debugging back to my XP
> development system before applying the SP1. Neither machine is happy
> now. WinDbg sits forever here:
>
> Microsoft (R) Windows Debugger Version 6.2.0013.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Using 1394 for debugging
> Opened \.\DBG1394_CHANNEL44
> Waiting to reconnect…
>
> I can hear “doinks” on the development system’s speakers when the
> Firewire cable is attached or detached from the target, so I know that
> the connection is physically good. I have disabled the 1394 network
> connections. I have disabled the network adapter on the target and on
> the host. I have changed the channel to 44, having previously used
> channel 1 for many many months. I have disabled USB legacy support.
> Nothing has helped.
>
> Well, not quite nothing. Uninstalling SP1 makes it work again :-0
>
> Does anyone have the magic recipe for making Firewire debugging work
> with SP1.
>
> Chris Myers
>
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@quatech.com To unsubscribe send a blank email to xxxxx@lists.osr.com
Gary,
I don’t know why it started working again for me. I’m just glad
that it did. Firewire has been a great debugging environment for me on XP,
or at least it was up until SP1.
Chris Myers
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@seagate.com]
Sent: Monday, October 06, 2003 4:47 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: WinDbg 1394 broken by XP SP1
Not for me. The 1394 debug interface is still dead as a door nail and
useless. Following this e-mail’s advice I set the following environment
variables: _NT_DEBUG_BUS to 1394 and _NT_DEBUG_1394_SYMLINK to “channel”. I
also tried “instance”. It still no worky.
Oh … target and host are both XP SP1a.
–
Gary G. Little
Seagate Technologies, LLC
RE: [ntdev] Re: WinDbg 1394 broken by XP SP1Gary, try getting a decent
single purpose 1394 card with the standard chipset. You mentioned that the
card has two functions and that might make it harder to be used by the
kernel debugger.
“Gary G. Little” wrote in message
news:xxxxx@ntdev…
Not for me. The 1394 debug interface is still dead as a door nail and
useless. Following this e-mail’s advice I set the following environment
variables: _NT_DEBUG_BUS to 1394 and _NT_DEBUG_1394_SYMLINK to “channel”. I
also tried “instance”. It still no worky.
Oh … target and host are both XP SP1a.
–
Gary G. Little
Seagate Technologies, LLC
“Chris Myers” wrote in message news:xxxxx@ntdev…
That did the trick. Thanks!
Chris Myers
>-----Original Message-----
>From: Ivan Bublikov [mailto:xxxxx@yahoo.com]
>Sent: Sunday, October 05, 2003 9:48 AM
>To: Windows System Software Devs Interest List
>Subject: [ntdev] Re: WinDbg 1394 broken by XP SP1
>
>
>On your HOST, try:
>
>set _NT_DEBUG_1394_SYMLINK=instance
>
>and then start windbg.
>
>
>“Chris Myers” wrote in message
news:xxxxx@ntdev…
> I have two XP test machines that I have updated to SP1. Both machines
> were very happy campers with Firewire debugging back to my XP
> development system before applying the SP1. Neither machine is happy
> now. WinDbg sits forever here:
>
> Microsoft (R) Windows Debugger Version 6.2.0013.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Using 1394 for debugging
> Opened \.\DBG1394_CHANNEL44
> Waiting to reconnect…
>
> I can hear “doinks” on the development system’s speakers when the
> Firewire cable is attached or detached from the target, so I know that
> the connection is physically good. I have disabled the 1394 network
> connections. I have disabled the network adapter on the target and on
> the host. I have changed the channel to 44, having previously used
> channel 1 for many many months. I have disabled USB legacy support.
> Nothing has helped.
>
> Well, not quite nothing. Uninstalling SP1 makes it work again :-0
>
> Does anyone have the magic recipe for making Firewire debugging work
> with SP1.
>
> Chris Myers
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@quatech.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
You’ve disabled 1394 on the target system? I recently omitted to do that
and had lots of grief until I did so.
“Gary G. Little” wrote:
Not for me. The 1394 debug interface is still dead as a door nail and
useless.
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini
Windows DDK MVP
Yeah … its disabled. I see a great big red X on it every time I install my
driver under test. And I see the DEBUG_1394 devices in DM when I look on the
host with WinDbg running.
Frankly, serial at 115.2 works so well that, other than trying it now and
then when I see something new here, expending any effort on getting 1394 to
work is literally not worth the effort of picking up screw driver. (although
a sledge hammer would be MUCH more gratifying.)
–
Gary G. Little
Seagate Technologies, LLC
“James Antognini” wrote in message
news:xxxxx@ntdev…
>
> You’ve disabled 1394 on the target system? I recently omitted to do that
> and had lots of grief until I did so.
>
> “Gary G. Little” wrote:
>
> > Not for me. The 1394 debug interface is still dead as a door nail and
> > useless.
>
> –
> If replying by e-mail, please remove “nospam.” from the address.
>
> James Antognini
> Windows DDK MVP
>
>
>
>