Ah0y folks!
For those of you who have been wondering "where the heck is that israeli spammer kid :s", i'm here, just the drive in my desktop pc died two weeks ago and i can't really do much of anything from my linux box [the specs are really poor].
So anyway you must be wondering what's up with the V5 mod.
Well, i'm starting to see why the other modders have failed in doing this one.
I already have the card, a V5 5500 AGP 3700, modded to a total of 128mb, but i'm hitting a deadlock when it comes to SLI [the v5's most obvious feature].
See, the bios i now have, recognizes this card as a 128meg, [64mb in dxdiag, as opposed to 32mb on a normal v5] and everything *seems* to work properly.
emphesis on *seems*
When I do any kind of 3d in it, for some bloody reason it 'forgets' about the additional ram.
it jumps back to 64mb [32x2] as if the extra ram just isn't there.
BUT, if the second VSA chip is disabled, i get the full 64mb for the first.
This is an oddity that goes beyond my understanding.
Once i get my desktop box back up, i'll continue to do my bios hacks to try and fix this show-stopper. but i think that it's the driver's fault here. not sure.
@paul
yeh it is possible, but you always get the best performance by using identical chips.
cause for example, you can use four samsungs and four hynix, but the samsungs will be 2mhz behind, or won't be able to coop with the timings that the hynix chips can. etc'
just the same as it is with your pc's ram. mixing different sticks from different vendors isn't always a pleasant expirience.
@
alt-f13
tnx
Home
