home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!fetrow
- From: fetrow@biostat.washington.edu (David Fetrow)
- Newsgroups: comp.archives.msdos.d
- Subject: Re: *** WHAT'S THE BEST COMM PROTOCOL ***
- Message-ID: <1992Dec22.060156.21865@u.washington.edu>
- Date: 22 Dec 92 06:01:56 GMT
- Article-I.D.: u.1992Dec22.060156.21865
- References: <1992Dec21.181829.4391@porthos.cc.bellcore.com> <1992Dec21.195526.29197@uwasa.fi> <BzMsK9.8y0@acsu.buffalo.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: Biostatistics, School of Public Health, Univ. of Wash.
- Lines: 28
-
- In article <BzMsK9.8y0@acsu.buffalo.edu> v393vlqr@ubvmsb.cc.buffalo.edu (Daniel W. Emmer) writes:
-
- >In my limited experience, Zmodem beats Kermit easily. The implementations
- >of Kermit that I've used (VAX/VMS and IBM/CMS) are both far too slow
- >(barely faster than XMODEM), running in the 7 to 9K per minute range w/ my
- >2400 bps modem (very approximate times; I haven't used it in a while...).
-
- Let's get very specific about what you need to do to make Kermit run at near
- Zmodem speeds. Here are the settings I use:
-
- set send packet 2000
- set rec packet 2000
- set window 2
-
- ..no claim that this is optimimum for your (or any situation) but it does
- speed up kermit something fierce for me; especially at higher serial speeds.
-
- Zmodem is essentially Xmodem with bigger packets and sliding
- windows (plus a few nice extra enhancements) which is about what these commands
- do to any reasonably recent and complete Kermit. Kermits usually are set
- up to use the ancient settings by default for backwards compatability,
- which makes it look a lot worse than it is if you don't take the time
- to experiment a bit.
-
-
- --
- -dave fetrow- INTERNET: fetrow@biostat.washington.edu
- BITNET: fetrow@uwalocke
-