Hoping wrote on 2025-04-26, 11:13:

The method shown by @360alaska2 and cutting the traces on the PCI connector, seems to me the simplest method for these cards to […]
Show full quote

The method shown by @360alaska2 and cutting the traces on the PCI connector, seems to me the simplest method for these cards to work in any PCI slot.
The method I posted, I think it is the most complete but a little more complicated, but simple anyway.
Not cutting the traces on the PCI connector is clearly looking for problems, and after using any of the published methods, the card should work in any PCI slot, at least as far as power is concerned.
Using only an 1117 regulator is totally feasible, although as far as power is concerned, it is a bit tight as most of them do not exceed 800mA.

Thanks

Finally got this late to the party Chinese Rage XL PCI tiny card in my hand. Its not easy to add 3DCIF support to this card.
Managed to add latest 4.11.2611 d3d/ogl/cif to Rage XL AGP at least, before latest driver for Rage XL AGP was 4.11.2582 .

marxveix wrote on 2025-05-01, 08:37:

Finally got this late to the party Chinese Rage XL PCI tiny card in my hand. Its not easy to add 3DCIF support to this card.
Managed to add latest 4.11.2611 d3d/ogl/cif to Rage XL AGP at least, before latest driver for Rage XL AGP was 4.11.2582 .

Just for trying to improve the drivers for these graphics cards, I thank you in advance.
You already have quite a bit of experience modifying these drivers, from what I've seen in other threads; so I'm looking forward to the results, to see if improvements can be made. There may already be many of these Rage XL PCI in use in old computers.

Hoping wrote on 2025-05-01, 14:42:

marxveix wrote on 2025-05-01, 08:37:

Finally got this late to the party Chinese Rage XL PCI tiny card in my hand. Its not easy to add 3DCIF support to this card.
Managed to add latest 4.11.2611 d3d/ogl/cif to Rage XL AGP at least, before latest driver for Rage XL AGP was 4.11.2582 .

Just for trying to improve the drivers for these graphics cards, I thank you in advance.
You already have quite a bit of experience modifying these drivers, from what I've seen in other threads; so I'm looking forward to the results, to see if improvements can be made. There may already be many of these Rage XL PCI in use in old computers.

When in the mood and have free time i try something. Small performance improvements probably possible also for Rage XL PCI (4752).

Found one quad display 4 x XL PCI card option (Rage XL Maxx - just same speed and no crossfire) 😀
https://store.cwc-group.com/4display.html

BinaryDemon wrote on 2025-04-17, 11:32:

elmatero wrote on 2025-04-17, 10:37:

My modified card died after three minutes, when i put it into Atx 3.3 volt pci capable motherboard. Afrer while screen goes black, and card never back to life.

Just curious was that test on purpose or accidental?

That was a test.

I have modded my PCI Rage XL with an AMS1117-3 voltage regulator.

I tested the card in my early socket 7 pentium board which has 5V PCI slots and it works just fine.

In my GA-5486AL, the board turns on but there are no beeps and nothing on the display.
The board does work just fine with other cards like my S3 Virge.

What could be the reason why the modded ATI Rage XL does not work in my 486 board?

ATI Display Information file : ATII9xAB.INF
INF file for mach64 ATI2DRAB display driver.
Manufacturer: ATI Technologies Inc.
M6.00.11-T02_ENU TESTING BUILD FOR ATI RAGE XL PCI 4752@3DCIF!
NOT OPTIMIZED! ATI RAGE XL PCI CIF DEMOS WORK, CIF GAMES NOT SO

Most of the Rage XL PCI 4752 drivers wont start @3DCIF apps/games at all, this one does star demos/games.
Here is one 3dcif ragexlpci-testing driver, someone with working XL PCI 4752 could try it @ CIF demos now.

3DCIF Demos are visible here
https://www.youtube.com/watch?v=Mnahhue0VWs
https://www.youtube.com/watch?v=C86fIHU6qro

Here are 3DCIF games, list not 100% complete, more games can be tricked to use 3DCIF API. NB! This driver still has errors within 3DCIF games!!!
https://www.youtube.com/watch?v=hZJs2h6LtY4

Added this driver with changed+edited file to attacments. Should work with other ATI2DRAB driver.
This is only to show that 3DCIF demos/games can be started with RageXLPCI 4752 PCI or integrated.

@HP Terminal T5300 and integrated Rage XL PCI 4752 just tested with clean Win95 install + DX61, i am still @56MB RAM (8MB VGA shared) + 64MB HDD. This is just starting point of the ati2drab or ati2drae cif starting driver and minimal goal is to improve performance and not loose ability to start 3DCIF stuff. With errors or without errors @CIF. Here i probably go up to DX6-DX7 based build or at least i think so now. Let see where i end up with this RageXLPCI 4752. Knight demo needs 5029 macxdd16.dll/macxdd32.dll to be ported, 5031.2 are too new for it from ati2drab earliest drivers. macxdd1632.zip has macxdd32.dll 5029 hexedited and works with ati2drab testing driver (ragexlpci-testing.zip).

marxveix wrote on 2025-08-12, 03:44:

ATI Display Information file : ATII9xAB.INF INF file for mach64 ATI2DRAB display driver. Manufacturer: ATI Techn […]
Show full quote

ATI Display Information file : ATII9xAB.INF
INF file for mach64 ATI2DRAB display driver.
Manufacturer: ATI Technologies Inc.
M6.00.11-T02_ENU TESTING BUILD FOR ATI RAGE XL PCI 4752@3DCIF!
NOT OPTIMIZED! ATI RAGE XL PCI CIF DEMOS WORK, CIF GAMES NOT SO

Most of the Rage XL PCI 4752 drivers wont start @3DCIF apps/games at all, this one does star demos/games.
Here is one 3dcif ragexlpci-testing driver, someone with working XL PCI 4752 could try it @ CIF demos now.

3DCIF Demos are visible here
https://www.youtube.com/watch?v=Mnahhue0VWs
https://www.youtube.com/watch?v=C86fIHU6qro

Here are 3DCIF games, list not 100% complete, more games can be tricked to use 3DCIF API. NB! This driver still has errors within 3DCIF games!!!
https://www.youtube.com/watch?v=hZJs2h6LtY4

Added this driver with changed+edited file to attacments. Should work with other ATI2DRAB driver.
This is only to show that 3DCIF demos/games can be started with RageXLPCI 4752 PCI or integrated.

@HP Terminal T5300 and integrated Rage XL PCI 4752 just tested with clean Win95 install + DX61, i am still @56MB RAM (8MB VGA shared) + 64MB HDD. This is just starting point of the ati2drab or ati2drae cif starting driver and minimal goal is to improve performance and not loose ability to start 3DCIF stuff. With errors or without errors @CIF. Here i probably go up to DX6-DX7 based build or at least i think so now. Let see where i end up with this RageXLPCI 4752. Knight demo needs 5029 macxdd16.dll/macxdd32.dll to be ported, 5031.2 are too new for it from ati2drab earliest drivers. macxdd1632.zip has macxdd32.dll 5029 hexedited and works with ati2drab testing driver (ragexlpci-testing.zip).

Thank you very much for the drivers. I haven't been able to try them yet due to health issues, but I'm looking forward to doing so.

Hoping wrote on 2025-09-13, 19:55:

marxveix wrote on 2025-08-12, 03:44:

ATI Display Information file : ATII9xAB.INF INF file for mach64 ATI2DRAB display driver. Manufacturer: ATI Techn […]
Show full quote

ATI Display Information file : ATII9xAB.INF
INF file for mach64 ATI2DRAB display driver.
Manufacturer: ATI Technologies Inc.
M6.00.11-T02_ENU TESTING BUILD FOR ATI RAGE XL PCI 4752@3DCIF!
NOT OPTIMIZED! ATI RAGE XL PCI CIF DEMOS WORK, CIF GAMES NOT SO

Most of the Rage XL PCI 4752 drivers wont start @3DCIF apps/games at all, this one does star demos/games.
Here is one 3dcif ragexlpci-testing driver, someone with working XL PCI 4752 could try it @ CIF demos now.

3DCIF Demos are visible here
https://www.youtube.com/watch?v=Mnahhue0VWs
https://www.youtube.com/watch?v=C86fIHU6qro

Here are 3DCIF games, list not 100% complete, more games can be tricked to use 3DCIF API. NB! This driver still has errors within 3DCIF games!!!
https://www.youtube.com/watch?v=hZJs2h6LtY4

Added this driver with changed+edited file to attacments. Should work with other ATI2DRAB driver.
This is only to show that 3DCIF demos/games can be started with RageXLPCI 4752 PCI or integrated.

@HP Terminal T5300 and integrated Rage XL PCI 4752 just tested with clean Win95 install + DX61, i am still @56MB RAM (8MB VGA shared) + 64MB HDD. This is just starting point of the ati2drab or ati2drae cif starting driver and minimal goal is to improve performance and not loose ability to start 3DCIF stuff. With errors or without errors @CIF. Here i probably go up to DX6-DX7 based build or at least i think so now. Let see where i end up with this RageXLPCI 4752. Knight demo needs 5029 macxdd16.dll/macxdd32.dll to be ported, 5031.2 are too new for it from ati2drab earliest drivers. macxdd1632.zip has macxdd32.dll 5029 hexedited and works with ati2drab testing driver (ragexlpci-testing.zip).

Thank you very much for the drivers. I haven't been able to try them yet due to health issues, but I'm looking forward to doing so.

Get healty and well! Its not some performance driver, just tryout for 3DCIF@4752 card.

Hoping wrote on 2025-04-26, 11:13:

The method shown by @360alaska2 and cutting the traces on the PCI connector, seems to me the simplest method for these cards to […]
Show full quote

The method shown by @360alaska2 and cutting the traces on the PCI connector, seems to me the simplest method for these cards to work in any PCI slot.
The method I posted, I think it is the most complete but a little more complicated, but simple anyway.
Not cutting the traces on the PCI connector is clearly looking for problems, and after using any of the published methods, the card should work in any PCI slot, at least as far as power is concerned.
Using only an 1117 regulator is totally feasible, although as far as power is concerned, it is a bit tight as most of them do not exceed 800mA.

Can you tell me and show me in the photo exactly which traces need to be cut? I'm going to use the N7803-1PV MEAN WELL pulse voltage converter. It is much cheaper than the linear TSR1-2433.

Here are the photos of the redesigned graphics card. Can someone tell me which traces need to be cut for normal operation on all platforms?

Based on the first post in the thread, it looks like cutting the trace just after the edge of the card is a good idea. You can easily find the location of the 3.3V on pinout.ru.

kagura1050 wrote on 2026-03-10, 09:49:

Based on the first post in the thread, it looks like cutting the trace just after the edge of the card is a good idea. You can easily find the location of the 3.3V on pinout.ru.

Based on information from https://pinouts.ru/Slots/PCI.shtml there are many 3.3 volt contacts. +3.3V and +V I/O are shown in the screenshots. I would like to know EXACTLY what to cut. Can you point your finger at solving the problem?

Only 3.3 v contacs. If you zoom the images on the first post, you'll can see the cuted traces. This is only needed if you are going to use the card on a board with 3.3 v on the slots. And in that case, there's no need to mod the card wirh a 3.3 v regulator. Cuting the traces makes the card 5 v only. It is diferent if you do what I did, moding the card to adjust the core voltage to the stock 2.5 v.

Hoping wrote on Today, 08:04:

Only 3.3 v contacs. If you zoom the images on the first post, you'll can see the cuted traces. This is only needed if you are going to use the card on a board with 3.3 v on the slots. And in that case, there's no need to mod the card wirh a 3.3 v regulator. Cuting the traces makes the card 5 v only. It is diferent if you do what I did, moding the card to adjust the core voltage to the stock 2.5 v.

I apologize for my poor English. But you've confused me even more. Initially, this card did not work for me on the ASUS P2B. Modification with a DC-DC converter solved this problem. In other words, the card should now work on all older platforms with PCI - 486, 586. But if I insert it now, for example, into LGA775, it will fail. And in order for the map to work on all platforms, I need to cut tracks. Where am I wrong?

Someone that tried the modded Rage XL into a newer motherboard that has the 3.3v present on the slot, can explain that, but I'm not going to prove that. Don't worry, my English also, isn't good enough.

Hoping wrote on Today, 12:19:

Someone that tried the modded Rage XL into a newer motherboard that has the 3.3v present on the slot, can explain that, but I'm not going to prove that. Don't worry, my English also, isn't good enough.

You must have misunderstood me. I just want to find out how I can make a universal card that will work on ALL systems from 486 to modern PCI. Can you explain this to me, please? I'm not asking for any proof from anyone.

The original mod just enable to use this card on any mainboard, with or without 3.3 v on the pci bus.
It just provide 3.3 v from the 5v on the card, instead of the PCI connector.
If a mainboard already have 3.3, the result is the 2 3.3 power are "in parallel", but it doesn't cause any problem with modern regulators.
There's nothing to cut.
I use this XL as well on a Socket 7 mainboard (no 3.3v) as on a Athlon XP board (with 3.3v)

nali wrote on Today, 16:19:

The original mod just enable to use this card on any mainboard, with or without 3.3 v on the pci bus. It just provide 3.3 v fro […]
Show full quote

The original mod just enable to use this card on any mainboard, with or without 3.3 v on the pci bus.
It just provide 3.3 v from the 5v on the card, instead of the PCI connector.
If a mainboard already have 3.3, the result is the 2 3.3 power are "in parallel", but it doesn't cause any problem with modern regulators.
There's nothing to c
I use this XL as well on a Socket 7 mainboard (no 3.3v) as on a Athlon XP board (with 3.3v)

I'm not an expert, but, in what I did, if I don't cut the traces, I don't know if I could set the desired voltage for the chip. I think you know more than I do. I understand that @AndroiDDQD is doing the simple version and it's different.