🚀 go-pugleaf

Andrys D Basten (andrys@netcom.com) wrote:
> In article <jnavasD0yvMs.Muy@netcom.com>, John Navas <jnavas@netcom.com> wrote:
> >Andrys D Basten (andrys@netcom.com) wrote:
> >
> >> >    Micropolis Corp ........... BBS ................... 818-709-3310 2400bps
> >
> >> I was able to get into this 709-3310 number with a 38400bps connection.
> >
> >
> >Was that super-V.34 or subpar-ISDN?  <grin>  (That's your
> >computer-to-modem speed, not the modem-to-modem speed.)

> Thanks for the email copy .  I didn't realize it was here as well.

> You may not realize it but others understand what calling in at 38400bps
> means.

> The point is that you cannot dial in at certain stated ascii-text speeds
> (after compression) unless the two modems can handle them.  The original
> note said that the bbs was '2400 bps' - just not so.  Basically, I was
> calling in at 14400, which is quite a difference, and the lines working
> well at 38400 for text transfers was worth a mention.  Not all 14400
> connections do.


Nice scramble.  <g>  Your posting was at least unclear, since you did *not*
"connect" at 38400, and since a serial port speed of 38400 can be used for
*any* connect speed (even 2400 bps).


> By the way, it isn't just computer to modem speed; it's the fact that
> allowing your hardware to use the available 38400-57600 compressed speeds,
> allows compressible ascii text to be sent at 3-4 times the speed depending
> on the connection you set.


That wouldn't seem terribly important for a support BBS where bulk
compressible text transfers are relatively rare.  Or am I missing
something?  ;-)


> 57600 does not work on certain boards very well,
> even with my 16550AFN uart, while it does on other boards, so I dial in at
> 38,400 to ensure quicker transfers that don't have to wait for resends.


Then there is something wrong with your system -- I use 57600 (or higher)
for *all* connections without any problems.

--
Best regards and happy holidays,
John  <JNavas@Netcom.com>