wargo@sdcsla.UUCP (Dave Wargo) (07/24/85)
This is a brief description on the in's and out's of moving things around from a vax to a mac. I picked bits and pieces from the net and came up with this. Any of you who feel that this letter is incorrect or needs updating send me a msg. I will update the file as I see fit and re-post when the need arises. Enjoy Dave Wargo ucbvax!sdcsvax!sdcsla:wargo ******************************************************************************** This short message will try to explain how one goes about moving files from a Unix type system to a Mac. Let's assume for the moment that you have a Unix system and a Mac, and you would like to be able to post and retrieve Mac files from the net. Since you can't post straight data to the net, you need some way to turn Mac files into text and reverse the process. In the past, this was done by fromhex/tohex, but now we have the new, improved compressed xbin format as a de facto standard, so you will want to use that. The first thing you'll need is macput/macget. The latest versions of these are archived in [SUMEX-AIM]<INFO-MAC> and are retrievable through ARPANet. If no one has posted the latest versions of the source, that would probably be a good idea. In case you're not familiar with these programs, they allow an XMODEM transmission to take place between a Mac and a Unix system. Next, you'll need xbin. This program un-compresses the files sent over the net. You should run xbin "xbin filename" and end up with three more files "filename.data, filename.info, filename.rsrc". This is where one now uses "macput". If you "macput filename" everything should move over to the Mac. You will get a sliding scale to let you know how thing are doing. You do not want to type in "macput filename.anything" just "macput filename". Sometimes I have found that something goes wrong "Bad block, Check sum error...". Well macput will continue to send junk, now not THRU your Mac to a file, but TO you Mac for execution. Were talking problems here. You will have to kill the program by typing in a bunch of control x's "^x^x^x^x^x^x". If you get an error you can try again (this has worked for me twice) or use "macput" with the "-u" option. This "-u" transmits the whole kit and kaboodle to the Mac as a text file. If the files gets to the Mac with the "-u" option then you will have to use "BinHex". Albiet, one will have to have "BinHex" on there Mac to use it. Unfortunately this is the old story of being told to look up a word in the dictionary without knowing how to spell the word. Hopefully "BinHex" will move over to the Mac without too much work. So Just say that you get the file over to the Mac with "macput". If it is an executable program then your all set. That is IF you have the application program to run it. Lets just say that someone sends a "Macpicture" image over the net. You "xbin" it and get the three files named "Macpicture.data, Macpicture.info and Macpicture.rsrc" Next you macput it "macput Macpicture" and it gets moved over to your Mac. Well you will need the "Macpaint" program to run it. Get the picture ! Hummm... To post something onto the net run BinHex on your Mac to convert the file. Use macget -u or a text file transfer to send it to the VAX. It should be pointed out that "Macterminal" should be setup for 8bit XON/OFF and talking to a modem. Then type macget on the unix system. Use the mouse to execute "send file" from the "File" menu. This should leave you with as file called "Filename.hcx" on the unix system. From here it can be sent over the net.
ech@spuxll.UUCP (Ned Horvath) (07/29/85)
Re: 'Got Bad Block' Whether it is MacTerminal braindamage or not, macput seems to ALWAYS work if you have disabled XON/XOFF in the Compatibility Settings. With xon/xoff enabled macput seems to fail about half the time. I've given up, I just turn it off, macput lots of stuff, and turn it back on. =Ned=
schuh@geowhiz.UUCP (David Schuh) (07/31/85)
> Re: 'Got Bad Block' > > Whether it is MacTerminal braindamage or not, macput seems to ALWAYS work > if you have disabled XON/XOFF in the Compatibility Settings. With xon/xoff > enabled macput seems to fail about half the time. I've given up, I just > turn it off, macput lots of stuff, and turn it back on. > > =Ned= Ahh. This is interesting, today I had finally decided to ask the net for help with some quirks in the works when I transfer. When I bring my mac in to our facility and can hook it up at 9600 bd, macput and macget work great never a problem (Xon/Xoff chosen no time delays). But when I take it home and use it on my 300 baud modem (acoustic), Puke city. Macput almost always jams up, but I have OK luck with macget. !?!?!?! I will try what you suggested and see if that helps but I dont understand why it should make any difference where my mac is. Perhaps someone could shed some light. PS. I have tried all sorts of settings for pauses between lines and chars.