Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!uwvax!astroatc!prairie!dan
From: dan@prairie.UUCP
Newsgroups: comp.sys.att,comp.sys.ibm.pc
Subject: Re: Summary of responses about Simultask
Message-ID: <463@prairie.UUCP>
Date: Thu, 4-Jun-87 13:36:22 EDT
Article-I.D.: prairie.463
Posted: Thu Jun  4 13:36:22 1987
Date-Received: Sat, 6-Jun-87 11:29:37 EDT
References: <315@ncspm.ncsu.edu>
Reply-To: dan@prairie.UUCP (Daniel M. Frank)
Distribution: world
Organization: Prairie Computing, Madison, Wisconsin
Lines: 31
Xref: utgpu comp.sys.att:421 comp.sys.ibm.pc:4037


   Very odd, all this talk about Microport and the 6300+.  I'll try to
make some sense of this, as best I can:

   My understanding is that Microport Unix and 6300+ Unix are both
descended from a single port of System V, called SV/286, which was
done by Interactive (I think).  In particular, limitations in the
compiler descend from that port.  SV/286 was written for the Intel
310.  Microport took it to the PC/AT and compatibles, while AT&T
independently ported it to the 6300+.

   The DOS/Merge software was written by Locus for the 6300+, and
is sold by AT&T for that machine.  DOS/Merge was then rewritten by
Locus for Microport Unix.  Apparently, the AT lacks some hardware
support for the Merge software which the 6300+ possesses.

   AT&T and Microport Unix are object code compatible.  AT&T has
updated and replaced several utilities, e.g. HoneyDanBer UUCP,
and may have tidied up other programs a bit more.  Microport has
had their hands full trying to support the AT compatibles, and has
concentrated more on the drivers.

   I want to stress that these two Unices are siblings.  The Unix
that runs on the 6300+ is NOT Microport Unix.


-- 
      Dan Frank (w9nk)
	ARPA: dan@db.wisc.edu			ATT: (608) 255-0002 (home)
	UUCP: ... uwvax!prairie!dan		     (608) 262-4196 (office)
	SNAILMAIL: 1802 Keyes Ave. Madison, WI 53711-2006