Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!dibble
From: dibble@cs.rochester.edu (Peter C. Dibble)
Newsgroups: comp.sys.m6809
Subject: Re: NEW GROUP - comp.sys.coco
Message-ID: <4554@sol.ARPA>
Date: Wed, 25-Nov-87 13:43:21 EST
Article-I.D.: sol.4554
Posted: Wed Nov 25 13:43:21 1987
Date-Received: Sun, 29-Nov-87 09:16:48 EST
References: <1143@wlbr.EATON.COM> <4096@watdcsu.waterloo.edu> <3932@pucc.Princeton.EDU>
Organization: U of Rochester, CS Dept., Rochester, NY
Lines: 22

In article <3932@pucc.Princeton.EDU>, EWTILENI@pucc.Princeton.EDU (Eric Tilenius) writes:
> My point is that anyone who has a CoCo or CoCo 3 and is NOT into the
> technical aspect won't even KNOW that comp.sys.m6809 is for their computer!
> I'm a member of a large, enthusiastic users group - but only about 30% of
> them are into OS-9, and I'd say that less than that number are really
> aware that it is an "m6809" which drives their computer.

Granted, the CoCo is aimed at people who have no interest in hardware or
software details.  The most sophisticated part of the CoCo comunity is served by
systems like Compuserve and Delphi, but that is a very small part.  The 
users of usenet are (in general) technically sophisticated -- probably more 
sophisticated than the users of other systems.  I doubt you
could find anyone in the CoCo or OS-9 groups on Compuserve or Delphi who
doesn't know that their computer contains a 6809 (and very likely some of the
other important chips).  I would be even more surprised if a CoCo user on
usenet didn't know what microprocessor his machine used.

I would not like to see comp.sys.m6809 renamed.  Adding a CoCo subgroup to
the Tandy, or the m6809, or even the OS9 group would be fine (though there is
hardly enough traffic here to justify a group).  

Peter Dibble