Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!philabs!cmcl2!harvard!seismo!rochester!ritcv!cci632!ccird1!rb From: rb@ccird1.UUCP (Rex Ballard) Newsgroups: net.micro.amiga Subject: Re: Questions on memory expans. and hard disks Message-ID: <407@ccird1.UUCP> Date: Thu, 8-May-86 19:48:31 EDT Article-I.D.: ccird1.407 Posted: Thu May 8 19:48:31 1986 Date-Received: Sun, 11-May-86 03:11:07 EDT References: <1974@caip.RUTGERS.EDU> <1026@amiga.amiga.UUCP> <230@chronon.chronon.UUCP> Reply-To: rb@ccird1.UUCP (Rex Ballard) Organization: CCI Rochester Development, Rochester NY Lines: 28 Summary: Good news, bad news? In article <230@chronon.chronon.UUCP> eric@chronon.UUCP (Eric Black) writes: >In article <1026@amiga.amiga.UUCP> bobp@snake.UUCP (Robert S. Pariseau) writes: >>Comspec Communications Inc., is shipping 2 Megabyte memory expansions for >>Their box is about the size of a paperback dictionary. > >[BTW Bob -- the expansion documentation packet is GREAT! Even sample >circuits and PAL EQUATIONS to handle the autoconfig protocol! Hate >that form factor, though! That MicroForge box is absurdly huge sitting >next to the Amiga, and the spec pretty much says it has to be that big, >and has to sit RIGHT THERE] >-- Great, Amiga has finally come up with documentation on "good expansion" standards, looking forward to seeing what come out. Questions: Can't you connect the Amiga to the Expansion devices via something like a ribbon cable? Do you HAVE do buy a big CAGE (remember the TI 99/4)? Could accessories be added in daisy chain fashion? Could someone come up with a "card case" to slip over the bare cards so you could go either way (cage or ribbon cables)? I'm kind of glad Amiga didn't follow the IBM/APPLE/ S-100 convention of a "rigid backplane" in the main box, but it would be so nice to be able to choose between a $30 "ribbon bus" and $300 "cage", especially since one might only need 1 or 2 "slots" at first, but might need 8 later on. Could someone provide a semi-brief description of what the "expansion" should be?