Xref: utzoo comp.unix.xenix:1830 comp.sys.ibm.pc:14028 Path: utzoo!mnetor!uunet!steinmetz!davidsen From: davidsen@steinmetz.steinmetz.ge.com (William E. Davidsen Jr) Newsgroups: comp.unix.xenix,comp.sys.ibm.pc Subject: Re: 386 questions Message-ID: <10208@steinmetz.steinmetz.ge.com> Date: 1 Apr 88 18:47:28 GMT References: <4219@ihlpf.ATT.COM> Reply-To: davidsen@crdos1.UUCP (bill davidsen) Organization: General Electric CRD, Schenectady, NY Lines: 33 Keywords: 386 unix In article <4219@ihlpf.ATT.COM> weave@ihlpf.ATT.COM (Weaver) writes: | I'm searching for a 386 box to run Interactive Systems Unix. I plan | to do development in support of a law office running Interactive Systems | Unix on an AT&T 386 machine. | | -What is an adequate configuration? Interactive Systems recommends | >= 4 M of ram and >= 40 M hard disk. Are their recommendations valid? I certainly wouldn't go any smaller than that. | | -How does Interactive's Unix compare (in price, performance, support etc) | with the Microport and Bell Technology versions, and with SCO Xenix for | that matter? Bell TEch is selling UNIX so you can use their hardware, the real thrust of their sales. About the only thing they really support is the device drivers which they write. | Would it make sense to do development on say Microport | Unix or SCO Xenix when my primary customer is using Interactive Unix? I wouldn't do development on anything else due to postability problems. I evaluated the IS C compiler for a business, and my opinion is that it's a real piece of... NO! I am trying not to do flames, just say that I was not impressed, because about a third of the working programs I tried to compile caused the compiler to crash (not complain, like core dump). You would be ahead to use the compiler which the customer has, or to look for a version of Greenhills for IN/ix to use for development, and move the binaries. -- bill davidsen (wedu@ge-crd.arpa) {uunet | philabs | seismo}!steinmetz!crdos1!davidsen "Stupidity, like virtue, is its own reward" -me