Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!topaz!rutgers!nike!ucbcad!ucbvax!sdcsvax!nobody
From: nobody@sdcsvax.UCSD.EDU (Unprivileged user)
Newsgroups: net.micro.pc
Subject: Re: Procomm 2.4.1 bugs
Message-ID: <2150@sdcsvax.UCSD.EDU>
Date: Mon, 20-Oct-86 15:28:08 EDT
Article-I.D.: sdcsvax.2150
Posted: Mon Oct 20 15:28:08 1986
Date-Received: Wed, 22-Oct-86 01:34:54 EDT
References: <216@dayton.UUCP>
Reply-To: rick@beowulf.UUCP (Rick Randall)
Distribution: world
Organization: EE/CS Dept. U.C. San Diego
Lines: 30

In article <216@dayton.UUCP> sjm@dayton.UUCP (Steven J. McDowall) writes:
>
>Having used Procomm 2.4.1 (tm) for a little while now, I still have
>found these various bugs (same as 2.4 suprise!):
>
>    1)  When in vt-100 mode, and in line-wrap (auto wrap) it still
>        wraps at the 80'th character, even if the next character is
>        a C/R or a L/F. It SHOULD wait for the 81'st character before
>        it decides it needs to wrap.

I have reported this problem to the authors, along with my
registration.

>
>    2)  When down loading using the Kermit protocol, it seems to ALWAYS
>        convert N/L (ie. Line Feeds) into C/R L/F pairs. Even if you specify
>        a binary file transfer. Needless to say, this wrecks havok. 
>        No where (at least where I can see :-) do I specify this conversion
>        to take place.
>

I have not experienced this problem -- I have downloaded many
binary files with versions 2.3, 2.4, and 2.4.1.

	Rick Randall    EECS Department 
			University of California, San Diego
			
	decvax\ 	rick@sdcsvax.ucsd.edu
	ihnp4  >--->	sdcsvax  ---> rick
	ucbvax/		rick@sdcsvax.uucp