18 days? I regularly got that out of Windows 95. My recent record uptime on Windows is 118 days on Vista before things just got weird and finally it bluescreened. Same box is currently at 61 days and counting. All time record is 249 days on NT4 - so much for Windows of yesteryear being unstable.
On the other hand, I've gotten over a year on boxes running Debian, with the only reason for shutting them down was moving or harddrive failure.
Well, all the major news outlets are based out of New York City, so anything that happens in New York tends to make the national news as it's a big deal to those running the news networks. The power outage a few years back was a good example of this - it was plastered on all the major channels, that's all they talked about the whole time the power was out, and the reporters were going on like it was the end of the world or something. Meanwhile, an ice storm can knock the power out to half of "flyover country" and it will barely get a mention in the nightly news.
Well, I don't think there were any successful hijackings until five years had passed since the attacks in 2001, so I guess people just have a short memory. It also seems that the hijackers also tend to take their demands straight to the flight crew, and in some cases like the Turkish Airlines hijacking the passengers didn't even know the plane was hijacked until it landed. Finally, I don't believe there have been any instances where the hijackers were able to take control of the aircraft away from the pilots.
You sure you need that stufF? Does everyone in NE drive high performance cars? I'm sure you still have plenty of people driving around in things like the old 90HP base Nissan Sentra who get along just fine.
Something I've noticed is that "Decades" are often defined by what happened in the last few years of that decade. The Sixties is remembered for Woodstock (68). The 70's for disco (late 70's/early 80's), Iranian hostages (79-80), etc.
How much do you want to bet that this decade will be remembered as the Social Networking decade (when was Myspace started?)
Well, that's not always true. The 1940's is known for WWII. The 1930's is best known for the Great Depression, even though WWII started in 1939. The 1910's is known for WWI. The 1860's for the American Civil War. With that said, the 2000's could be known for the terrorist attacks in 2001, but also could be remembered for the economic meltdown of 2008 if things get really bad and doesn't recover for the next few years.
When was the last time you saw a riced up Honda from the current body style? The boy racers are modding cars from the late 80's to the very early 2000's. Today's cars are extremely complex, even my '99 model seems simple in comparison.
I'd say you're rather ignorant yourself. Not everyone installed their warezed copies of Windows yesterday. I even know of at least one computer out there still running the infamous FCKGW key, which is blacklisted from even installing XP SP1. And lots of people still running V2C47 which no longer update (for fear of the dreaded WGA) and are thus stuck somewhere in SP2.
The problem was is there was no year zero. So the first century started on January 1st of year 1. So the first century, or after 100 years had passed, ended on December 31st of year 100. So it follows that 2000 years did not pass until January 1st of year 2001.
Of course, a decade is just a span of ten years, so it's just as correct to call 2000-2009 a decade just as much as 2001-2010. However, if you wanted to refer to the 201st decade, that would have to be 2001-2010 because once again, there was no year zero.
It's actually a logical choice. Imagine a barter system, now try to think what item(s) may be a preferred in such a system. Food? Can't store wealth, it spoils. Water? Any amount with value is going to be heavy and awkward. Live animals? Can't be divided (well, without significantly reducing their value). Lumber? Too bulky. Precious metals? Small, rare enough to be value, stores easily, divisible. Yeah, I can see why it might become money.
But, AMD CPUs were cheaper, and AMD CPUs ended up in budget machines that had cheaper, crappier motherboards with crap chipsets. End result, unreliable machine.
Well, to be fair for a while you couldn't get a decent chipset in an AMD machine no matter how much you spent. The whole Socket A era was plagued by shitty chipsets - VIA's were pure garbage, then there was SiS and even AMD's own chipsets were flakey. It wasn't until towards the end when the nForce2 came out that AMD users could enjoy a system as stable as a run-of-the-mill P4 running whatever Intel chipset that was popular at the time. Then the 64 bit era happened and nVidia's chipsets rapidly went downhill. At least AMD got their act together, and I can't complain about their chipsets for the Phenom II/Athlon II systems.
Why not? The next version of Office for the PC was Office 2000, and that came out around the same time as Windows ME - so if you were running Windows 98 you were probably running Office 97. At the least, I would expect MS to patch Office 97 if it had problems running in Windows 98.
Typically, you give your name and address at the purchasing stage, after a price has been agreed upon. So what price do you present to an anonymous browser, or do you force everyone to hand over their personal information before you show them a price?
The problem with that is that the TN panels (which almost every single one of the 16:9 panels are) have a terrible vertical viewing angle. When you rotate the screen then you end up with a very noticeable poor horizontal viewing angle.
"Most of the variables in CRAP are one or two letters long. Originally, this was due to the memory constraints involved when programmers first designed and built the system." This is not particularly plausible. C is a compiled language, so using long variable names has no effect on the amount of memory used at run-time. It would also have been more or less a non-issue in terms of RAM used at compile-time. C only dates back to 1972, and didn't start to get popular until ca. 1980. By that time, using long variable names would have had a pretty negligible effect on RAM used by the compiler in proportion to total available RAM. And in any case, if compiles are taking too long, you just break up your files into smaller parts.
You also need to take into account the space the.c file is going to take before it's compiled too. I just took a look at a smallish program I made, consisting of about 3800 lines of source. It's 108k, which is not a trivial amount of ram on a computer from the early-mid 1980's.
If the current owner of the car is smart, they'll refuse to do that, for exactly the same reason you would not want to do it once it is your car. I sure would refuse if I was the seller, if you don't want the car then, fine. Another buyer will come along.
I've found the most likely components to fail on a computer are mechanical parts like the fans and drives, and the electrolytic capacitors - things that wear out faster the more the computer is left on. While it's true that thermal cycling will shorten the life of components like the CPU, chipset, and graphics cards I've found that those components are so reliable it's not an issue.
It's obvious that failures are more likely to show up when you turn the computer on, as that's when it's hardest on the components. But it doesn't follow that it's best to leave the computer on all the time, if the additional wear and tear on the components from leaving it on outweigh the wear and tear from powering it on. To use a car analogy, starting the engine of a car is hard on it, but I doubt you would leave your car running 24/7 even if the fuel was free.
Besides, I think of powering the computer on as a bit of a stress test that can highlight when something is starting to get marginal before it completely fails. I've never lost data on a harddisk in a computer that I regularly turn off, as it will give signs of impending failure when I turn the computer on long before it finally quits. However, when a harddrive goes out on a computer that's left on all the time it tends to be completely gone by the time I've realized something is wrong with it.
It could also be a problem if the CPU is being throttled because it's running too hot. I've seen a few computers that seem to be built with the assumption that the CPU will idle most of the time and size their thermal solution accordingly.
Actually, that's only been the case since 1942. Before then, it was the last Thursday of the month. The reason it was changed was that retailers wanted a longer holiday shopping season, so FDR changed Thanksgiving to the third Thursday of the month, thinking a longer shopping season would help the economy (really!). After a couple of years with much protesting (and no real boost to holiday sales), it was changed to the fourth Thursday of the month as a compromise.
Interestingly, not all the states went along with it at first, with the split going right down political lines. So for a few years, there was the "Democratic Thanksgiving" followed a week later by the "Republican Thanksgiving". I believe Texas was the last state to adopt Thanksgiving as the fourth Thursday sometime after 1956.
Slashdot Mirror
18 days? I regularly got that out of Windows 95. My recent record uptime on Windows is 118 days on Vista before things just got weird and finally it bluescreened. Same box is currently at 61 days and counting. All time record is 249 days on NT4 - so much for Windows of yesteryear being unstable.
On the other hand, I've gotten over a year on boxes running Debian, with the only reason for shutting them down was moving or harddrive failure.
Well, all the major news outlets are based out of New York City, so anything that happens in New York tends to make the national news as it's a big deal to those running the news networks. The power outage a few years back was a good example of this - it was plastered on all the major channels, that's all they talked about the whole time the power was out, and the reporters were going on like it was the end of the world or something. Meanwhile, an ice storm can knock the power out to half of "flyover country" and it will barely get a mention in the nightly news.
Well, I don't think there were any successful hijackings until five years had passed since the attacks in 2001, so I guess people just have a short memory. It also seems that the hijackers also tend to take their demands straight to the flight crew, and in some cases like the Turkish Airlines hijacking the passengers didn't even know the plane was hijacked until it landed. Finally, I don't believe there have been any instances where the hijackers were able to take control of the aircraft away from the pilots.
You sure you need that stufF? Does everyone in NE drive high performance cars? I'm sure you still have plenty of people driving around in things like the old 90HP base Nissan Sentra who get along just fine.
Well, that's not always true. The 1940's is known for WWII. The 1930's is best known for the Great Depression, even though WWII started in 1939. The 1910's is known for WWI. The 1860's for the American Civil War. With that said, the 2000's could be known for the terrorist attacks in 2001, but also could be remembered for the economic meltdown of 2008 if things get really bad and doesn't recover for the next few years.
When was the last time you saw a riced up Honda from the current body style? The boy racers are modding cars from the late 80's to the very early 2000's. Today's cars are extremely complex, even my '99 model seems simple in comparison.
I'd say you're rather ignorant yourself. Not everyone installed their warezed copies of Windows yesterday. I even know of at least one computer out there still running the infamous FCKGW key, which is blacklisted from even installing XP SP1. And lots of people still running V2C47 which no longer update (for fear of the dreaded WGA) and are thus stuck somewhere in SP2.
The problem was is there was no year zero. So the first century started on January 1st of year 1. So the first century, or after 100 years had passed, ended on December 31st of year 100. So it follows that 2000 years did not pass until January 1st of year 2001.
Of course, a decade is just a span of ten years, so it's just as correct to call 2000-2009 a decade just as much as 2001-2010. However, if you wanted to refer to the 201st decade, that would have to be 2001-2010 because once again, there was no year zero.
It's actually a logical choice. Imagine a barter system, now try to think what item(s) may be a preferred in such a system. Food? Can't store wealth, it spoils. Water? Any amount with value is going to be heavy and awkward. Live animals? Can't be divided (well, without significantly reducing their value). Lumber? Too bulky. Precious metals? Small, rare enough to be value, stores easily, divisible. Yeah, I can see why it might become money.
Well, to be fair for a while you couldn't get a decent chipset in an AMD machine no matter how much you spent. The whole Socket A era was plagued by shitty chipsets - VIA's were pure garbage, then there was SiS and even AMD's own chipsets were flakey. It wasn't until towards the end when the nForce2 came out that AMD users could enjoy a system as stable as a run-of-the-mill P4 running whatever Intel chipset that was popular at the time. Then the 64 bit era happened and nVidia's chipsets rapidly went downhill. At least AMD got their act together, and I can't complain about their chipsets for the Phenom II/Athlon II systems.
By deep Deep Googling, I guess that meant skipping the first and second results and having to click on the third result?
http://support.microsoft.com/kb/126492
Why not? The next version of Office for the PC was Office 2000, and that came out around the same time as Windows ME - so if you were running Windows 98 you were probably running Office 97. At the least, I would expect MS to patch Office 97 if it had problems running in Windows 98.
Typically, you give your name and address at the purchasing stage, after a price has been agreed upon. So what price do you present to an anonymous browser, or do you force everyone to hand over their personal information before you show them a price?
The problem with that is that the TN panels (which almost every single one of the 16:9 panels are) have a terrible vertical viewing angle. When you rotate the screen then you end up with a very noticeable poor horizontal viewing angle.
Mystery solved?
http://scrapetv.com/News/News%20Pages/Everyone%20Else/images-3/death-star-firing.jpg
How about those iPhone worms?
You also need to take into account the space the .c file is going to take before it's compiled too. I just took a look at a smallish program I made, consisting of about 3800 lines of source. It's 108k, which is not a trivial amount of ram on a computer from the early-mid 1980's.
If the current owner of the car is smart, they'll refuse to do that, for exactly the same reason you would not want to do it once it is your car. I sure would refuse if I was the seller, if you don't want the car then, fine. Another buyer will come along.
I've found the most likely components to fail on a computer are mechanical parts like the fans and drives, and the electrolytic capacitors - things that wear out faster the more the computer is left on. While it's true that thermal cycling will shorten the life of components like the CPU, chipset, and graphics cards I've found that those components are so reliable it's not an issue.
It's obvious that failures are more likely to show up when you turn the computer on, as that's when it's hardest on the components. But it doesn't follow that it's best to leave the computer on all the time, if the additional wear and tear on the components from leaving it on outweigh the wear and tear from powering it on. To use a car analogy, starting the engine of a car is hard on it, but I doubt you would leave your car running 24/7 even if the fuel was free.
Besides, I think of powering the computer on as a bit of a stress test that can highlight when something is starting to get marginal before it completely fails. I've never lost data on a harddisk in a computer that I regularly turn off, as it will give signs of impending failure when I turn the computer on long before it finally quits. However, when a harddrive goes out on a computer that's left on all the time it tends to be completely gone by the time I've realized something is wrong with it.
The company is dead, but the RCA trademark lives on. Your TV is most likely a re-branded Audiovox.
It could also be a problem if the CPU is being throttled because it's running too hot. I've seen a few computers that seem to be built with the assumption that the CPU will idle most of the time and size their thermal solution accordingly.
There's this:
http://www.thinkgeek.com/gadgets/lights/831e/
Don't own one, so I don't know how well it works exactly. Kind of want one though.
Actually, that's only been the case since 1942. Before then, it was the last Thursday of the month. The reason it was changed was that retailers wanted a longer holiday shopping season, so FDR changed Thanksgiving to the third Thursday of the month, thinking a longer shopping season would help the economy (really!). After a couple of years with much protesting (and no real boost to holiday sales), it was changed to the fourth Thursday of the month as a compromise.
Interestingly, not all the states went along with it at first, with the split going right down political lines. So for a few years, there was the "Democratic Thanksgiving" followed a week later by the "Republican Thanksgiving". I believe Texas was the last state to adopt Thanksgiving as the fourth Thursday sometime after 1956.
I guess that left you feeling a little blue...