🚀 go-pugleaf

I rolled back the video card drivers a bit more carefully than I did
the first time and managed to get the 45.xx drivers installed.  The
game displays correctly now, thanks for your help!

Dragon

On Sun, 21 Dec 2003 00:01:14 -0600, "Margolis" <someone@somewhere.org>
wrote:

>"none" <none@specified.com> wrote in message
>news:anq9uv817p30oijik48ot8rmcvuv51ru98@4ax.com...
>> I'm attempting to play a patched version (latest patch) of Generals on
>> a Dell 4400 series with a 2 gig chip and 512k RAM with an NVIDIA
>> GEforce2 MX card with 64mb of memory.  I currently am running the
>> 45.xx drivers for the card, after reading a post that suggested that
>> the 52.xx drivers caused some problems.  I'm experiencing the problem
>> under both drivers.   From the opening menu screen the terrain does
>> not display properly regardless of the resolution settings- the ground
>> has large black areas where textures should be mapped.  It seems like
>> areas that should have textures are mapped correctly, but areas that
>> are a solid color turn black and stay that way.  The same thing
>> happens in the missions- the first mission for the USA path, which
>> takes place in snow, for instance, is completly black with ghostly
>> little tanks running around on it.
>>
>> Any ideas?
>>
>> Dragon
>
>
>this sounds exactly like the 52.16 driver problems.   Check your drivers to
>verify if they truly are the 45.xx drivers.   Did you change your drivers
>with an executable or through windows device manager?  If it was through
>windows device manager and you have broadband there is a very good chance
>that even though you pointed to the 45.xx  drivers on your computer, it
>still downoaded and installed the 52.16 drivers from window update site
>instead.
>
>If that is truly not the problem, did the game work before? Make sure you
>completely uninstall the drivers and reboot and cancel the video driver
>installation that will pop up.  Then install the new drivers.  You could go
>back to the 44.90 drivers, but the 45.23 drivers should also work well.
>This was a bug specific to the 52.16.  You could also go to www.guru3d.com
>and download the 53.03 drivers which fixed quite a few bugs in the 52.16,
>including this problem ;o)
>
>if you are using winxp, you could also just restore back to a point before
>the driver problem popped up.