Host is XP, target Vista using 1394, latest version of Windbg. 1394 *net* adapter disabled, 1394 host controller enabled on Host machine. 1394 Host controller yellowed out on target Vista machine (also tried disabling it, no difference)
Can break in with Ctrl Break at any time, including boot, but host doesn’t seem to recognize the connection as it continues to display “Debuggee not connected” Sometimes I can press F5 in windbg to get the target to resume - most of the times not.
With vista target, don’t disable the 1394 controller. That’s taken care of for you. Maybe even in XP SP2, but not sure.
Try KD, just to see if it’s limited to windbg? Less moving parts.
Ctrl+D in kd will turn on noisy transport spew. Look for errors. It’s a different keystroke in windbg - I forgot, maybe Ctrl+Shift+D. If you see errors, try different 1394 cards. I’ve had luck with TI chipsets
Host is XP, target Vista using 1394, latest version of Windbg. 1394 net adapter disabled, 1394 host controller enabled on Host machine. 1394 Host controller yellowed out on target Vista machine (also tried disabling it, no difference)
Can break in with Ctrl Break at any time, including boot, but host doesn’t seem to recognize the connection as it continues to display “Debuggee not connected” Sometimes I can press F5 in windbg to get the target to resume - most of the times not.
Jason, getting READ: Error 80070014. READ: Wait for type 7 packet
The ports are built in to the two computers I’m using. By any chance do you know how I could setup a 1394 network outside of debugging so I could see if it’s a chipset problem? Thanks,
No experience outside of debuggers. But I spent some time looking at this and here’s the interesting info:
All players in the 1394 chain can cause damage, even if they’re not part of the conversation.
Hubs too. If a hub doesn’t play nice, badness ensues.
If 1 part of the 1394 chain causes problems, all nodes in the chain typically go down together.
Some cards work great, until plugged into the wrong motherboard. I’ve had 2 machines not want to talk at all. I swapped the 1394 cards between the two machines, and they worked perfectly.
I’ve never done this, but I’ve heard you can use another 1394 card even if there is an onboard card already. I think you’d have to specify some extra options in boot.ini. sent mail to xxxxx@microsoft.com and someone there should know the details, if you’re interested.
But I think it all comes down to hardware quality, in the end. Really the luck of the draw.
Jason, getting READ: Error 80070014. READ: Wait for type 7 packet
The ports are built in to the two computers I’m using. By any chance do you know how I could setup a 1394 network outside of debugging so I could see if it’s a chipset problem? Thanks,
The target is using the 1394a controller using code in the OS and not the
driver stack that other uses of 1394a will have. It appears that the code
was done with the TI chipset in mind. All others will have problems to some
degree. I have used Via with few problems, but I don’t any more.
wrote in message news:xxxxx@windbg… > Jason, getting READ: Error 80070014. READ: Wait for type 7 packet > > The ports are built in to the two computers I’m using. By any chance do > you know how I could setup a 1394 network outside of debugging so I could > see if it’s a chipset problem? Thanks, > > Scott >