public inbox for gentoo-performance@lists.gentoo.org
 help / color / mirror / Atom feed
From: XFry <xfry@yandex.ru>
To: Pierrick Couturier <gentoo-performance@lists.gentoo.org>
Subject: Re[2]: [gentoo-performance] How to get Maximum performance in Graphics on Nvidia Drivers
Date: Tue, 24 Jan 2006 22:23:29 +0300	[thread overview]
Message-ID: <608434114.20060124222329@yandex.ru> (raw)
In-Reply-To: <43D53F84.8080503@free.fr>

Çäđŕâńňâóéňĺ, Pierrick.

Âű ďčńŕëč 23 ˙íâŕđ˙ 2006 ă., 23:41:40:

> prymitive wrote:
>> ---- Wiadomość Oryginalna ----
>> Od: Roman Gaufman <hackeron@gmail.com>
>> Do: gentoo-performance@lists.gentoo.org
>> Data: Mon, 23 Jan 2006 19:57:28 +0000
>> Temat: Re: [gentoo-performance] How to get Maximum performance 
>> in Graphics on Nvidia Drivers
>>
>>   
>>> 1) get a GeForce 7800 GTX
>>> 2) use masked drivers
>>> 3) dont use antialiasing or sharpening of any kind
>>> 4) overclock the card until your pc crashes every couple of minutes
>>> 5) play games with low demands (higher fps)
>>>
>>> you'll have kick ass performance!
>>>     
>>
>>  Don't forget to switch to 320x240 resolution (or lower) ;)
>>
>>
>>   
> 2x Geforce 7800 GTX with SLI-ready motherboard (2x PCI-Express 16x) are 
> even better ;-)

   that's good
   but it is too expensive (GF 7800)

   I Asked: is there some configuration tricks to get more performance on GF FX 5500. (Or Any GF)
   MotherBoard: Asus TUV4X (VIA Apollo Pro 133T/AGP4x)

-- 
Ń óâŕćĺíčĺě,
 XFry                          mailto:xfry@yandex.ru

-- 
gentoo-performance@gentoo.org mailing list



  reply	other threads:[~2006-01-24 16:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  0:40 [gentoo-performance] gentoo-performance Ken Robbins
2006-01-20  2:28 ` lnxg33k
2006-01-20  2:30   ` Chris
2006-01-20  2:50     ` lnxg33k
2006-01-20  3:32       ` Kyle Lutze
2006-01-20  4:39       ` Christopher Bergström
2006-01-20  5:21         ` Jeremy Brake
2006-01-20  5:26           ` lnxg33k
2006-01-20  5:46             ` Michael Liesenfelt
2006-01-20  5:43           ` darren kirby
2006-01-20  6:02             ` Christopher Bergström
2006-01-20  7:44               ` darren kirby
2006-01-20  6:35           ` Alec Warner
2006-01-20  6:53             ` Jeremy Brake
2006-01-20 16:48             ` [gentoo-performance] gentoo-performance (sync speedups) lnxg33k
2006-01-21  0:36               ` Alec Warner
2006-01-21  1:03                 ` lnxg33k
2006-01-20 13:51         ` [gentoo-performance] gentoo-performance Bill Roberts
2006-01-20 14:43           ` Christopher Bergström
2006-01-23 22:38             ` [gentoo-performance] How to get Maximum performance in Graphics on Nvidia Drivers XFry
2006-01-23 19:57               ` Roman Gaufman
2006-01-23 20:08                 ` prymitive
2006-01-23 20:41                   ` Pierrick Couturier
2006-01-24 19:23                     ` XFry [this message]
2006-01-25  0:07                       ` Pierrick Couturier
2006-01-25  0:13                         ` Chris
2006-01-23 20:02               ` omghaai
2006-01-23 20:04                 ` [gentoo-performance] /proc/* under 2.6 Chris
2006-01-20  3:29     ` [gentoo-performance] gentoo-performance Alex Efros

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=608434114.20060124222329@yandex.ru \
    --to=xfry@yandex.ru \
    --cc=gentoo-performance@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox