asdf53 wrote on 2022-02-15, 13:28:

I have a Radeon 9600 Pro and at first I couldn't get it to work either with the newer Catalyst drivers. Even though the drivers […]
Show full quote

I have a Radeon 9600 Pro and at first I couldn't get it to work either with the newer Catalyst drivers. Even though the drivers install without any error message and the card shows up correctly in the device manager, I am still limited to a desktop resolution of 640x480 and Direct3D games don't work.

However, I found this older driver version from 2003:

https://www.helpjet.net/Fs-31741585-59851182-78185101.html

Apparently it's from May 15 2003, Catalyst 3.4 (6.14.10.6343), and it supports the following cards:

Copy code to clipboard

1"ATI MOBILITY FIRE GL 7800" = M7_ENU, PCI\VEN_1002&DEV_4C58
2"ATI MOBILITY FIRE GL 9000" = M9_ENU, PCI\VEN_1002&DEV_4C64
3"ATI MOBILITY RADEON 9600 Series" = M10_ENU, PCI\VEN_1002&DEV_4E50
4"MOBILITY RADEON" = M6_ENU, PCI\VEN_1002&DEV_4C59
5"MOBILITY RADEON 7500" = M7_ENU, PCI\VEN_1002&DEV_4C57
6"MOBILITY RADEON 9000" = M9_ENU, PCI\VEN_1002&DEV_4C66
7"MOBILITY RADEON 9200" = M9Plus_ENU, PCI\VEN_1002&DEV_5C63
8"MOBILITY RADEON 9200 " = M9Plus_ENU, PCI\VEN_1002&DEV_5C61
9"RADEON 7000 SERIES" = RV100_ENU, PCI\VEN_1002&DEV_5159
10"RADEON 7200 SERIES" = R6_ENU_default, PCI\VEN_1002&DEV_5144
11"RADEON 7500 SERIES" = RV200_ENU, PCI\VEN_1002&DEV_5157
12"RADEON 8500 SERIES" = R200_ENU, PCI\VEN_1002&DEV_514c
13"RADEON 9000 SERIES" = RV250_ENU, PCI\VEN_1002&DEV_4966
14"RADEON 9000 SERIES - Secondary" = RV250_ENU, PCI\VEN_1002&DEV_496e
15"RADEON 9100 SERIES" = R200_ENU, PCI\VEN_1002&DEV_514D
16"RADEON 9200" = RV280_ENU, PCI\VEN_1002&DEV_5961
17"RADEON 9200 - Secondary" = RV280_ENU, PCI\VEN_1002&DEV_5941
18"RADEON 9200 PRO" = RV280_ENU, PCI\VEN_1002&DEV_5960
19"RADEON 9200 PRO - Secondary" = RV280_ENU, PCI\VEN_1002&DEV_5940
20"RADEON 9500" = R300_ENU, PCI\VEN_1002&DEV_4144
21"RADEON 9500 - Secondary" = R300_ENU, PCI\VEN_1002&DEV_4164
22"RADEON 9500 PRO / 9700" = R300_ENU, PCI\VEN_1002&DEV_4E45
23"RADEON 9500 PRO / 9700 - Secondary" = R300_ENU, PCI\VEN_1002&DEV_4E65
24"RADEON 9600" = RV350_ENU, PCI\VEN_1002&DEV_4152
25"RADEON 9600 - Secondary" = RV350_ENU, PCI\VEN_1002&DEV_4172
26"RADEON 9600 PRO" = RV350_ENU, PCI\VEN_1002&DEV_4150
27"RADEON 9600 PRO - Secondary" = RV350_ENU, PCI\VEN_1002&DEV_4170
28"RADEON 9700 PRO" = R300_ENU, PCI\VEN_1002&DEV_4E44
29"RADEON 9700 PRO - Secondary" = R300_ENU, PCI\VEN_1002&DEV_4E64
30"RADEON 9800 - Secondary" = R350_ENU, PCI\VEN_1002&DEV_4E69
31"RADEON 9800 PRO" = R350_ENU, PCI\VEN_1002&DEV_4E48

This driver works for me under Windows 95 OSR 2.5. I can select high resolutions, 32 bit color, and play Direct3D games. Since it also lists the Radeon 9200, you could give it a try. I couldn't get the corresponding version of the ATI control panel to work either, but it's not needed for basic operation. I also couldn't get OpenGL to work with these drivers (Quake 3 and Half-Life refuse to start in OpenGL mode).

I also found this history of older ATI driver versions, very helpful to see which versions came out and when:
https://alt.3dcenter.org/downloads/treiber-radeon.php
The download links do not work anymore, but you can google the file names to see if it's still available somewhere. Keep in mind that there are two versions of the early 2000's ATI drivers, one Win2k/XP version and one Windows ME version, you need the Win ME version. Windows 98 and 95 are not officially supported at all, but the Windows ME driver works in some cases.

Are you able to set monitor refreshrate with this driver normally? Because my initial tests were with a Radeon 9600 and an LCD monitor, so I had no reason to change the default.

However I'm currently testing a 9200 with a tube monitor and regardless of which refreshrate I set through Display Properties, the monitor seems to default back to 60 Hz, even though according the driver 85 Hz might be set, eg.

edit:
Looks to have something to do with the video card/driver not being able to deal with the DDC info supplied by the monitor.
The solution that keeps turning up is to uncheck the Use DDC information-setting in the monitor properties of the Displays-tab in advanced display properties.

Does anyone know which registry key the toggle modifies? This guy asked already, but didn't get an answer...

I found the solution in this thread:

I had to append the registry with the following keys:

HKEY_LOCAL_MACHINE\SOFTWARE\ATI Technologies\Driver\0000\DAL
HKEY_LOCAL_MACHINE\SOFTWARE\ATI Technologies\Driver\0000\VxD

Within DAL, I had to create a new binary value: IDCRegOptionDontUserOSMonitorInfo
and set it to 00 00 00 00
Within VxD, I had to create a new binary value: EnableDDC
and set it to 00

I tried modifying the same values within an already existing Driver\0001 hierarchy, but that didn't seem to have any effect. Not sure why the 0000-key and it's sub-keys and values are missing.

Now I'm able to set the refresh rate just like expected. 😀

asdf53 wrote on 2022-02-17, 07:12:

I installed the working 9600 drivers, then I extracted just the old OpenGL driver file (atio9xxx.dll) from the 8500 drivers and put it into windows\system. I now had 9600 drivers with just the 8500 OpenGL driver. When that didn't work, I tried force installing the whole 8500 driver package by spoofing the PCI ID, but that didn't work either, Windows refuses to use these drivers. No wonder it didn't work, but it was worth a try.

I also found this!

Mixing Old OpenGL Driver with Newer Driver […]
Show full quote

Mixing Old OpenGL Driver with Newer Driver

For one reason or another (for example, to correct CounterStrike problems) you may find youself wanting to use, say, Catalyst 3.5's OpenGL driver with the Catalyst 4.4's (one reason you might do this is to get the Dawn demo running). This is possible - Although note that it is NOT possible to mix and match DirectX drivers.

How-To
Install any driver, whichever one you prefer, if you've not already done so. We'll change it's OGL driver in a bit.
Download, but do not install, the Catalyst driver that contains the desired OpenGL driver. You can find previous Catalyst driver versions here. Save whichever driver you downloaded to the desktop.
Download and install WinZip.
Use WinZip to open the Catalyst driver with the desired OpenGL driver. To do this right click the Catalyst package (which should be on the desktop, as I told you), select WinZip, and then "Open With WinZip".
Search for the file atioglxx.dl_ - Double click that file.
A new iteration of WinZip will popup. This is normal. Highlight "atioglxx.dll" and select "Extract" from within WinZip. Extract it to the desktop.
Highlight atioglxx.dll on the desktop and cut it (press CTRL + X) - this puts it onto the clipboard so we can move it.
Browse to C:\Windows\System32 and paste the atioglxx.dll file there (Press CTRL + V). Confirm file replacement. If nothing happens, then you did not cut correctly the atioglxx.dll file as, I told you to in #7.
There, you're done! Go ahead and delete the driver you downloaded to the desktop, since it is no longer necessary.

This can be done with any OpenGL driver on any card with ANY Catalyst as many times as you want - just remember to CONFIRM file replacement in the System32 folder!

[Source] https://www.rage3d.com/board/showthread.php?t … readid=33738545

Do you think we might have a winner here?

leonardo wrote on 2022-09-01, 13:02:

I also found this! […]
Show full quote

asdf53 wrote on 2022-02-17, 07:12:

I installed the working 9600 drivers, then I extracted just the old OpenGL driver file (atio9xxx.dll) from the 8500 drivers and put it into windows\system. I now had 9600 drivers with just the 8500 OpenGL driver. When that didn't work, I tried force installing the whole 8500 driver package by spoofing the PCI ID, but that didn't work either, Windows refuses to use these drivers. No wonder it didn't work, but it was worth a try.

I also found this!

Mixing Old OpenGL Driver with Newer Driver […]
Show full quote

Mixing Old OpenGL Driver with Newer Driver

For one reason or another (for example, to correct CounterStrike problems) you may find youself wanting to use, say, Catalyst 3.5's OpenGL driver with the Catalyst 4.4's (one reason you might do this is to get the Dawn demo running). This is possible - Although note that it is NOT possible to mix and match DirectX drivers.

How-To
Install any driver, whichever one you prefer, if you've not already done so. We'll change it's OGL driver in a bit.
Download, but do not install, the Catalyst driver that contains the desired OpenGL driver. You can find previous Catalyst driver versions here. Save whichever driver you downloaded to the desktop.
Download and install WinZip.
Use WinZip to open the Catalyst driver with the desired OpenGL driver. To do this right click the Catalyst package (which should be on the desktop, as I told you), select WinZip, and then "Open With WinZip".
Search for the file atioglxx.dl_ - Double click that file.
A new iteration of WinZip will popup. This is normal. Highlight "atioglxx.dll" and select "Extract" from within WinZip. Extract it to the desktop.
Highlight atioglxx.dll on the desktop and cut it (press CTRL + X) - this puts it onto the clipboard so we can move it.
Browse to C:\Windows\System32 and paste the atioglxx.dll file there (Press CTRL + V). Confirm file replacement. If nothing happens, then you did not cut correctly the atioglxx.dll file as, I told you to in #7.
There, you're done! Go ahead and delete the driver you downloaded to the desktop, since it is no longer necessary.

This can be done with any OpenGL driver on any card with ANY Catalyst as many times as you want - just remember to CONFIRM file replacement in the System32 folder!

[Source] https://www.rage3d.com/board/showthread.php?t … readid=33738545

Do you think we might have a winner here?

OK... no dice with OpenGL just yet. Trying the atio9xxx.dll from the Radeon 7000-series driver CD just causes crashes. The one from Catalyst 6.2 (Win98) does not crash, but Unreal will cancel startup with an error and while Homeworld will even run after switching to OpenGL, it states that it is not accelerated and recommends switching to software rendering instead.