while they were navigating around a mountain, not trying to land?
His story makes no sense at all, in any capacity, and a search of crashdatabase.com finds no crash matching any of the "Facts" of his poorly remembered, almost assuredly appocryphal story more than 30 years old.
This story doesn't pass the smell test, or would you have us believe that planes run the risk of their instrument landing systems just "switching on" and attempting to land the plane automatically every time they pass an airport with ILS aids?
October 1, 1958, the official start of the National Aeronautics and Space Administration (NASA), was the beginning of a rich history of unique scientific and technological achievements in human space flight, aeronautics, space science, and space applications.
The nature of the TSE agent is being investigated and is still a matter of debate. According to the prion theory, the agent is composed largely, if not entirely, of a self-replicating protein, referred to as a prion. Another theory argues that the agent is virus-like and possesses nucleic acids which carry genetic information. Although strong evidence collected over the past decade supports the prion theory, the ability of the TSE agent to form multiple strains is more easily explained by a virus-like agent.
I defy you to find any pieces in a standard LEGO set that will only fit with one other piece, in one specific way apart from the two parts of hinged pieces, or specific accessories (like brooms, shovels, snakes, etc).
This "specialized pieces killed LEGO" bullshit has to stop. There aren't any more specialized pieces in the newer sets than there were in older sets. They've introduced some new curved sections that get reused in lots of sets, and a bunch of mini-fig accessories with the Harry Potter sets for things like spellbooks, brooms and crystal balls.
Infact, that would tend to indicate that device manufacturers are just shovelling shit drivers out for their low end products, and putting the real developers on their high end models.
Mind you, I've been picking Lexmark here just as a printer manufacturer, I've got a Z-55 and the drivers under Windows XP have been pretty rock solid. I haven't encountered any issues with them to date, unlike say, older HP-4 Drivers and Adobe Acrobat/PostScript files.
If everyone else can manage to write a printer driver that doesn't send the computer into fits of hysterics, why must it be Microsoft's fault?
Surely there is a possibility that Lexmark has a fucking bug in their driver.
Of course not, this is Slashdot, everyone but Microsoft writes perfect code. All bugs, are either Microsoft's bug, or they hid the specs so people couldn't write compatible code.
What if it's a plain old bug in the fucking driver?
What was I thinking, as we all know, the only developers with bugs in their code are Microsoft Developers. Everyone else writes perfect code.
McFact No. 1: For years, McDonald's had known they
had a problem with the way they make their coffee - that their coffee was served
much hotter (at least 20 degrees more so) than at other restaurants.
McFact No. 2: McDonald's knew its coffee sometimes caused serious
injuries - more than 700 incidents of scalding coffee burns in the
past decade have been settled by the Corporation - and yet they never so
much as consulted a burn expert regarding the issue.
McFact No. 3: The woman involved in this infamous case suffered very
serious injuries - third degree burns on her groin, thighs and buttocks that
required skin grafts and a seven-day hospital stay.
McFact No. 4: The woman, an 81-year old former department store clerk who
had never before filed suit against anyone, said she wouldn't have brought
the lawsuit against McDonald's had the Corporation not dismissed her request for
compensation for medical bills.
McFact No. 5: A McDonald's quality assurance manager testified in the
case that the Corporation was aware of the risk of serving dangerously hot
coffee and had no plans to either turn down the heat or to post warning about
the possibility of severe burns, even though most customers wouldn't think
it was possible.
McFact No. 6: After careful deliberation, the jury found McDonald's was
liable because the facts were overwhelmingly against the company. When it came
to the punitive damages, the jury found that McDonald's had engaged in willful,
reckless, malicious, or wanton conduct, and rendered a punitive damage award of
2.7 million dollars. (The equivalent of just two days of coffee sales, McDonalds
Corporation generates revenues in excess of 1.3 million dollars daily from the
sale of its coffee, selling 1 billion cups each year.)
McFact No. 7: On appeal, a judge lowered the award to $480,000, a fact
not widely publicized in the media.
McFact No. 8: A report in Liability Week, September 29, 1997, indicated
that Kathleen Gilliam, 73, suffered first degree burns when a cup of coffee
spilled onto her lap. Reports also indicate that McDonald's consistently keeps
its coffee at 185 degrees, still approximately 20 degrees hotter than at other
restaurants. Third degree burns occur at this temperature in just two to seven
seconds, requiring skin grafting, debridement and whirlpool treatments that cost
tens of thousands of dollars and result in permanent disfigurement, extreme pain
and disability to the victims for many months, and in some cases, years.
McFact No. 1: For years, McDonald's had known they had a problem with the way they make their coffee - that their coffee was served much hotter (at least 20 degrees more so) than at other restaurants.
McFact No. 2: McDonald's knew its coffee sometimes caused serious injuries - more than 700 incidents of scalding coffee burns in the past decade have been settled by the Corporation - and yet they never so much as consulted a burn expert regarding the issue.
McFact No. 3: The woman involved in this infamous case suffered very serious injuries - third degree burns on her groin, thighs and buttocks that required skin grafts and a seven-day hospital stay.
McFact No. 4: The woman, an 81-year old former department store clerk who had never before filed suit against anyone, said she wouldn't have brought the lawsuit against McDonald's had the Corporation not dismissed her request for compensation for medical bills.
McFact No. 5: A McDonald's quality assurance manager testified in the case that the Corporation was aware of the risk of serving dangerously hot coffee and had no plans to either turn down the heat or to post warning about the possibility of severe burns, even though most customers wouldn't think it was possible.
McFact No. 6: After careful deliberation, the jury found McDonald's was liable because the facts were overwhelmingly against the company. When it came to the punitive damages, the jury found that McDonald's had engaged in willful, reckless, malicious, or wanton conduct, and rendered a punitive damage award of 2.7 million dollars. (The equivalent of just two days of coffee sales, McDonalds Corporation generates revenues in excess of 1.3 million dollars daily from the sale of its coffee, selling 1 billion cups each year.)
McFact No. 7: On appeal, a judge lowered the award to $480,000, a fact not widely publicized in the media.
McFact No. 8: A report in Liability Week, September 29, 1997, indicated that Kathleen Gilliam, 73, suffered first degree burns when a cup of coffee spilled onto her lap. Reports also indicate that McDonald's consistently keeps its coffee at 185 degrees, still approximately 20 degrees hotter than at other restaurants. Third degree burns occur at this temperature in just two to seven seconds, requiring skin grafting, debridement and whirlpool treatments that cost tens of thousands of dollars and result in permanent disfigurement, extreme pain and disability to the victims for many months, and in some cases, years.
At the same time you're sending that "Lock this file" message to the server, two other clients are also sending the same message.
What if the client that requested it originally goes offline? Do you leave the file locked forever? Until that client requests the file again? Until that client reattaches to the drive?
How do you track these things reliably when you may have a transient connection to the drive where you're trying to lock files for exclusive access.
First off, Microsoft was denied the ability to argue prior-art in the original trial.
Secondly, it's the W3C that's requested the Patent Re-examination.
Thirdly, it's a patent re-examination, it's rare, but it's a normal part of the process. No one is changing any rules at all here.
But of course, it's benefits Microsoft, so clearly, there must be some shenanigans going on, Microsoft getting(buying) special treatment that no one else would get, right?
Destroyed panels don't create orbital debris that cascades destroying the array. It's also pretty trivial to send your little manufacturing robots out to repair the damage, rather than trying to launch something through the cloud of orbital debris left from your disintegrating solar arrays.
He'd never seen a CD MP3 player that got more than 8 hours of battery life.
90-150 hours is significantly longer than 8 hours. It weighs only about 2 or 3 grams more than an iPod as well, and is just as thin.
It's certainly a viable alternative unless you must have the smallest device possible, in which case you might want to look into a memory based MP3 player (like the new Sony NetWalkman) or even a MuVo.
I've got an MZ-N707 NetMD player. I rarely charge the batteries about once a week, and I've got about 2.5 hours of commute time a day.
It's also smaller than an iPod, and transferring MP3's and WMA's to the device isn't a problem.
My only wish would be the ability to store data on my MiniDisc's for occasional file transfers between Home/Work.
I've also hacked the Firmware on my N707 to function as an R900, which gives added some playback modes and a timer. Unfortunately, the 707 doesn't have the memory necessary to remember individual MD settings.
Sony D-NE1 ATRAC3/MP3 CD Walkman.
5 3/8" x 5 3/8" x 5/8", 6.25 ounces, 90-150 hours on a charged set of batteries. [2 NH14WM(a) Rechargeable batteries for the player and 2 "AA" Batteries for the Backlight Remote] The NH-14MW are 1.2v 1350maH batteries.
Microsoft is not behind every negative article or study about every company in the technology space except for microsoft. Nor are they behind every review or study that shows a Microsoft product in a positive light.
A little healthy paranoia is a good thing. Seeing Microsoft behind EVERYTHING is definetly not healthy.
Microsoft is not behind every negative article or study about every company in the technology space except for microsoft. Nor are they behind every review or study that shows a Microsoft product in a positive light.
A little healthy paranoia is a good thing. Seeing Microsoft behind EVERYTHING is definetly not healthy.
If a computer in the act of being installed is exposed to the net unprotected, your System Admin's need to be dragged out and shot.
If it's getting infected by an infected computer INSIDE the corporate firewall, your IT department needs to be dragged out into the street and shot.
There is absolutely NO GOOD REASON that a computer should be freely attackable in a corporate environment unless the IT Department is grossly incompetent.
Slashdot Mirror
while they were navigating around a mountain, not trying to land?
His story makes no sense at all, in any capacity, and a search of crashdatabase.com finds no crash matching any of the "Facts" of his poorly remembered, almost assuredly appocryphal story more than 30 years old.
would have had to be switched on by the pilots.
This story doesn't pass the smell test, or would you have us believe that planes run the risk of their instrument landing systems just "switching on" and attempting to land the plane automatically every time they pass an airport with ILS aids?
October 1, 1958, the official start of the National Aeronautics and Space Administration (NASA), was the beginning of a rich history of unique scientific and technological achievements in human space flight, aeronautics, space science, and space applications.
vCJD is variant Creutzfeldt-Jakob Disease.
n /
The nature of the TSE agent is being investigated and is still a matter of debate. According to the prion theory, the agent is composed largely, if not entirely, of a self-replicating protein, referred to as a prion. Another theory argues that the agent is virus-like and possesses nucleic acids which carry genetic information. Although strong evidence collected over the past decade supports the prion theory, the ability of the TSE agent to form multiple strains is more easily explained by a virus-like agent.
http://www.who.int/mediacentre/factsheets/fs180/e
In their one current mission, the orbiter survived and the lander is presumed lost.
HP isn't making them, they're rebranded iPod's with a colored faceplate and an HP Logo.
I defy you to find any pieces in a standard LEGO set that will only fit with one other piece, in one specific way apart from the two parts of hinged pieces, or specific accessories (like brooms, shovels, snakes, etc).
This "specialized pieces killed LEGO" bullshit has to stop. There aren't any more specialized pieces in the newer sets than there were in older sets. They've introduced some new curved sections that get reused in lots of sets, and a bunch of mini-fig accessories with the Harry Potter sets for things like spellbooks, brooms and crystal balls.
that take the whole OS Down?
The only times I've personally seen XP Blue screen, were from Video Card drivers (Thanks ATI you cocksuckers)
I've never personally seen a scanner, or printer, or modem or a frigging web cam crash an XP machine.
Infact, that would tend to indicate that device manufacturers are just shovelling shit drivers out for their low end products, and putting the real developers on their high end models.
Mind you, I've been picking Lexmark here just as a printer manufacturer, I've got a Z-55 and the drivers under Windows XP have been pretty rock solid. I haven't encountered any issues with them to date, unlike say, older HP-4 Drivers and Adobe Acrobat/PostScript files.
If everyone else can manage to write a printer driver that doesn't send the computer into fits of hysterics, why must it be Microsoft's fault?
Surely there is a possibility that Lexmark has a fucking bug in their driver.
Of course not, this is Slashdot, everyone but Microsoft writes perfect code. All bugs, are either Microsoft's bug, or they hid the specs so people couldn't write compatible code.
What if it's a plain old bug in the fucking driver? What was I thinking, as we all know, the only developers with bugs in their code are Microsoft Developers. Everyone else writes perfect code.
Nor is it Microsoft's fault if ATI can't write a quality display driver.
but it's also not Microsoft's fucking fault if Lexmark can't write a quality print driver.
McFact No. 1: For years, McDonald's had known they had a problem with the way they make their coffee - that their coffee was served much hotter (at least 20 degrees more so) than at other restaurants.
McFact No. 2: McDonald's knew its coffee sometimes caused serious injuries - more than 700 incidents of scalding coffee burns in the past decade have been settled by the Corporation - and yet they never so much as consulted a burn expert regarding the issue.
McFact No. 3: The woman involved in this infamous case suffered very serious injuries - third degree burns on her groin, thighs and buttocks that required skin grafts and a seven-day hospital stay.
McFact No. 4: The woman, an 81-year old former department store clerk who had never before filed suit against anyone, said she wouldn't have brought the lawsuit against McDonald's had the Corporation not dismissed her request for compensation for medical bills.
McFact No. 5: A McDonald's quality assurance manager testified in the case that the Corporation was aware of the risk of serving dangerously hot coffee and had no plans to either turn down the heat or to post warning about the possibility of severe burns, even though most customers wouldn't think it was possible.
McFact No. 6: After careful deliberation, the jury found McDonald's was liable because the facts were overwhelmingly against the company. When it came to the punitive damages, the jury found that McDonald's had engaged in willful, reckless, malicious, or wanton conduct, and rendered a punitive damage award of 2.7 million dollars. (The equivalent of just two days of coffee sales, McDonalds Corporation generates revenues in excess of 1.3 million dollars daily from the sale of its coffee, selling 1 billion cups each year.)
McFact No. 7: On appeal, a judge lowered the award to $480,000, a fact not widely publicized in the media.
McFact No. 8: A report in Liability Week, September 29, 1997, indicated that Kathleen Gilliam, 73, suffered first degree burns when a cup of coffee spilled onto her lap. Reports also indicate that McDonald's consistently keeps its coffee at 185 degrees, still approximately 20 degrees hotter than at other restaurants. Third degree burns occur at this temperature in just two to seven seconds, requiring skin grafting, debridement and whirlpool treatments that cost tens of thousands of dollars and result in permanent disfigurement, extreme pain and disability to the victims for many months, and in some cases, years.
Excerpt from: Courtesy Legal News and Views, Ohio Academy of Trial Lawyers
Also see Van O'Steen and Partners
Newsaic : Mirrow Law
McFact No. 1: For years, McDonald's had known they had a problem with the way they make their coffee - that their coffee was served much hotter (at least 20 degrees more so) than at other restaurants.
McFact No. 2: McDonald's knew its coffee sometimes caused serious injuries - more than 700 incidents of scalding coffee burns in the past decade have been settled by the Corporation - and yet they never so much as consulted a burn expert regarding the issue.
McFact No. 3: The woman involved in this infamous case suffered very serious injuries - third degree burns on her groin, thighs and buttocks that required skin grafts and a seven-day hospital stay.
McFact No. 4: The woman, an 81-year old former department store clerk who had never before filed suit against anyone, said she wouldn't have brought the lawsuit against McDonald's had the Corporation not dismissed her request for compensation for medical bills.
McFact No. 5: A McDonald's quality assurance manager testified in the case that the Corporation was aware of the risk of serving dangerously hot coffee and had no plans to either turn down the heat or to post warning about the possibility of severe burns, even though most customers wouldn't think it was possible.
McFact No. 6: After careful deliberation, the jury found McDonald's was liable because the facts were overwhelmingly against the company. When it came to the punitive damages, the jury found that McDonald's had engaged in willful, reckless, malicious, or wanton conduct, and rendered a punitive damage award of 2.7 million dollars. (The equivalent of just two days of coffee sales, McDonalds Corporation generates revenues in excess of 1.3 million dollars daily from the sale of its coffee, selling 1 billion cups each year.)
McFact No. 7: On appeal, a judge lowered the award to $480,000, a fact not widely publicized in the media.
McFact No. 8: A report in Liability Week, September 29, 1997, indicated that Kathleen Gilliam, 73, suffered first degree burns when a cup of coffee spilled onto her lap. Reports also indicate that McDonald's consistently keeps its coffee at 185 degrees, still approximately 20 degrees hotter than at other restaurants. Third degree burns occur at this temperature in just two to seven seconds, requiring skin grafting, debridement and whirlpool treatments that cost tens of thousands of dollars and result in permanent disfigurement, extreme pain and disability to the victims for many months, and in some cases, years.
Excerpt from: Courtesy Legal News and Views, Ohio Academy of Trial Lawyers
Also see Van O'Steen and Partners
Newsaic : Mirrow Law
At the same time you're sending that "Lock this file" message to the server, two other clients are also sending the same message.
What if the client that requested it originally goes offline? Do you leave the file locked forever? Until that client requests the file again? Until that client reattaches to the drive?
How do you track these things reliably when you may have a transient connection to the drive where you're trying to lock files for exclusive access.
First off, Microsoft was denied the ability to argue prior-art in the original trial.
Secondly, it's the W3C that's requested the Patent Re-examination.
Thirdly, it's a patent re-examination, it's rare, but it's a normal part of the process. No one is changing any rules at all here.
But of course, it's benefits Microsoft, so clearly, there must be some shenanigans going on, Microsoft getting(buying) special treatment that no one else would get, right?
because modern aircraft don't currently have to dodge numerous no-fly zones and controlled airspaces, scattered all over the map already.
Destroyed panels don't create orbital debris that cascades destroying the array. It's also pretty trivial to send your little manufacturing robots out to repair the damage, rather than trying to launch something through the cloud of orbital debris left from your disintegrating solar arrays.
He'd never seen a CD MP3 player that got more than 8 hours of battery life. 90-150 hours is significantly longer than 8 hours. It weighs only about 2 or 3 grams more than an iPod as well, and is just as thin. It's certainly a viable alternative unless you must have the smallest device possible, in which case you might want to look into a memory based MP3 player (like the new Sony NetWalkman) or even a MuVo.
I've got an MZ-N707 NetMD player. I rarely charge the batteries about once a week, and I've got about 2.5 hours of commute time a day.
It's also smaller than an iPod, and transferring MP3's and WMA's to the device isn't a problem.
My only wish would be the ability to store data on my MiniDisc's for occasional file transfers between Home/Work.
I've also hacked the Firmware on my N707 to function as an R900, which gives added some playback modes and a timer. Unfortunately, the 707 doesn't have the memory necessary to remember individual MD settings.
How about this?
Sony D-NE1 ATRAC3/MP3 CD Walkman. 5 3/8" x 5 3/8" x 5/8", 6.25 ounces, 90-150 hours on a charged set of batteries. [2 NH14WM(a) Rechargeable batteries for the player and 2 "AA" Batteries for the Backlight Remote] The NH-14MW are 1.2v 1350maH batteries.
Sony D-NE1
Apple iPod (40 GB Model)
4.1 x 2.4 x 0.62, 6.2 ounces. 630mah LiON Battery, 8 hours on a charge (Apple Literature)
Microsoft is not behind every negative article or study about every company in the technology space except for microsoft. Nor are they behind every review or study that shows a Microsoft product in a positive light.
A little healthy paranoia is a good thing. Seeing Microsoft behind EVERYTHING is definetly not healthy.
Microsoft is not behind every negative article or study about every company in the technology space except for microsoft. Nor are they behind every review or study that shows a Microsoft product in a positive light.
A little healthy paranoia is a good thing. Seeing Microsoft behind EVERYTHING is definetly not healthy.
in a corporate environment.
If a computer in the act of being installed is exposed to the net unprotected, your System Admin's need to be dragged out and shot.
If it's getting infected by an infected computer INSIDE the corporate firewall, your IT department needs to be dragged out into the street and shot.
There is absolutely NO GOOD REASON that a computer should be freely attackable in a corporate environment unless the IT Department is grossly incompetent.