Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!CMS1.UCS.LEEDS.AC.UK!ORG5NMC
From: ORG5NMC@CMS1.UCS.LEEDS.AC.UK
Newsgroups: comp.os.vms
Subject: (none)
Message-ID: <8708281539.AA02415@ucbvax.Berkeley.EDU>
Date: Fri, 28-Aug-87 08:04:11 EDT
Article-I.D.: ucbvax.8708281539.AA02415
Posted: Fri Aug 28 08:04:11 1987
Date-Received: Sun, 30-Aug-87 01:12:00 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 24


Dear all,
         A friend of mine has been experimenting with mailboxes
and has found two problems that as yet we know no way round.

1) I have a detatched process that communicates to a process
   on an interactive terminal via a mailbox. At certain times
   the detatched process needs to communicate interactivly
   with the terminal and run utilities such as the EDT editor.
   Since the mailbox is a non interactive device the editor
   will not run in screen mode nor will input prompts be passed
   via the mailbox.

2) We have a number of terminals on a LAT server and need at
   times to debug a graphics program. As no terminal can be
   identified by device name we assign dbg$input/dbg$output
   to a pair of mailboxes which are connected to a program
   running on the graphics terminal. The DBG> prompt is
   lost and the debugger cannot be run in screen mode.

Can anybody help? What I think I need is a mailbox that looks
like a terminal. Does anybody have such a beasty.

                               Neill.