Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mimsy!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions,comp.text
Subject: Re: Troff - "Typesetter busy" message
Message-ID: <6179@brl-smoke.ARPA>
Date: Sun, 26-Jul-87 00:51:31 EDT
Article-I.D.: brl-smok.6179
Posted: Sun Jul 26 00:51:31 1987
Date-Received: Sun, 26-Jul-87 07:35:22 EDT
References: <585@ritcv.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 18
Xref: mnetor comp.unix.questions:3353 comp.text:998

In article <585@ritcv.UUCP> hxd9622@ritcv.UUCP (Herman Darmawan) writes:
>After that, troff reports "Typesetter busy" message.

REMINDER:  When asking for help with a problem, give DETAILS
such as what version of the software (UNIX, DWB, whatever)
you're using, the exact command invocation, etc.

Old troff (pre-DITROFF) reports "typesetter busy" when you
attempt to open /dev/cat (Wang/GSI C/A/T typesetter interface)
and either your C/A/T is in use by another troff OR you don't
have such an animal attached to your system.  I suspect the
latter is the case.  How DO you typeset stuff, anyway?
Should you be using new (DI)troff instead?  If you have a
C/A/T emulator for some other printer, then perhaps you need
to specify the troff -t option and route its output somewhere.
Or did someone perhaps install a new release of troff?
Without further details, it's pretty hard to know what your
problem is.