majors@milton.u.washington.edu (Robert Majors) (08/29/90)
In what order should one binhex & Stuff to move several files across the Internet (also, from a Mac to a Unix box running Dynix, back to a Mac)? I have been told to Stuff first, then binhex the StuffIt archive. I did this, then used the Kermit mode on the Unix box, and sent the archive from my Mac (using Microphone II), once as text, and once as Macbinary (I wasn't sure which). When I brought it back to my Mac in the reverse order, binhex 5.0 wouldn't recognize it. Bob Majors majors@u.washington.edu
demarsee@gamera.acs.syr.EDU (Darryl E. Marsee) (08/30/90)
You should Stuffit, then Binhex; transfer as text; then deBinHex and deStuffit. Do not use Binhex 5.0; it has known bugs. Either use the Binhex/DeBinhexing capability of Stuffit (preferred) or Binhex 4.0.
leonardr@svc.portal.com (Leonard Rosenthol) (08/30/90)
In article <6818@milton.u.washington.edu>, majors@milton.u.washington.edu (Robert Majors) writes: > In what order should one binhex & Stuff to move several files across > the Internet (also, from a Mac to a Unix box running Dynix, back to a > Mac)? I have been told to Stuff first, then binhex the StuffIt > archive. That is the correct order. The reason is that first you want to combine and compress the files into one single 'archive' - Stuffit. Once you have the single file, you then need to convert the file into a form which can be transmitted across the internet - Binhex. > I did this, then used the Kermit mode on the Unix box, and > sent the archive from my Mac (using Microphone II), once as text, > and once as Macbinary (I wasn't sure which). When I brought it > back to my Mac in the reverse order, binhex 5.0 wouldn't recognize it. > When sending archives to a host, you want MacBinary turned off! What MacBinary does it to append a 128 byte header to the file which can be used by another Macintosh for decoding the file on the other side - since you will not be doing this - don't use MacBinary. The other problem here is that you are using Binhex 5.0, and the version which is used for creating files for the Internet is Binhex 4.0 - you can also use the Encode and Decode Binhex functionality in Stuffit and that way you only need one application instead of two! Leonard Rosenthol Software Ventures -- Leonard Rosenthol Software Ventures Corp. MicroPhone II Development Team
russotto@eng.umd.edu (Matthew T. Russotto) (08/30/90)
In article <DEMARSEE.90Aug29144901@gamera.acs.syr.EDU> demarsee@gamera.acs.syr.EDU (Darryl E. Marsee) writes: >You should Stuffit, then Binhex; transfer as text; then deBinHex >and deStuffit. Do not use Binhex 5.0; it has known bugs. Either >use the Binhex/DeBinhexing capability of Stuffit (preferred) or >Binhex 4.0. Binhex 5 has known bugs? That's a new one on me, especially since it was widely used for quite a while on CI$ and BBSs with 8 bit connections. It doesn't do printable characters only, that's all. -- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu .sig under construction, like the rest of this campus.
wiseman@tellabs.com (Jeff Wiseman) (08/31/90)
In article <6818@milton.u.washington.edu> majors@milton.u.washington.edu (Robert Majors) writes: >In what order should one binhex & Stuff to move several files across >the Internet (also, from a Mac to a Unix box running Dynix, back to a >Mac)? I have been told to Stuff first, then binhex the StuffIt >archive. I did this, then used the Kermit mode on the Unix box, and >sent the archive from my Mac (using Microphone II), once as text, >and once as Macbinary (I wasn't sure which). When I brought it >back to my Mac in the reverse order, binhex 5.0 wouldn't recognize it. > That's `cause binhex 5.0 is NOT a newer version of binhex 4.0! Try using binhex 4.0, that might solve the problem. By the way, if you have a direct connection to your unix box from the mac, try stuffing your files on the mac, upload them as MacBinaries, and then use mcvert with the "-Ux" argument to binhex them. One thing after this you should check the end of the file to make sure that there is an empty line at the end (ie. after the last ":" in the binhex format). Mcvert seems to miss this sometimes, especially if the last ":" happens to fit exactly at the end of the column block. Hope this helps! -- Jeff Wiseman: ....uunet!tellab5!wiseman OR wiseman@TELLABS.COM