Actually, I'd go with minicom if it's handy.

It's easier to fiddle with bit protocols on the fly with minicom.

(baud, flow control, parity, etc.)

With tip, you have to either tweak your /etc/remote, which is plenty
cryptic as it is, or muck with the built-in (and equally cryptic)
variable settings (~sba=9600 and such) on the fly.

('course, if you're a crusty 'tip' veteran who knows all the tilde
commands and variable settings, then heck, just go with tip.)

Michael Maciolek			michael.maciolek@exodus.net
Senior Network/Systems Engineer		781-273-3081 voice/fax
Exodus Professional Services
---------------------------------------------------------------------
Give me liberty or give me something of equal or lesser value from
your glossy 32-page catalog.  [used by 'Elvis Maximus' on slashdot]
---------------------------------------------------------------------

On Tue, 3 Oct 2000, Henry B. Hotz wrote:

  >At 8:03 PM -0500 10/2/00, Philip Brodd wrote:
  >>An old post on this issue from the archives suggests trying to 
  >>communicate with
  >>the printer via a terminal program to see if it's listening.  I'd like to try
  >>this, but I'm not sure how to do it.
  >>
  >>Would Minicom work for this purpose?  And would I just point it at /dev/tty01
  >>and start typing, or something?
  >
  >I'd suggest tip.  See the man page.  Also look at the man page for /etc/remote.
  >
  >As to what you type after you connect, I don't know but maybe:  some 
  >ordinary text followed by a line feed (ctl-J) and a form feed (ctl-L, 
  >is it?).
  >
  >
  >Signature held pending an ISO 9000 compliant
  >signature design and approval process.
  >h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu
  >