termcap file, printing, porting

[Lerebours, Jose]

> I still have a couple of issues:
> 
> 1.)/etc/termcap - The ESC key doesn't work like it is
> supposed to. It doesn't save when I hit it. Before
> 'ESC-ESC' was what we hit to save changes. Also,
> instead of lines around the menu borders, the
> characters "3" and "8" are the borders. It makes it
> hard to enter numerical data, since the field input
> bleeds into the 3's and 8's.
> I don't have a complete list of the environmental
> variables. Is this an /etc/termcap issue or a variable
> one?
> 

Your best bet is to usr /appl/fp/termcap in lieu of 
/etc/termcap.  To do this, user variables FPTERM and
FPTERMCAP


> 2.)printing - I set up the default printer using
> sysadmsh, then selected '7' from the main FP menu and
> added a printer there. For the command, I entered lp
> -dprinter_name.
> I still have problems trying to print reports.
> 

A couple of questions:

Q. Can you print to printer from command line?
   If not ... fix that.

Q. How are you telling your application which
   printer to use other than setting up within
   printer admin?

Q. Is printer enabled and accepting jobs?


> 3.)porting to Linux/BSD - I have tried to mount the
> floppies on Linux -- even recompiled to recongize
> Xenix FS -- but I had no luck. Same with FreeBSD. I
> have even tried to format a partition on a BSD drive
> to the Xenix FS. Has anyone had luck moving from old
> SCO to Linux or BSD without having to do a total
> rewrite. It's ridiculous that we are still using such
> old hardware and an OS that is unsupported. I'm trying
> to convince the owner to move to something more
> current.
> 

Porting to Linux should be pretty simple.  Of course,
you will have to buy new licenses for the new platform.

As far as porting your programs and data, it is as simple
as `tar cv` and `tar xv`

I do not know how, but there is a way to make your SCO
binaries run in Linux. If you cannot manage that, new
runtime licenses will be needed.  Suse/Ken?


I wonder if you are billing for your time.  I do only
because while trying to save money and not upgrade to
new server with new OS and new runtime, your customer
is putting out a lot more money and taking mush longer
than necessary.  Funny thing is, at the end of it all,
they just might have to put out and do what they should
have done to begin with.

What I hate about things like this is that they never
seen to remember how many times you advised them of
this from the very moment you walked in.  They will,
however, wonder why it took you so long to do such a
simple thing.

This is what I normally refer to as:

"Been held responsible for something over which you
you have no authority"


Good luck!


Jose Lerebours