berger@clio.las.uiuc.edu (12/18/87)
The ProComm implementation of Kermit has some flaws. Parity is very
important. I've had my greatest success with SPACE parity.
Mike Berger
Center for Advanced Study
University of Illinois
berger@clio.las.uiuc.edu
{ihnp4 | convex | pur-ee}!uiucuxc!clio!bergernez@bucc2.UUCP (12/18/87)
/* Written by athena.mit.edu!arwall in comp.sys.ibm.pc */ /* ---------- "Using Kermit from Procomm 2.42" ---------- */ > > I normally use Crosstalk (and its Kermit) to download text and binary > files from MIT's Unix systems....recently I've grown fond of Procomm, > but I haven't been able to get its Kermit to communicate very well at > all with UNIX's Kermit. I would include some diagnostics here, but I'm > not familiar enough to know what's relevant and what isn't--so, if you > have clues about KERMIT, any help in diagnosing and correcting the > problem would be greatly appreciated....e-mail of course.. > > anders > /* End of text from comp.sys.ibm.pc */ I used to have problems with Procomm's KERMIT, too. It seems that Procomm only behaves when the port settings are 8 data bits, 1 stop bit and no parity - no matter what the communication settings should be (our campus computer network uses 7/1/E). To alleviate this problem, I simply change the settings to 8/1/N before the kermit transfer, and restore them to 7/1/E when done. (This can be done with a command file...) Rich Neswold =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= / bucc2!nez ...!ihnp4!bradley!- cyber!xx64194 \ buee730!nez =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "It's a dirty, sadistic job - but somebody gets to do it."