Very Computer

What I need is the ability to -run- existing 16-bit compiled and linked code
on a 32-bit UNIX operating system and have it interface to native UNIX code.

I have a package running on an 80286.  I want to move it to a UNIX platform,
and UnixWare is what my company would like to use.

The package DOES NOT run under DOS.  It runs on our own system which DOES
NOT use any protected mode capabilities of the 80286.  However, executables
that we load and run -are- in DOS's 16-bit ".EXE" format (the non-Windows
format).  Loading the executable into memory is not a problem.  I already
have a solution for that.  What I need to resolve is the following:

  1.  How do I tell UnixWare that the code I want it to execute is 16-bit
        code, and
  2.  How do I call 32-bit routines from the 16-bit code?

Note:  The executable is already being passed the address of a table of
service routine addresses in segment:offset format.  The executable then
uses these routine addresses for every access to system services for file,
I/O, and other operations.

BTW:  UnixWare -does- come with a product called Merge from Locus Computing
Corporation, but it does not fully meet our needs.

--

Apertus Technologies                                       (612) 828-0582
Eden Prairie, MN

My client program needs to be able to communicate with the "talkd" daemon of
the unix However, I do not have the message structure that used by Sun Unix
(Sun 4.3.1).

I have the message structure for BSD (which I ftp from bsd source code),
but the message structure from BSD is for "ntalk" !!

Someone mentioned to me that there exists two version of message structure
for talkd !!  

Can anyone out there have any idea of how to locate information about it??

I try to check in the Manual and rfc but no luck.

Thanks

Department of Applied Computing
University of Tasmania at Launcestion