Path: utzoo!utgpu!attcan!uunet!van-bc!dbinette
From: dbinette@van-bc.UUCP (Dave Binette)
Newsgroups: comp.sources.d
Subject: Re: Remote control of PC via modem
Keywords: buddy-driver CTTY GATE2
Message-ID: <2077@van-bc.UUCP>
Date: 30 Dec 88 08:14:26 GMT
References: <4652@phoenix.Princeton.EDU> <104@unibase.UUCP> <190@serene.UUCP> <13246@ncoast.UUCP> <208@serene.UUCP> <310@antares.UUCP> <132 <222@serene.UUCP> <13302@ncoast.UUCP>
Reply-To: dbinette@van-bc.UUCP (Dave Binette)
Followup-To: comp.sources.d
Organization: Wimsey Associates, Vancouver, BC.
Lines: 48

The IBM BBS community has had a handle on this one for a long time. typically
they use a device driver loosely termed a 'buddy-driver' that allows 
simultaneous use of the computer via modem *and* locally, typically to
facilitate on-line games.

Some of the popular drivers are,  GATEWAY2.SYS  IBMAUX.SYS
but the one i prefer is called  2COMALL.SYS  as it allows use of COM[1-4]
and supports ^S ^Q and ^C (many of the others don't).

Of course if the 'buddy driver' you choose doesn't support ANSI then the 
data sent to the other side will look ok (if that computer supports ANSI)
but yous wont (even if you have ANSI.SYS installed) as the ANSI.SYS is bypassed
by the BUDDY DRIVER.

additionally the host PC must not have any TSR installed that processes 
command line editing (like CED, DOSEDIT) although it may not cause any real
problems, it wont function approriatley.

Programs doing direct screen writes and some type of direct keyboard reads
also will not work correectly.

This behaviour can sometimes be circumvented by utilizing the buddy-driver in
different ways

eg..

ctty 2COM1
program
ctty CON

or

ctty <2COM1 >2COM1

or

command /c program <2COM1 > 2COM1

it depends on the  particular program. although if the program is going to
work correctly usually format 1 will suffice.

Other methods of remote operation include using a program called

carbon copy+  (i'm sure there arre others)

/* hope this helps

but possibly the best way m