First post, by bofh.fromhell
- Rank
- Oldbie
Greetings fellow retro nerds.
While doing some testing using similar hardware except motherboard/CPU/Memory I've encountered a weird thing.
Hardware is as follows:
System 1: Intel 815EP chipset with a 1GHz Pentium 3 EB using 512MB memory.
System 2: Intel 850 Chipset, 1.5GHz S423 Pentium 4 and 512MB RDRAM.
System 3: AMD 760 Chipset, Thunderbird 1200C and 1GB DDR Memory.
All peripherals are identical (nothing our of the ordinary) the graphics card is a Quadro FX3000.
Its running a fresh Windows 2000 SP4 (also tried with the unofficial SP5), DX9 installed.
Latest chipset drivers are installed.
All benchmarks run just fine with the latest Quadro 169.96 drivers, EXCEPT Quake 3 Arena (both demo ver 1.11 and retail 1.32c) on the AMD system!
I can only get the AMD system to run Q3A if I install the Forceware 162.67 drivers.
Now why would only the AMD system prevent Q3 from running properly with the Quadro drivers?
I guess I could just compare the systems using the Forceware drivers, but this thing annoys me.
In my experience Q3 runs on just about anything!
Q3 errorlog below.
To me it looks like the standard wrong resolution errors.
But that should be easily sorted by deleting the .cfg files.
Q3 1.32c win-x86 May 8 2006
----- FS_Startup -----
Current search path:
D:\Spel\Quake3\baseq3\pak8.pk3 (9 files)
D:\Spel\Quake3\baseq3\pak7.pk3 (4 files)
D:\Spel\Quake3\baseq3\pak6.pk3 (64 files)
D:\Spel\Quake3\baseq3\pak5.pk3 (7 files)
D:\Spel\Quake3\baseq3\pak4.pk3 (272 files)
D:\Spel\Quake3\baseq3\pak3.pk3 (4 files)
D:\Spel\Quake3\baseq3\pak2.pk3 (148 files)
D:\Spel\Quake3\baseq3\pak1.pk3 (26 files)
D:\Spel\Quake3\baseq3\pak0.pk3 (3539 files)
D:\Spel\Quake3/baseq3
----------------------
4133 files in pk3 files
execing default.cfg
execing q3config.cfg
execing autoexec.cfg
Hunk_Clear: reset the hunk ok
...detecting CPU, found AMD w/ 3DNow!
------- Input Initialization -------
No window for DirectInput mouse init, delaying
Joystick is not active.
------------------------------------
----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'C:\WINNT\system32\opengl32.dll' ): succeeded
...setting mode -1: 600 800 FS
...using colorsbits of 32
...calling CDS: failed, bad mode
...trying next higher resolution: ok
...registered window class
...created window@0,0 (600x800)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 32, 24, 8 )
...35 PFDs found
...GLW_ChoosePFD failed
...GLW_ChoosePFD( 32, 24, 0 )
...35 PFDs found
...GLW_ChoosePFD failed
...failed to find an appropriate PIXELFORMAT
...restoring display settings
...WARNING: could not set the given mode (-1)
...setting mode -1: 600 800 FS
...using colorsbits of 16
...calling CDS: failed, bad mode
...trying next higher resolution: ok
...created window@0,0 (600x800)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 16, 24, 8 )
...35 PFDs found
...GLW_ChoosePFD failed
...GLW_ChoosePFD( 16, 24, 0 )
...35 PFDs found
...GLW_ChoosePFD failed
...failed to find an appropriate PIXELFORMAT
...restoring display settings
...WARNING: could not set the given mode (3)
...shutting down QGL
...unloading OpenGL DLL
...assuming '3dfxvgl' is a standalone driver
...initializing QGL
...WARNING: missing Glide installation, assuming no 3Dfx available
...shutting down QGL
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
GLW_StartOpenGL() - could not load OpenGL subsystem
