Windows 10 SCO Filepro issue

[Fairlight]

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->
-- 
Audio panton, cogito singularis.