Path: utzoo!attcan!uunet!aplcen!samsung!xylogics!merk!alliant!linus!mbunix!ted
From: ted@mbunix.mitre.org (Ede)
Newsgroups: comp.lang.postscript
Subject: Re: IP over Ethernet to printers
Keywords: ethernet postscript printers
Message-ID: <113030@linus.mitre.org>
Date: 11 Jul 90 15:22:15 GMT
References: <521@al.ele.tue.nl>
Sender: usenet@linus.mitre.org
Organization: The MITRE Corp., Bedford, MA
Lines: 31

In article <521@al.ele.tue.nl> jos@es.ele.tue.nl writes:
>The QMS solution of hooking their printers on ethernet has been mentioned
>here by several before.

They have multiple solutions, just call a QMS salesperson.  They'll be
happy to tell you all about them :-).

>In this respect the QMS ethernet option just cheets you.
>You will obtain some (closed) PC-box which hooks up to the
>ethernet, and then connects with a normal (serial) line to the printer.
>This will therefor not result in any speed improvements.

>=== just to clarify some things ===
yeah, right.

I referred to QMS's *Imagen* line, which has a ethernet controller on
the same bus a the printer controller/interpreter.  So there's no
async bottleneck in the path.

I wouldn't call the QMS printcontroller a "cheat".  It just doesn't do
*exactly* what you want it to do.  It does appear to have some worthwhile
features though.  (I don't have one.)

BTW, We do have a PrintServer 40.  And when the Ricoh engine is
working, the printer really runs well.  Personally, I prefer the
Cannon engines.

|Ted Ede -- ted@mbunix.mitre.org -- The MITRE Corporation -- Burlington Road|
| linus!mbunix!ted -- Bedford MA, 01730 -- Mail Stop B090 -- (617) 271-7465 |
|                   - this line intentionally left blank -                  |
+---------------------------------------------------------------------------+