jeff lawson
unread,Mar 16, 2006, 6:38:06 PM3/16/06Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jb...@googlegroups.com
Hello all...I may be a bit behind the time, but I just encountered an interesting issue with new HP "Host Based" printers and jobs spooled out of jBASE. I thought I would run some stuff by everyone and see what kind of feedback I get...
Environment:
Windows/jBASE 3.4.x
jBASE spooler and formqueues setup with PROG lp
Background:
On HP "Host Based" printers (1500,2600N,3500,3550,1010,1012,1015,1160...and more to come) jobs spooled direclty from DOS based/legacy type applications (PRINT, lp, etc) are of "RAW" datatype and hang in the spooler in a "printing" status. These jobs are of datatype IMF, and the IMF Print Processor for the printers above can not handle printing them.
With normal PCL6 driven HP Printers and drivers, these jobs are of type "RAW" and the print processor is WINPrint.
According to my conversations with HP Support, jobs that are sent to these new generation "host based" printers through DOS and such are a known limitation and will not work. The printers do not come with basic PCL6 driver compatibility and cannot be connected and used with Standard TCP/IP port and Generic/Text Only drivers either.
Question:
Has anyone ran into this and looked at a different way to print with jBASE formqueues which bypasses the "DOS" print job incompatibility that HP is claiming? Are there other useful connect commands beside PROG lp that people have found successfull within Windows/jBASE
3.4.x?
Jeff