Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!geoffs From: geoffs@brl-tgr.ARPA (Geoffrey Sauerborn ) Newsgroups: net.micro,net.rumor Subject: Re: Coleco ADAM Message-ID: <8025@brl-tgr.ARPA> Date: Tue, 5-Feb-85 08:28:53 EST Article-I.D.: brl-tgr.8025 Posted: Tue Feb 5 08:28:53 1985 Date-Received: Wed, 6-Feb-85 22:00:42 EST References: <282@teklds.UUCP> Reply-To: geoffs@brl-tgr.ARPA (Geoffrey Sauerborn (TANK) ) Distribution: na Organization: Ballistic Research Lab Lines: 31 Summary: In article <282@teklds.UUCP> davidh8@teklds.UUCP (David Haight) writes: > > I am the (un)fortunate owner of a Coleco ADAM. ( Me too) > .... Does anyone > know a source for schematics and/or documentation > on the internal micro-code? > As far as I've heard and read, Coleco was (is?) very hush-hush as to giving out memory maps, disassembled code,...etc. {As I recall, under a very strict licensing agreement they supposedly would loan the info to third party developers; with the stipulation that *any* software developed which Coleco thought was not of market quality (or some such vague term), could be confiscated by Coleco. And at any time they could revoke the license.} I think there were (are?) at least two reasons for this: 1. To hogg as much of the software market as they could. 2. To protect their video game's internals too - since it must be a subset of the whole Adam. They didn't learn from Texas Instr. - - - - - - - - - - .ps .000001 (my opinions only)