Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site lasspvax.UUCP
Path: utzoo!linus!philabs!prls!amdimage!amdcad!decwrl!decvax!tektronix!uw-beaver!cornell!lasspvax!kevin
From: kevin@lasspvax.UUCP (Kevin Saunders)
Newsgroups: net.micro.att
Subject: Re: Open architecture of AT&T computers?
Message-ID: <423@lasspvax.UUCP>
Date: Fri, 2-Aug-85 10:15:17 EDT
Article-I.D.: lasspvax.423
Posted: Fri Aug  2 10:15:17 1985
Date-Received: Tue, 6-Aug-85 05:38:33 EDT
References: <1701@ecsvax.UUCP> <1116@ihuxn.UUCP> <204@mplvax.UUCP> <395@cuae2.UUCP>
Reply-To: kevin@lasspvax.UUCP (Kevin Saunders)
Organization: LASSP, Cornell University
Lines: 25

In article <395@cuae2.UUCP> cwd@cuae2.UUCP (Chris Donahue) replies to:
>> Are you speaking of things like "3b2/300 Computer Feature and Interface
>> Design Manual" Select Code 305-492?  I ordered one of these in March, and
with:
>I guess you didn't read my article defining "open architecture"
>in the eyes of AT&T. Sorry, we are unable to support anyone who wants to
>develop I/O feature cards. We have to restrict ourselves to VARs. 

Does this mean you *won't* send the man a manual?  It seems it's 
been delayed just because he's not "kosher" . . .  
It sounded as if Mr. Donahue's interfacing needs were 
rather academic/personal... but even if not, if people are willing to take the 
risk of stuffing an "off-brand" board into their machine, developed 
without AT&T handholding, why not allow hardware folks to obtain the 
manuals?  

I pray the UNIXPC architecture will be OPEN.  Compare Macintosh (or 
more to the point, "SLisa") & PC memory upgrade costs for a clue to why 
it *should* be that way . . . Consumers notice these little details, 
like having to undergo a walletectomy for minor upgrades.  
Tandy & (maybe) Apple learned this lesson the hard way:  
Nothing is more useless than a bus without cheap boards to stuff in it.

Sinc,
Kevin Eric Saunders