Soldato
What Shankly said was right though. It's not guaranteed to have low clocks when two monitors are connected. The default behaviour is to raise the memory clocks. See AMD MAtt's post above.
I told him to do what he said he was going to do. There was no call for him to call Shankly stupid and rude. He didn't come in here looking for help, he came in to rant and rave and then take out his frustrations on people trying to help him.
As I said, I put the rant down to frustration, I'm sure we've all been there.
Shankly said
But then MyBrains (and others) have shown that he wasn't wrong. How can Shankly saying it won't and didn't run at 300/150 be right when people are showing that it can and does in some scenarios?It's a matter of a fact your wrong on this one sorry don't take it personal
Remember there were at least a couple of people here telling him he was wrong, that it was impossible for it to behave the way it did (and now does again) and that he was just remembering it wrong. On top of the problem he had that was getting him annoyed that can't have been helping, so maybe he didn't react in the calmest manner. Suggesting things to try is one thing, telling him it can't be done isn't helping. In this case it was also wrong.
At least Shankly is big enough to admit that he was wrong.