Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!MTSG.UBC.CA!Les_Ferch. From: Les_Ferch.@MTSG.UBC.CA Newsgroups: comp.sys.apple Subject: Macintosh-->ProDOS Message-ID: <2085792@mtsg.ubc.ca> Date: 24 Feb 90 00:10:50 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 37 > Even!if!I@knew.my.path,I!wouldn't.tell!YOU! Sure, ask a bunch of questions without giving a mailing address... (By the way, in case you didn't know, the polite thing to do is give an address so people can send replies directly to you, if they choose, and then you can summarize for the rest of us.) Anyhow, I know there has been a deluge of responses to this, but in case none of them helped and you want to be even more confused, here's mine: I'm afraid your problem wasn't very clearly stated so I'll just try to give you some useful information. TEXT FILES (includes BINSCII and BINHEX files) - be wary of EBCDIC(IBM mainframes)/ASCII(most others) translation problems - transfer as TEXT files (ie. don't use binary mode) - BINSCII and BINHEX are both text format bot NOT the same format BINARY FILES (includes Shrinkit, Stuffit, Binhex5[aka MacBinary] files) - use BINARY or IMAGE transfer modes with ftp or Kermit - Shrinkit is NOT the same format as Stuffit GETTING FILES FROM MAC TO GS (it's simple) - Use Apple File Exchange (AFE) on the Mac (comes with the Mac System Software) - Insert a formatted GS 800K disk after firing up AFE. - Do NOT use any translation at all (ie. use "Default Translation", which is just a straight copy) for TEXT or BINARY files. MUNGED FILES - BINSCII files sent via email are often munged by mailers that like to do silly, inexplicable things. I find it impossible to email BINSCII files between myself (in Vancouver, B.C.) and a net-friend in Florida. - Check BINSCII files with a text editor (are there lines shorter than other lines? Are extra characters added at the beginning of lines? Are there "garbage" characters in the file?) Les_Ferch@mtsg.ubc.ca