Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucdavis!csusac!csuchico.edu!lorner From: lorner@csuchico.edu (Lance Orner) Newsgroups: comp.sys.handhelds Subject: Re: HP48SX Kermit Problems Keywords: 48, file-transfer Message-ID: <1990Mar23.194338.13911@csuchico.edu> Date: 23 Mar 90 19:43:38 GMT References: <1990Mar21.003623.29652@santra.uucp> <31210009@hpcvia.CV.HP.COM> Sender: news@csuchico.edu (USENET) Reply-To: lorner@cscihp.UUCP (Lance Orner) Organization: California State University, Chico Lines: 29 In reference to Kermit transfer with the 48s: I've gotten it the 48 to work with my own jury-rigged cable on the Macintosh, using White Knight software. Everything works well and good, except that the 48 expects linefeeds after every line, but the Macintosh will usually fight with them. On most word processors on the Mac, all of the linefeeds will show up as little square boxes at the beginning of each line. A program like Microsoft Work will seem to have all of the original lines printed like a huge run-on sentence, with little boxes separateing them, but some processors are a little better than this. With Word, if you copy one of those little boxes onto the clipboard, do the global change function to change the box (which you paste into the field) to a newline characted (in this case '^n'), the screen will be formatted correctly. Then, when you save it, save the file as a text file _with line feeds_, then the file will transfer correctly. I had set up my terminal program to strip out all of these linefeeds completely when downloading automaticlly so I wouldn't have have to worry about them later. But now, I had to turn that off, so the linefeeds will come through, so I can change them to newline characters that don't mess up the Mac, and then back to linefeeds on the way out. Sort of a struggle, but you can sort of streamline the system when doing a lot of files at once. Does this make any sence? ----Lance Orner California St. Univ., Chico lorner @ csuchico.edu