Recent content by beamer145

Damn, I had a glimpse of hope that would work (I was going to try that as well, maybe I still will ) :( >beamer sorry, if I dumped bios with GPU-Z then it could be same as yours? You dumped your bioses with GPU-Z, and I dumped mine with RBE -> that is why they are different. But I think yours...

Lol, without giving me a keyword, that makes it kind of finding a needle in a haystack (you have 579 posts you know) + I don't even know to recognize the needle if I encounter it. But I will give it a first try: you mention the need for "balancing" checksums a few times... But that should...

I just ran into the issue that RBE seems to be corruption biosses even if you don't edit them. Eg if you load an image of an asus 6950 2GB DCII from disk and immediately save it again in RBE, it will change the bytes at offsets 0x0007, 0xDE39, 0xDE7A, 0xDE7E. I am guessing it also does this for...

@AZONIC[rus] Whoops, just looked at NEX'es files and he has the same combination of orig and RBE modded as you. So obviously I am wrong, big sorry :( I just did a few more tests, and the whole thing with differences at positions 0x0007, 0xDE39, 0xDE7A, 0xDE7E -> turns out that it actually is...

The difference is in bytes 0x0007, 0xDE39, 0xDE7A, 0xDE7E , see a few post back where I made the list. The logic I use to get to my conclusion is: [Step1]: In the files you uploaded, there is no way that you can get from your original(2).bin to your modRBE.bin using the RBE or w1zzard php...

Sorry that i ask it again, but you mean that if you check with GPUZ after a powercycle you see that you have 1536 shaders (and not just that the script says 'modding successfull' (or something like that) )? If so, can you open your original bios in eg hxd and copy paste eg the first 16 bytes ...

I have also seen this. I think RBE really misinterpretates the bioses from the newer cards (with the 4 at position 7 (sjeeses, how many times have I already typed this ???) ). If you looked at the selection between 6950 or 6970 shaders, is would have been at 6950 though (when using the...

Your original bios is not equal to either of my original bioses. So, based on the fact that you are in the same serial range as I am + the fact that you somehow obtained a modded version that is equal to what I get from RBE with my original bios, I am pretty sure your original(2).bin is not...

I see your both original bioses are identical as you suggested earlier. I suspect either you (when reading it out) or some guy at the production facility (when putting it in ) had to much vodka :), because that is definitely not a correct state for the card to be when it is sold as new (idea...

That is very interesting ... I would have expected a difference in the last 6 numbers but your's starts with B8, mine B9 If that is some kind of HW revision indication, it could be used to determine unlockability.... Now I am wondering about AZONIC[rus]'s SN of course :)

Well, I just realized that if you would ever need the modded version of the other output configuration (single DVI, all 4 DP ports), the only think you have to do is grab the bios from switch position 0, mod it, flip switch, upload that modded bios to position 1..... As long as you keep both...

Not sure why you mention that (you seem to imply that you expected a difference in that string when modding ?). For clarity, modding will wil not change this string, it will only change 1 checksum byte and 1 other byte regarding the shaders. The fact that you have this string (with -100 and...

BTW another thing that is maybe interesting to know : to identify for which switch position a bios was made you can look at the string at offset A8. For switch away from the connector (commenly refered to as position 0), you have...

Do you mean you had 2 different original bioses from 2 different switch positions that each matched with techpower database bioses ? Because that is OK. I was under the impression that you were saying that both bioses (from different switch positions) were equal , matching the single link you...

@evellik The 0x0007 I mention are just offsets in the file (offset 0x0007 or 7 or the 7th byte in your file) Eg HXD shows the offset as a combination of the column on the left side and top row indices. But is seems my '4 at offset 7 means not shader unlockable' theory needs refinement (or at...