[net.micro.16k] Perhaps a name change is in order

jbuck@epimass.UUCP (05/02/86)

>Every year or so it has to be said.
>
>Net.micro.16k is NOT for discussion of computers with 16k RAM.
>It is for discussion of the National Semiconductor 32000 series
>architecture, the first member of which was once named the "16032"
>(abbreviated "16k").
>-=- Andrew Klossner   (decvax!tektronix!tekecs!andrew)       [UUCP]
>                      (tekecs!andrew.tektronix@csnet-relay)  [ARPA]

This name is obviously no longer appropriate.  I suspect that the group
is currently so small because National 32000 users don't know they have
a group.  How about a change?

I propose net.micro.nsc.  Other suggestions are welcome.


-- 
- Joe Buck <ihnp4!pesnta!epimass!jbuck>
  Entropic Processing, Inc.
  Cupertino, California

wsr@lmi-angel.UUCP (Wolfgang Rupprecht) (05/05/86)

In article <> jbuck@epimass.UUCP (Joe Buck) writes:
>I suspect that the group is currently so small because National 32000
>users don't know they have a group.

Gee, and all this time I thought that it was because there aren't any
users... :-)

				-wr







-- 
	Wolfgang Rupprecht		{harvard|cca|mit-eddie}!lmi-angel!wsr

wsr@lmi-angel.UUCP (Wolfgang Rupprecht) (05/05/86)

In article <> jbuck@epimass.UUCP (Joe Buck) writes:
>I suspect that the group is currently so small because National 32000
>users don't know they have a group.

Gee, and here I was thinking that it was indicative of the number of 
users. :-)
-- 
	Wolfgang Rupprecht		{harvard|cca|mit-eddie}!lmi-angel!wsr

friesen@psivax.UUCP (Stanley Friesen) (05/05/86)

In article <204@epimass.UUCP> jbuck@epimass.UUCP (Joe Buck) writes:
>>
>>Net.micro.16k is NOT for discussion of computers with 16k RAM.
>>It is for discussion of the National Semiconductor 32000 series
>>architecture,
>
>This name is obviously no longer appropriate.  I suspect that the group
>is currently so small because National 32000 users don't know they have
>a group.  How about a change?
>
>I propose net.micro.nsc.  Other suggestions are welcome.
>
	I second this motion! I certainly didn't know what it was
about.(I now intend to subscribe to the group).
-- 

				Sarima (Stanley Friesen)

UUCP: {ttidca|ihnp4|sdcrdcf|quad1|nrcvax|bellcore|logico}!psivax!friesen
ARPA: ??

chad@anasazi.UUCP (05/05/86)

I agree the name doen't reflect the purpose of the group.  I read it
for quite a while before I figured it out.  I thought it was for
micro's that had 16 bit memory paths (8086 vs 8080 for example).
However net.micro.nsc, though better, still is ambiguous since
National makes lots of things--including analog stuff.  Also, TI
second-sources the parts.  How about "net.micro.32xxx"?
	-crl
-- 
"I read the news today...oh, boy!"
	-John Lennon
_____________________________________________________________________
UUCP:    {mot!terak}!anasazi!chad               Voice: Hey, Chad!
Ma Bell: (602) 870-3330                         ICBM:  N33deg,33min
Surface: International Anasazi, Inc.                   W112deg,03min
         7500 North Dreamy Draw Drive
         Suit 120
         Phoenix, AZ 85020

pavo@sally.UUCP (budsky) (05/06/86)

I think a name change is a GREAT idea.  maybe we could change it
everytime national announces a new part!  or maybe when a part
blows up we could call it net.challenger.  but what i really think
we ought to do is continue talking about name changes instead of
technical issues relating to the NS 32xxx chip set.

		jim

peno@enea.UUCP (Pekka Nousiainen) (05/07/86)

>>Net.micro.16k is NOT for discussion of computers with 16k RAM.
>>It is for discussion of the National Semiconductor 32000 series

What!!??  I've just spent a year working on an NS32016 machine and
I *never* checked out net.micro.16k because, yes, I did think it was
for 16k RAM....

--
Path:  ...!mcvax!enea!peno        In "real" life:  Pekka Nousiainen

chongo@nsc.UUCP (Landon Noll) (05/09/86)

In article <1143@psivax.UUCP> you write:
 >In article <204@epimass.UUCP> jbuck@epimass.UUCP (Joe Buck) writes:
 >>>
 >>>Net.micro.16k is NOT for discussion of computers with 16k RAM.
 >>
 >>This name is obviously no longer appropriate.  I suspect that the group
 >>is currently so small because National 32000 users don't know they have
 >>a group.  How about a change?
 >>
 >>I propose net.micro.nsc.  Other suggestions are welcome.
 >>

I do agree that the name should be changed.  I suggest:

		net.micro.ns32000  -or-  net.micro.ns32k

That gets the National Semiconductor in the name as well as the chip
family name.  (net.micro.nsc might cause some people at nsc.UUCP to
think this a group for 'nsc' users to talk about tiny objects... :-)  )

If folks agree th change the group, I promise to try and keep marketing from
adjusting the name of the chipset again.... :-)

chongo <My other micro has a 32532> /\ns/\

root@ucsfcca.UUCP (05/11/86)

> >Every year or so it has to be said.
> >
> >Net.micro.16k is NOT for discussion of computers with 16k RAM.
> 
> This name is obviously no longer appropriate.  I suspect that the group
> is currently so small because National 32000 users don't know they have
> a group.  How about a change?
> 

Clearly 16k is a bad name. Of the proposals made I vote for 

            net.micro.ns32k

How do we get it done?

Thos Sumner    (...ucbvax!ucsfcgl!ucsfcca.UCSF!thos)