TIP: Click on subject to list as thread! ANSI
echo: maximus
to: CHRIS HOLTEN
from: JACK SMITH
date: 1997-06-16 08:23:00
subject: Bogus Baud rates!!!

On Jun 15, 1997, Chris Holten wrote:
 JS> No problem there, Chris.  I've been working with modems/ports for about
 JS> 12 years and your statements are correct.  Took me around a week to get
 CH> Hmmm, browsing the web? My ISP, running sun sparc
 CH> workstations with cisco routers only runs thier baud rate
 CH> (not locked) at either 38400 or 57600 and don't use modem
 CH> compression, so even though I lock at 115200, it doesn't do..
Yep.  I hear that but both ISPs I use lock at 115200 with compression 
abled.
 CH> Lots of fidonet BBS sysops run with compression disabled
 CH> because they get a bit better throughput when xfering
 CH> compress files (2-3% better), but they don't get squat
 CH> transferring text. I suspect some ISP's run with thier modem..
Never did that, never will. ;)  I _can_ see the wisdom in shutting off MNP5 
though.
 CH> Hee Hee, almost 10 years ago, long before there were modems
 CH> being used in the fidonet that could lock baud at 115200, I
 CH> wrote a DOOR program that would run 115200 baud simply...
Chris, this is quite a rundown and I'm saving it for future reference.  Like 
you, I've read countless "lies" concerning this subject over the past nine 
years, starting when I got my first "high-speed" modem, a 9600 BPS USR HST.  
I hooked it to an 8mhz XT machine and was told that this wouldn't work well-- 
if at all.  Hogwash!  I put in a 16550 and consistently achieved 1105 CPS on 
archived file xfers.  The DTE was set at 19200 which was as high as the modem 
would handle.
 CH> Turns out desqview is a -horribly- slow multitasker when
 CH> doing screen writes, in most cases much much slower writing
 CH> text to the screen than even 16 bit windows, so with a
 CH> typical 386/486 desqview setup, locking the baud at rates
 CH> higher than 38,400 really didn't make much difference in..
That's the truth also.  I ran DV (on a 486) for a couple of years and 
anything above 38400 was a useless endeavor, to say nothing of the problems I 
had with a couple of doors which, BTW, seemed to run/display fine under 
straight DOS with a port speed of 57600.
 CH> that it didn't matter above 38400 baud. I think the reason
 CH> that fidonet sysops thought desqview was better, was because
 CH> desqview didn't drop charactors like 16 bit windows did.
Ahh... but I'm currently running WfWg 3.11 with the 3rd party Cybercom driver 
and ADF as the FOSSIL for the mailer and Max.  No character dropping here and 
I sometimes get 3300 CPS on a ZIP file xfer.  Phone line quality has the 
greatest effect on this, of course.  Screen displays are quite a bit faster 
than they ever were with DV.
 CH> .. X00 by Ray Guinn was absolutely the sorriest
 CH> FOSSIL driver to use in windows that there ever was and..
Amen.  X00 was nothing short of a total disaster when I tried it with WfWg. 
Never really gave BNU a chance when I found that ADF would work quite nicely 
even with the DTE at 115200.
Maximus/NT 3.01b1:
Now for a question.  I'm interested in running the above under Win95 but I've 
been told that it can't be done with a Win95 mailer.  I've also been told the 
reason for this concerns Win95's 16-bit command processor.  So the question 
is this: What do you think would happen if I installed a 3rd party 32-bit 
command processor under Win95 and tried it?
 -Jack
  ogre@nashville.com
... Always listen to what experts say can't be done. Then do it.
--- Squish/386 v1.11
---------------
* Origin: UltraTech - Nashville, TN ftpMS Hub {V.34/V.FC} (1:116/30)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.