Dave, I not only believe that this will work (RS-232 and a network connection
to the same LJ) but I believe that a client of mine had this situation in
place as it was one of the very confusing setups that I was trying to undo.
The LaserJet doesn't know that the origin of two different print jobs is the
same system (a HP-3000) and the HP-3000 thinks that there are two different
devices -- one for each LDEV number.  The LJ must handle input from any and
all interfaces that it has on a first come first printed basis so one or the
other will wait.  Check the manual on this but I'm sure this is correct.
While you are at it, why not connect a PC to the LJ via the parallel
interface so you can have three-way contention???  The LJ should be smart
enough to handle it all just fine.  Note that this will NOT work with Series
III or older LJs as they are configured for one interface or the other but
NOT both at once.

Wayne Boyer
Cal-Logic

PS: another really really good reason to retain and old connection for a
while is if you don't know all the places that a LDEV number for the old
connection is used.  I've seen spool files get generated for nonexistent
printers after a LJ got moved around.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *