Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!nosc!humu!pegasus!news
From: news@pegasus.com (0000-Usenet News(0000))
Newsgroups: comp.unix.i386
Subject: Re: System V and Xenix compatibility
Message-ID: <1990Jul7.004456.15038@pegasus.com>
Date: 7 Jul 90 00:44:56 GMT
References: <17032@haddock.ima.isc.com>
Organization: Pegasus,  Honolulu
Lines: 13

In article <17032@haddock.ima.isc.com> peterf@haddock.ima.isc.com (Peter Fischman) writes:
>
>	I recently came off a project that ported a DOS application,
>	Lotus 1-2-3 (you may have heard of it), to System V and Xenix.
>	We developed on 386/ix and used gcc and gmake.  The executable
>	runs on 386/ix, SCO Unix SysV.3.2, SCO Xenix386 2.3.2, AT&T
>	Unix SysV.3.2, and AT&T Unix SysV.4.  The only part of the code
>	that cares about the flavor of the OS is the video driver.  The
>	SCO video interface is different from 386/ix and AT&T.  That's
>	not much, in retrospect.

You tied directly into the video driver instead of using termcap or
terminfo?  How come?