nali wrote on 2026-03-13, 20:18:

" I don't know if I could set the desired voltage for the chip. " -- > I'm not sure you understand why this modification exist. […]
Show full quote

" I don't know if I could set the desired voltage for the chip. " -- > I'm not sure you understand why this modification exist.

There's no "desired" voltage we have to choose.
This card get 5 v and 3.3v from the PCI. It needs both.
On old PCI versions, there's no 3.3, so we get 3.3 locally on the board from the 5v with a regulator.
If a new mainboard already has 3.3, with a AMS1117 there's no problem. I have no idea with a switching regulator like you have. Electronic can do weirds things.

If you really want to cut traces, then you have to cute all the traces on the PCI connector of the card where 3.3 is delivered.
There's about 12, see the pinout on Wiki ( the B side is the components side), the A side is the nude back.

https://en.wikipedia.org/wiki/Peripheral_Comp … nt_Interconnect

Okay, my English isn't very good. But maybe you shouldn't answer anything without reading the target and motive in the first post. The card according to specifications needs three voltages, 2.5v for the "GPU," 3.3v for the SRAM and 5v for the VBIOS.
The 3.3v for the "GPU" is an unnecessary and quite important overvolting. But, everyone who does it any way they want.
And, I did the mod on the first page, so I know why I did this modification and I have quite clear the traces I needed to cut.
What I don't know is if keeping the traces uncut, on a motherboard that has the 3.3v on the slot, the voltage adjustment for the "GPU" I wanted will work properly.

nali wrote on 2026-03-13, 20:18:

" I don't know if I could set the desired voltage for the chip. " -- > I'm not sure you understand why this modification exist. […]
Show full quote

" I don't know if I could set the desired voltage for the chip. " -- > I'm not sure you understand why this modification exist.

There's no "desired" voltage we have to choose.
This card get 5 v and 3.3v from the PCI. It needs both.
On old PCI versions, there's no 3.3, so we get 3.3 locally on the board from the 5v with a regulator.
If a new mainboard already has 3.3, with a AMS1117 there's no problem. I have no idea with a switching regulator like you have. Electronic can do weirds things.

If you really want to cut traces, then you have to cute all the traces on the PCI connector of the card where 3.3 is delivered.
There's about 12, see the pinout on Wiki ( the B side is the components side), the A side is the nude back.

https://en.wikipedia.org/wiki/Peripheral_Comp … nt_Interconnect

@elmatero's video card burned out after modification without cutting traces in the PCI slot with 3.3 volts.
Re: Chinese Rage XL PCI mods, improved compatibility and looking for a good overclock.

AndroIDDQD wrote on 2026-03-15, 06:48:

nali wrote on 2026-03-13, 20:18:

" I don't know if I could set the desired voltage for the chip. " -- > I'm not sure you understand why this modification exist. […]
Show full quote

" I don't know if I could set the desired voltage for the chip. " -- > I'm not sure you understand why this modification exist.

There's no "desired" voltage we have to choose.
This card get 5 v and 3.3v from the PCI. It needs both.
On old PCI versions, there's no 3.3, so we get 3.3 locally on the board from the 5v with a regulator.
If a new mainboard already has 3.3, with a AMS1117 there's no problem. I have no idea with a switching regulator like you have. Electronic can do weirds things.

If you really want to cut traces, then you have to cute all the traces on the PCI connector of the card where 3.3 is delivered.
There's about 12, see the pinout on Wiki ( the B side is the components side), the A side is the nude back.

https://en.wikipedia.org/wiki/Peripheral_Comp … nt_Interconnect

@elmatero's video card burned out after modification without cutting traces in the PCI slot with 3.3 volts.
Re: Chinese Rage XL PCI mods, improved compatibility and looking for a good overclock.

I find out that my Tekram P5MVP-A4 motherboad proviede 5V on 3,3 V line, that was the real reason of burning the card - 5V on GPU Core.
thread: 3.3V PCI cards got extra hot on Super Socket 7 Mainboard

So it makes sense !
I could not find any reason why this mod could burn a card. Unless a soldering mistake, of course.
And I've been playing with electronic for 35 years, it's even been my job 😀

Did you manage to fix it ?
The fix would be just cutting the trace, but on a multilayer board it's not always possible 🙁
Or destroy the pin, also not easy on a PCI connector.

Is there 5 volt on all 3.3 PCI slots ?
A solution would be cutting all the 3.3v input on the Ati card, of course.
Maybe it's where the confusion comes from here above.

Yes on all PCI stots On this motherbord are 5v on 3,3 V line. Finaly I'm using on it 5V PCI cards (IDE and network adaper) and in AGP port ATI RAGE PRO. On AGP ther is correct voltage of 3,3 V.

hello everyone

I recently bought this graphics card. I tried all the drivers in the area and overclocking.
I’m very pleased; the card adds compatibility with Windows 98 and DOS to my 'retro' PC with a Radeon HD, which doesn’t have drivers for Win98.
I use Powerstrip 3.2 for overclocking;
my non‑extreme (everyday) settings are: 139 for 3D, 100 for DOS.

Driver 2647 worked for me:
-Unreal without visual defects in D3D
-FF7 with D3D HAL
-stock OGL little bit slow, replaced with OGL1107. for GlQuake set gl_ztrick 0 and no visual issues
-Sin works lagging with any OGL, SciTech GLDirect 3 CAD driver fixed it

Some bench results:
3Dmark99 default settings - 2382 marks 800x600
Final Reality 3D performance - 6.21
Unreal Gold around castle fly cycle - 34.4 fps 512x384
GlQuake demo1 - 59.9 fps 512x384
Quake 2 demo1 - 46.6 fps 512x384
Quake 3 demo1 - 49.0 fps 512x384

P.S.
In 2647, the OpenGL driver was renamed; for OpenGL replacement batch file should look like this:

COPY Atoglrp9.dll C:\WINDOWS\SYSTEM\ATIO9XAE.DLL

1q2w3e wrote on Today, 06:52:

P.S.
In 2647, the OpenGL driver was renamed; for OpenGL replacement batch file should look like this:

COPY Atoglrp9.dll C:\WINDOWS\SYSTEM\ATIO9XAE.DLL

Also you can rename it in the install .inf back to Atoglrp9.dll as it was before and install the driver with Atoglrp9.dl_ or Atoglrp9.dll.

1q2w3e wrote on Today, 06:38:

Some bench results: 3Dmark99 default settings - 2382 marks 800x600 Final Reality 3D performance - 6.21 Unreal Gold around castle […]
Show full quote

Some bench results:
3Dmark99 default settings - 2382 marks 800x600
Final Reality 3D performance - 6.21
Unreal Gold around castle fly cycle - 34.4 fps 512x384
GlQuake demo1 - 59.9 fps 512x384
Quake 2 demo1 - 46.6 fps 512x384
Quake 3 demo1 - 49.0 fps 512x384

Quake2 should be faster than Quake3? Could you add also default (no oc) results at default 640x480x16 resolution for Quake 1/2/3 (ztrick 0 for glquake and no other game tweaks)?

marxveix wrote on Today, 07:21:

1q2w3e wrote on Today, 06:38:

Some bench results: 3Dmark99 default settings - 2382 marks 800x600 Final Reality 3D performance - 6.21 Unreal Gold around castle […]
Show full quote

Some bench results:
3Dmark99 default settings - 2382 marks 800x600
Final Reality 3D performance - 6.21
Unreal Gold around castle fly cycle - 34.4 fps 512x384
GlQuake demo1 - 59.9 fps 512x384
Quake 2 demo1 - 46.6 fps 512x384
Quake 3 demo1 - 49.0 fps 512x384

Quake2 should be faster than Quake3? Could you add also default (no oc) results at default 640x480x16 resolution for Quake 1/2/3 (ztrick 0 for glquake and no other game tweaks)?

q2 textures to max, otherwise q3 textures on middle, no tweaks, just settings in menu
non-OC 640x480 16 bit results:
GLquake 23.9
Quake2 21.0
Quake3 20.5