Path: utzoo!attcan!uunet!ogicse!dali!brutus.cs.uiuc.edu!rpi!uupsi!rodan!jfbruno From: jfbruno@rodan.acs.syr.edu (John F. Bruno) Newsgroups: comp.sys.ibm.pc Subject: Re: Procomm - - Something Bet Message-ID: <2649@rodan.acs.syr.edu> Date: 27 Mar 90 15:43:34 GMT References: <90032502290027@masnet.uucp> <1990Mar25.200722.27200@uncecs.edu> <260EB804.17139@maccs.dcss.mcmaster.ca> Reply-To: jfbruno@rodan.acs.syr.edu (John F. Bruno) Organization: Syracuse University, Syracuse, NY Lines: 24 In article <260EB804.17139@maccs.dcss.mcmaster.ca> cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) writes: >In article <1990Mar25.200722.27200@uncecs.edu> mvolo@uncecs.edu (Michael R. Volow) writes: >$I'm also considering switching from Procomm+ to Telix because of the >$internal Zmodem (although the next Procomm+ version may have this). >$Does Telix allow big packet Kermit or Super Kermit? > > As far as I can tell, it only supports plain vanilla Kermit (i.e. up >to 94-byte packets). > > One thing I like about it, though, is that I have yet to make it >crash. I cannot say the same thing for Procomm's Kermit. Telix kermit has a limit of 90 byte packets. I use kermit to transfer stuff between the AT here and a Gould Unix mainframe and a VAX mainframe. Procomm ALWAYS works flawlessly, Telix NEVER works. I use telix for everything except kermit transfers. ---jb >-- > More half-baked ideas from the oven of: >**************************************************************************** >Stephen M. Dunn cs4g6ag@maccs.dcss.mcmaster.ca > = "\nI'm only an undergraduate ... for now!\n";