Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcsvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxj!houxm!whuxlm!akgua!sdcsvax!rfox
From: rfox@sdcsvax.UUCP (Richard Fox)
Newsgroups: net.micro.cbm
Subject: Re: C64/UNIX communication & file xfers
Message-ID: <573@sdcsvax.UUCP>
Date: Tue, 8-Jan-85 13:08:43 EST
Article-I.D.: sdcsvax.573
Posted: Tue Jan  8 13:08:43 1985
Date-Received: Fri, 11-Jan-85 23:26:40 EST
References: <482@sftig.UUCP>
Organization: EECS Dept. U.C. San Diego
Lines: 38

> 
> 		1) Obtain an XMODEM type terminal program for the C64
> 		2) Obtain or write a TERMCAP and place it in /usr/lib/terminfo on the
> 		    UNIX (tm) machine
> 		3) Modify the .profile file on the UNIX (tm) machine
> 


This procedure is a little drawn out and not needed. I have recently (last night)
used xmodem to transfer to and fro unix to the 64. I did not need to declare a
term type to use the program, thus when asked I replied "dumb".
Then I used the xmodem command we have installed on line. If there are unixes
out there without this command then send me a reply and I'll see what I can
do. Anyways after typing the xmodem command on unix I transfer control to
xmodem and tell it what I want to do and the rest happens like magic. 

Here's a procedural example:

UNIX: xmodem rtcf    /* rt=receive text, cf error checking */
64:   upload
	
	
and the rest should be history.

Now this protocol works great for transfer of text files only, unless you 
make some modifications .. it doesn't interpret basic programs because of the
ascii mismatch but since a basic version of xmodem is only 20 blocks it should
be very easy to add the neccessary additions to make it work for basic program
files.


If there are still any questions or suggestions please send mail or post it to 
the net



rich