Does 175.16_geforce_winxp_32bit_english_whql.exe have problems withCRT TV output via composite?

Mr.E Solved! wrote:
> Ant wrote:
>> On 6/3/2008 9:20 PM PT, Mr.E Solved! typed:
>>
>>> I have no idea which driver to go back to, weren't there more than
>>> one version of the 174.74 betas kicking around?
>>
>> Tip for you: Always keep the previous driver(s) that worked just in
>> case. I am glad I kept the working one before 175.16 even if it is a
>> beta.
>
> Aren't you cute thinking I don't have the entire library of versions to
> pick and choose from. <pinches your cheek>
>
> At issue is I don't know which version to use, since the past several
> save been steadily degrading performance, also I use nhancer which makes
> it problematic to deal with video driver uninstalling and reinstalling.
>
> NVidia has purposely tried to lock out nhancer's meddling, and you have
> to play the matching-version game or nothing works.
>
> Not to mention ntune needs to be uninstalled and reinstalled in the
> proper order in the driver update process, if you want to be sure of
> getting the right settings as ntune and the new nvidia control panel are
> now permanently entwined.
>
> There is lots of dark pc-juju floating around these days, I don't like
> it one bit.
>
>

174.74 has been stable since beta, before that I used 169.61 (a Quadro
driver). Actually using Quadro drivers is a good idea in many cases
since they're not so heavily optimized and easier to track down what's
causing a crash or bug; they're usually more stable and subjectively
have better IQ. Also unless you absolutely need nTune, I recommend
removing it as it has caused several stuttering and crash related issues
with my brother's 8600 setup and I've seen many complaints about it
(probably due to the service that gets installed). A good alternative
is 'hwmonitor' or RivaTuner for temps.

root wrote:
>> I don't understand how NVIDIA certified this driver for release. Beta
>> was better than the certified!! I am scared to upgrade my NVIDIA drivers
>> now.
>
> WHQL = windows hardware quality labs. If this driver is certified it's a big mistake by microsoft. I don't think it is qualified for xp since 175.16 (beta) breaks remote desktop on the machine it's installed on. You can't remote desktop into the system. http://forums.nvidia.com/index.php?s...ic=67147&st=20
>
>


Try the 175.80's

http://en.expreview.com/2008/05/29/d...driver-leaked/

Links to Win XP 32-bit and 64-bit as well as Vista 32-bit and 64-bit 175.80

On 6/4/2008 11:01 PM PT, Mr.E Solved! typed:

>>> I don't understand how NVIDIA certified this driver for release. Beta
>>> was better than the certified!! I am scared to upgrade my NVIDIA drivers
>>> now.
>>
>> WHQL = windows hardware quality labs. If this driver is certified it's
>> a big mistake by microsoft. I don't think it is qualified for xp since
>> 175.16 (beta) breaks remote desktop on the machine it's installed on.
>> You can't remote desktop into the system.
>> http://forums.nvidia.com/index.php?s...ic=67147&st=20
>
> Try the 175.80's
>
> http://en.expreview.com/2008/05/29/d...driver-leaked/
>
>
> Links to Win XP 32-bit and 64-bit as well as Vista 32-bit and 64-bit 175.80

I wonder if it fixes my TV out issue? Meh, I will just wait a bit until
I really need an upgrade.
--
"Everyone knows an ant can't move a rubber tree plant." --Motto of FTL
Foundation (in Isaac Asimov book)
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
( ) or ANTant@zimage.com
Ant is currently not listening to any songs on his home computer.

"Mr.E Solved!" <Iamsingle@askme.out> wrote in
news:O5adnVJtCcBnitvVnZ2dnUVZ_sWdnZ2d@comcast.com:

> I can't get BF2 to stay stable either, it quickly CTDs with no warning
> or trace after a few minutes.

That's because DICE use spaghetti code. Their games are a cluster **** in
general and always require massive patching. It's a miracle they run at
all.

root <no@1.invalid> wrote in news:g27hl1$***$1@news.albasani.net:

>
> WHQL = windows hardware quality labs. If this driver is certified it's
> a big mistake by microsoft.

WHQL is a sham. I bet all they do is run one game and give them WHQL
certification.

On 6/5/2008 5:48 AM PT, House Of The White Rose typed:

> "Mr.E Solved!" <Iamsingle@askme.out> wrote in
> news:O5adnVJtCcBnitvVnZ2dnUVZ_sWdnZ2d@comcast.com:
>
>> I can't get BF2 to stay stable either, it quickly CTDs with no warning
>> or trace after a few minutes.
>
> That's because DICE use spaghetti code. Their games are a cluster **** in
> general and always require massive patching. It's a miracle they run at
> all.

Um, the OP didn't have problems before the driver upgrade.
--
"He who storms in like a whirlwind returns like an ant." --Borneo
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
( ) or ANTant@zimage.com
Ant is currently not listening to any songs on his home computer.

"House Of The White Rose" <no@email.invalid> wrote in message
news:FhR1k.7789$gc5.2988@pd7urf2no...
> root <no@1.invalid> wrote in news:g27hl1$***$1@news.albasani.net:
>
>>
>> WHQL = windows hardware quality labs. If this driver is certified it's
>> a big mistake by microsoft.
>
> WHQL is a sham. I bet all they do is run one game and give them WHQL
> certification.

It can take days to qualify a video driver.
Try it and see for yourself.
http://www.microsoft.com/whdc/default.mspx
http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx

"Rev. 11D Meow!" <Jimmy@Crack.corn> wrote in news:1u5olr.h31.17.1
@news.alt.net:

> It can take days to qualify a video driver.
> Try it and see for yourself.
> http://www.microsoft.com/whdc/default.mspx
> http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx

Then how is it that I have used WHQL drivers in the past that have been
more buggy than beta drivers?

"House Of The White Rose" <no@email.invalid> wrote in message
news:O0j2k.8269$js6.6555@pd7urf1no...
> "Rev. 11D Meow!" <Jimmy@Crack.corn> wrote in news:1u5olr.h31.17.1
> @news.alt.net:
>
>> It can take days to qualify a video driver.
>> Try it and see for yourself.
>> http://www.microsoft.com/whdc/default.mspx
>> http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx
>
> Then how is it that I have used WHQL drivers in the past that have been
> more buggy than beta drivers?

I knew a guy that WHQLed a hardware device that didn't actually exist.

Rev. 11D Meow! wrote:
> "House Of The White Rose" <no@email.invalid> wrote in message
> news:O0j2k.8269$js6.6555@pd7urf1no...
>> "Rev. 11D Meow!" <Jimmy@Crack.corn> wrote in news:1u5olr.h31.17.1
>> @news.alt.net:
>>
>>> It can take days to qualify a video driver.
>>> Try it and see for yourself.
>>> http://www.microsoft.com/whdc/default.mspx
>>> http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx
>> Then how is it that I have used WHQL drivers in the past that have been
>> more buggy than beta drivers?
>
> I knew a guy that WHQLed a hardware device that didn't actually exist.
>
>
>

If code is sent in before the beta is released, it may be a snapshot of
what should be the final release, but a beta may be a snapshot from
after the point at which the original code was sent (with merged bug fixes).