It is currently Sun, 18 Nov 2018 03:50:01 GMT



 
Author Message
 Xenix Compatibility will be dropped
I've just spoken with SCO Sales, and have learned that Xenix
compatibility, as described below, has been dropped from UnixWare
7.0.1 -- forever.  It will not be available as an add-on package.

Since OpenServer is supposed to be merged with UnixWare 7, start
looking for replacements for any legacy programs you may be running
(versions of FoxPro come to mind).

Personally, I would have appreciated better notification of their
intent, other than this section of the release notes of UnixWare
7.0.1:

 XENIX

    XENIX compatibility has been removed.  Various  modules and commands have
    been removed from the system.  These include the DOS commands doscat,
    doscp, dosdir, dosls, dosmkdir, dosrmdir, and dosrm.  Equivalent
    functionality can be obtained from the ``mtools'' package found on the
    Skunkware CD. The following exec modules and commands i286x, x286emul,
    i286emul, and xout were removed.  These modules and commands provided
    compatibility for 286 and 386 XENIX binaries.  The XENIX filesystem and
    all supporting commands for it have been removed.  The module xnamfs has
    been removed which supports XENIX semaphores and shared data.

    The XENIX libraries libx, libxcurses, and libxtermlib have been removed.
    Support for the system call nap is now in libc.  The system calls
    creatsem, execseg, chsize, locking, nbwaitsem, opensem, proctl, sdenter,
    sdfree, sdgetv, sdleave, sdwaitv, sigsem, unexecseg, and waitsem that
    were in libx were not moved to another library.  The corresponding man
    pages for these system calls no longer exist.

    If you execute a XENIX binary you can expect exec to return ENOEXEC, and
    an error message similar to:

       file: cannot execute [Exec format error]

    depending on your shell.  You can identify whether a binary is a XENIX
    binary by using the file command.

Bill



 Sat, 10 Mar 2001 03:00:00 GMT   
 Xenix Compatibility will be dropped
This move was understandable.  As I recall these were the things that
went to court
because everytime SCO was sold, part of the money had to go to Bill
Gates.  They
removed those pieces and no longer have Microsoft code in the OS.


 Sat, 10 Mar 2001 03:00:00 GMT   
 Xenix Compatibility will be dropped
I here it no longer supports the DOS 32MB dirve limits either ;-)


 Mon, 12 Mar 2001 03:00:00 GMT   
 Xenix Compatibility will be dropped
I here it no longer runs on a 286 either ;-)


 Mon, 12 Mar 2001 03:00:00 GMT   
 Xenix Compatibility will be dropped

Could anyone clarify *exactly* how I can tell which are XENIX binaries?
I have used the file command on several old prograsm (Integra, Informix SQL, ...)
and get things such as

integra: Microsoft a.out separate pure segmented word-swapped V2.3 V3.0 386
executable

(which does NOT run under 7.0.1)

and

isql: iAPX 386 executabel not stripped

(which does run under 7.01 even though I thought it was a Xenix version)

Thanks
R.Parr
Temp{*filter*}Arts



 Fri, 16 Mar 2001 03:00:00 GMT   
 Xenix Compatibility will be dropped
"Randall J. Parr" <rp...@temporal.com> writes:

That's Xenix.  Note the magic word "Microsoft".

That's COFF (svr3, e.g. SCO Unix, ISC Unix).  Should still work.

--
John Hughes <j...@Calva.COM>,
        Atlantic Technologies Inc.              Tel: +33-1-4313-3131
        66 rue du Moulin de la Pointe,          Fax: +33-1-4313-3139
        75013 PARIS.



 Sat, 17 Mar 2001 03:00:00 GMT   
 Xenix Compatibility will be dropped

[snip]

This is probably a Xenix executable.

And this a SCO Unix binary (which should run on Xenix/386, AFAIK).

Cheers,

--
----------------------------------------------
Alex Arnon                      
System Support Engineer         Tochna Veod
                                Maskit 8
a...@sco.sintec.co.il           Herzlia
Tel:    972-9-9526834           Israel
        972-9-9526830
Fax:    972-9-9526844



 Fri, 06 Apr 2001 03:00:00 GMT   
 Xenix Compatibility will be dropped
In article <360FB11B.DE3A5...@temporal.com>,
Randall J. Parr <rp...@temporal.com> wrote:

          ^^^^^^^^^^^^^^^

A real big clue right their.  Microsoft owns Xenix and the the
'magic' file contains the info that 'file' uses for output display.

Anything that matches Microsoft in the output will be gone.  There
are quite a lot in the magic file if you care to look at it.

--
Bill Vermillion   bv @ wjv.com



 Fri, 06 Apr 2001 03:00:00 GMT   
 
   [ 8 post ] 

Similar Threads

1. SCO Xenix Binary Compatibility?

2. Xenix to Linux software compatibility

3. Xenix/SCO compatibility

4. binary compatibility between sco xenix and sco unix

5. Binary compatibility between Sco xenix and Sco unix

6. binary compatibility between sco xenix and sco unix

7. I AM GONNA PUKE - I AM GONNA PUKE - I AM GONNA PUKE - I AM GONNA PUKE - I AM GONNA PUKE - I AM GONNA PUKE - I AM GONNA PUKE -

8. Reading multi-volume xenix tar files on non xenix systems

9. xenix to unix file conversion FROM XENIX TAPE

10. Mount xenix /u system under SCO 5.02 and WD network card with Xenix


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software