SuSe 10 Linux Termcap for filePro

[Nancy Palmquist]

Fairlight wrote:
>>From inside the gravity well of a singularity, Nancy Palmquist shouted:
> 
>>I got two excellent suggestions about this problem.  I tried Bob's 
>>suggestion about the termcap.  It made no difference in the display.
>>
>>I also got a suggestion from both Bob and Craig about checking the LANG= 
>>  setting in Yast.  I found it and the LANG was set to English (US) but 
>>on the detail page it had UTF-8 encoding checked.  Well, the yast 
>>graphics displayed crappy also, so I unchecked that setting.
> 
> 
> Gack...il8n is evil.  This started showing up in earnest about the era of
> Red Hat 8.0.
> 
> 
>>After yast did it's thing, the yast display's graphics were fixed.
>>
>>However, the filePro graphics were still crappy.
> 
> 
> Can we narrow down "crappy" to a definition a bit more conduscive to fixing
> the problem, please?

All the boxes around stuff display incorrectly as other characters such 
as 3 (vertical lines) A with a little sideways colon on the top 
(horizonal), etc.  If I could cut and paste it so you could see I would 
but it looks like the stuff we got without the mapchan -n on Unix.


> 
> 
>>I tried the termcap suggestion in conjunction with the yast suggestion. 
>>  No better.
>>
>>xterm made worse graphic issues.  SCOANSI seemed to work the best - by 
>>best I mean only one bad graphic character instead of two.
> 
> 
> Which one/two are bad?

1 character makes it hard to read but does not disrupt the screen too 
much so it is good.
2 characters make the screen layout strange making it almost impossible 
to use.  This is bad.  I got this to stop when I unchecked the UTF-8 
encoding.



> 
> 
>>Well something must still be missing.  I can't figure what.
>>
>>Thanks for the great suggestions.  Got any more ideas?  ;-)
> 
> 
> Don't use it from a SCO console is the first thing that comes to mind.  :)

Of course that is a solution, but that is my work setting.  I usually do 
not work my *nix programs from my windows computer.  I have more brain 
freezes when I am looking at windows and trying to do *nix.  I certainly 
could do it but it will make me change my style.  I hate doing that. 
The computers work for me not the other way around.

> 
> Actually, you -do- have 'mapchan -n' set during this...right?
> 

SCO Unix - yes

Not sure how to even do that if you mean SuSe.

> Further...  Don't use xterm.  SCO's console is not an xterm, and your
> results will not improve.  Trying semi-random settings and praying they
> work isn't likely to be fruitful.
> 

When I log in from SCO, the default term is scoansi.


> You took Bob's suggestion and used the scoansi termcap in the main termcap.
> You've not yet said (or if you did, I missed it) what corresponding PFTERM
> you're using simultaneously.  What -are- you putting in that variable?  And
> is the entry the same as on a system that does work for you?
> 

I tried it - did not help.  I returned the termcap to original state.

PFTERM was not set - so it defaulted to scoansi.

I tried TERM=scoansi-new (which is what my SCOUnix is using for scoansi)
TERM=scoansi

PFTERM=ansi	'still broken
PFTERM=scoansi	'still broken
PFTERM=linux	'still broken but I got color
PFTERM=xterm	'real bad - I just wanted to try it.



> Let's also take a step back a second.  Can you actually use fP from a SuSE
> 9.x box on the same exact SCO console without problems?  Are you -only-
> having problems with SuSE 10, or is 9.x an issue as well?  If 9.x is fine,
> then we could start a differential analysis of the relevant factors between
> the two...something systematic.  There are only so many subsystems involved
> here, which is to say "not many".

SuSE 9.x worked just fine.  It is no longer with us.  RIP....

All the other SuSE 9 boxes I connect to, I use puTTY so it is not giving 
me this problem.

> 
> Another thought:  What version of fP?  5.6?  5.0.xx where xx >= 10?  
> 

I supplied this info.  5.0.14

> Ken?  If she has 5.6, is the linux version of that still compiled
> dynamically, or have you folks reverted back to static linking?  I'm
> thinking it's -possible- libtermcap may have been changed (although it
> would surprise me at this late date).  Its potential relevance depends on
> the linking.
> 

I had to install libtermcap.so.2 to get it to work.  Does that help?

Sorry I did not respond yesterday.  Much to do, not much time.

Nancy
-- 
Nancy Palmquist 		MOS & filePro Training Available
Virtual Software Systems	Web Based Training and Consulting	
PHONE: (412) 835-9417		   Web site:  http://www.vss3.com