Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!goofy.apple.com!chesley
From: chesley@goofy.apple.com (Harry Chesley)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Xmodem XCMDs?
Message-ID: <4007@internal.Apple.COM>
Date: 1 Sep 89 16:40:20 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 32
References:<3666@merrimack.edu> <3987@internal.Apple.COM> <2961@quanta.eng.ohio-state.edu>

In article <2961@quanta.eng.ohio-state.edu> czei@quanta.eng.ohio-state.edu 
(Michael Czeiszperger) writes:
>>The HyperCard Serial Port Toolkit (available from APDA) includes an XModem 
>>XCMD.
> 
> Yes, but it doesn't come with instructions on how to use it...

     XModem <command>,<folder path>,<file name>

Where <command> is either "send" or "receive". <folder path> is the folder 
to receive into. And <file name> is the name to give the received file. It 
actually receives into a temporary file in the folder, then renames it to 
the <file name> if and only if the receive is successfull. It does 
straight XModem, and therefore doesn't care if the contents are MacBinary 
or whatever.

There are two other XCMDs, MacBinify and DeMacBinify, which convert a file 
on disk to and from MacBinary format.

     MacBinify <original name>,<MacBinned name>
     put DeMacBinify(<MacBinned name>,<new file name>) into foo

DeMacBinify returns the original name of the file, so to completely 
restore things you need to do a rename to the name returned by 
DeMacBinify. (It doesn't automatically use this name because it might have 
to write over an arbitrary file on disk...)

These XCMDs weren't documented in the normal Toolkit documentation because 
they weren't developed at Apple as a part of the Toolkit. They were 
developed by me on my own time for use with HyperBBS, and at the last 
minute I decided to donate them (and the source code in the case of 
XModem) to the Toolkit...