Path: utzoo!utgpu!watmath!clyde!att!rutgers!ucsd!sdcsvax!odin.ucsd.edu!holtz From: holtz@odin.ucsd.edu (Fred Holtz) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: Thanks to everyone who helped with SIMTEL20 Message-ID: <5616@sdcsvax.UCSD.EDU> Date: 3 Dec 88 09:54:54 GMT References: <1383@virginia.acc.virginia.edu> Sender: news@sdcsvax.UCSD.EDU Organization: University of California, San Diego Lines: 22 In article <1383@virginia.acc.virginia.edu> lhb6v@watt.acc.Virginia.EDU (Laura H. Burchard) writes: >my local UNIX mainframe, and from there to m PC. For anybody >else who has the same problem, the procedure is this: > >ftp to SIMTEL20 >set filetype to tenex (just type 'tenex') >get files >exit ftp >make sure that your modem is set to 7E1. >set kermit file type to binary (on both PC and mainframe) >send files to PC > This procedure will work, but sending a file using binary kermit is slower than uuencoding the file, sending it via text kermit, then uudecoding on the PC side. The uuencoding increases file size about 50%, but it has been my experience that binary kermit file transfers are > 90% longer than text mode transfers. I don't know why kermit has such a large overhead for binary file transfers; any kermit gurus out there that can clue me in?? Fred Holtz holtz@sdcsvax.ucsd.edu --or-- sdcsvax!holtz (last week anyway :-)