Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cuae2!ltuxa!we53!sw013b!dj3b1!killer!ndmce!pollux!infotel!ut-ngp!ut-sally!seismo!nbires!hao!noao!arizona!caset!catuc!peter
From: peter@catuc.UUCP@ndmce.uucp (Peter Collins)
Newsgroups: net.micro.pc,net.unix-wizards
Subject: Re: Remote operation of a PC from a UNIX system using ``cu''
Message-ID: <308@ndmce.uucp>
Date: Fri, 17-Oct-86 17:01:37 EDT
Article-I.D.: ndmce.308
Posted: Fri Oct 17 17:01:37 1986
Date-Received: Tue, 21-Oct-86 05:19:52 EDT
References: <1311@kitty.UUCP> <275@bakerst.UUCP> <612@chinet.UUCP>
Sender: news@ndmce.uucp
Organization: Computer Automation, Tucson, AZ
Lines: 10
Keywords: IBM PC, remote operation, UNIX system, ``cu''
Xref: watmath net.micro.pc:10540 net.unix-wizards:20003
Summary: Procomm is the way to go

> Better to use a communications program
> that offers a host mode. PIBTERM and PROCOMM are two Shareware / PD programs
> that can do this. This may not be applicable in your case, but my biggest

I've been using procomm this way now for several weeks. Its worked just
fine for controlling my pc from a remote unix machine via cu. Just be sure
not to run any program that talks directly to the pc screen or keyboard.
Debug works fine remotely as does edlin and most c compilers I've tried.

pc