You're going to have to let HPT transform the AFPDS into ASCII with carriage
returns and line feeds while it is being sent to the LPD. LPD means "Line
Printer Deaemon" and the default LPD is not very smart. It doesn't
necessarily do anything with fonts or graphics. So you'll have to be sure to
set up HPT with a workstation customization that matches the capabilities of
----- Original Message -----
From: "Jack Tucky" <jacktucky@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Monday, February 17, 2014 2:20 PM
Subject: Problem printing to remote Outq
We have a signature pad device that installs a print driver on the PC.
If I use notepad to create a document and print it to the signature pad
device, an application pops up that allows us to sign on the pad and
it in the PDF.
I have the system I configured with a remote outq. I point that to the
mochasoft LPD program. Mocha redirects to the same signature pad driver.
If I send a plain old QSYSPRT spool file, it works fine.
Now I send an *AFPDS file to mochasoft LPD and the signature pad shows
I was looking about removing the remote outq and creating a lan attached
device but I think I would still need a driver on the PC. We don't have a
license for Client Access.
I've tried all sorts of different printer devices on the remote outq,
changing mocha to send RAW, etc.
Any help or ideas would be appreciated.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives