Robert Gault wrote:
> deimos wrote:
>
>> de Moni wrote:
>>
>>> Those who are saying that ATI's drivers suck, then come
>>> and see screwed up graphics of my GF2 Titanium powered
>>> by the latest 66.93-drivers by NVidia!
>>>
>>> UT2003: Every goddamn thing in level starts to flicker and
>>> makes playing quite impossible.
>>>
>>> C&C Generals: Every goddamn vehicle and building is white,
>>> flags are white and there's no way to tell what units/buldings
>>> belongs to who. Areas where should be color marks are
>>> showing just plain white.
>>>
>>> Battlezone2: Radar doesn't show shapes of the terrain, only
>>> dots (units). No damage bars when I'm shooting enemy and
>>> no line between command menu and unit I'm commanding.
>>>
>>> So, what driver to use to get everything work correctly?
>>> Would be absolute pain to download every driver set
>>> using dial-up and I don't have NVidia-drivers anywhere on
>>> CDs.
>>>
>>
>> Use the latest official drivers. They'll work just fine and provide
>> software level support for any DX version.
>>
>> If you're experiencing strange artifacting, take a very close look at
>> your system configuration and chipset bugs. For example, whether
>> Sideband Addressing and Fast-Writes might be affecting it, or
>> aggressive memory settings, or a bad chipset driver (i.e. motherboard
>> chipset, like KT333, etc) with known incompatibilities.
>>
>> Anytime I've ever had a problem with artifacts it's always been one of
>> several 3 things:
>>
>> 1. Overclocking
>> 2. Chipset driver (e.g. "MWQ" bug on a KT133a, AGP timings)
>> 3. Configuration (FastWrites on in BIOS, but GPU BIOS does not support).
>>
>
> You keep saying that but you should read the threads on the nZone
> forums. There are many reports of 66.94 (official nVidia release) not
> working for any Win98 system and no reports of anyone having success.
>
> Ex. http://forums.nvidia.com/index.php?showtopic=1568
I didn't see Win98 in the original thread. Also, such an OS which is
inherently unstable and prone to errors is not a very good platform to
diagnose bugs.
Additionally, if it were _one_ release only (66.94), then the problem
could easily be traced to it, but I have not seen that common cause.
Many of the posts relate to older versions or unspecified ones.
So to diagnose this particular situation, 'de Moni' should revert to a
previous WHQL driver version and start from there. All previous
releases are available on NVIDIA's ftp:
ftp://download.nvidia.com
61.77, 56.72, and 52.16 might be a good place to start.
Now if it still doesn't work and reproduces the same errors/artfiacts
without respect to the driver version, you have to look deeper into
what's causing it.
It's very possible that the Win98 driver is incompatible with many cards
or it's a bad release (not all that many people use a Win9x system much
anymore so it might be understandable for less regression and error
testing to have occurred). Sometimes AGP settings are _strictly_
enforced through the driver itself and this may conflict with Win98's
AGP subsystem or chipset drivers for Win98.
But you shouldn't just automatically assume it's one component without
further inspection.