Mail Archives: opendos/2004/02/17/21:12:04
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C3F5C4.664726C0
Content-Type: text/plain
Hmmm ... If the program _doesn't_ mess around with the
UART registers, it _can't_ use anything higher than 19k2.
If it _does_ mess around with them, then it will bypass X00
anyway. So, how can X00 help solve the "I can't get more
than 19200 baud" problem? I know there has been lots of
discussion involving lots of software, etc. that I'm unfamiliar
with, but I thought the original problem was an inability to
go beyond 19k2. Perhaps the software in question can be
configured to _either_ use Int 14h to set baud rate or mess
around with the UART registers. In that case, it needs to be
configured to do the latter, because AFAIK, Int 14h doesn't
support > 19200 baud (or 9600 for XT). Or have I missed
something here ... ?
Joe.
> -----Original Message-----
> From: shadow AT shadowgard DOT com [SMTP:shadow AT shadowgard DOT com]
> Sent: Wednesday, February 18, 2004 7:32 AM
> To: opendos AT delorie DOT com
> Subject: RE: X00 and other stuff, com speed with m$dos 6.22
>
> On 17 Feb 2004 at 16:56, da Silva, Joe wrote:
>
> >
> > Well ... that's just about all programs, they all mess around with
> > the UART registers to set baud rates > 9600 (XT) or > 19200 (AT)
> > because, AFAIK, the Int 14h services do not cater for baud rates
> > higher than this. I wonder if that's the problem - the software here
> > relies on Int 14h services to set baud rate and hence cannot set
> > anything beyond 19200?
>
> That's *why* I suggested X00. If the progran is using Int 14 services
> as opposed to directly accessing the UART, then X00 will *ignore the
> command to change the baud rate and leave it at what it was "locked"
> at.
>
> --
> Leonard Erickson (aka shadow)
> shadow at krypton dot rain dot com
>
------_=_NextPart_001_01C3F5C4.664726C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: X00 and other stuff, com speed with m$dos 6.22</TITLE>
</HEAD>
<BODY>
<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Hmmm ... If the =
program _doesn't_ mess around with the</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">UART registers, it =
_can't_ use anything higher than 19k2.</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">If it _does_ mess =
around with them, then it will bypass X00</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">anyway. So, how can =
X00 help solve the "I can't get more</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">than 19200 =
baud" problem? I know there has been lots of</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">discussion =
involving lots of software, etc. that I'm unfamiliar</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">with, but I thought =
the original problem was an inability to</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">go beyond 19k2. =
Perhaps the software in question can be</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">configured to =
_either_ use Int 14h to set baud rate or mess</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">around with the =
UART registers. In that case, it needs to be</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">configured to do =
the latter, because AFAIK, Int 14h doesn't</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">support > 19200 =
baud (or 9600 for XT). Or have I missed</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">something here ... =
?</FONT>
</P>
<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Joe.</FONT>
</P>
<UL>
<P><FONT SIZE=3D1 FACE=3D"Arial">-----Original Message-----</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">From: </FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">shadow AT shadowgard DOT com =
[SMTP:shadow AT shadowgard DOT com]</FONT>
<BR><B><FONT SIZE=3D1 FACE=3D"Arial">Sent: </FONT></B> <FONT =
SIZE=3D1 FACE=3D"Arial">Wednesday, February 18, 2004 7:32 AM</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">To: </FONT></B> <FONT SIZE=3D1 =
FACE=3D"Arial">opendos AT delorie DOT com</FONT>
<BR><B><FONT SIZE=3D1 =
FACE=3D"Arial">Subject: </FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Arial">RE: X00 and other stuff, com speed =
with m$dos 6.22</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">On 17 Feb 2004 at 16:56, da Silva, Joe =
wrote:</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">> </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">> Well ... that's just about all =
programs, they all mess around with </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">> the UART registers to set baud =
rates > 9600 (XT) or > 19200 (AT) </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">> because, AFAIK, the Int 14h =
services do not cater for baud rates </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">> higher than this. I wonder if =
that's the problem - the software here </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">> relies on Int 14h services to =
set baud rate and hence cannot set </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">> anything beyond 19200? </FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">That's *why* I suggested X00. If the =
progran is using Int 14 services </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">as opposed to directly accessing the =
UART, then X00 will *ignore the </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">command to change the baud rate and =
leave it at what it was "locked" </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">at.</FONT>
</P>
<P><FONT SIZE=3D2 FACE=3D"Arial">--</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Leonard Erickson (aka shadow)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">shadow at krypton dot rain dot =
com</FONT>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C3F5C4.664726C0--
- Raw text -