Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!mcnc!ecsvax!mvolo From: mvolo@ecsvax.UUCP (Michael R. Volow) Newsgroups: comp.sys.ibm.pc Subject: Re: PROCOMM PLUS bugs Message-ID: <4735@ecsvax.UUCP> Date: 5 Mar 88 14:46:20 GMT References: <9826@shemp.CS.UCLA.EDU> <4686@ecsvax.UUCP> <3629@cup.portal.com> <6606@iuvax.cs.indiana.edu> Organization: UNC Educational Computing Service Lines: 30 Summary: Generic PCKermit does better In article <6606@iuvax.cs.indiana.edu>, bobmon@iuvax.cs.indiana.edu ([bob, mon]) writes: > I've tried the TestDrive package from simtel20 for a while, and I really am > bothered by some things. Especially, the backquote key (or any other > PRINTABLE key) is used to turn the menu line on/off. Is this a deliberate > > > >Heck, with either Procomm 2.4.2 or Procomm Plus, when I download > >binary files from our usenet vax node to my pc, the packets are often > >45-60 bytes only! They are 90 bytes on upload. I like the versa- > > Are you sure this isn't being caused by values > 127 being sent as two bytes? > Does mskermit do better on binary files? Regarding packet size on MSKermit-->Procomm Kermit downloads, Procomm Kermit shows variable packet sizes, but usually in the range of 40-70, but generic PCKermit shows 90 byte packets. So I don't know if the packets are the same size but the screen display is different, or what. I thought that it might be the handling of >ASC 127 characters, but why the difference between the two programs. Procomm Kermit uploads of binary files to MSKermit are 90 bytes. And downloads from our local 8-bit BBS (RBBS) to my PC using Kermit also show 40-70 byte packet size in Procomm's Kermit. Regarding Procomm's menu trigger key, this can be changed or turned off in Procomm configuration program eneral, . Michael Volow, M.D. Dept of Psychiatry, Durham VA Medical Center, Durham, N.C. 27705 919 286 0411 mvolo@ecsvax.UUCP