Windows 10 SCO Filepro issue

[Rod Caddy]

I will resend the information in the morning. 

⁣
Rod Caddy
817-793-4148 Cell
1-877-657-1480

Sent from BlueMail ​

On Oct 30, 2018, 9:17 PM, at 9:17 PM, Brian White via Filepro-list <filepro-list at lists.celestial.com> wrote:
>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.
>
>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...
>
>Again I don't really think that's actually happening either because it
>would be a silly way to rig things up.
>
>But it's perfectly possible and would result in these symptoms.
>
>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.
>
>I'd need to see the contents of fppath and pfconfig too.
>
>-- 
>bkw
>
>
>
>On Tue, Oct 30, 2018, 9:19 PM Fairlight via Filepro-list <
>filepro-list at lists.celestial.com wrote:
>
>> I don't think we disagree entirely.  That's essentially what I'm
>trying to
>> get at:  What -is- the default printer, exactly?  It could be
>anything.
>> Could be a printer, could be a shared printer, could be a shell
>script that
>> tucks the contents away in a deep, dark hole.  We don't know, so we
>have to
>> ask.
>>
>> I will concede, after thinking about it a moment longer, that it
>> -shouldn't- be (easily) possible to make a pass-thru printer as a
>queue
>> device, largely because it should theoretically be divorced from the
>tty at
>> the point of intake, and have no real way of knowing what tty to
>speak to.
>> It would really depend on how determined you were, and the facilities
>of
>> the print queue.  It does seem improbable, especially on SCO.  So
>that
>> suggested possibility is almost certainly ruled out.  Granted.
>>
>> Everyone has been correct in saying that the print spooler -should-
>be the
>> first hop, though, all things being equal.
>>
>> The real question is, "What -exactly- is the default printer
>definition?"
>> That, and was something else other than lp/lpr defined as the print
>command
>> in filePro in a way that would affect Hardcopy?  (I'm not even sure
>that's
>> possible for Hardcopy; like I said, it's been decades, and I was
>really
>> never a paper person anyway.  I used it like twice, probably.)
>>
>> m->
>>
>>
>> On Wed, Oct 31, 2018 at 10:40:55AM +1100, Ken Cole thus spoke:
>> > Mark,
>> >
>> > I disagree.
>> >
>> > There should be no "transparent pass-thru device".
>> >
>> > The way H-Hardcopy works is entirely on the Unix/Linux server and
>it
>> > prints directly to the users default Unix printer or maybe the
>system
>> > default Unix printer.
>> >
>> > The only trickery that may be going on is that the printer is a
>SAMBA
>> > printer that is directing the print job back to a Windows printer
>or
>> > some sort of scripting to direct it back to a Windows printer and
>> > those capabilities may not be available or from a security
>perspective
>> > allowed in Win 10.
>> >
>> > Ken
>> > On Wed, 31 Oct 2018 at 09:55, Fairlight via Filepro-list
>> > <filepro-list at lists.celestial.com> wrote:
>> > >
>> > > On Tue, Oct 30, 2018 at 03:16:13PM -0700, Bob Rasmussen via
>> Filepro-list thus spoke:
>> > > > If you're trying to do H = Hardcopy, that should happen
>strictly
>> > > > from SCO to printer; what you use for terminal emulator should
>be
>> > > > irrelevant. Isn't that right?
>> > >
>> > > That's correct, although it would appear to a user to not be the
>case
>> if
>> > > the target printer were set up to be a transparent pass-thru
>device.
>> > >
>> > > m->
>> > > --
>> > > Audio panton, cogito singularis.
>> > > _______________________________________________
>> > > Filepro-list mailing list
>> > > Filepro-list at lists.celestial.com
>> > > Subscribe/Unsubscribe/Subscription Changes
>> > > http://mailman.celestial.com/mailman/listinfo/filepro-list
>> >
>>
>> --
>> Audio panton, cogito singularis.
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
><http://mailman.celestial.com/pipermail/filepro-list/attachments/20181030/601c4fb6/attachment.html>
>_______________________________________________
>Filepro-list mailing list
>Filepro-list at lists.celestial.com
>Subscribe/Unsubscribe/Subscription Changes
>http://mailman.celestial.com/mailman/listinfo/filepro-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20181030/771b6a8f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 189.png
Type: image/png
Size: 4239 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20181030/771b6a8f/attachment.png>