PM> First, SCFN's docs specifically requested not to use a fast modem
PM> hoping their own 2400's would 'negotiate' yours down to that speed.
IMHO, they didn't know what they were talking about. Unless it's
been told not to, a V.E. Courier, for example, should negotiate a
connect speed down to 300 baud, if that's the best it can do with
the modem on the other end.
PM> What do you mean by a 'locked port'?
You set the port speed on all of your directory entries to a high
speed, like 38400, 57600, or 115200, and let the modem negotiate the
actual connect speed, with the UART buffer and hardware flow control
compensating for the difference. This is because data can move that
much faster between the modem and the PC than it can between modems,
even at the highest connection speeds. (This presumes you've got a
16550, rather than 8250, UART when using an external modem, internal
modems providing their own.)
PM> Yes, XON/XOFF sw flow was off. CTS/RTS hw flow was on. DSR/DTR hw
PM> flow was off.
PM> I tried and tried with the new modem, but the problem persisted. I
PM> have no trouble connecting at all, at any speed up to 28.8. But
PM> that's as far as it goes. I get CONNECT 19200, for example, the
PM> status line says VT102 19200 N81 and Online. But no welcome screen,
PM> no prompt, nothing. I had to Alt-H and go to the TBCS BBS to ask if
PM> anyone else in Pinellas County was getting on-line okay.
PM> At this point I feel convinced that the problem is at their end.
I agree with your conclusion. Once the modems make the connection,
it becomes a software problem. The software should see that there's
been a connection and respond appropriately.
PM> I, however, cannot shrug it off. My rig is a 386/20 with 4MB RAM,
PM> (non-expandable AFAICS), and 512K Video RAM.
That's really not enough memory and the system's really too slow if
you're running Windows.
PM> I thought of trying one of the DOS Internet browsers I've seen
PM> mention of, but I was advised strongly against it.
It's certainly worth a shot, but you've got to connect with the ISP
first.
PM> OBTW, another cause for delay in replying was that TBCS lost its FIDO
PM> feed a couple of times in the interim, and I thought that if I'd had
PM> any replies they'd have got lost.
I know that feeling. I've been telnetting here via AOL, using TFW
as the telnet client, because of persistent problems with the Fido
feed to my "home" bbs. (It seems mail gets through about once a
week and it's about a week old when it does get through.)
--- Blue Wave v2.12
---------------
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)
|