<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 10/31/2018 7:12 PM, Brian White via
Filepro-list wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAO0vv2ZO_oQm7-0=8RDH3qVeMm+S9pjJQDb4-VxFyhvHhg1N7g@mail.gmail.com">
<pre wrap="">Good grief... after all this time, I finally look at the png screen
captures, and instantly what do I see? A variable that controls filepro's
behavior exactly as I said since the beginning. PFPT=on tell fp binaries to
try to use pathrough printing, by default, if possible. Both clients are
setting PFPT=on, both clients are setting TERM=scoansi.
For passthrough printing from filepro to work, several things must all be:
* The termcap entry that matches $TERM must include PN and PS caps which
work on that terminal. In filepro, the termcap entry is built up from two
files, /etc/termcap and $PFDATA/$PFDIR/fp/termcap (or could also be
specified entirely in an environment variable $TERMCAP which overrides the
termcap files)
* The terminal must actually recognize those escape codes from the PN and
PS termcap caps, and do something with the data collected in between the
printer-on and printer-off codes. IE, if the terminal software has a config
option for what to do with passthrough print data, you might have to
actively configure it to say what printer it should send the print data to,
else it might simply eat the data and do nothing with it.
* The destination that the terminal software sends the data to, must be
able to make sense of PCL5 data. There are a few different ways to arrange
this. Sometimes there is an option you can set in the printer driver
properties that says not to mess with the data, just forward it to the
printer raw. That would/should work as long as the printer itself actually
understands pcl5. Today, many don't. HP in particular confuses things even
more by having printer drivers that sometimes silently translate pcl5 from
an application into pcl6 for the printer, making you think the printer
supports pcl5 when it really doesn't. In the case of HP, try to look for
alternative versions of the printer driver, with PCL or PCL5 in the
driver's name. Remove the currently installed driver and install that
alternative, and that *might* make passthrough printing from filepro
through that terminal start working. Alternatively, if the "terminal
software" is AnzioWin, it has it's own built-in pcl interpreter, and should
always work with any printer that any other Windows app can print to, since
it interprets the pcl itself and renders it as graphics and hands the
bitmap data to windows's native gdi printing interface for windows to
print, without caring what kind of printer you have as long as you have a
working windows driver for it, the same as any other windows app does.
You could also try removing PFPT=on from the envirnment, which will cause H
hardcopy to go to whatever printer is set as default in pfconfig.
Also verify, HOW is TERM getting set to "scoansi"? (and how is PFPT getting
set to on?)
Is it being hard-coded in .profile or /etc/profile? Or is it coming from
the terminal emulator?
What I'm getting at is, are both terminal client apps really configured to
emulate sco-ansi?
</pre>
</blockquote>
<p><font face="Helvetica, Arial, sans-serif">I get what you are
saying with PFPT=on but then why does it work on the W7 box
using the same login and settings? I'm sorry if I'm being thick
but that makes no sense to me.</font><br>
</p>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<br>
<div class="moz-signature">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<title></title>
<a href="www.pro-set.com"><img alt="Pro-Set Systems Logo"
src="cid:part1.15F2F6B8.C346533F@pro-set.com" align="left"
height="50" width="42" border="0"></a> Rod Caddy<br>
Pro-Set Systems<br>
<a class="moz-txt-link-abbreviated" href="mailto:rcaddy@pro-set.com">rcaddy@pro-set.com</a><br>
<small> The information in this e-mail is confidential and may
be privileged. If<br>
you are not the intended recipient, please destroy this
e-mail and <br>
notify the sender immediately. You should not retain, copy,
distribute <br>
or use this e-mail for any purpose, nor disclose any of its
contents to <br>
any other person.<br>
</small>
<pre class="moz-signature" cols="72">
</pre>
</div>
</div>
</body>
</html>