zappo@hou2e.UUCP (H.LANG) (04/03/85)
With respect to your difficulty using Smartcom II and having extra Line Feeds inserted, there is a Parameter in Smartcom II called "Include Line Feeds". You probably have it set. Tryy toggling it so that an extra line feed is not used. This feature exist since some systems you might communicate have implied line feeds following a carriage return, while others do not. If you still have porblems after trying this, contact me via email directly. Howard Lang hou2e!zappo
ronbe@tekred.UUCP (Little Guy) (04/05/85)
>*** SmartCom send file problem *** > >When I use SmartCom II to send a text file from floopy to unix >(capture using ed), it inserts a LF after every CR, so the file >becomes double-spaced. The same is true for PC-talk III. > >Can some one suggest a fix? I've got a TRS80 Model III with this same problem. I don't know how many other machines don't handle CR and LF right. I'm assuming that we're talking about the same thing... On my machine (and most Rat Shack machines, a carriage return and a line feed are treated the same. That is, both are treated like a CR + LF. A CR should move the cursor to the beginning of the current line, and a LF should move the cursor straight down one line. So when you press ENTER, you probably only send a CR, but the host machine changes it to a CR + LF. Then when it gets echoed back, you get double spacing. I know of no way to fix the termcap to handle this. The simplest solution is to patch your SmartCom program to ignore either CR or LF. However, then you can't use full-screen editors too well. I ended up writing my own terminal program that handles the characters correctly. Good Luck -- Support bacteria - It's the only culture some people have! ...tektronix!tekred!ronbe (Ron Bemis)