Unsucessfull test in Hyper terminal

Hi all,
I am new to kernel debugging.
I am trying to connect my Host and PC machines with a Null Modem Cable
and via Hyperterminal.
I used the folowing steps to test as per help.

To test the null-modem connection
On the host computer, click the Start button, point to Programs,
then point to Accessories, then point to Communications, then click
HyperTerminal. If HyperTerminal is not installed, install it from the
product CD-ROM using Add/Remove Programs from Control Panel.
In the Connection Description dialog box, enter a name for the
new connection. (The name doesn't matter.)
In the Connect To dialog box, click on the Connect using drop
down list. Select the COM port corresponding to the port to which the
null-modem cable is connected on this machine.
Accept the defaults for the COM port properties in the next
dialog box.
Repeat steps 1 through 4 for the target computer.
HyperTerminal is now open and ready for testing. Type in a
string of characters on the host system. If the null-modem cable is
properly installed and the correct COM ports were chosen within
HyperTerminal on both systems, the string of characters typed in on the
host will be displayed in the HyperTerminal window of the target system.


After these steps , the hyper-terminal interface says "Connected" at the
bottom status bar. But When I type from my key board I see nothing on my
host nor in my target machine.
I have tried all combinations with the com ports and replaced the Cable
but no success.
Any Ideas.
Regards,
Anurag

I do wish serial cables would be less difficult to get working,
especially for new folks.

  • Make sure you have your com ports enabled in the bios
  • don’t try to use non-legacy com ports (i.e. no usb com ports, etc)
  • make sure com1 is at 3f8, irq3
  • Try to get a null modem cable, 9-pin female to 9-pin female (don’t
    use converters; sometimes they re-cross inside)
  • Make sure the com settings really are identical - I’d test with
    9600bps, 8 data bits, 1 stop bit, no parity, and no flow control.

When you actually go to modify your boot.ini, you should probably use
/baudrate:115200 or it’ll be too slow.

If none of the above work, you should try hooking up another serial
device to the ports on each box (i.e. an old mouse or something) just to
test the physical ports. Older motherboards required a ribbon connector
between the 9-pin port and the board; perhaps it’s wired up wrong (the
red strip should be by pin 1).

Good luck.

-sd

On Tue, 2004-08-10 at 04:14, Anurag Sarin wrote:

Hi all,
I am new to kernel debugging.
I am trying to connect my Host and PC machines with a Null Modem Cable
and via Hyperterminal.
I used the folowing steps to test as per help.

To test the null-modem connection
On the host computer, click the Start button, point to
Programs, then point to Accessories, then point to
Communications, then click HyperTerminal. If HyperTerminal is
not installed, install it from the product CD-ROM using
Add/Remove Programs from Control Panel.

In the Connection Description dialog box, enter a name for the
new connection. (The name doesn’t matter.)
In the Connect To dialog box, click on the Connect using drop
down list. Select the COM port corresponding to the port to
which the null-modem cable is connected on this machine.

Accept the defaults for the COM port properties in the next
dialog box.
Repeat steps 1 through 4 for the target computer.
HyperTerminal is now open and ready for testing. Type in a
string of characters on the host system. If the null-modem
cable is properly installed and the correct COM ports were
chosen within HyperTerminal on both systems, the string of
characters typed in on the host will be displayed in the
HyperTerminal window of the target system.


After these steps , the hyper-terminal interface says “Connected” at
the bottom status bar. But When I type from my key board I see nothing
on my host nor in my target machine.

I have tried all combinations with the com ports and replaced the
Cable but no success.
Any Ideas.
Regards,
Anurag


You are currently subscribed to windbg as:
xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

Hello Steve ,
Thanks for your response . Only irq3 was irq4 in my case.
Tried it , but no sucess ,any other ideas ?

Regards,
Anurag

-----Original Message-----
From: Steve Dispensa [mailto:xxxxx@positivenetworks.net]
Sent: Tuesday, August 10, 2004 3:36 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Unsucessfull test in Hyper terminal

I do wish serial cables would be less difficult to get working,
especially for new folks.

  • Make sure you have your com ports enabled in the bios
  • don’t try to use non-legacy com ports (i.e. no usb com ports, etc)
  • make sure com1 is at 3f8, irq3
  • Try to get a null modem cable, 9-pin female to 9-pin female (don’t
    use converters; sometimes they re-cross inside)
  • Make sure the com settings really are identical - I’d test with
    9600bps, 8 data bits, 1 stop bit, no parity, and no flow control.

When you actually go to modify your boot.ini, you should probably use
/baudrate:115200 or it’ll be too slow.

If none of the above work, you should try hooking up another serial
device to the ports on each box (i.e. an old mouse or something) just to
test the physical ports. Older motherboards required a ribbon connector
between the 9-pin port and the board; perhaps it’s wired up wrong (the
red strip should be by pin 1).

Good luck.

-sd

On Tue, 2004-08-10 at 04:14, Anurag Sarin wrote:

Hi all,
I am new to kernel debugging.
I am trying to connect my Host and PC machines with a Null Modem Cable

and via Hyperterminal. I used the folowing steps to test as per help.

To test the null-modem connection
On the host computer, click the Start button, point to
Programs, then point to Accessories, then point to
Communications, then click HyperTerminal. If HyperTerminal is
not installed, install it from the product CD-ROM using
Add/Remove Programs from Control Panel.

In the Connection Description dialog box, enter a name for the
new connection. (The name doesn’t matter.)
In the Connect To dialog box, click on the Connect using drop
down list. Select the COM port corresponding to the port to
which the null-modem cable is connected on this machine.

Accept the defaults for the COM port properties in the next
dialog box.
Repeat steps 1 through 4 for the target computer.
HyperTerminal is now open and ready for testing. Type in a
string of characters on the host system. If the null-modem
cable is properly installed and the correct COM ports were
chosen within HyperTerminal on both systems, the string of
characters typed in on the host will be displayed in the
HyperTerminal window of the target system.


After these steps , the hyper-terminal interface says “Connected” at
the bottom status bar. But When I type from my key board I see nothing

on my host nor in my target machine.

I have tried all combinations with the com ports and replaced the
Cable but no success. Any Ideas.
Regards,
Anurag


You are currently subscribed to windbg as:
xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@divassoftware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

haha… my bad - com1 is irq4. Sorry for the mis-information :frowning:

Other ideas? Nope. Look for a standard serial mouse and try to get it
working on that port. Try kd again only after that mouse works.

-sd

On Tue, 2004-08-10 at 09:09, Anurag Sarin wrote:

Hello Steve ,
Thanks for your response . Only irq3 was irq4 in my case.
Tried it , but no sucess ,any other ideas ?

Regards,
Anurag

-----Original Message-----
From: Steve Dispensa [mailto:xxxxx@positivenetworks.net]
Sent: Tuesday, August 10, 2004 3:36 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Unsucessfull test in Hyper terminal

I do wish serial cables would be less difficult to get working,
especially for new folks.

  • Make sure you have your com ports enabled in the bios
  • don’t try to use non-legacy com ports (i.e. no usb com ports, etc)
  • make sure com1 is at 3f8, irq3
  • Try to get a null modem cable, 9-pin female to 9-pin female (don’t
    use converters; sometimes they re-cross inside)
  • Make sure the com settings really are identical - I’d test with
    9600bps, 8 data bits, 1 stop bit, no parity, and no flow control.

When you actually go to modify your boot.ini, you should probably use
/baudrate:115200 or it’ll be too slow.

If none of the above work, you should try hooking up another serial
device to the ports on each box (i.e. an old mouse or something) just to
test the physical ports. Older motherboards required a ribbon connector
between the 9-pin port and the board; perhaps it’s wired up wrong (the
red strip should be by pin 1).

Good luck.

-sd

On Tue, 2004-08-10 at 04:14, Anurag Sarin wrote:
> Hi all,
> I am new to kernel debugging.
> I am trying to connect my Host and PC machines with a Null Modem Cable

> and via Hyperterminal. I used the folowing steps to test as per help.
> --------------------------------------------------------
> To test the null-modem connection
> On the host computer, click the Start button, point to
> Programs, then point to Accessories, then point to
> Communications, then click HyperTerminal. If HyperTerminal is
> not installed, install it from the product CD-ROM using
> Add/Remove Programs from Control Panel.
>
> In the Connection Description dialog box, enter a name for the
> new connection. (The name doesn’t matter.)
> In the Connect To dialog box, click on the Connect using drop
> down list. Select the COM port corresponding to the port to
> which the null-modem cable is connected on this machine.
>
> Accept the defaults for the COM port properties in the next
> dialog box.
> Repeat steps 1 through 4 for the target computer.
> HyperTerminal is now open and ready for testing. Type in a
> string of characters on the host system. If the null-modem
> cable is properly installed and the correct COM ports were
> chosen within HyperTerminal on both systems, the string of
> characters typed in on the host will be displayed in the
> HyperTerminal window of the target system.
>
>
> --------------------------------------------------------------
>
> After these steps , the hyper-terminal interface says “Connected” at
> the bottom status bar. But When I type from my key board I see nothing

> on my host nor in my target machine.
>
> I have tried all combinations with the com ports and replaced the
> Cable but no success. Any Ideas.
> Regards,
> Anurag
>
> —
> You are currently subscribed to windbg as:
> xxxxx@positivenetworks.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@divassoftware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@positivenetworks.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

My COM1 Host and target machines work fine with the serial mouse hence
tested.

1>My null modem canle in 9 pin female one end and 9 pin female other
end, the help says 9 pin female one end and 25 pin female on the
other.We do not get 25 pin male slot with these new machines.Is this a
problem ? or 9 pin to 9 pin will do.

2>When I felt the cable one side was quite warm and the other was not.
Does this signal some thing ? Well this was my second cable that I
bought thinking the first one was faulty.

Any Ideas will be great help.

-----Original Message-----
From: Steve Dispensa [mailto:xxxxx@positivenetworks.net]
Sent: Tuesday, August 10, 2004 9:18 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Unsucessfull test in Hyper terminal

haha… my bad - com1 is irq4. Sorry for the mis-information :frowning:

Other ideas? Nope. Look for a standard serial mouse and try to get it
working on that port. Try kd again only after that mouse works.

-sd

On Tue, 2004-08-10 at 09:09, Anurag Sarin wrote:

Hello Steve ,
Thanks for your response . Only irq3 was irq4 in my case.
Tried it , but no sucess ,any other ideas ?

Regards,
Anurag

-----Original Message-----
From: Steve Dispensa [mailto:xxxxx@positivenetworks.net]
Sent: Tuesday, August 10, 2004 3:36 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Unsucessfull test in Hyper terminal

I do wish serial cables would be less difficult to get working,
especially for new folks.

  • Make sure you have your com ports enabled in the bios
  • don’t try to use non-legacy com ports (i.e. no usb com ports, etc)
  • make sure com1 is at 3f8, irq3
  • Try to get a null modem cable, 9-pin female to 9-pin female (don’t
    use converters; sometimes they re-cross inside)
  • Make sure the com settings really are identical - I’d test with
    9600bps, 8 data bits, 1 stop bit, no parity, and no flow control.

When you actually go to modify your boot.ini, you should probably use
/baudrate:115200 or it’ll be too slow.

If none of the above work, you should try hooking up another serial
device to the ports on each box (i.e. an old mouse or something) just
to test the physical ports. Older motherboards required a ribbon
connector between the 9-pin port and the board; perhaps it’s wired up
wrong (the red strip should be by pin 1).

Good luck.

-sd

On Tue, 2004-08-10 at 04:14, Anurag Sarin wrote:
> Hi all,
> I am new to kernel debugging.
> I am trying to connect my Host and PC machines with a Null Modem
> Cable

> and via Hyperterminal. I used the folowing steps to test as per
> help.
> --------------------------------------------------------
> To test the null-modem connection
> On the host computer, click the Start button, point to
> Programs, then point to Accessories, then point to
> Communications, then click HyperTerminal. If HyperTerminal
is
> not installed, install it from the product CD-ROM using
> Add/Remove Programs from Control Panel.
>
> In the Connection Description dialog box, enter a name for
the
> new connection. (The name doesn’t matter.)
> In the Connect To dialog box, click on the Connect using
drop
> down list. Select the COM port corresponding to the port to
> which the null-modem cable is connected on this machine.
>
> Accept the defaults for the COM port properties in the next
> dialog box.
> Repeat steps 1 through 4 for the target computer.
> HyperTerminal is now open and ready for testing. Type in a
> string of characters on the host system. If the null-modem
> cable is properly installed and the correct COM ports were
> chosen within HyperTerminal on both systems, the string of
> characters typed in on the host will be displayed in the
> HyperTerminal window of the target system.
>
>
> --------------------------------------------------------------
>
> After these steps , the hyper-terminal interface says “Connected” at
> the bottom status bar. But When I type from my key board I see
nothing

> on my host nor in my target machine.
>
> I have tried all combinations with the com ports and replaced the
> Cable but no success. Any Ideas.
> Regards,
> Anurag
>
> —
> You are currently subscribed to windbg as:
> xxxxx@positivenetworks.net To unsubscribe send a blank email to
> xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@divassoftware.com To

unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as:
xxxxx@positivenetworks.net To unsubscribe send a blank email to
xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@divassoftware.com To
unsubscribe send a blank email to xxxxx@lists.osr.com

see below
Norbert.

"Duct tape is like the Force. It has a Light Side, a Dark Side and it
holds the Universe together."
---- snip ----

My COM1 Host and target machines work fine with the serial mouse hence
tested.
fine !
1>>My null modem canle in 9 pin female one end and 9 pin female other
end, the help says 9 pin female one end and 25 pin female on the
other.We do not get 25 pin male slot with these new machines.Is this a
problem ? or 9 pin to 9 pin will do.

It is OK to have 9<->9.

2>>When I felt the cable one side was quite warm and the other was not.

Does this signal some thing ? Well this was my second cable that I
bought thinking the first one was faulty.

Use a multimeter and check the wiring.
make sure:
2<--->3
3<--->2
5<--->5
4- -4
| |
6- -6
7- -7
| |
8- -8

or
2<--->3
3<--->2
5<--->5
4<--->6
6<--->4
7<--->8
8<--->7

Any Ideas will be great help.

-----Original Message-----
From: Steve Dispensa [mailto:xxxxx@positivenetworks.net]
Sent: Tuesday, August 10, 2004 9:18 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Unsucessfull test in Hyper terminal

haha... my bad - com1 is irq4. Sorry for the mis-information :frowning:

Other ideas? Nope. Look for a standard serial mouse and try to get it
working on that port. Try kd again only after that mouse works.

-sd

On Tue, 2004-08-10 at 09:09, Anurag Sarin wrote:
> Hello Steve ,
> Thanks for your response . Only irq3 was irq4 in my case.
> Tried it , but no sucess ,any other ideas ?
>
> Regards,
> Anurag
>
> -----Original Message-----
> From: Steve Dispensa [mailto:xxxxx@positivenetworks.net]
> Sent: Tuesday, August 10, 2004 3:36 PM
> To: Kernel Debugging Interest List
> Subject: Re: [windbg] Unsucessfull test in Hyper terminal
>
>
> I do wish serial cables would be less difficult to get working,
> especially for new folks.
>
> - Make sure you have your com ports enabled in the bios
> - don't try to use non-legacy com ports (i.e. no usb com ports, etc)
> - make sure com1 is at 3f8, irq3
> - Try to get a null modem cable, 9-pin female to 9-pin female (don't
> use converters; sometimes they re-cross inside)
> - Make sure the com settings really are identical - I'd test with
> 9600bps, 8 data bits, 1 stop bit, no parity, and no flow control.
>
> When you actually go to modify your boot.ini, you should probably use
> /baudrate:115200 or it'll be too slow.
>
> If none of the above work, you should try hooking up another serial
> device to the ports on each box (i.e. an old mouse or something) just
> to test the physical ports. Older motherboards required a ribbon
> connector between the 9-pin port and the board; perhaps it's wired up
> wrong (the red strip should be by pin 1).
>
> Good luck.
>
> -sd
>
> On Tue, 2004-08-10 at 04:14, Anurag Sarin wrote:
> > Hi all,
> > I am new to kernel debugging.
> > I am trying to connect my Host and PC machines with a Null Modem
> > Cable
>
> > and via Hyperterminal. I used the folowing steps to test as per
> > help.
> > --------------------------------------------------------
> > To test the null-modem connection
> > On the host computer, click the Start button, point to
> > Programs, then point to Accessories, then point to
> > Communications, then click HyperTerminal. If HyperTerminal
is
> > not installed, install it from the product CD-ROM using
> > Add/Remove Programs from Control Panel.
> >
> > In the Connection Description dialog box, enter a name for
the
> > new connection. (The name doesn't matter.)
> > In the Connect To dialog box, click on the Connect using
drop
> > down list. Select the COM port corresponding to the port to
> > which the null-modem cable is connected on this machine.
> >
> > Accept the defaults for the COM port properties in the next
> > dialog box.
> > Repeat steps 1 through 4 for the target computer.
> > HyperTerminal is now open and ready for testing. Type in a
> > string of characters on the host system. If the null-modem
> > cable is properly installed and the correct COM ports were
> > chosen within HyperTerminal on both systems, the string of
> > characters typed in on the host will be displayed in the
> > HyperTerminal window of the target system.
> >
> >
> > --------------------------------------------------------------
> >
> > After these steps , the hyper-terminal interface says "Connected" at
> > the bottom status bar. But When I type from my key board I see
nothing
>
> > on my host nor in my target machine.
> >
> > I have tried all combinations with the com ports and replaced the
> > Cable but no success. Any Ideas.
> > Regards,
> > Anurag
> >
> > ---
> > You are currently subscribed to windbg as:
> > xxxxx@positivenetworks.net To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
>
>
> ---
> You are currently subscribed to windbg as: xxxxx@divassoftware.com To

> unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> ---
> You are currently subscribed to windbg as:
> xxxxx@positivenetworks.net To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>


You are currently subscribed to windbg as: xxxxx@divassoftware.com To
unsubscribe send a blank email to xxxxx@lists.osr.com


You are currently subscribed to windbg as: xxxxx@stollmann.de
To unsubscribe send a blank email to xxxxx@lists.osr.com

---- snip ----

Hello,

* On Thu, Aug 12, 2004 at 04:41:17PM +0200 Norbert Kawulski wrote:

Use a multimeter and check the wiring.
make sure:
2<—>3
3<—>2
5<—>5
4- -4
| |
6- -6
7- -7
| |
8- -8

or
2<—>3
3<—>2
5<—>5
4<—>6
6<—>4
7<—>8
8<—>7

From my experience, only

2<–>3
3<–>2
5<–>5 (GND)

is needed for WinDBG to work.

Regards,
Spiro.


Spiro R. Trikaliotis
http://www.trikaliotis.net/

That true it is only 2,3,5. But he has a cable with 9 pins !
You would want for example a 3<-->7 connection or any other
shortcuts.
Norbert.

"A good deed never goes unpunished."
---- snip ----

Hello,

* On Thu, Aug 12, 2004 at 04:41:17PM +0200 Norbert Kawulski wrote:

> Use a multimeter and check the wiring.
> make sure:
> 2<--->3
> 3<--->2
> 5<--->5
> 4- -4
> | |
> 6- -6
> 7- -7
> | |
> 8- -8
>
> or
> 2<--->3
> 3<--->2
> 5<--->5
> 4<--->6
> 6<--->4
> 7<--->8
> 8<--->7

>From my experience, only

2<-->3
3<-->2
5<-->5 (GND)

is needed for WinDBG to work.

Regards,
Spiro.

---- snip ----

You would not want for example a 3<-->7 connection or any other
shortcuts.

Norbert.

""Criminal Lawyer" is a redundancy."
---- snip ----

That true it is only 2,3,5. But he has a cable with 9 pins !
You would want for example a 3<-->7 connection or any other
shortcuts.
---- snip ----

I got it.
Well the Null modem cable I had, had configuration
2<-->2
3<-->3
I changed it to
2<-->3
3<-->2
It works great now.
The vendor said that the previous one was also a type of null modem
cable but I guess not the one we need .

Thanks all for your help.
Regards,
Anurag
-----Original Message-----
From: Norbert Kawulski [mailto:xxxxx@stollmann.de]
Sent: Thursday, August 12, 2004 9:21 PM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Unsucessfull test in Hyper terminal

You would not want for example a 3<-->7 connection or any other
shortcuts.

Norbert.

""Criminal Lawyer" is a redundancy."
---- snip ----

That true it is only 2,3,5. But he has a cable with 9 pins ! You would

want for example a 3<-->7 connection or any other shortcuts.
---- snip ----


You are currently subscribed to windbg as: xxxxx@divassoftware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Hello,

* On Fri, Aug 13, 2004 at 02:44:23PM +0530 Anurag Sarin wrote:
I got it.

Well the Null modem cable I had, had configuration
2<–>2
3<–>3

Oh, this connection could have broken your computers, as two transmit
lines were connected to each other.

The vendor said that the previous one was also a type of null modem
cable but I guess not the one we need .

No. The cable you have bought could have been used for connection a
modem to the PC (DTE <-> DCE connection), but not to connect two
computer with each other. Anyway, two female connectors is unusual for
DTE <-> DCE (although I have seen this in the past).

I’m happy it works now for you.

Regards,
Spiro.