Camelmaster
Chieftain
Major kudos go to 'kcbrown' from the www.apolyton.net boards. I saw this fix there, and so I thought it was so good that I should show it here, too. Here is his original message. This did the trick for me!
------------------------------------------------------------------------------------
Here's how you fix this problem.
1. Go to http://www.guru3d.com/files and click on Videocard Drivers, then NVIDIA detonator drivers. You'll be presented with a list of drivers.
2. Grab the Detonator 12.41 WHQL drivers that are appropriate for your platform. The drivers are in the form of an executable, but at least for Win2K you can open it up in your zip file handler program (I use Powerarchiver myself, but most people use Winzip).
3. Extract the nvoglnt.dll file into the directory that Civ3 is installed (i.e., the directory that the game executable resides in). This works under Win2K, as executables seem to pick up DLLs first in the home directory of the executable, then the system directories. This might not work everywhere. If it doesn't have an effect, then you'll have to place it in your system32 directory or system directory (wherever your current nvoglnt.dll file resides).
This procedure worked for me. Give it a shot...can't hurt...
------------------------------------------------------------------------------------
Here's how you fix this problem.
1. Go to http://www.guru3d.com/files and click on Videocard Drivers, then NVIDIA detonator drivers. You'll be presented with a list of drivers.
2. Grab the Detonator 12.41 WHQL drivers that are appropriate for your platform. The drivers are in the form of an executable, but at least for Win2K you can open it up in your zip file handler program (I use Powerarchiver myself, but most people use Winzip).
3. Extract the nvoglnt.dll file into the directory that Civ3 is installed (i.e., the directory that the game executable resides in). This works under Win2K, as executables seem to pick up DLLs first in the home directory of the executable, then the system directories. This might not work everywhere. If it doesn't have an effect, then you'll have to place it in your system32 directory or system directory (wherever your current nvoglnt.dll file resides).
This procedure worked for me. Give it a shot...can't hurt...