Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Re: shared printer problem
Message-ID: <860704080158.001@CitHex.Caltech.Edu>
Date: Fri, 4-Jul-86 11:02:37 EDT
Article-I.D.: CitHex.860704080158.001
Posted: Fri Jul  4 11:02:37 1986
Date-Received: Sat, 5-Jul-86 12:45:20 EDT
References: <325:macmillan@wnre.aecl.cdn>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 8
Approved: info-vax@sri-kl.arpa

VMS normally DOES check for the presence of the printer, and prints messages
on the console telling you the printer is offline when an attempt is made to
print to a device that's not connected.  If you are really talking about a
printer (and not a terminal), then you've probably done something like
shorted several of the wires coming out of the vax to make it think the
printer's always on-line, and need to reverse this.  If it's over a terminal
interface, you have to set the terminal /MODEM and use the appropriate pins
(as I recall, they are 4, 6, 8, and/or 20) to do hardware handshaking.