doom patched cat 4.9 error

  • Thread starter Thread starter Highlandish
  • Start date Start date
H

Highlandish

I installed the cat4.9 over my omega4.7 and I lost all ability to adjust my
cards opengl and direct3d settings, I did a system restore and got it all
back again, so is this normal, is it worth it? is there a way to extract the
files I need and overwrite my originals manually so I don't loose the omega
interface? if so what files do I need?
 
no.

If you read the omega recommendations - the dude says to remove all traces
of other drivers. I guess u can use them together then.
 
always uninstall the old drivers before installing new ones
- if you want more tweakable options then use rage3d's
tweak program in conjunction with the new drivers.
 
Quoth The Raven "Sleepy said:
always uninstall the old drivers before installing new ones
- if you want more tweakable options then use rage3d's
tweak program in conjunction with the new drivers.
Click to expand...


thanks, I'll either do that or wait until omega come out with a 4.9
 
Open up the Catalyst 4.9 archive with something like Winrar or XP's CAB file
viewer. Extract the atioglxx.dl_ file, rename it to atioglxx.dll and put it
in your Doom 3 directory. This way you get the benefits of the revised 4.9
OpenGL driver in D3 without f---ing with the rest of your system.

Damn, this reminds me of the 3dfx MiniGL days...
 
Open up the Catalyst 4.9 archive with something like Winrar or XP's CAB file
viewer. Extract the atioglxx.dl_ file, rename it to atioglxx.dll and put it
in your Doom 3 directory. This way you get the benefits of the revised 4.9
OpenGL driver in D3 without f---ing with the rest of your system.

Damn, this reminds me of the 3dfx MiniGL days...
Click to expand...


Yes, I can confirm that this works. Although one note, is my
understanding that after extracting the atioglxx.dl_ file, it is still
compressed and you have to manually expand it before it is usable,
just renaming it may not work. I used the following command I found
on google:

expand atioglxx.dl_ atioglxx.dll

Then I put the dll file into my D3 directory (I used both the D3 root,
and "base", not sure which is correct but it works.) I have one small
bug after this, after playing Doom I have to go into the ATI driver
control panel to reset the gamma/color settings or other games are
much too bright. No biggie.
 
Quoth The Raven "First of One said:
Open up the Catalyst 4.9 archive with something like Winrar or XP's
CAB file viewer. Extract the atioglxx.dl_ file, rename it to
atioglxx.dll and put it in your Doom 3 directory. This way you get
the benefits of the revised 4.9 OpenGL driver in D3 without f---ing
with the rest of your system.

Damn, this reminds me of the 3dfx MiniGL days...
Click to expand...

thanks heaps!, only I don't yet have doom3, is there a place to put the file
to make all games use it like the system32/drivers folder?
 
thanks heaps!, only I don't yet have doom3, is there a place to put the file
to make all games use it like the system32/drivers folder?
Click to expand...

I tried this but Doom3 became pretty unstable and had to remove the
new .dll after a few tries. :( Not sure why it didn't work.. I
extracted and expanded.. then renamed and put in base directory and
the main Doom3. I've tried it with it just in the base directory as
well. No dice. Maybe there is another file that is needed for it to
work(?).

....Waiting for the Omega 4.8's or 4.9's I guess.

Pluvious
 
Hmm, never heard about this one. What app are you using to extract the file?
My understanding is that the drivers are packed in a self-extracting CAB
file. So when you extract it from the CAB, it's decompressed.
 
Hmm, never heard about this one. What app are you using to extract the file?
My understanding is that the drivers are packed in a self-extracting CAB
file. So when you extract it from the CAB, it's decompressed.
Click to expand...



I used WinRAR to extract it (maybe there is an option in WinRAR to
extract and expand it, I don't know). After extraction, I had a file
named atioglxx.dl_ that was about 3 megabytes in size. After
"expanding" it, it's about 6 megabytes in size. I was just following
some instructions I dug up on Google, so I'm not sure if the expand
step is still needed.
 
Back
Top