This is a multi-part message in MIME format.
------=_NextPart_000_0323_01BCE2BD.F9582110
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Look, lets just start using the product numbers on the chips. From now =
on, it's 47y23598712340981340983250980982435. OK? Good.
Steve Phelan.
Robin Sequira wrote in message <62ti5i$...@camel12.mindspring.com>...
Why wait till the last second? There are some ppl that will confuse, =
especially if they don't keep up with the news.
=20
--=20
<<Phoenix>>
=20
Kieron Dodds wrote in message =
<01bce0e0$4eea3800$65722599@desktop>...
>Ah, well then it'll probably be Voodoo, but until that time, it =
doesn't
>really matter.
>
>Robin Sequira <phu...@minsdpring.com> wrote in article
><62qu42$...@camel18.mindspring.com>...
>> So you think they'll *never* have two different chip out at the =
same
>time?
>> What if you say "get a 3Dfx", someone gets a Rush, and is pissed =
that it
>> isn't as fast as Voodoo? Or what if they start making some higher =
end
>card
>> and consumer level cards. What then, huh? Huh, huh?
>>=20
>> --
>>=20
>> <<Phoenix>>
>>=20
>> Kieron Dodds wrote in message =
<01bce013$d0434040$2f752599@desktop>...
>> >Isn't this argument a little anal? I mean, it's not like you're =
saying,
>> >"get a Diamond". Saying 3Dfx means you get Voodoo or a newer =
version of
>> >Voodoo.
>> >
>> >Robin Sequira <phu...@minsdpring.com> wrote in article
>> ><62oimj$...@camel12.mindspring.com>...
>> >> Should we say 3Dfx card, or Voodoo card? It's like Netscape =
Navigator.
>> >When
>> >> we say Netscape, we mean Netscape's product, Navigator, and =
when we
>say
>> >> 3Dfx, we mean Voodoo. But Navigator is pretty much Netscape's =
only
>> >end-user
>> >> product. 3Dfx will be coming out with more chips like the =
Voodoo 2 and
>> >> Banshee, and the Rush is already here. So shouldn't we say =
"get a
>Voodoo"
>> >> instead of "Get a 3Dfx?" In the future, that might cause =
confusion,
>which
>> >we
>> >> cold avoid by saying "voodoo" now.
>> >>
>> >> --
>> >> <<Phoenix>>
>> >>
>> >>
>> >>
>> >>
>>=20
>>=20
>>=20
------=_NextPart_000_0323_01BCE2BD.F9582110
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN">
<META content=3D'"MSHTML 4.71.1712.3"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Look, lets just start using the =
product numbers=20
on the chips. From now on, it's 47y23598712340981340983250980982435. OK? =
Good.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Steve Phelan.</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<DIV>Robin Sequira<PHU...@MINSDPRING.COM> wrote in message <<A=20
=
href=3D"mailto:62ti5i$...@camel12.mindspring.com">62ti5i$...@camel12.mind=
spring.com</A>>...</DIV>
<DIV><FONT face=3DVerdana>Why wait till the last second? There are =
some ppl=20
that will confuse, especially if they don't keep up with the=20
news.</FONT></DIV>
<DIV><FONT face=3DVerdana><BR>--=20
<BR><<Phoenix>><BR></FONT> </DIV>
<DIV>Kieron Dodds<SHADO...@EARTHLINK.NET> wrote in message=20
<01bce0e0$4eea3800$65722599@desktop>...</DIV>>Ah, well then =
it'll=20
probably be Voodoo, but until that time, it doesn't<BR>>really=20
matter.<BR>><BR>>Robin Sequira <<A=20
href=3D"mailto:phu...@minsdpring.com">phu...@minsdpring.com</A>> =
wrote in=20
article<BR>><<A=20
=
href=3D"mailto:62qu42$...@camel18.mindspring.com">62qu42$...@camel18.mind=
spring.com</A>>...<BR>>>=20
So you think they'll *never* have two different chip out at the=20
same<BR>>time?<BR>>> What if you say "get a =
3Dfx",=20
someone gets a Rush, and is pissed that it<BR>>> isn't as fast =
as=20
Voodoo? Or what if they start making some higher =
end<BR>>card<BR>>>=20
and consumer level cards. What then, huh? Huh, huh?<BR>>> =
<BR>>>=20
--<BR>>> <BR>>> <<Phoenix>><BR>>> =
<BR>>>=20
Kieron Dodds wrote in message=20
<01bce013$d0434040$2f752599@desktop>...<BR>>> >Isn't =
this=20
argument a little anal? I mean, it's not like you're=20
saying,<BR>>> >"get a Diamond". Saying 3Dfx =
means=20
you get Voodoo or a newer version of<BR>>> =
>Voodoo.<BR>>>=20
><BR>>> >Robin Sequira <<A=20
href=3D"mailto:phu...@minsdpring.com">phu...@minsdpring.com</A>> =
wrote in=20
article<BR>>> ><<A=20
=
href=3D"mailto:62oimj$...@camel12.mindspring.com">62oimj$...@camel12.mind=
spring.com</A>>...<BR>>>=20
>> Should we say 3Dfx card, or Voodoo card? It's like Netscape =
Navigator.<BR>>> >When<BR>>> >> we say =
Netscape, we=20
mean Netscape's product, Navigator, and when =
we<BR>>say<BR>>>=20
>> 3Dfx, we mean Voodoo. But Navigator is pretty much =
Netscape's=20
only<BR>>> >end-user<BR>>> >> product. 3Dfx =
will be=20
coming out with more chips like the Voodoo 2 and<BR>>> =
>>=20
Banshee, and the Rush is already here. So shouldn't we say "get =
a<BR>>Voodoo"<BR>>> >> instead of "Get a=20
3Dfx?" In the future, that might cause=20
confusion,<BR>>which<BR>>> >we<BR>>> >> cold =
avoid=20
by saying "voodoo" now.<BR>>> >><BR>>> =
>>=20
--<BR>>> >> <<Phoenix>><BR>>>=20
>><BR>>> >><BR>>> >><BR>>>=20
>><BR>>> <BR>>> <BR>>> =
</BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0323_01BCE2BD.F9582110--
