OT: broken/useless ansi - console driver??

[John Esak]

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of
> Jean-Pierre A. Radley
> Sent: Monday, October 24, 2005 12:04 PM
> To: FilePro Mailing List
> Subject: Re: OT: broken/useless ansi - console driver??
>
>
> John Esak propounded (on Sun, Oct 23, 2005 at 10:22:13PM -0400):
> | > So, after reading this thread long enough, I logged in on another
> | > console multiscreen.  My terminal was announced as being at386-ei.
> | >
> | > On executing p the filePro Main Menu displayed as expected.  Then,
> | > on going into a filePro file (fpcust) using dclerk, from there
> | > everything looked as usual except the EOF markers were just little
> | > dots in midline (I hadn't made the tremcap edit JPR suggested).
> | >
> | Don't know how this is possible, Bob. If you logged in and saw
> that you were
> | at386-ei... *and* everything looked right in filePro, then something is
> | untold here. Since there is NO at386-ei termcap in filePro, all
> I can guess
> | is JP added one for you unbeknonst to you. Or, you are still
> going through
> | FacetWin and not really going upstairs to your comptuer room
> and logging in
> | on the actual console. (Still I wouldn't think anything would
> look right in
> | filePro unless someone hadn't given you some help.)
>
> I lately installed a 5.O14 runtime for a new customer (on OSR 6.0.0, as
> it happens); it most assuredly contains an at386-ie clause in the fP
> termcap file, plus an at386-iec clause, which simply adds PV to enable
> color.
>
> Said termcap file is four and a half years old:
>
> 	# gtar tvfj UX5014FullRun_5.tar.bz2 | grep termcap
> 	-rwxr-xr-x 0/3    51323 2001-03-22 13:30:39 ./fpinstall/tmp/termcap
>
> The entry is older than that, though:
>
> 	# cd /appl/fp
> 	# grep -l at386-ie termcap*
> 	termcap
> 	termcap.by.K6
> 	termcap_5.0.04D4
> 	termcap_5.0.04K1D4
> 	termcap_5.0.05D4
> 	termcap_5.0.05K1D4
> 	termcap_5.0.05K2D4
> 	termcap_5.0.05K5D4
> 	termcap_5.0.05K6D4
> 	termcap_5.0.06D4
> 	termcap_5.0.07D4
> 	termcap_5.0.09D4
> 	termcap_5.0.10D4
> 	termcap_5.0.11D4
> 	termcap_5.0.13D4
>
> In that group, termcap_5.0.04D4 is from Nov 1, 2000.
>
> --
> JP

In regards to filePro, this was an error on my part. Apologies. There is an
entry in the distributed termcap file... something I have not replaced since
the first beta testing of 5.0, probably in early 2000 or even late 1999.
Afte having lots of troulbe with the install clobbering not only my
personalized termcap file, but my edits, printers and other things as well.
I took to not replacing my configuration files with the new ones, but doing
the type of install that touched nothing, or did the installs since then by
hand. So, in regards filePro, I spoke without looking at the latest termcap
from them, which as you say could be 5 years old now.

I might be testing all this illegally. If this is the case, my apologies
again. I have been running this SCO 6.0 as a guest operating system using
Virtual PC. If I have to stay with at386-ie, so be it. It all seems to work,
but not all of it. Under FacetWin using ansi... EVERYTHING works. In
contrast to this, using the real console (in NJ not near me), the ansi
termcap still does not work anything close to how it should... nothing to do
with filePro at all... using scoadmin it shows wrong graphics, etc. My point
is simply that they should not have taken away the ability to run things as
they were, only to move on to at386-ie. Yes, I know some things in the old
ansi's and "soansi's" did not work... but they never bothered me. Adapting
to the new thing should have been made painless. Like I say, it is just an
opninion.

John