From: "da Silva, Joe" 

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_01C3F51A.D7E99470
Content-Type: text/plain

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?

Joe.

> -----Original Message-----
> From:	shadow{at}shadowgard.com [SMTP:shadow{at}shadowgard.com]
> Sent:	Sunday, February 15, 2004 12:05 PM
> To:	opendos{at}delorie.com
> Subject:	Re: X00 and other stuff, com speed with m$dos 6.22
> 
> On 14 Feb 2004 at 21:56, Lindner-Thalmaessing{at}t-online wrote:
> 
> > On 07.02.2004 shadow{at}shadowgard.com wrote:
> 
> > > save it into the non-volatile RAM in the modem so I can just do an ATZ
> > > and have the modem be set the way I want it.
> > 
> > What happens then, if I switch the modem's power off?
> 
> The stuff stored in the modem's non-volatile RAM stay until you write 
> over it, Which requires using the AT&W command.
> 
> > > the "time to wait for carrier" setting in any
program needs to be set
> to
> > > 60 seconds. And if there's a setting for how long to wait for logon to
> > > complete before timing out, that needs to be set to 90 seconds. I was
> > > having trouble with that on my uucp connections. I had to find the
> (well
> > > hidden!) setting for time to wait for transfer to start and increase
> it.
> > 
> > My cfg is as follows:
> 
> 
> 
> > Any proposal, what to change?
> 
> Didn't see anything that needed changing. Looks like you need to work 
> on the settings for the modem.
> 
> > > Before loading my mailer I run a batch file:
> > > COMMSET.BAT
> > 
> > Must I also change my $baud in my cfg, when running your commset.bat?
> 
> Nope, because the Lock command will prevent the program from changing 
> the baud rate anyway. Unless it is ill behaved enough to mess with 
> the UART directly.
>  
	-------- snip --------


------_=_NextPart_001_01C3F51A.D7E99470
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable






RE: X00 and other stuff, com speed with m$dos 6.22



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?


Joe.


-----Original
Message-----
From:  
shadow{at}shadowgard.com
[SMTP:shadow{at}shadowgard.com]
Sent:  
Sunday, February 15, 2004 12:05
PM
To:    
opendos{at}delorie.com
Subject:       
Re: X00 and other stuff, com
speed with m$dos 6.22


On 14 Feb 2004 at 21:56,
Lindner-Thalmaessing{at}t-online wrote:


> On 07.02.2004
shadow{at}shadowgard.com wrote:


> > save
it into the non-volatile RAM in the modem so I can just do an
ATZ
> > and
have the modem be set the way I want it.
> 
> What happens
then, if I switch the modem's power off?


The stuff stored in the
modem's non-volatile RAM stay until you write 
over it, Which requires
using the AT&W command.


> > the
"time to wait for carrier" setting in any program needs
to be set to
> > 60
seconds. And if there's a setting for how long to wait for logon
to
> >
complete before timing out, that needs to be set to 90 seconds. I
was
> >
having trouble with that on my uucp connections. I had to find the
(well
> >
hidden!) setting for time to wait for transfer to start and increase
it.
> 
> My cfg is as
follows:


<snip>


> Any proposal,
what to change?


Didn't see anything that
needed changing. Looks like you need to work 
on the settings for the
modem.


> > Before
loading my mailer I run a batch file:
> >
COMMSET.BAT
> 
> Must I also
change my $baud in my cfg, when running your commset.bat?


Nope, because the Lock
command will prevent the program from changing 
the baud rate anyway.
Unless it is ill behaved enough to mess with 
the UART directly.
 
-------- snip --------




------_=_NextPart_001_01C3F51A.D7E99470--

--- Internet Rex 2.29