Windows 10 SCO Filepro issue

[John Sica]

One method to troubleshoot this is something that Bob(Anzio) showed me once.

If the Unix "System" printer queue is paused, and the Windows print 
queue is paused, it might help determine where the job was originally 
intended to print to.  It might have to be done one at a time though, 
because you can set up the windows local printer to be the same printer 
as the "System" printer.  This may appear to be the same physical 
printer, but not the same logical printer. If the job is sent through 
the Windows 10 printer and uses the Windows 10 print driver, then just 
selecting the wrong print driver (PCL6 instead of PCL5) would cause this 
to happen.   This would make perfect sense if Windows 10 doesn't have 
the same driver for the "System" printer that Windows 7 has.   I know 
it's a long shot, but it's worth looking at.

John


On 10/30/2018 11:18 PM, Fairlight via Filepro-list wrote:
> On Tue, Oct 30, 2018 at 10:42:42PM -0500, Rod Caddy thus spoke:
>>     As a reminder if I go to a windows 7 box it prints as expected.
> Then I'm back to what Brian was saying about the environment.  It sounds
> environmental, if the software itself is all identical (except OS version).
>
> Is there anything you have set in your old Win7 terminal emulators in terms
> of environment variables sent to the server that you have not configured in
> the fresh installations during debugging?  People do things they don't
> remember later, like key off of a certain terminal type, or off of a custom
> environment variable.  I personally use a special terminal type on one
> server to indicate to me that I should use different settings at login, but
> then change the terminal type on the server side, just as an example.
> Would I remember that unless something broke?  Not necessarily.
>
> I agree with Brian's recommendation to check `set`.  Also check your
> /etc/profile, check user .profile and/or any other shell login scripts,
> etc.
>
> I would -also- suggest dropping to a Windows commmand prompt on both
> Win7 and Win10 and trying `set` there, as well, to look at the Windows
> environment.  Additionally, I'd pick -one- terminal emulator (other than
> Anzio Lite) to test on both Win10 and Win7, and start combing through the
> configurations for a difference.
>
> Be utterly methodical and thorough.
>
> m->