Maverick
I did not say it would not be of use to check .. what I said is if his Vcard BIOS is reporting the incorrect memory no Windows tool will show it correctly
how are you going to verify his Vcard or system BIOS?
Have you looked at his system?DX could say 512 and others say 1GB.. or the opposite,.. do you know why that could be?
I do
The chipset register of the system BIOS may not be working correctly with this card and that too can cause 1, 2 or even 3 different readouts to conflict.
The initial suggestion of using bufferpools and the tool I posted (drop to the desktop to check while FSX is running) would have resolved that without pulling the card. If he read above 512MB there is no question that the card has >512 because that tool reads the data sent from system memory to Vmem and bypasses the card and system BIOS which was one of the reasons it was not working in Vista when it was initially released and why it has a bug whereby >2GB of system memory caused incorrect values to display.
I verified the tool posted was corrected and updated for Vista use, something I was not aware of at the time of my initial post.
Regardless I said your suggestion of checking the chips is the most secure method of establishing the memory amount however I also said it needed a bit of refining so he did not assume something that was not true from the suggestion you made of counting chips. They need to be verified by ID number, not # of chips on the PCB
Although you may have some knowledge so far what I have seen is your suggestions are amateur at best Maverick and
you have a lot to learn. 1/2 arse suggestions with a 'know it all' ego are dangerous.
http://www.simviation.com/cgi-bin/yabb2 ... 801474/3#3no question?