Article View: alt.games.quake2
Article #270987Re: Celeron vs. P3 for gaming?
From: qwer...
Date: Mon, 27 Nov 2000 00:00
Date: Mon, 27 Nov 2000 00:00
30 lines
1813 bytes
1813 bytes
In article <8urj96$1f0$1...@nnrp1.deja.com>, qwer...@my-deja.com wrote: > I can't take it any more, the P166 is going to server duty and I'm > building a new system. My question is this: I have been advised by > several game-junky friends that it's not worth the extra $ to get a P3 > chip over a minimum 600mHz Celeron. True of not? Cause I certainly have > better things to do with the extra bucks. I just want something that > won't choke on wide-open maps with lots of models (ie- arena-type > railgun only servers). Thanks!! > > Mark > > Sent via Deja.com http://www.deja.com/ > Before you buy. > Update in case anyone's interested. I ponied up for a Cel633 (they didn't have a 600 so gave me a boxed 633 for the same $....nice). An ABIT VL6 mobo, 128meg PC133 RAM, and new ATX case. Went from 20ish fps for the old P166 (16bit @ 640x480) to 94.4 fps @ 800x600 (Voodoo3 2000). Damn, why did I not do this earlier. Total cash outlay was a little under $300 for the lot and just stripped the 166 of cards/HD/etc. Next project is to overclock the CPU to 900ish and the Voodoo to 166. Results to follow. Mark Sent via Deja.com http://www.deja.com/ Before you buy.
Technical Details
Message-ID:
<8vu9kv$58d$1@nnrp1.deja.com>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<8urj96$1f0$1@nnrp1.deja.com>Show Full Headers
Complete Article Headers
From: qwer...@my-deja.com Subject: Re: Celeron vs. P3 for gaming? Date: 2000/11/27 Message-ID: <8vu9kv$58d$1@nnrp1.deja.com> X-Deja-AN: 698327594 References: <8urj96$1f0$1@nnrp1.deja.com> X-Http-Proxy: 1.0 cache590, 1.0 x65.deja.com:80 (Squid/1.1.22) for client 158.111.217.31, 158.111.4.25 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Mon Nov 27 18:37:21 2000 GMT X-MyDeja-Info: XMYDJUIDqwerty700 Newsgroups: alt.games.quake2 X-Http-User-Agent: Mozilla/4.7 [en] (Win95; I) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit