Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site amdcad.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!amdcad!jimb
From: jimb@amdcad.UUCP (Jim Budler)
Newsgroups: net.micro.mac
Subject: Re: macput/macget & Red Ryder problem
Message-ID: <8757@amdcad.UUCP>
Date: Sun, 26-Jan-86 23:42:45 EST
Article-I.D.: amdcad.8757
Posted: Sun Jan 26 23:42:45 1986
Date-Received: Tue, 28-Jan-86 05:16:39 EST
References: <27000013@convexs>
Reply-To: jimb@amdcad.UUCP (Jim Budler)
Organization: AMD, Sunnyvale, California
Lines: 29

In article <27000013@convexs> allison@convexs.UUCP writes:
>
>I'm having trouble getting Red Ryder (and Smartcom, for that matter) to do
>xmodem file transfer with macput and macget.  Red Ryder's xmodem works fine
>...
>If these programs work with MacTerminal ONLY, would someone mind explaining
>why?  If that's the case, it would seem that MacTerminal's xmodem protocol
>isn't "standard" xmodem, since Red Ryder's xmodem works with Compuserve.

That's the case.  MacTerminal's xmodem ( when in the mac-to-mac mode) is 
non-standard. MacPut/MacGet were written to work with that form of xmodem.

Red Ryder opted for the MacBinary mode of transferring the two forks over
MacTerminal's mode.  MacBinary has the advantage that it works with standard
xmodem, or kermit, while MacTerminal's method required a variation.

Red Ryder and MacBinary are newer than MacTerminal and macput/get, and
MacBinary, which requires an eight bit data path, is not considered
acceptable for Usenet binary file transfers.

Now that MacBinary will be more standard (MacTerminal2.0 includes it)
a binhex to MacBinary conversion program may come along soon.
-- 
 Jim Budler
 Advanced Micro Devices, Inc.
 (408) 749-5806
 Usenet: {ucbvax,decwrl,ihnp4,allegra,intelca}!amdcad!jimb
 Compuserve:	72415,1200