StarCraft II To Be Released On July 27 220
Comment Don't overlook the hardware basics... (Score 1) 274
Sometimes a quick visual inspection of the interior of the computer can lead to the cause of the problem. Double-check the cabling, cards, memory, etc. to make sure that everything is secured in place. Even if the cards appear to be fine, I've seen it where they sometimes need to be removed and reseated. Don't forget about cooling as well. Make sure that the system has adequate cooling, that the existing fans/heatsinks are not clogged with dust and have good mobility with the flick of a finger. Double-check the fans are operational with case open and system is powered, and most motherboards have basic temperature monitoring for the CPUs and speed monitoring for the fans. On the motherboard, make sure to check the capacitors. Over the years (as recently as a couple weeks ago), I've had to replace motherboards because the capacitors had gone bad:
see -- http://en.wikipedia.org/wiki/Capacitor_plague
Some people have already mentioned it, but it needs to be stressed, a *good* power supply is mandatory and if necessary a UPS. The power supply can be perfectly operational and even pass with a power supply tester (also a good investment), but if the power being supplied to it is not consistent (brown-outs) or simply not adequate to drive all the components (e.g. video cards, # of drives, etc.) that can cause problems. In one case by simply swapping the cheap power supply out for a good quality one that I had as a spare from an older system resolved the problem.
Inproper BIOS settings can also cause problems. Memory/CPU voltages or speed may be incorrect? Conflicting on-board video/audio still enabled when add-in video cards and audio cards have been added?
I still haven't even gotten to the software debugging side of things...
World's First Formally-Proven OS Kernel 517
Sensual Stretching *NSFW* 3
Submission + - NTP: A Taste of Its Own Medicine
Submission + - Has Verizon forfeited common carrier status?
In October, a U.S. vigilante group asked Verizon to cut off net access to Epifora, a Canadian ISP that hosts a number of (entirely legal) web sites that offer support to minor-attracted adults. Shortly thereafter, Verizon gave 30 days notice to Epifora, ending a 5 year relationship.
The telecoms have traditionally refrained from censoring legal content, arguing that as a "common carrier", it is outside of their scope to make such decisions. Furthermore, they have refrained because if they did so in some cases, it might make them legally liable for other cases where they did not exercise censorship.
The questions are: has Verizon forfeited their claims to common carrier status by selectively censoring legal speech which they do not like? can the net effectively route around censorship if the trunk carriers are allowed to pick and choose whom they allow to connect? Are there implications for net neutrality?
There have been few published articles about this case, yet it could be a harbinger of things to come. Perhaps Verizon is counting on the fact that few people will object to MAA forums being cut off — the thin edge of the wedge.
Here are two articles:
http://www.guidemag.com/magcontent/invokemagconte
http://www.cippic.ca/ (may be difficult to find the blurb on the page — they posted it 25 October)
Bookmark Tamarind Village Hotel is peaceful accommodation in Chiang Mai (blogspot.com)
Comment Might explain a few things... (Score 2, Insightful) 39
It's sad that this Y2K bug wasn't caught. And make no doubt, this *is* a Y2K bug. In one of the companies I worked for, the Y2K date testing started with Sept. 9, 1999 (9999 - some programs used four nines as a exit/quit/terminate), with dates right through to Feb. 29th, 2004.