Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site cuae2.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!cuae2!cwd
From: cwd@cuae2.UUCP (Chris Donahue)
Newsgroups: net.micro.att
Subject: Re: Open architecture of AT&T computers?
Message-ID: <395@cuae2.UUCP>
Date: Wed, 31-Jul-85 09:09:04 EDT
Article-I.D.: cuae2.395
Posted: Wed Jul 31 09:09:04 1985
Date-Received: Fri, 2-Aug-85 00:08:07 EDT
References: <1701@ecsvax.UUCP> <1116@ihuxn.UUCP> <204@mplvax.UUCP>
Organization: AT&T-IS, /app/eng, Lisle, IL
Lines: 18

> 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
> it was back-ordered with no predicted delivery date.
> 	carl lowenstein		marine physical lab	u.c. san diego
> 	{ihnp4|decvax|akgua|dcdwest|ucbvax}	!sdcsvax!mplvax!cdl

If you ordered one of these, you haven't received it because of a backlog.
It is restricted to Value Added Resellers of AT&T only. My group controls
the distribution of that particular document (because we support what is
done with it). 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. The
design of a 3B2 I/O feature card is MUCH more complex than designing a card
for a PC, so it requires alot more support resources.

Chris Donahue
AT&T Info. Sys.
Application Engineering