I have a crashing driver in the field, and I’m trying to get a kd
session set up between a couple of computers with pc anywhere on them.
Despite being able to type back and forth between a couple of hyperterms
over the null-modem, I can’t get remote kd to work at all.
The box is a laptop (IBM Thinkpad T41), XPSP1, and has *no built-in
serial ports*, so i’m trying to use the one in the docking station.
Does anyone know if that should work?
Thanks.
-sd
> The box is a laptop (IBM Thinkpad T41), XPSP1, and has *no built-in
serial ports*, so i’m trying to use the one in the docking station.
Does anyone know if that should work?
Yes, the serial port on the docking station should work. I did that a lot.
Calvin Guan Software Engineer
ATI Technologies Inc. www.ati.com
It has been my experience that these ports will not work with WinDbg. They
will work with just about everything else, including hyperterminal, but not
WinDbg.
–
Bill McKenzie
Software Engineer - Prism 802.11 Wireless Solutions
Conexant Systems, Inc.
“Steve Dispensa” wrote in message
news:xxxxx@ntdev…
> I have a crashing driver in the field, and I’m trying to get a kd
> session set up between a couple of computers with pc anywhere on them.
> Despite being able to type back and forth between a couple of hyperterms
> over the null-modem, I can’t get remote kd to work at all.
>
> The box is a laptop (IBM Thinkpad T41), XPSP1, and has no built-in
> serial ports, so i’m trying to use the one in the docking station.
> Does anyone know if that should work?
>
> Thanks.
>
> -sd
>
>
>
The problem is that the machine boots with the serial port disabled. It
relies on the PnP manager to turn on the device later, if it’s in use. This
is done so that IR and modems and plug-in PC-cards can get enough IRQs. IBM
has always done it this way and I’ve always had to hack around it.
Go into your BIOS setup. There will be an option to enable the COM port at
a fixed DOS address, which will trigger the behavior that you want. I’ve
used Thinkpads almost exclusively for my development for years. Trust me,
the debugger can be made to work. It’s much easier since IBM switched from
their own BIOS code base to Phoenix’s.
–
Jake Oshins
Windows Kernel Group
This posting is provided “AS IS” with no warranties, and confers no rights.
“Bill McKenzie” wrote in message
news:xxxxx@ntdev…
> It has been my experience that these ports will not work with WinDbg.
> They
> will work with just about everything else, including hyperterminal, but
> not
> WinDbg.
>
> –
> Bill McKenzie
> Software Engineer - Prism 802.11 Wireless Solutions
> Conexant Systems, Inc.
>
>
> “Steve Dispensa” wrote in message
> news:xxxxx@ntdev…
>> I have a crashing driver in the field, and I’m trying to get a kd
>> session set up between a couple of computers with pc anywhere on them.
>> Despite being able to type back and forth between a couple of hyperterms
>> over the null-modem, I can’t get remote kd to work at all.
>>
>> The box is a laptop (IBM Thinkpad T41), XPSP1, and has no built-in
>> serial ports, so i’m trying to use the one in the docking station.
>> Does anyone know if that should work?
>>
>> Thanks.
>>
>> -sd
>>
>>
>>
>
>
>
On Wed, 2004-05-19 at 16:52, Jake Oshins wrote:
The problem is that the machine boots with the serial port disabled. It
relies on the PnP manager to turn on the device later, if it’s in use.
Jake,
Thanks a lot - I’ll give this a try.
-sd
Cool, good to know.
–
Bill McKenzie
Software Engineer - Prism 802.11 Wireless Solutions
Conexant Systems, Inc.
“Jake Oshins” wrote in message
news:xxxxx@ntdev…
> The problem is that the machine boots with the serial port disabled. It
> relies on the PnP manager to turn on the device later, if it’s in use.
This
> is done so that IR and modems and plug-in PC-cards can get enough IRQs.
IBM
> has always done it this way and I’ve always had to hack around it.
>
> Go into your BIOS setup. There will be an option to enable the COM port
at
> a fixed DOS address, which will trigger the behavior that you want. I’ve
> used Thinkpads almost exclusively for my development for years. Trust me,
> the debugger can be made to work. It’s much easier since IBM switched
from
> their own BIOS code base to Phoenix’s.
>
> –
> Jake Oshins
> Windows Kernel Group
>
> This posting is provided “AS IS” with no warranties, and confers no
rights.
>
>
> “Bill McKenzie” wrote in message
> news:xxxxx@ntdev…
> > It has been my experience that these ports will not work with WinDbg.
> > They
> > will work with just about everything else, including hyperterminal, but
> > not
> > WinDbg.
> >
> > –
> > Bill McKenzie
> > Software Engineer - Prism 802.11 Wireless Solutions
> > Conexant Systems, Inc.
> >
> >
> > “Steve Dispensa” wrote in message
> > news:xxxxx@ntdev…
> >> I have a crashing driver in the field, and I’m trying to get a kd
> >> session set up between a couple of computers with pc anywhere on them.
> >> Despite being able to type back and forth between a couple of
hyperterms
> >> over the null-modem, I can’t get remote kd to work at all.
> >>
> >> The box is a laptop (IBM Thinkpad T41), XPSP1, and has no built-in
> >> serial ports, so i’m trying to use the one in the docking station.
> >> Does anyone know if that should work?
> >>
> >> Thanks.
> >>
> >> -sd
> >>
> >>
> >>
> >
> >
> >
>
>
>