Mail Archives: opendos/2004/02/07/18:03:49
On 7 Feb 2004 at 19:14, Lindner-Thalmaessing AT t-online wrote:
> Martin Foster and Leonard Erickson asked me for the type of modem I
> have. Well, it's a USRobotics Sportster Voice 33.6 Faxmodem.
Ok, that should be able to (and does, from what you show below)
connect at 31200
> When configuring its WATTCP.CFG with higher rates, the
> following screen output will occur:
>
> *---------
>
> at&FL2M2
>
> OK
> t-online atdt0191011
>
> CONNECT 31200/ARQ
> pktdrvr.bat ppp 2F8 3 115200 60 t-online
> Resident size: 87632
> coreleft: 2560
> COM1 2F8 3: [NS16550A] [rlsd line control] 115200 bps
> MC: int 0 DTR On RTS On CTS On DSR On RI Off CD On
> RX: int 0 chars 0 hw over 0 hw hi 0 fifo TO 0 sw over 0 sw hi 0
> TX: int 0 chars 0 THRE TO 0
> main: connect ppp0 <--> COM1.
> sifdown: IP interface inactive.
> main: COM1, carrier lost.
> Connection terminated.
> PPP link is down, driver not installed.
> The consequence of "main: COM1, carrier lost." is, that the traffic
> then will be interrupted, and out of the modem's speaker a constant
> beep can be heared for some time.
What's probably going on is that the program and the modem aren't
agreeing on the way things should be set up.
One thing that is critical is that the modem has to be set to 115200
bps and then told to *always* talk to the computer at that rate,
regardless of what rate it is talking to the other modem at.
I'll have to look up the settings for "lock baud rate" on a USR.
That's one of the things I do when I first get a modem. And I then
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.
BTW, that long tone indicates that the modem (probably on the other
end) is still trying to talk to you.
Oh yes, another problem with older programs and modern modems is that
it can take well over 30 seconds to get the handshaking finished. So
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.
> So, how should my complete command line look alike for
> - X00 active on com2 only?
> - higher transfer rate than the max 19200 bps under m$dos?
I install X00.SYS in CONFIG.SYS.
But installing it in Autexec or at the command line works much the
same.
X00 E 1
The 1 is support only 1 comm port. The E has something to do with
status messages during install.
Before loading my mailer I run a batch file:
COMMSET.BAT:
loadfix xu set:1:115200:8n1
loadfix xu lock:1:115200:8n1
loadfix xu port:1:on
The loadfix is needed if you've got too much conventional RAM free.
The exe packer used on X00 gets upset if it is loading to an address
that starts below the 64k mark. The usual error message is "packed
file is corrupt".
XU is a utility included with X00. It's used for changing port
settings, and for getting port status.
XU S (after X00 is running) will give you a status report for all 8
of the possible ports. You'll want to pay attention to the line that
says Chip Type. If it lists anything other than 16550A, you may want
to replace your serial port hardware. If it lists 8250, you
*definitely* want to replace it!
Anyway, the first line is a set command. Remember that X00 starts
numbering the ports with 0. So COM2 is port 1.
xu set:1:115200:8n1
sets port 1 (COM2) to 115200 bps, and 8 bit, no parity, 1 stop bit.
The next line
xu lock:1:115200:8n1
*locks* the port to those settings. So any attempt by another program
to change those settings will be ignored.
Finally:
xu port:1:on
turns on (enables) the port for use.
--
Leonard Erickson (aka shadow)
shadow at krypton dot rain dot com
- Raw text -