l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 Dec 10 22:54

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Xterm and terminal types
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Xterm and terminal types

On Friday 10 December 2004 03:54 pm, Shwaine wrote:
>From my experiences (which was over 5 years ago), getting fully compliant 
> client programs that can successfully interpret all of SCO's stuff is 
> rather dicey. I can't remember what I did for Linux (or if I even got it 
> working on Linux or not) since it was so long ago. I do remember several 
> weeks of trying to access FoxPro for SCO to only get a mess on screen 
> (that program had a curses-like gui interface, so it really tested the 
> limits of compatability). I also remember that only one Windows program 
> was able to access it correctly, although I don't remember which, and that 
> using ANSI terminals did not work. So for everyone that thinks SCO ANSI is 
> just an extension of ANSI, I can tell you from experience that it's a very 
> BIG extension such that you should not expect an ANSI terminal to get you 
> much beyond the basic command line.
> I would suggest that you take a laptop or test machine to your sister's 
> now (if possible) and test out all the ideas offered here on their 
> particular application. Even terminals which claim to support SCO ANSI 
> might not for their program, depending on how well it supports SCO ANSI. 
> My general thought is if it's still tied to SCO even now, that it probably 
> does make extensive use of SCO specific extensions, otherwise it probably 
> would have been ported to another *nix long ago, so you need something 
> which is almost flawless in emulation. You might want to ask your sister 
> why they only use the one Windows program and if it's because others 
> didn't work, then that's another point in evidence that you'll need a 
> terminal which fully supports SCO ANSI.

This makes sense, and is excellent feedback.  I'll try
"export TERM=linux" after the remote login and see what

If that's not good enough then it appears the problem can be
solved by throwing money at it; currently they use a Windows
app called PowerTerm, and there seems to be a Linux version
of the same product available for $89.


-- Rod
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.