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>>
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?
--
<<Phoenix>>
>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.
>> 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>>
Ah, well then it'll probably be Voodoo, but until that time, it doesn't
really matter.
> 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
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>>
Quoted text (18 lines)
> and consumer level cards. What then, huh? Huh, huh? > -- > <<Phoenix>> > >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. > >> 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 weThis is a multi-part message in MIME format.
------=_NextPart_000_024D_01BCE15C.AC425380
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Why wait till the last second? There are some ppl that will confuse, =
especially if they don't keep up with the news.
--=20
<<Phoenix>>
it
saying,
>> >"get a Diamond". Saying 3Dfx means you get Voodoo or a newer = version of
>> >Voodoo.
>> >> 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,
------=_NextPart_000_024D_01BCE15C.AC425380
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>
<META content=3D'"MSHTML 4.71.2016.0"' name=3DGENERATOR>
</HEAD>
<BODY>
<DIV><FONT face=3DVerdana>Why wait till the last second? There are some =
ppl that=20
will confuse, especially if they don't keep up with the =
news.</FONT></DIV>
<DIV><FONT face=3DVerdana><BR>--=20
<BR><<Phoenix>><BR></FONT> </DIV>
it'll=20
probably be Voodoo, but until that time, it doesn't<BR>>really=20
matter.<BR>><BR>>Robin Sequira <<A=20
wrote in=20
article<BR>><<A=20
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", =
someone=20
gets a Rush, and is pissed that it<BR>>> isn't as fast as Voodoo? =
Or what=20
if they start making some higher end<BR>>card<BR>>> and =
consumer level=20
cards. What then, huh? Huh, huh?<BR>>> <BR>>> --<BR>>> =
<BR>>> <<Phoenix>><BR>>> <BR>>> Kieron =
Dodds wrote=20
>Isn't=20
this argument a little anal? I mean, it's not like you're=20
saying,<BR>>> >"get a Diamond". Saying 3Dfx =
means you=20
get Voodoo or a newer version of<BR>>> >Voodoo.<BR>>>=20
><BR>>> >Robin Sequira <<A=20
wrote in=20
article<BR>>> ><<A=20
spring.com</A>>...<BR>>>=20
>> Should we say 3Dfx card, or Voodoo card? It's like Netscape=20
Navigator.<BR>>> >When<BR>>> >> we say Netscape, we =
mean=20
Netscape's product, Navigator, and when we<BR>>say<BR>>> =
>> 3Dfx,=20
we mean Voodoo. But Navigator is pretty much Netscape's only<BR>>> =
>end-user<BR>>> >> product. 3Dfx will be coming out with =
more=20
chips like the Voodoo 2 and<BR>>> >> Banshee, and the Rush =
is=20
already here. So shouldn't we say "get =
a<BR>>Voodoo"<BR>>>=20
>> instead of "Get a 3Dfx?" In the future, that might =
cause=20
confusion,<BR>>which<BR>>> >we<BR>>> >> cold =
avoid by=20
saying "voodoo" now.<BR>>> >><BR>>> >> =
--<BR>>> >> <<Phoenix>><BR>>> =
>><BR>>>=20
>><BR>>> >><BR>>> >><BR>>> =
<BR>>>=20
<BR>>></BODY></HTML>
------=_NextPart_000_024D_01BCE15C.AC425380--
Quoted text (9 lines)
>Ah, well then it'll probably be Voodoo, but until that time, it doesn't >really matter. >> 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 =Quoted text (10 lines)
>> 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 >> >Isn't this argument a little anal? I mean, it's not like you're =Quoted text (9 lines)
>which >> >we >> >> cold avoid by saying "voodoo" now. >> >> -- >> >> <<Phoenix>> >>=20 >>=20This 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$[email hidden]>...
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 <[email hidden]> wrote in article
><62qu42$[email hidden]>...
>> 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
<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 <[email hidden]> wrote in article
>> ><62oimj$[email hidden]>...
>> >> 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,
------=_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<[email hidden]> wrote in message <<A=20
=
href=3D"mailto:62ti5i$[email hidden]">62ti5i$[email hidden]=
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<[email hidden]> 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:[email hidden]">[email hidden]</A>> =
wrote in=20
article<BR>><<A=20
=
href=3D"mailto:62qu42$[email hidden]">62qu42$[email hidden]=
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:[email hidden]">[email hidden]</A>> =
wrote in=20
article<BR>>> ><<A=20
=
href=3D"mailto:62oimj$[email hidden]">62oimj$[email hidden]=
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--
Quoted text (8 lines)
>card >> and consumer level cards. What then, huh? Huh, huh? >>=20 >> -- >>=20 >> <<Phoenix>> >>=20 >> Kieron Dodds wrote in message =Quoted text (13 lines)
>which >> >we >> >> cold avoid by saying "voodoo" now. >> >> >> >> -- >> >> <<Phoenix>> >> >> >> >> >> >> >> >> >>=20 >>=20 >>=20This is a multi-part message in MIME format.
------=_NextPart_000_00D7_01BCE2ED.786458A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
OK, so it's agreed. But wait, that's different for individual chips, =
isn' t it?
--=20
<<Phoenix>>
Look, lets just start using the product numbers on the chips. From =
now on, it's 47y23598712340981340983250980982435. OK? Good.
=20
=20
------=_NextPart_000_00D7_01BCE2ED.786458A0
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"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<META content=3D'"MSHTML 4.71.2016.0"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>OK, so it's agreed. But =
wait, that's=20
different for individual chips, isn' t it?</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2><BR>--=20
<BR></FONT><BR><<Phoenix>><BR> </DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<<A=20
=
<DIV><FONT color=3D#000000 size=3D2>Look, lets just start using the =
product=20
numbers on the chips. From now on, it's =
47y23598712340981340983250980982435.=20
OK? Good.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV> </DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_00D7_01BCE2ED.786458A0--
This is a multi-part message in MIME format.
------=_NextPart_000_0050_01BCE36D.0B721EA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hmmm,=20
A long time ago I bought a Rockwell based modem, I tried it out, it =
sucked, I returned it, got a real modem. =20
Most people should read a few reviews which are everywhere on the net =
and in game magazines. I'd go with game mag's reviews over general =
computer mags since that's what they, and we, are most interested in, =
and they'll give the most detailed reviews. (chart comparisons, =
framerates, what computer setup they have, what games they're running, =
resolutions, etc)
Go to your favorite computer store (ONE THAT HAS A HARDWARE RETURN =
POLICY), buy the card based upon what you learned in your reviews, then =
if it doesn't perform as you expected, RETURN IT and get another one. =
If you've done your homework reading/comparing reviews, chances are you =
won't need to return it. (I obviously didn't when buying that software =
based modem).
Obviously you can take people's recommendations from the newsgroups, but =
you do have to take them with a grain of salt. From a lot of reported =
framerates I've read about, you've gotta wonder if the people claiming =
these figures are inflating them a bit. Of course, by scanning the =
headers in a newsgroup, you can quickly see which cards have buggy =
drivers, etc.
There's quite an abundance of cards out there, people calling them =
different names, people not fully understanding what card does what, =
etc, etc. So by reading the reviews, you'll be able to see comparisons =
and the actual names of the cards. As opposesd to someone saying get a =
3dfx card, buy a Rush, go Voodoo, etc. because a stingray is actually a =
3dfx Voodoo Rush card whereas a monster3d is a 3dfx voodoo graphics =
card, so there will definetly be some confusion unless you follow the =
above advice, or you're some smart-ass computer whiz who knows =
everything anyway ;)
My $.08 in your $.25 conversation.
-FaNaTiC- =20
OK, so it's agreed. But wait, that's different for individual chips, =
isn' t it?
=20
--=20
=20
<<Phoenix>>
=20
Look, lets just start using the product numbers on the chips. =
From now on, it's 47y23598712340981340983250980982435. OK? Good.
=20
=20
------=_NextPart_000_0050_01BCE36D.0B721EA0
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"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!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>Hmmm, </FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>A long time ago I bought a Rockwell based modem, I =
tried it=20
out, it sucked, I returned it, got a real modem. </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Most people should read a few reviews which are =
everywhere on=20
the net and in game magazines. I'd go with game mag's reviews over =
general=20
computer mags since that's what they, and we, are most interested in, =
and=20
they'll give the most detailed reviews. (chart comparisons, framerates, =
what=20
computer setup they have, what games they're running, resolutions,=20
etc)</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Go to your favorite computer store (ONE THAT HAS A =
HARDWARE=20
RETURN POLICY), buy the card based upon what you learned in your =
reviews, then=20
if it doesn't perform as you expected, RETURN IT and get another =
one. If=20
you've done your homework reading/comparing reviews, chances are =
you won't=20
need to return it. (I obviously didn't when buying that software =
based=20
modem).</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Obviously you can take people's recommendations from =
the=20
newsgroups, but you do have to take them with a grain of salt. =
From a lot=20
of reported framerates I've read about, you've gotta wonder if the =
people=20
claiming these figures are inflating them a bit. Of course, by =
scanning=20
the headers in a newsgroup, you can quickly see which cards have buggy =
drivers,=20
etc.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>There's quite an abundance of cards out there, =
people calling=20
them different names, people not fully understanding what card does =
what, etc,=20
etc. So by reading the reviews, you'll be able to see comparisons =
and the=20
actual names of the cards. As opposesd to someone saying get a =
3dfx card,=20
buy a Rush, go Voodoo, etc. because a stingray is actually a 3dfx Voodoo =
Rush=20
card whereas a monster3d is a 3dfx voodoo graphics card, so there will =
definetly=20
be some confusion unless you follow the above advice, or you're some =
smart-ass=20
computer whiz who knows everything anyway ;)</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>My $.08 in your $.25 conversation.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>-FaNaTiC- </FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
=
spring.com</A>>...</DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>OK, so it's agreed. =
But wait,=20
that's different for individual chips, isn' t it?</FONT></DIV>
<DIV><FONT color=3D#000000 face=3DArial size=3D2><BR>--=20
<BR></FONT><BR><<Phoenix>><BR></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; =
PADDING-LEFT: 5px">
<<A=20
=
<DIV><FONT color=3D#000000 size=3D2>Look, lets just start using =
the product=20
numbers on the chips. From now on, it's=20
47y23598712340981340983250980982435. OK? Good.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT> </DIV>
<DIV> </DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0050_01BCE36D.0B721EA0--
