Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site phri.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!houxm!vax135!timeinc!phri!roy
From: roy@phri.UUCP (Roy Smith)
Newsgroups: net.unix
Subject: Re: array processors and unix
Message-ID: <162@phri.UUCP>
Date: Sat, 26-Jan-85 17:26:40 EST
Article-I.D.: phri.162
Posted: Sat Jan 26 17:26:40 1985
Date-Received: Tue, 29-Jan-85 05:45:25 EST
References: <7458@brl-tgr.ARPA> <26@amdimage.UUCP> <110@rtech.ARPA>
Organization: Public Health Research Inst. (NY, NY)
Lines: 26

> What it will take to get FPS to support UNIX.
> ---------------------------------------------
>         3)  UNIX being what it is, most UNIX AP customers are more able, if
> 	    not willing, to write their own software.  (I believe, there is
> 	    also a San Diego firm that will supply UNIX software for the AP,
> 	    called AP-UNIX.)
> 				J. Wong / ucbvax!mtxinu!rtech!wong

	Last address I had for Apunix Computer Services was 1380 Garnet
Ave, Suite E-292, San Diego, CA 92109 (619)-452-7819, contact person; Peter
Berens.  Their stuff looks good on paper (driver, compiler, assembler,
debugger, emulator, user library, etc), but I havn't actually used it yet.
Does anybody have hands-on experience with Apunix software on an FPS AP?

	It seems to me that if FPS is relying on people to "roll their
own", they may be fooling themselves.  True, Unix hackers are really into
this sort of stuff, but I don't know too many people that would plunk down
$40-200K for hardware, and then roll up their sleeves to write a driver,
compiler, assembler, user library, etc. before they could use it.
-- 
allegra!vax135!timeinc\
   cmcl2!rocky2!cubsvax>!phri!roy  (Roy Smith)
         ihnp4!timeinc/

The opinions expressed herein are mine, and do not necessarily
reflect the views of The Public Health Research Institute.