× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Once I've use a device like that, and I remember we configured a
Remote OUTQ using LPD/LPR protocol. In your print server I can see you
have AnyNet and LPD (
ftp://iocorp.com/Host_Print/Manuals/LanRPC%20Users%20Guide.pdf )

If you need just line printing, maybe LPD could be your easy choice,
and setup like this

CRTDEVPRT DEVD(PRT10) DEVCLS(*VRT) TYPE(4245) MODEL(T12)
ENDWTR WTR(PRT10) OPTION(*IMMED)
CHGOUTQ OUTQ(PRT10) RMTSYS('PRTSVR01') RMTPRTQ('COM1') CNNTYPE(*IP)
DESTTYPE(*OTHER) TRANSFORM(*NO)





2015-11-03 16:17 GMT-06:00 Bob Kohlndorfer <bkohlndorfer@xxxxxxxxxx>:
I am trying to create a device description for a 4245 model T12 (Twinax)
printer connected to a Power 720 machine with an IO Corp LAN-RPC+ TCP/IP
Print Server.

How do I treat this setup?

I tried creating it with Class *LAN and Type 4245 Model T12, but I get the
error message that Device Type and Model not valid for device class.

Do I need to create the DEVD as a PJL and let the device worry about
converting it to what the 4245 printer needs?



TIA,

Bob

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.