Windows 10 SCO Filepro issue

[Brian White]

> I'm not talking about windows print screen, I'm talking about Hardcopy
> in filePro.
>

I don't know why hardcopy would be any different than any other printing
from fp.

You also said something about a unix spool not passthrough print. If the
default printer in pfconfig is a unix lp command, then I don't see how the
server knows or cares what os the desktop is running.

I think the setup is not described in enough detail.

Log in from one of the win7 machines where printing works, and from the
win10 machine where printing doesn't work.

Run "set |sort |less" on each. (if you don't have less installed, then
capture and view any other way. pg, more, vi/view etc...)

Anything different that could affect printing? There are env variables that
affect both the spooler and fp's notions of default printer destination, or
could inadvertantly affect printing in some indirect way like, totally
contrived example:

The env is set up to do passthrough after all, PFPT=on (or true or
whatever), and your fp/termcap has a scoansi entry that includes PN & PS,
abd only the scoansi entry has it, and TERM or PFTERM is set to scoansi on
most desks, but it's set to something else like xterm on the new desk.

It's not literally exactly that, because the break key would not be Del,
and you couldn't miss that. It's an example only.

Are you logging in as the same user on both working and non-working desks?
There is a gotcha with sco osr5 printing where a newly added user might not
have permission to use the printing system at all until you manually add
them in scoadm (or figure out how the default got changed and change it
back, I forget the details myself)

It could be anything, until you describe the setup more, to remove some of
the infinite possibilities.

Follow the trail from fp yo the printer. What is fp going to try to do when
you say Y to hardcopy? You have to look at all fp env vars to determine
that. For instance, the PFCONFIG var, if it exists, says where to load the
fp config file from, which may override the file pointed to by fppath vars.
So, it's possible for two different desks to load two entirely different
config fles, which may contain 2 entirely different sets of pfprinter and
other variables.

Now you hopefully know what fp should try to do, next depends on what that
was. Was pfprinter the same fp printer name like printer1 on both? Was the
definition of printer1 the same on both? was PFPT either on or off or
absent the same on both? Was the defintion of printer1 a normal valid lp
command line? Can you successfully use that same lp command, as that same
user, from a shell prompt, on both?

-- 
bkw
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20181026/3fb13200/attachment.html>