<div dir="auto">But a single fp variable can tell fp to do passthrough for all printing that doesn't specify a destination explicitly. There is also a variable that affects the unix lp command. I don't really suppose he's using either of those but who knows. It's obviously something and until we know what it is, it could be anything. That's why I said to look at the full env of both working and non-working terminals. I couldn't see the attached files that presumably showed the environments on my phone and I keep forgetting to try from my laptop.<div dir="auto"><br></div><div dir="auto">Something about this story is not really as stated, because there is nothing between the fp binary and the unix spooler that gives a fig about what terminal or os the user logged in from. But there are an infinite number of ways you could wind up with these symptoms. Windows10 is a coincidense or red herring unless the print job is somehow going through the windows10 machine. That could actually be happening, and not just by passthrough print. Maybe all the other stations are set up to share their own default printer via smb or lpd, and the setup on the server makes each user print back to themselves via those shares. And on the new win10 machine it doesn't work because the lpr service isn't installed, or isn't even available any more, or the firewall blocks it etc...</div><div dir="auto"><br></div><div dir="auto">Again I don't really think that's actually happening either because it would be a silly way to rig things up.</div><div dir="auto"><br></div><div dir="auto">But it's perfectly possible and would result in these symptoms.</div><div dir="auto"><br></div><div dir="auto">Why were those attachements scrubbed any way? Were they graphical screen shot images? Rod, why in the world do that? Just cut & paste the text, email to yourself from the users desk, then forward that here, and then it's plain text and it would be right here to see with no scrubbing.</div><div dir="auto"><br></div><div dir="auto">I'd need to see the contents of fppath and pfconfig too. <br><div dir="auto"><br></div><div dir="auto">-- </div><div dir="auto">bkw<br><div dir="auto"><br></div><div dir="auto"><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Oct 30, 2018, 9:19 PM Fairlight via Filepro-list <<a href="mailto:filepro-list@lists.celestial.com">filepro-list@lists.celestial.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I don't think we disagree entirely. That's essentially what I'm trying to<br>
get at: What -is- the default printer, exactly? It could be anything.<br>
Could be a printer, could be a shared printer, could be a shell script that<br>
tucks the contents away in a deep, dark hole. We don't know, so we have to<br>
ask.<br>
<br>
I will concede, after thinking about it a moment longer, that it<br>
-shouldn't- be (easily) possible to make a pass-thru printer as a queue<br>
device, largely because it should theoretically be divorced from the tty at<br>
the point of intake, and have no real way of knowing what tty to speak to.<br>
It would really depend on how determined you were, and the facilities of<br>
the print queue. It does seem improbable, especially on SCO. So that<br>
suggested possibility is almost certainly ruled out. Granted.<br>
<br>
Everyone has been correct in saying that the print spooler -should- be the<br>
first hop, though, all things being equal.<br>
<br>
The real question is, "What -exactly- is the default printer definition?"<br>
That, and was something else other than lp/lpr defined as the print command<br>
in filePro in a way that would affect Hardcopy? (I'm not even sure that's<br>
possible for Hardcopy; like I said, it's been decades, and I was really<br>
never a paper person anyway. I used it like twice, probably.)<br>
<br>
m-><br>
<br>
<br>
On Wed, Oct 31, 2018 at 10:40:55AM +1100, Ken Cole thus spoke:<br>
> Mark,<br>
> <br>
> I disagree.<br>
> <br>
> There should be no "transparent pass-thru device".<br>
> <br>
> The way H-Hardcopy works is entirely on the Unix/Linux server and it<br>
> prints directly to the users default Unix printer or maybe the system<br>
> default Unix printer.<br>
> <br>
> The only trickery that may be going on is that the printer is a SAMBA<br>
> printer that is directing the print job back to a Windows printer or<br>
> some sort of scripting to direct it back to a Windows printer and<br>
> those capabilities may not be available or from a security perspective<br>
> allowed in Win 10.<br>
> <br>
> Ken<br>
> On Wed, 31 Oct 2018 at 09:55, Fairlight via Filepro-list<br>
> <<a href="mailto:filepro-list@lists.celestial.com" target="_blank" rel="noreferrer">filepro-list@lists.celestial.com</a>> wrote:<br>
> ><br>
> > On Tue, Oct 30, 2018 at 03:16:13PM -0700, Bob Rasmussen via Filepro-list thus spoke:<br>
> > > If you're trying to do H = Hardcopy, that should happen strictly<br>
> > > from SCO to printer; what you use for terminal emulator should be<br>
> > > irrelevant. Isn't that right?<br>
> ><br>
> > That's correct, although it would appear to a user to not be the case if<br>
> > the target printer were set up to be a transparent pass-thru device.<br>
> ><br>
> > m-><br>
> > --<br>
> > Audio panton, cogito singularis.<br>
> > _______________________________________________<br>
> > Filepro-list mailing list<br>
> > <a href="mailto:Filepro-list@lists.celestial.com" target="_blank" rel="noreferrer">Filepro-list@lists.celestial.com</a><br>
> > Subscribe/Unsubscribe/Subscription Changes<br>
> > <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" rel="noreferrer noreferrer" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
> <br>
<br>
-- <br>
Audio panton, cogito singularis.<br>
_______________________________________________<br>
Filepro-list mailing list<br>
<a href="mailto:Filepro-list@lists.celestial.com" target="_blank" rel="noreferrer">Filepro-list@lists.celestial.com</a><br>
Subscribe/Unsubscribe/Subscription Changes<br>
<a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" rel="noreferrer noreferrer" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
</blockquote></div>