dm- wrote on 2025-02-18, 05:24:

for older cards you have to move strap resistors

Incorrect, see my second edit a couple of posts above.

I think you're on to something.... no matter what I change it to, it always goes to Device ID 0329. I don't suppose you would know which are the hardware strap IDs? I can reference my FX5200, but I wouldn't know where to look

ok
i was playing yesterday with fx5200 bios using NiBitor,
changed id to 5200 Ultra, have 5200 Ultra installed on board
but it is still detecting as a regular 5200

what i doing wrong?

dm- wrote on 2025-02-18, 06:28:

ok i was playing yesterday with fx5200 bios using NiBitor, changed id to 5200 Ultra, have 5200 Ultra installed on board but it i […]
Show full quote

ok
i was playing yesterday with fx5200 bios using NiBitor,
changed id to 5200 Ultra, have 5200 Ultra installed on board
but it is still detecting as a regular 5200

what i doing wrong?

On these older cards you will have to physically change the strap id resistors on the back side of the GPU. You'll have to reference a actual 5200 ultra to see how the resistors should be set up.

chrismeyer6 wrote on 2025-02-18, 13:02:

On these older cards you will have to physically change the strap id resistors on the back side of the GPU. You'll have to reference a actual 5200 ultra to see how the resistors should be set up.

Well, if anyone has that info, I'd appreciate it (Quadro FX500 to FX5200). RivaTuner also works in the meantime.

Here's a pic of the back of the FX500:

Does anyone know how to mod the Quadro4 NVS200 to a GeForce 4 MX440?

Rivatuner does it partially but has "Use ROM straps for PCI DeviceID programming" greyed out... So it only does a very soft mod which does not fool the driver and performance is much lower than it should be.

The only thing I could find was from this article from 20 years ago:
https://web.archive.org/web/20040626114312/ht … DIA/Quadro4Mod/

Did not find any Quadro FX1100 to FX5700 /5700U straps.

Please share

Hello

trying to change straps for fx5200 using nvflash and it did not work.

second value is out of range. if i remove one digit from second value nvflash accept and doing reflash but it's going wrong and card does not work anymore.

I hope I'll mod my Quadro FX 1000, too, this weekend, but after saving the BIOS and trying to actually edit it, my brain just shuts down like I'm a sedated monkey or something. Had two rough nights since my boy is getting his first tooth.

Anyway, the Arctic NVSilencer 2 seems great for this mod, since it not just fits but looks so similar to the infamous "dustbuster" without incorporating its fatal design flaw.

Danger Manfred wrote on 2025-07-19, 10:22:

I hope I'll mod my Quadro FX 1000, too, this weekend, but after saving the BIOS and trying to actually edit it, my brain just shuts down like I'm a sedated monkey or something. Had two rough nights since my boy is getting his first tooth.

Anyway, the Arctic NVSilencer 2 seems great for this mod, since it not just fits but looks so similar to the infamous "dustbuster" without incorporating its fatal design flaw.

So I at least attempted it, step by step, and got so far that I raised the Voltage in 3D mode, which enabled me to clock as far as 490/850. The memory on my Quadro FX 1000 is K4N26323AE-GC1K, so should be capable of 1100 MHz, but CoolBits fails as soon as 860 with the default timings of the FX 1000.

How did you guys find out the right timings, though? I only see a non-human-readable long string, not actual timing values, so I'd only mess it up if I changed anything about it.

Also, the missing caps (130 and 131) - does anyone know what their function is? As in: is there any hope that if I add them, the card might do more than the current 490 MHz core clock?

Danger Manfred wrote on 2025-07-20, 06:35:

How did you guys find out the right timings, though? I only see a non-human-readable long string, not actual timing values, so I'd only mess it up if I changed anything about it.

You use the 5800U Timings. Just get a BIOS from that card and copy them over. No manual editing with random numbers please 😀
I'm sure there are screenshots of the correct 500MHz timings in this thread somewhere. I might've posted some myself.

I'm revisiting this thread because I just bought a second FX1000 for very cheap. I hope the seller actually sends me the card and it works as advertised. It also has GC1K installed as per the pictures. Excited to mod one more. I hope I remember how to do this stuff (and that the card runs on 5800U spec, and not just 5800, which still doesn't seem like a given, but I'll do my best).

the reason for use original quadro bios is a different installed pcb components.

original fx 5800 does have 1 vga and 1 dvi output with no external tdms transceiver.

quadro fx 1000 does have 2 dvi output with external tdms SIL transceivers.

flashing fx5800 bios to quadro will force to use only VGA output, DVI will be lost on both outputs.

ps

found straps for fx 5200, just use chatgpt for this -)

@above me: I wasn't talking about using a 5800U BIOS, I was talking about using the timings from a 5800U BIOS.

My second card works very well. Haven't done any mods yet though. The GC1K Memory only clocks to about 425MHz without artifacts, which is a lot lower than the 460 on my other card.

The GPU seems to mean business though. Here's 500MHz in 3D Mark 03 without any mods and the original voltage of 1,3V. That IS the limit though, I get artifacts at 510. Still, I don't think I got that high with the first card, but I was very occupied with memory clocks on that thing. 😁

Trying to convert an FX5500 to an FX5200 (it's really a 5200, but Chinese manufacturers are so imaginative), I tried:

nvflash --straps 0x7E10C03F 0x80C02080 0x00000000 0x00000010

But it tells me "Strap values out of range". What could have happened?

Feanor_twh wrote on 2026-03-16, 14:52:

Trying to convert an FX5500 to an FX5200 (it's really a 5200, but Chinese manufacturers are so imaginative), I tried:

nvflash --straps 0x7E10C03F 0x80C02080 0x00000000 0x00000010

But it tells me "Strap values out of range". What could have happened?

Why do you want to change the id, what's the advantage?

afaik, fx 5500 uses the same chip as fx 5200. What are the core/mem clocks of your card?

It's not really necessary, but I think be nice if the card BIOS didn't trick the system for think it is a 5500, only for then trick the drivers to think again it's a 5200, since the 45.23 drivers do not natively recognize the 5500.

You know you can Hardware ID swap 5200 from .inf file, into 5500 and driver should work just fine... right ?

Feanor_twh wrote on 2026-03-16, 22:35:

It's not really necessary, but I think be nice if the card BIOS didn't trick the system for think it is a 5500, only for then trick the drivers to think again it's a 5200, since the 45.23 drivers do not natively recognize the 5500.

The attachment FX5500.gif is no longer available

If you want help/suggestions, post the straps already in your card. I.e., the output of

nvflash --display 112

I didn't know that, it's a good solution.

But the other one was more elegant, it's a shame being so near to the end haha

slivercr wrote on Yesterday, 00:13:

Feanor_twh wrote on 2026-03-16, 22:35:

It's not really necessary, but I think be nice if the card BIOS didn't trick the system for think it is a 5500, only for then trick the drivers to think again it's a 5200, since the 45.23 drivers do not natively recognize the 5500.

The attachment FX5500.gif is no longer available

If you want help/suggestions, post the straps already in your card. I.e., the output of

nvflash --display 112

This is

Feanor_twh wrote on Yesterday, 10:44:

slivercr wrote on Yesterday, 00:13:

Feanor_twh wrote on 2026-03-16, 22:35:

It's not really necessary, but I think be nice if the card BIOS didn't trick the system for think it is a 5500, only for then trick the drivers to think again it's a 5200, since the 45.23 drivers do not natively recognize the 5500.

The attachment FX5500.gif is no longer available

If you want help/suggestions, post the straps already in your card. I.e., the output of

nvflash --display 112

This is

The attachment nvflash.jpg is no longer available

Looking at the straps from your picture (would've been ideal that you posted text, make it easy for people to help you)

1S0-AND: 7E 20 C0 3F
2S0-OR:  81 50 20 80
3S1-AND: 00 00 00 00
4S1-OR:  80 00 00 10

1DeviceID bits        :  xxxx xxxx   xx32 xxxx   xx10 xxxx   xxxx xxxx
2Old Strap0-AND (hex) :  7E          20          C0          3F
3Old Strap0-AND (bin) :  0111 1110   0010 0000   1100 0000   0011 1111
4Old Strap0-OR (hex)  :  81          50          20          80
5Old Strap0-OR  (bin) :  1000 0001   0101 0000   0010 0000   1000 0000

Your previous attempt shows you modified both S0 straps
nvflash --straps 0x7E10C03F 0x80C02080 0x00000000 0x00000010

1DeviceID bits        :  xxxx xxxx   xx32 xxxx   xx10 xxxx   xxxx xxxx
2Old Strap0-AND (hex) :  7E          20          C0          3F
3Old Strap0-AND  (bin) : 0111 1110   0010 0000   1100 0000   0011 1111
4New Strap0-AND  (bin) : 0111 1110   0001 0000   1100 0000   0011 1111
5New Strap0-AND (hex) :  7E          10          C0          3F
6Old Strap0-OR (hex)  :  81          50          20          80
7Old Strap0-OR  (bin) :  1000 0001   0101 0000   0010 0000   1000 0000
8New Strap0-OR  (bin) :  1000 0000   1100 0000   0010 0000   1000 0000
9New Strap0-OR (hex)  :  80          C0          20          80

You seem to have touched bits that were not relevant to change DeviceID.

1. Compare DeviceID

10326 = 032 0110 (5500)
20322 = 032 0010 (5200)
3DevID bit: 3210

You need to turn 0326 into 0322, we only need to change the last number: change it from 0110 to 0010

2. Read straps
Copying the straps here again

1DeviceID bits        :  xxxx xxxx   xx32 xxxx   xx10 xxxx   xxxx xxxx
2Old Strap0-AND (hex) :  7E          20          C0          3F
3Old Strap0-AND (bin) :  0111 1110   0010 0000   1100 0000   0011 1111
4Old Strap0-OR (hex)  :  81          50          20          80
5Old Strap0-OR  (bin) :  1000 0001   0101 0000   0010 0000   1000 0000

Since your S0-AND / S0-OR straps are different from the usual "passthru" straps we dont know what the actual HW strap is, except for DeviceID[21]: since it seems to result in a 0, its assumed its also 0 in HW Strap.

1HW Strap   : 0???   (DeviceID set by resistors)
2Strap0-AND : 1000   (AND)
3Results in : 0000   (result of bitwise AND)
4Strap0-OR  : 0110   (OR)
5Results in : 0110   (result of bitwise OR, and effective DeviceID)

3. Calculate the new straps
It seems we can use S0-OR exclusively to change 0110 into 0010 as follows

1HW Strap   : 0???   (DeviceID set by resistors)
2Strap0-AND : 1000   (AND)
3Results in : 0000   (result of bitwise AND)
4Strap0-OR  : 0010   (OR)
5Results in : 0010   (result of bitwise OR, and effective DeviceID)

1DeviceID bits        :  xxxx xxxx   xx32 xxxx   xx10 xxxx   xxxx xxxx
2Old Strap0-AND (hex) :  7E          20          C0          3F
3New Strap0-AND (hex) :  7E          20          C0          3F
4Old Strap0-OR (hex)  :  81          50          20          80
5Old Strap0-OR  (bin) :  1000 0001   0101 0000   0010 0000   1000 0000
6New Strap0-OR  (bin) :  1000 0001   0100 0000   0010 0000   1000 0000
7New Strap0-OR (hex)  :  81          40          20          80

Try the following
nvflash --straps 0x7E20C03F 0x81402080 0x00000000 0x00000010

If those don't work, I'm out of ideas.