Running OpenServer applications under ACP

You shouldn't have to do anything special to get an existing SCO OpenServer Release 5 application to run on UnixWare 7. The application compatibility features delivered with UnixWare 7 are described in ``Application compatibility''

Source code changes will be necessary for many applications originally compiled for use on SCO OpenServer, so that the source code can be recompiled with the UnixWare and OpenServer Development Kit. See ``Source code compatibility''.

Compatibility exceptions

The following list is a brief summary of the known compatibility exceptions for SCO OpenServer application binaries and source code in UnixWare 7:

General exceptions:

• No binary compatibility for SCO OpenServer scoadmin applications. These need to be rewritten to use the UnixWare 7 scoadmin interface and desktop.

• No binary compatibility for SCO OpenServer driver binaries. These need to be rewritten to use the UnixWare 7 driver interfaces.

• No binary compatibility for SCO OpenServer desktop applications. These need to be rewritten to use the UnixWare 7 scoadmin interface and desktop.

SCO OpenServer kernel:

• Some undocumented SCO OpenServer flags for the mmap(2) system call functions are not supported.

• The SUDS system call extensions are not supported (aio, sem, latch, timers).

• Specific SCO OpenServer system administration or debugging system call support is not provided; for example:

  • cxenix -- syssetconf extra values not supported

  • ptrace -- extra functions not supported

  • waitsys -- extra functions not supported

  • sysi86 -- some features (e.g., PIPE features) not supported

  • uadmin -- halt options not supported

• Compatibility for SCO OpenServer system tunables not provided.

Packaging:

custom+ (SSA support) is not provided.

Commands:

Some key OSR-specific commands have been ported. If the command name is unique, it is found where it is supposed to be (e.g. /usr/bin). If the command name conflicts with the corresponding SCO UnixWare 2.1.X command, it is installed in /OpenServer/bin and can be executed by setting the OSRCMDS environment variable to ``on''. Note that data transfer commands such as cpio(1) are handled with OSRCMDS. Shell scripts from SCO OpenServer can be invoked with OSRCMDS set for SCO OpenServer versions of commands.

Graphics:

• Scoterm was not brought forward; though you can link xterm to scoterm, as in:

     ln /usr/X/bin/xterm /usr/bin/X11/scoterm
  

• Most application pixmaps, bitmaps, and masks from SCO OpenServer will not work.

• Motif User Interface Language (UIL) files are not portable from SCO OpenServer.

• Applications that used IXI Drag and Drop will not work.

• The scoforeground/scobackround X resources (from SCO OpenServer) will not be available.

• Some keyboard definitions provided by SCO OpenServer applications may not work.

Internationalization:

If you specify an SCO OpenServer long name as the locale, SCO UnixWare 2.1.X apps will not work properly.

Networking:

The file system suffixes used by the NetWare UNIX Client Auto-Mounter (NUCAM) are different from those used on SCO OpenServer. Applications that make assumptions about the format of the file system names mounted automatically by the NUCAM under /.NetWare may fail.

Printing:

The SCO OpenServer version of the lpr command is not available. The lpr(1bsd) command on UnixWare 7 is the BSD version. SCO OpenServer-style printer filters can't be delivered by third parties.

Driver interfaces:

• Device compatibility for the /dev/marry, /dev/string, /dev/table interfaces is not provided. The iknt, scancode, and audit SCO OpenServer drivers are not provided.

• The power management driver and UPS interfaces are not provided.

• A small number of console ioctls were not carried forward.

• The mapkey, mapstr, mapscrn commands are not compatible. See mapkey(1M).

• The vidi driver does not set the 9th pixel.

• The SCO OpenServer AIO and vdisk drivers are not provided.

• Specific ioctls on SCO OpenServer mass storage devices are not provided.

• SCO OpenServer terminfo files were not brought forward; SCO UnixWare 2.1.X files are supported.

• The kernel build tools (idtools) are not fully compatible between SCO OpenServer and SCO UnixWare 2.1.X. As such, install scripts that expect to install drivers may fail.

Filesystems:

No direct access to SCO OpenServer HTFS and DTFS filesystems. Data conversion utilities must be run by the user if the user needs to access data on disks with these filesystem types.

SCO OpenServer filesystem command compatibility is not provided.

System files:

Applications that attempt to access SCO OpenServer-specific administrative data files, either directly or indirectly through SCO OpenServer libraries brought forward to UnixWare, are not supported.

Applications that attempt to access SCO OpenServer system data files directly or indirectly may experience problem if these files also exist in UnixWare with a different format (for example, utmp).

Security:

• SCO OpenServer security calls are not supported. Apps that manipulated user account information, privileges, authorization, and auditing will not work.

• SCO OpenServer security system calls (stopio, getluid, and statpriv) are not supported.

• SecureWare commands are not supported.

• Applications that link with libprot.so will fail.

Licensing:

No support for keyadm licensing for SCO UnixWare 2.1.X applications.