guess you can try installing 6105 driver, and then just copy the opengl32.dll from 6263 as its the only file that has to do with opengl. i am not sure if it would work with other versions of driver though.

feipoa wrote:

I want to use the ATI Direct3D drivers from display driver version 4.11.6105 on a system with display driver version 4.11.6263 installed. The OpenGL drivers from .6263 work, but the Direct3D drivers do not. Likewise, the Direct3D drivers from 6105 work well, but the OpenGL drivers from that package do not. I would prefer not to reinstall the whole display driver when swapping between D3D and OpenGL games. The card of interest is a Rage 128 VR. Does anyone know which system files I'd need to copy from 6105 into my 6263 installation?

I have done similar things to my Rage 128GL back in 1999 or 2000. I wanted to use D3D from drive A and OGL from B. So I installed drive A and copied atio9xaa.dll from B to the system folder.
My 2 cents:
1, It might be better to install the driver with desired D3D driver.
2, You can figure out the OpenGL DLL filename and its residing system folder by going through the driver files in device manager.

noshutdown wrote:

guess you can try installing 6105 driver, and then just copy the opengl32.dll from 6263 as its the only file that has to do with opengl. i am not sure if it would work with other versions of driver though.

opengl32.dll is a windows system file and not included in the ati driver.

OpenGL driver will be just one big file with obvious name like atiogl32.dll, so much easier to change it. Eventually many ogl games might first look into their directory for a opengl32.dll, allowing you to have specific version for each game.

I did not see where in the Device Manager to determine which file names are for D3D and which are for OpenGL. I do see a file named atio9xaa.dll. So this is the only file you had to copy over post driver installation?

I have attached a list of the relavent installation files.

I was not successful in this endevour. I transfered the atio9xaa.dll file from .6263 into \windows\system folder on a system with .6105 drivers installed. Perhaps there is more than 1 opengl file needed? Alternately, how do I determine which are the DirectX files so that I can transfer them into a system with the .6263 driver version installed?

feipoa wrote:

I was not successful in this endevour. I transfered the atio9xaa.dll file from .6263 into \windows\system folder on a system with .6105 drivers installed. Perhaps there is more than 1 opengl file needed? Alternately, how do I determine which are the DirectX files so that I can transfer them into a system with the .6263 driver version installed?

It should be \windows\system32 folder for Win9x systems.

I am using Windows 95c. atio9xaa.dll is located in \windows\system, not \windows\system32. Perhaps Windows 98/98SE/ME place files in different locations. \windows\system32 is empty, with the exception of \windows\system32\drivers, which contains only these files,

Ativbtxx.sys
Ativmdxx.sys
Ativpdxx.sys
Ativraxx.sys
Ativrvxx.sys
Ativsnxx.sys
Ativttxx.sys
Ativtuxx.sys
Ativxbxx.sys
Ativxsxx.sys

feipoa wrote:

I am using Windows 95c. atio9xaa.dll is located in \windows\system, not \windows\system32. Perhaps Windows 98/98SE/ME place fi […]
Show full quote

I am using Windows 95c. atio9xaa.dll is located in \windows\system, not \windows\system32. Perhaps Windows 98/98SE/ME place files in different locations. \windows\system32 is empty, with the exception of \windows\system32\drivers, which contains only these files,

Ativbtxx.sys
Ativmdxx.sys
Ativpdxx.sys
Ativraxx.sys
Ativrvxx.sys
Ativsnxx.sys
Ativttxx.sys
Ativtuxx.sys
Ativxbxx.sys
Ativxsxx.sys

You are right. I was wrong about the system folder.
What error did you encounter after the file swap? OpenGL not working at all? Or the same problem with 6105 driver?

GLQuake was loading overly slow. GLQuake says that the GL version is 1.1.1274 with the .6263 driver installed. When I installed the .6105 driver and coppied over atio9xaa.dll from the .6263 package, GLQuake says that the GL version is 1.1.0.

SOLVED!

Are file name extensions with an underscore _ compressed or in some other way altered? Usually the filename extensions with an underscore are for installation files which have their underscore removed by the installer during installation. That was my previous assumption, but it seems that assumption is false. The filename with the underscore is on the order of 800 KB while the same file after being installed by the installer is around 1.7 MB. Previously, I had simply renamed the file extension from *.dl_ to *.dll.

What I did next was to replace the atio9xaa.dl_ file in the .6105 installer package with the atio9xaa.dl_ file from the .6263 installer package. I then proceeded to install the drivers from the .6105 as one normally would using setup.exe.

I can now use Direct3D and OpenGL with this modified .6105 driver vesion. Thanks a lot for your help.

feipoa wrote:

SOLVED! […]
Show full quote

SOLVED!

Are file name extensions with an underscore _ compressed or in some other way altered? Usually the filename extensions with an underscore are for installation files which have their underscore removed by the installer during installation. That was my previous assumption, but it seems that assumption is false. The filename with the underscore is on the order of 800 KB while the same file after being installed by the installer is around 1.7 MB. Previously, I had simply renamed the file extension from *.dl_ to *.dll.

What I did next was to replace the atio9xaa.dl_ file in the .6105 installer package with the atio9xaa.dl_ file from the .6263 installer package. I then proceeded to install the drivers from the .6105 as one normally would using setup.exe.

I can now use Direct3D and OpenGL with this modified .6105 driver vesion. Thanks a lot for your help.

Yes, probably compressed with the Microsoft MS-DOS COMPACT/EXPAND utilities or similar compression would be my guess, since that's what they do to the filenames. http://support.microsoft.com/kb/80751
Who made the installer, InstallShield?

feipoa wrote:

SOLVED! […]
Show full quote

SOLVED!

Are file name extensions with an underscore _ compressed or in some other way altered? Usually the filename extensions with an underscore are for installation files which have their underscore removed by the installer during installation. That was my previous assumption, but it seems that assumption is false. The filename with the underscore is on the order of 800 KB while the same file after being installed by the installer is around 1.7 MB. Previously, I had simply renamed the file extension from *.dl_ to *.dll.

What I did next was to replace the atio9xaa.dl_ file in the .6105 installer package with the atio9xaa.dl_ file from the .6263 installer package. I then proceeded to install the drivers from the .6105 as one normally would using setup.exe.

I can now use Direct3D and OpenGL with this modified .6105 driver vesion. Thanks a lot for your help.

Happy to know it worked out for you!
The files with underscored extensions are created by Microsoft's compressor:

wikipedia wrote:

Compression format(s) used by some DOS and Windows install programs. MS-DOS includes expand.exe to uncompress its install files. The compressed files are created with a matching compress.exe command. The compression algorithm is LZSS.

The decompressor, expand.exe, should be included by a lot of DOS/Windows versions. 7-zip can also decompress those files.

Yes, it was InstallShield. Good to know about those underscore file extensions. This is the first time I've run into the situation, but have always wondered why certain installation media had those underscores.

What was curious was that the Cyrix 5x86 was able to use the Direct3D functionality of the 4.11.6263 driver, while the AMD 5x86 was not. If anyone else is looking to run an ATI Rage128 VR with the AMD Am5x86 and tinker around with OpenGL and Direct3D games, the above noted solution is for you. I had to test around a dozen driver versions.

I am having a similar problem with the GeForce2 MX400. While I can get OpenGL working with the Am5x86 using Detonator 12.41, Direct3D will not function with this CPU. A Pentium Overdrive was required for D3D. The Windows display driver would not even function with a Cyrix 5x86. I've tried NVIDIA drivers 6.5 and onward, but could not find functioning D3D drivers. I did attempt some version 2, 3, and 5's from NVIDIA, but they did not support my MX400. For your curiousity, the Am5x86-160 could play GLQuake with sound enabled at 1280x1024 with 26 fps in timedemo 1. The POD-100 scored 36 fps on the same system. Due to the lack of functioning D3D drivers for the Am5x86 on the GF2 card, I have decided to use the ATI Rage 128 VR in this system, which is a lot slower in GLQuake, but allows for D3D games like Outlaws, MDK, Battlezone, etc. I've also considered just running the POD-100 in this system with the GF2, but then it wouldn't be a 486 any longer.

lazibayer wrote:

noshutdown wrote:

guess you can try installing 6105 driver, and then just copy the opengl32.dll from 6263 as its the only file that has to do with opengl. i am not sure if it would work with other versions of driver though.

opengl32.dll is a windows system file and not included in the ati driver.

it depends on driver behavior and windows version. some cards' opengl icd has their own filename, while others replace microsoft's opengl32.dll.

The best resource is a long closed geocities site....
https://web.archive.org/web/20090729173235/ht … om/ziyadhosein/
All are later versions though ... if the files are small enough, Archive may get them

Matth79 wrote:

The best resource is a long closed geocities site....
https://web.archive.org/web/20090729173235/ht … om/ziyadhosein/
All are later versions though ... if the files are small enough, Archive may get them

Those are quite a bit newer driver versions. I was trying to stick with DirectX6 drivers. Correct me if I'm wrong, but I think,

4.11.x needs DX6 or later installed
4.12.x needs DX7 or later installed
4.13.x needs DX8 or later installed

That website lists the Direct3D file as ati3draa.dll and the OpenGL file as ati09xaa.dll. Do you think I can drop these files into windows/system for any display driver version provided it uses the same DirectX revision?

I was noticing that Outlaws gets a little garbled inside the horse stable, so I am still going to try various other D3D/OGL combinations.

The glitches that occur in the barn with Outlaws also occurs with the Cyrix 5x86 (.6105), so the issue is likely driver-related. .6263 fixes all such issues with the barn glitches, but only works on the Cyrix 5x86. So far, only driver version 4.11.6105 has been able to function with D3D and the Am5x86, albiet with some glitches in certain game scenes. The next newer driver version I have is 4.11.6216, however D3D and the Am5x86 do not get along at all. I suspect I need a driver revision between .6105 and .6216. The display driver version number can be determined by viewing the properties of file ATI2DRAA.drv. Does anyone have a Win9x driver version between 4.11.6105 and 4.11.6216? This timeframe spanned from April 1999 to Sept 1999, so it is very likely there are some additional driver releases between these two revisions.

These are the driver revisions I have tested thus far:

4.11.6060
4.11.6068
4.11.6071
4.11.6076
4.11.6105
4.11.6216
4.11.6220
4.11.6263
4.11.6713 - erroneous?
4.12.6288
4.12.6292
4.13.7078
4.13.7192
w86060en

The glitches that occur with the .6105 driver release is such that the whole sceen is shaking vigurously back and forth when I enter the barn.

EDIT: Driver version 4.11.6114 has been located and installed, however Direct3D is non-functional. It would appear that 4.11.6105 is the only pseudo-functional D3D driver for the ATI Rage128 VR when using an Am5x86 CPU.