Null modem cable problems.

[Devin Smith]

Is there any way to test and see if my null modem cable is any good?

If I open up two Hyperterminals on Windows I can type back and forth,
or if I use Minicom and Hyperterminal I can type from one computer
over the COM port and receive it on the other but when I run ReactOS
in debug mode with the /DEBUG and /DEBUGPORT=COM1 I can't get anything
to come across the communications port.

the /BAUDRATE=19200 and I know all my setting are correct in the
terminal computer that is receiving but I'm unable to get any data at
all..

Is ReactOS not using 8N1 for the parity settings ?

I'm currently trying to figure out why I'm getting a
SESSION4_INITIALIZATION_FAILED bug check error. Maybe ReactOS hasn't
opened up the COM port yet for communications ?

Any help?

Thanks in advance,

Devin

[Magnus Olsen]

Hi
it exists two type of debuing in ros on com port. 
That was some one did point it out for me
one for remote debug witg gcc debuger. 
one that only output only text

if you want simpile text output. use buad rate 115200 it works. 
Ractos are using 8N1 and baud rate 115200.

I am usings baud rate 115200 it works fine.
for text output. I have not try any other debuging option on null cable.

----- Original Message ----- 
From: "Devin Smith" [e-mail]
To: [e-mail]
Sent: Friday, September 10, 2004 6:24 AM
Subject: [ros-general] Null modem cable problems.
> Is there any way to test and see if my null modem cable is any good?
>
> If I open up two Hyperterminals on Windows I can type back and forth,
> or if I use Minicom and Hyperterminal I can type from one computer
> over the COM port and receive it on the other but when I run ReactOS
> in debug mode with the /DEBUG and /DEBUGPORT=COM1 I can't get anything
> to come across the communications port.
>
> the /BAUDRATE=19200 and I know all my setting are correct in the
> terminal computer that is receiving but I'm unable to get any data at
> all..
>
> Is ReactOS not using 8N1 for the parity settings ?
>
> I'm currently trying to figure out why I'm getting a
> SESSION4_INITIALIZATION_FAILED bug check error. Maybe ReactOS hasn't
> opened up the COM port yet for communications ?
>
> Any help?
>
> Thanks in advance,
>
> Devin
> _______________________________________________
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

[Devin Smith]

Hi,

Thanks, it seems to work fine at 115200. I'm very glad my cable
_isn't_ bad. Strange that Freeloader or ReactOS doesn't read my baud
rate line but obviously 115200 is better then 19200.

None the less, I think it should be documented that only 115200 works.
I was using 19200 since this was the default that NT4 (and 2000?) was
set at.

Thanks,

Devin.

On Fri, 10 Sep 2004 07:22:20 +0200, Magnus Olsen
[e-mail] wrote:
> Hi
> it exists two type of debuing in ros on com port.
> That was some one did point it out for me
> one for remote debug witg gcc debuger.
> one that only output only text
>
> if you want simpile text output. use buad rate 115200 it works.
> Ractos are using 8N1 and baud rate 115200.
>
> I am usings baud rate 115200 it works fine.
> for text output. I have not try any other debuging option on null cable.
>
> ----- Original Message -----
> From: "Devin Smith" [e-mail]
> To: [e-mail]
> Sent: Friday, September 10, 2004 6:24 AM
> Subject: [ros-general] Null modem cable problems.
> > Is there any way to test and see if my null modem cable is any good?
> >
> > If I open up two Hyperterminals on Windows I can type back and forth,
> > or if I use Minicom and Hyperterminal I can type from one computer
> > over the COM port and receive it on the other but when I run ReactOS
> > in debug mode with the /DEBUG and /DEBUGPORT=COM1 I can't get anything
> > to come across the communications port.
> >
> > the /BAUDRATE=19200 and I know all my setting are correct in the
> > terminal computer that is receiving but I'm unable to get any data at
> > all..
> >
> > Is ReactOS not using 8N1 for the parity settings ?
> >
> > I'm currently trying to figure out why I'm getting a
> > SESSION4_INITIALIZATION_FAILED bug check error. Maybe ReactOS hasn't
> > opened up the COM port yet for communications ?
> >
> > Any help?
> >
> > Thanks in advance,
> >
> > Devin
> > _______________________________________________
> > ros-general mailing list
> > [e-mail]
> > http://reactos.com/mailman/listinfo/ros-general

[Vizzini]

On Thu, 2004-09-09 at 23:24, Devin Smith wrote:
> Is there any way to test and see if my null modem cable is any good?
>
> If I open up two Hyperterminals on Windows I can type back and forth,

That's the way I usually test this.  If you can do that, your cable
should be fine.

-Vizzini