Don is correct as usual. However, it does beg the question of what purpose
that mysterious "NET" tab from the Kernel Debug dialog serves. It showed up
in the last release or two with no documentation, I sent an inquiry but
didn't get much in the way of a response. It clearly opens up a port on the
local machine, I'm just wondering what support there is for the other end of
OSR Open Systems Resources, Inc.
"Don Burn" <***@stopspam.windrvr.com> wrote in message
> You cannot do this. The test system has to be connected by serial, 1394
> or a newer than you have USB. Does the test system have a serial port?
> If so you can use a USB to serial on the host.
> Don Burn (MVP, Windows DDK)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
> "Adi" <***@discussions.microsoft.com> wrote in message
>> I'm using WinDbg ver. 6.11.0001.404. My host is a notebook (Dell studio)
>> without a serial port, my target is an old PC without Firewire and only
>> 1.0 ports. So I tought to connect my target and host machine via a cross
>> network (ethernet) cable. I noticed a new NET tab in "Kernel Debugging"
>> dialogue box, where you specify the Port Number. However I do not know
>> how do
>> I set the debug parameters in the traget boot.ini in order to connect via
>> tcp. I could not find ANY documentation of this option (I searched for
>> hours over the Internet and nothing...). Can you explain how to use this
>> option? thanks.
>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature database 4120 (20090601) __________
>> The message was checked by ESET NOD32 Antivirus.
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4120 (20090601) __________
> The message was checked by ESET NOD32 Antivirus.