Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
So much pressure! If I had that pipe and I was just browsing webpages, I'd feel like I'm failing the Google engineers. I'd feel like I have to stream massive HD video all day. I don't know if I can consume that much content...
The problems you have enumerated are:
1. Insufficient infrastructure to meet demand
2. Lack of sufficient competitive alternatives
Neither problem is solved in any real, long-term sense by ISP throttling or traffic shaping.
The problem isn't kids getting home at 4:00 and playing...
Wave "hi" to the fatal flaw in the argument.
It's precisely the lack of other places to take your business that makes the simple market solution untenable.
How many choices do you have where you're at right now? 1? 2? It's not like a hammer. If suddenly I refuse to buy Craftsman hammers...
Read the comments to the article. Every single one tearing her a new one. Absolutely no support from anyone. And thankfully, virtually every comment is rational and intelligently written.
Unfortunately GPU-Z doesn't display the PCI-E bus speed. :( I appreciate the help though.
On my other system (650i based board), nTune can show PCI-E bus speed, but I haven't found anything that does the same for my Intel chipset board.
I'm using an Intel P965-based board (Gigabyte GA-965P-S3), and I'm trying to find a way to check my PCI-E bus speed from Windows.
In my BIOS, I have it set to Auto. Interestingly, when I set it to 100Mhz (the standard PCI-E speed), a couple of unusual things happen (my FSB boots at 332MHz...
The problem with this argument is that it's entirely based on the faulty assumption that the source code in the hands of a "hacker" would be a roadmap to every flaw and hole in the program. Not to insult anyone's intelligence, but such arguments are usually made by people to whom programming is...