maxc0849@ucselx.sdsu.edu (Human1 ~InnerTangent~) (11/15/90)
Hello! First, thanks for all those who mailed me about their best modem programs to the "newcommer" -- me :-). The overall people prefer the Zterm for it's protocols and vt100 emulation. Now the problem: I need to transfer binary files (.hqx) between my UNIX account and some school Macs that's hooked up with network. cond. We have software on these Macs that let us loggin into the UNIX BSD machine. No problem. But, when it comes to transfering files, it only support something called "MacBinary". not Zmodem, Ymodem, or Xmodem. Is there a solution to my problem? I'm very ignorant about all these Mac things. could someone suggest me a way to go? Thank you. (Please reply by net-mail. I'll post a summary here later.) I really appreciate any help/suggestions you can offer!! Sincerely, Bill.
n074ez@tamuts.tamu.edu (Joe Bezdek) (11/15/90)
I've got almost exactly the same problem. So if anyone has any answers, please either post it on the net or email me a reply as well. Thanks! Joe
topix@gpu.utcs.utoronto.ca (R. Munroe) (11/15/90)
In article <1990Nov14.194720.19950@ucselx.sdsu.edu> maxc0849@ucselx.sdsu.edu (Human1 ~InnerTangent~) writes: > > Hello! > > First, thanks for all those who mailed me about their best modem >programs to the "newcommer" -- me :-). The overall people prefer the >Zterm for it's protocols and vt100 emulation. > > Now the problem: > > I need to transfer binary files (.hqx) between my UNIX > account and some school Macs that's hooked up with network. > >cond. We have software on these Macs that let us loggin into the UNIX >BSD machine. No problem. But, when it comes to transfering files, it >only support something called "MacBinary". not Zmodem, Ymodem, or Xmodem. > > Is there a solution to my problem? I'm very ignorant about all these >Mac things. could someone suggest me a way to go? Thank you. > > (Please reply by net-mail. I'll post a summary here later.) > > I really appreciate any help/suggestions you can offer!! > > Sincerely, > Bill. Basically, what you need is a communications package that supports kermit transfers. Kermit is a public domain transfer protocol from Columbia University (I think it's Columbia - imagine the flames if I'm wrong). Most Mac communications programs offer kermit transfers: MacKermit (which is public domain - I'm using it on my Mac right now, logged onto the University of Toronto's general-purpose unix machine), MicroPhone II (you pay for this one), and VTPro (costs $, too) come immediately to mind. Since you seem to be able to log onto the unix system from the Mac, I won't spend any time on that part. Once you're in and you want to send a binary file from the unix box to the Mac, try this procedure: 1. On the Mac - find the menu choice that selects kermit transfer options and set the transfer mode to Binary (as opposed to Text or ASCII). This will be in a different place in different programs so I leave it as a bit of detective work for the reader. 2. On the unix side - type: kermit -s yourfile.xxx -i The -i option tells the unix kermit to send in binary mode. 3. On the Mac side - select Receive Kermit from the File menu (Note: the File menu is where 'Receive Kermit' is in most programs but not all of them). Some programs will receive the file and give it the same name as the unix system; others will ask you to name the incoming file. To send a file to a unix system: 1. Same as above. 2. On the unix side - type: kermit -r -i You don't give it an incoming name, it will name the file whatever it's called on the Mac 3. On the Mac side - select Send Kermit (or Send File, or whatever your program calls it) from the File menu. A couple of notes: - If the file you are sending is ASCII don't select the Binary transfer mode option on your Mac. Instead, select Text (or sometimes ASCII) mode. On the unix side use, for sending, kermit -s yourfile.xxx for receiving, kermit -r Notice that the -i option is gone - that's only for binary. - If you want to complicate things more, find MacCompress and Tar for your Mac (Mac BBS or archive sites). They are both either shareware or freeware programs that do exactly what compress and tar do on a unix system. A typical session might look like this: 1. On the unix side: tar cvf mytarfile.tar file1 file2 file3 ... filen compress mytarfile.tar 2. On the Mac side: Enter communications program - set mode switch to Binary 3. On the Unix side: kermit -s mytarfile.tar.Z -i 4. On the Mac side: Select 'Receive File' from the File menu. wait. get a coffee. wait some more. watch 3 or 4 Twin Peaks episodes. wait some more. (modems and serial lines aren't the quickest way of transfering files - big files take lots of time) Exit comm program. Enter MacCompress. Decompress myfile.tar.Z Note: if you compress files with MacCompress that are going to be sent to a unix system, choose Unix Format in the Format menu and, if you are compressing a binary file, deselect CR<<->>LF under the Options menu. Exit MacCompress. Enter Tar. Extract files from myfile.tar. There you go. Easy ain't it. Good Luck Bob Munroe topix@utcs.utoronto.ca
johnston@oscar.ccm.udel.edu (11/15/90)
In article <1990Nov15.022708.6324@gpu.utcs.utoronto.ca>, topix@gpu.utcs.utoronto.ca (R. Munroe) writes. >In article <1990Nov14.194720.19950@ucselx.sdsu.edu> maxc0849@ucselx.sdsu.edu (Human1 ~InnerTangent~) writes: >>cond. We have software on these Macs that let us loggin into the UNIX >>BSD machine. No problem. But, when it comes to transfering files, it >>only support something called "MacBinary". not Zmodem, Ymodem, or Xmodem. >> Is there a solution to my problem? >> >> (Please reply by net-mail. I'll post a summary here later.) My net-mail reply bounced, and I think that the last follow-up may have missed an important point. The 'software' described above sounds suspiciously like NCSA telnet; it's the only terminal emulation package I can think of with the word MacBinary as a main menu item. If so, the excellent description of unix kermiting posted by <topix@gpu.utcs.utoronto.ca> neglects the really easy way of doing host <--> Mac transfers! NCSA telnet can be set up to gives the Mac its own IP address. The ftp process is initiated with a simple menu command; the user need only set the file type to binary or ascii and then get and put. The implementation of ftp is fairly robust: if the user imagines that the Mac is a remote host, the familiar ftp commands are available. For example, the command 'ls' lists Mac directories, 'cd' changes volume/path, and 'get' sends a file from the Mac to the host. Seems backwards at first, but it sure as hell is fast! So, Bill (maxc0849@ucselx.sdsu.edu), I think you're actually one of the *lucky* ones. If they could only get NCSA telnet and ftp to work by modem on my noisy phone line! ........ ;-) Bill (johnston@oscar.ccm.udel.edu)
headley@zazen.macc.wisc.edu (George Headley) (11/16/90)
In article <1990Nov14.194720.19950@ucselx.sdsu.edu> maxc0849@ucselx.sdsu.edu (Human1 ~InnerTangent~) writes: > Now the problem: I need to transfer binary files (.hqx) between my > UNIX account and some school Macs that's hooked up with network. I am sure I'll be corrected (flamed) if I'm wrong about this (EMail PLEASE). I am almost positive that by convention files with the .hqx extension had been put through BinHex 4.0 to turn them from binary into ASCII so that the problems of binary tranfer could be avoided, if this is really the case several of Bill's problems are solver. George _______________________________________________________________________________ George Headley Office: (608) 262-7240 Technical Support Consultant Academic Computing Center Internet: headley@macc.wisc.edu University of Wisconsin - Madison Bitnet: headley@wiscmacc.bitnet -- _______________________________________________________________________________ George Headley Office: (608) 262-7240 Technical Support Consultant Academic Computing Center Internet: headley@macc.wisc.edu University of Wisconsin - Madison Bitnet: headley@wiscmacc.bitnet
mazu@terre.DMI.USherb.CA (Marc Mazuhelli) (11/16/90)
In article <1990Nov15.022708.6324@gpu.utcs.utoronto.ca> topix@gpu.utcs.utoronto.ca (R. Munroe) writes: >Basically, what you need is a communications package that supports >kermit transfers. Kermit is a public domain transfer protocol >from Columbia University (I think it's Columbia - imagine the flames >if I'm wrong). Most Mac communications programs offer kermit transfers: >MacKermit (which is public domain - I'm using it on my Mac right now, >logged onto the University of Toronto's general-purpose unix machine), >MicroPhone II (you pay for this one), and VTPro (costs $, too) come >immediately to mind. Unfortunately, ZTerm doesn't support Kermit (yet; I don't know about future releases...) Kermit is a *v e r y s l o o o o w* protocol; ZModem is much better, and it's a lot more automatic! I think a better solution would be to install rz and sz (I think they are in the publick domain) on the Unix host. There may be versions of rz and sz or of other programs that support zmodem on Unix on apple.com. Sorry I can't be sure about where to get it; they're already installed on our system. With ZTerm, you just need to log on to your host, go to the right directory and type "sz files", with wildcards if you like, and ZTerm should start receiving the files without any other intervention! You can also program the name of the command that receives files on your Unix host in ZTerm (in our case, rz), and when you want to transfer files from the Mac to the host, just issue the Send Zmodem command in ZTerm, choose the files and it will invoke the rz command automatically! It's great! You would also wait *a lot* less than with Kermit. It's amazing to see how the send or receive light on a modem says on continuously while transfering with Zmodem. By contrast, with kermit, it's on for a short period and off a while, then on and off again, ... I use our GatorBox to transfer files from our Sun to my Mac when I'm at work, but I occasionaly use ZTerm with sz when I'm at home and I don't want to wait until the next working day. Hope this helps! -- { Marc Mazuhelli | professeur } { internet: mazu@dmi.USherb.CA | Departement de math-info. } { <this space intentionaly ... | Universite de Sherbrooke } { ... left blank> | Sherbrooke, Quebec, Canada }
cmorgan@ooc.uva.nl (Chris Morgan/RIKS) (11/27/90)
maxc0849@ucselx.sdsu.edu (Human1 ~InnerTangent~) writes: > I need to transfer binary files (.hqx) between my UNIX > account and some school Macs that's hooked up with network. >cond. We have software on these Macs that let us loggin into the UNIX >BSD machine. No problem. But, when it comes to transfering files, it >only support something called "MacBinary". not Zmodem, Ymodem, or Xmodem. I think the best solution here is to get hold of a copy of NCSA Telnet for your Mac. NCSA Telnet (available from sumix I think) supports FTP like your UNIX machgine does (should). Trasnfereing files is simplicity in itself - simply hit apple-f and a connection is automatically opeden up between your Mac and the remote UNIX host. At this point it is the UNIX host that is controlling things. now simply type get (mac to UNIX) or send (UNIX to Mac) file_name <cr>. Ftp will send or receive your file in seconds. NCSA Telnet requires that you configure the accompanying Config.tel file. But this is no problem simply add the following line for your UNIX host at the bottom somewhere - name=host_name; hostip=host_ip_number Depending on what type of Mac you are using the following line must appear also in the config.tel file - hardware=Ethernet or hardware=EtherSe If you are using an Ethernet network then these lines will speed things up a bit - mtu=1024 maxseg=1024 rwin=4096 Hope this is all useful - if all else fails, you can obtain a copy of the documentation for NSCA Telnet also from sumix (I think). Chris Morgan cmorgan@ooc.uva.nl