ccasths@pyr.gatech.EDU (Scott Hinckley) (06/18/88)
I have been able to download files to our mainframes with no problem using FTP. My problem has been in getting them up to my Apple. The only way I have to get them is to list them to a screen and capture the buffer. The downside of this is that there is a carriage return (or maybe it is a line feed) at the end of each 80col. This means that all program lines (in an EXECable file) running over 80col die during EXEC. The file I am trying to get will allow me to do direct file transfers but until then... Any suggestions on how to get rid of those linebreaks? Appleworks re-inserts them when writing to an ASCII file on disk. +=======================================================================+ |Scott Hinckley - OCS User Assistant AKA - Galaxy's End | |Georgia Insitute of Technology, Atlanta Georgia, 30332 | |uucp: ...!gatech!pyr!ccasths | |ARPA: ccasths@pyr.gatech.edu | +=======================================================================+
SEWALL@UCONNVM.BITNET (Murph Sewall) (06/20/88)
> I have been able to download files to our mainframes with no problem using >FTP. My problem has been in getting them up to my Apple. The only way I The conventional usage refers to the host (mainframe) as "up" (use ftp to transfer to mainframe and 'download' to Apple). >have to get them is to list them to a screen and capture the buffer. The >downside of this is that there is a carriage return (or maybe it is a line >feed) at the end of each 80col. This means that all program lines (in an >EXECable file) running over 80col die during EXEC. The file I am trying >to get will allow me to do direct file transfers but until then... >Any suggestions on how to get rid of those linebreaks? Appleworks re-inserts >them when writing to an ASCII file on disk. What commware are you using? Surely your mainframe supports Kermit; if you haven't Kermit already, you probably can "capture" the EZ Install EXECs because they are < 80 columns. Kermit will download files that will EXEC just fine if they haven't been corrupted before they arrive at your mainframe. EXEC expects <cr> at the end of lines, but lines may be as long as 255 characters. Depending on what's being EXEC'd, EXEC may not like LFs (^J) a whole lot (LF's crash EXECUTIONER files). I'm not an AppleWorks user, but you should be able to define the page width to 255 and define a "printer" that doesn't want LF's (LF=NO) so that you can write an ASCII file to disk that'll work. --------------------- Disclaimer: The "look and feel" of this message is exclusively MINE! (subject to change without notice; void where prohibited) ARPA: sewall%uconnvm.bitnet@mitvma.mit.edu Murphy A. Sewall BITNET: SEWALL@UCONNVM School of Business Admin. UUCP: ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL University of Connecticut
STEIN@UCONNVM.BITNET (Alan Stein) (06/22/88)
Appleworks allows you to set a platen width up to 13". At 10 cpi, that would allow 130 characters provided that the left and right margins are set to 0. Fortunately, one can also set the number of characters per inch; unfortunately, I don't know the limit on that, although I recall using at least 16 cpi, which would get you up to 208 characters per line. ARPA: stein%uconnvm.bitnet@mitvma.mit.edu Alan H. Stein BITNET: STEIN@UCONNVM University of Connecticut UUCP: ...ihnp4!psuvax1!UCONNVM.BITNET!STEIN at Waterbury CompuServe: 71545,1500 Genie: ah.stein Department of Mathematics