phipps@fortune.UUCP (Clay Phipps) (04/13/84)
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