Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site fortune.UUCP
Path: utzoo!watmath!clyde!floyd!harpo!ihnp4!fortune!phipps
From: phipps@fortune.UUCP (Clay Phipps)
Newsgroups: net.micro.pc
Subject: Back To PC-Talk-II / Re: Request Help With PC-Talk XModem Protocol
Message-ID: <3047@fortune.UUCP>
Date: Thu, 12-Apr-84 18:32:07 EST
Article-I.D.: fortune.3047
Posted: Thu Apr 12 18:32:07 1984
Date-Received: Fri, 13-Apr-84 21:00:59 EST
References: <848@ihuxi.UUCP>
Organization: Fortune Systems, Redwood City, CA
Lines: 29

I know that this doesn't address the problem as posed,
but may provide an alternative solution.

I am still using PC-Talk II, which has no special protocol
for data transfer, and as far as I can tell, it works fine for me.
I do have some apprehension about using it for C source code, however
[from postings to "net.sources" and "net.micro.pc", NOT UN*X source].
For file reception (host to PC), after logging in to our VAX host,
the keyboard sequence on my PC is

    cat vax-filename<ALT-r>pc-filename<CR>

The pc-filename is typed in response to a prompt issued by PC-Talk.
For file transmission (PC to host), after logging in to our VAX host,
the keyboard sequence on my PC is

    cat >>vax-filename<ALT-t>pc-filename<CR>

The ">>" above is the familiar UN*X shell "append" file operator;
"<ALT-r>" and "<ALT-t>" denote multikey "alt-codes";
"<CR>" denotes the broken-arrow "return" key (actually, 2 <CR>s
may be necessary where I have indicated just one -- I forget).

-- Clay Phipps


-- 
   {cbosgd decvax!decwrl!amd70 harpo hplabs!hpda ihnp4 sri-unix ucbvax!amd70}
   !fortune!phipps