Technical article 126154

My legacy SCO OpenServer 5, SCO Unix and SCO Xenix applications are not displaying correctly on the OpenServer 6 console.

OpenServer 6.0.0

Written · Last revised

Problem

I have a legacy application that ran without problems on the SCO OpenServer 5 "scoansi" console but when I try to run this application on OpenServer 6.0.0 I have problems that include:

1) Line drawing characters being replaced by accented characters 2) Function keys do not return the expected values

Cause

The most likely causes of these problems are poorly written applications that are using hardwired escape sequences to control the display.

There also may be problem caused by a clash between the codeset that the application is using and that used by the OpenServer 6.0.0 console.

Solution

The proper way to resolve this problem is to get the Application Developer to change the application so that it correctly handles display devices in general.

If this is not an option then what follows are a number of suggestions that may allow you to workaround the problem:

1) Run the application in an OpenServer 6.0.0 scoterm(XC), from an OpenServer 5 scoansi console or in any Windows or Unix terminal emulator capable of emulating scoansi.

2) Run the command
mapchan -n

to turn off mapping on the console.

3) Use the shell script below to change the behavior of the OpenServer 6 console to an ansi emulation. Note that this script:

- will not enable a full scoansi emulation but may improve the behavior of the application - has not been tested with non-US keyboard types - will allow you to change the console behavior to ansi from at368-ie and visa versa - can only be run as the root user

============================[snip]==========================================
#!/bin/sh
# Switch the terminal emulation for the console from the
default
# "at386-ie" to "ansi", or vice versa
#
# NOTE: not for use with non-US keyboards!
case "$1" in
   ansi)
       # change console term type
       defadm coterm TERM=ansi
       sed -e 's/^at386-ie/ansi/' < /etc/ttytype > /etc/ttytype.$$
       cp /etc/ttytype.$$ /etc/ttytype
       rm -f /etc/ttytype.$$
# change console font
defadm cofont COFONT=pc850
# remap function keys
[ -f /usr/lib/keyboard/strings.d/at386-ie ] || \
  cp /usr/lib/keyboard/strings /usr/lib/keyboard/strings.d/at386-ie
cp -f /usr/lib/keyboard/strings.d/ansi /usr/lib/keyboard/strings
;;
at386*)
    # change console term type
    defadm coterm TERM=at386-ie
    sed -e 's/^ansi/at386-ie/' < /etc/ttytype > /etc/ttytype.$$
    cp /etc/ttytype.$$ /etc/ttytype
    rm -f /etc/ttytype.$$
# change console font
defadm cofont COFONT=8859-1
       # remap function keys
       cp -f /usr/lib/keyboard/strings.d/at386-ie /usr/lib/keyboard/strings
       ;;
esac
/sbin/loadfont
mapstr

From the Xinuos technical article database, record 126154. Reproduced with permission. The original is at www.sco.com/ta/126154, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.