Unfortunately, this time the team's confusion of imperial/metric units causes the slug to make a gentle, safe landing on the planet's surface rather than impacting explosively. Oops.
My father-in-law is a dispatcher for Keyspan, the company responsible for that blunder. Apparently, some of the older gas lines are not clearly marked as to whether they are high pressure or low pressure lines (which is what caused this balls-up). The tech hooked a high-pressure feed line up to a low-pressure residential feed line. This caused gas leaks in many homes along this line as the high-pressure gas popped open any weak fittings or connections inside the house. MAJOR screw-up.
Our company bought a handfull of these things they all went in for multiple repairs. The machines were still covered under the warranty period, so the repairs cost us nothing (outside of employee down-time). The $1,000 per machine will more than cover the repair costs on each.
Makes 'modern' product placement seem pretty harmless, eh?
I dunno, have you seen the blatant motorola cell-phone product placement going on in CSI New York lately? It is just as brutal as your "Spaffco" example. They even somehow managed to work the phone and their cool custom ringtones into the final plot twist. Brutal.
In broader terms, this makes Windows far more like Linux and Unix - and even the MacOS - where the graphics subsystem is a separate component, rather than being hard-wired into the OS kernel.
Looks like the cat's already out of the bag. On to the next wild theory.
Where in the article did they claim that it was a "feature"? They merely stated that moving it out of the kernel would add stablity to the OS. If anything, the article makes it sound like that they realized that the way they were doing it was the cause of many system crashes (which it was) and that it was a bad design decision. They are now correcting that bad decision, end of story.
They don't really try to disprove myths, they try VERY HARD to make them happen. Especially when there's explosions involved.
Not only that, but they will resport to absolute brute force methods to try and duplicate the results that the myth supposedly purports. Probably the best example of this was the "Exploding Scuba Tank". They tried to "encourage" an aluminum scuba tank to explode by shooting it with a high-powered rifle. The best they could achieve with this method was to put a bullet-sized hole in the tank and let the 3000 or so psi "leak" out and blast the tank around the test chamber like a rocket. They finally got the tank to explode by using a bit of C-4. The devastation caused by the C-4 in conjunction with the 3000 psi tank exploding was quite impressive...
I saw the lawer pointing to what appeared to be a hash number on the photo.
How are they embedding the hash into the image? If they generate the hash off of the orginal image, as soon as they embed the hash into the image, the resulting hash off of the modified image would be changed. If you did an MD5 hash of the image after the generated hash was embedded, the two would not match and would make the photo appear to be doctored. Perhaps this is the crux of the matter?
Why am I getting broken or gray images on a site?
Broken images (when there is a small red "x" where the image should be) occur when the images are not available on our servers. Usually this means that we did not archive them. Gray images are the result of robots.txt exclusions. The site in question may have blocked robot access to their images directory.
Interesting. Our sites date back to 1999. The images files from the older versions of sites do not show up, as these files were deleted long ago. The newer versions that use the images files that are still resident in our/images directory work fine. I am not sure how they handle images.
That's because they don't save the image files, as far as I can tell. The images actually point back to the site that was archived through some sort of re-direct on the WBM site. If the images files no longer exist on the original site, they will not display on the WBM archived page.
I guess ASP.net uses the.net framework on client-side also making it impossible to make the app compatible with Firefox unless you get rid of.NET
Incorrect. It does not use anything from the.NET framework on the client-side. ASP.net simply produces a combination of HTML and JavaScript. Now, this HTML/JavaScript code that it produces may not be standards-compliant, therefore it may not work correctly in non-IE browsers. Within the Visual Studio IDE you can select which browsers you wish to code for using the targetSchema property within your aspx page, but this doesn't work very well. If your application did not work correctly in other browsers, it is because it was coded poorly, or you used some of the ASP.net controls that don't work very well in other browsers, such as the form validation controls.
No PDF generation libraries out of the box, but there are classes for image manipulation (system.drawing). They are comparable to the GD libraries for Perl. If you would like more info on all of the goodies, try the MSDN site (works best with IE, unfortunately).
How so? If is box is running in standalone mode (no connection to the TiVo servers), he is fine. The box just takes in a video stream, encodes and stores it. It just works like a vcr, but with some of the cool TiVo features. There is no need to keep up with software upgrades, if you do not wish to.
If it works like their current direct advertising, the TiVo box will connect to their servers (through the phone line or via the internet), download the commercial (or image, or whatever it may be) during its normal content download timeframe and save it to a partition on the units' hard drive. The advertisers then send a bit of information along in either the closed captioning or the alternate language portion of the commercial broadcast (not sure which) that the TiVo recognizes as meaning "OK, time to display the ad". If the person happens to hit fast forward, they can then overlay the image for the product on the screen. They already do something similar with certain commercials. When the TiVo recognizes the flag, it overlays a little image that says "Hit the thumb's up button to learn more". This then takes you into a menu screen that allows you to view more detailed ads about the product.
Slashdot Mirror
Unfortunately, this time the team's confusion of imperial/metric units causes the slug to make a gentle, safe landing on the planet's surface rather than impacting explosively. Oops.
Apparently, Bill has a soft spot for exotic Porsches.
My father-in-law is a dispatcher for Keyspan, the company responsible for that blunder. Apparently, some of the older gas lines are not clearly marked as to whether they are high pressure or low pressure lines (which is what caused this balls-up). The tech hooked a high-pressure feed line up to a low-pressure residential feed line. This caused gas leaks in many homes along this line as the high-pressure gas popped open any weak fittings or connections inside the house. MAJOR screw-up.
Our company bought a handfull of these things they all went in for multiple repairs. The machines were still covered under the warranty period, so the repairs cost us nothing (outside of employee down-time). The $1,000 per machine will more than cover the repair costs on each.
Makes 'modern' product placement seem pretty harmless, eh?
I dunno, have you seen the blatant motorola cell-phone product placement going on in CSI New York lately? It is just as brutal as your "Spaffco" example. They even somehow managed to work the phone and their cool custom ringtones into the final plot twist. Brutal.
From the article:
In broader terms, this makes Windows far more like Linux and Unix - and even the MacOS - where the graphics subsystem is a separate component, rather than being hard-wired into the OS kernel.
Looks like the cat's already out of the bag. On to the next wild theory.
Where in the article did they claim that it was a "feature"? They merely stated that moving it out of the kernel would add stablity to the OS. If anything, the article makes it sound like that they realized that the way they were doing it was the cause of many system crashes (which it was) and that it was a bad design decision. They are now correcting that bad decision, end of story.
Too funny. You have inspired me to introduce a new googlebomb target:
scumbag, swine, pig, bastard
They don't really try to disprove myths, they try VERY HARD to make them happen. Especially when there's explosions involved.
Not only that, but they will resport to absolute brute force methods to try and duplicate the results that the myth supposedly purports. Probably the best example of this was the "Exploding Scuba Tank". They tried to "encourage" an aluminum scuba tank to explode by shooting it with a high-powered rifle. The best they could achieve with this method was to put a bullet-sized hole in the tank and let the 3000 or so psi "leak" out and blast the tank around the test chamber like a rocket. They finally got the tank to explode by using a bit of C-4. The devastation caused by the C-4 in conjunction with the 3000 psi tank exploding was quite impressive...
I saw the lawer pointing to what appeared to be a hash number on the photo.
How are they embedding the hash into the image? If they generate the hash off of the orginal image, as soon as they embed the hash into the image, the resulting hash off of the modified image would be changed. If you did an MD5 hash of the image after the generated hash was embedded, the two would not match and would make the photo appear to be doctored. Perhaps this is the crux of the matter?
Interesting. Our sites date back to 1999. The images files from the older versions of sites do not show up, as these files were deleted long ago. The newer versions that use the images files that are still resident in our /images directory work fine. I am not sure how they handle images.
That's because they don't save the image files, as far as I can tell. The images actually point back to the site that was archived through some sort of re-direct on the WBM site. If the images files no longer exist on the original site, they will not display on the WBM archived page.
I guess ASP.net uses the .net framework on client-side also making it impossible to make the app compatible with Firefox unless you get rid of .NET
.NET framework on the client-side. ASP.net simply produces a combination of HTML and JavaScript. Now, this HTML/JavaScript code that it produces may not be standards-compliant, therefore it may not work correctly in non-IE browsers. Within the Visual Studio IDE you can select which browsers you wish to code for using the targetSchema property within your aspx page, but this doesn't work very well. If your application did not work correctly in other browsers, it is because it was coded poorly, or you used some of the ASP.net controls that don't work very well in other browsers, such as the form validation controls.
Incorrect. It does not use anything from the
I cut v notches in the trailing tips of the blade to increase the noise created by the fans 3 fold.
Two words, man: whistle tips. Just add them to the exhaust ports at the back of the case and Woo! Woo! We just pimped your box, yo!
Step 1) Figure out how to get clock to stop blinking 12AM
I'm not so sure about that. The mainstream television news in Boston (Channel 7, NBC affiliate) was reporting it this morning.
No PDF generation libraries out of the box, but there are classes for image manipulation (system.drawing). They are comparable to the GD libraries for Perl. If you would like more info on all of the goodies, try the MSDN site (works best with IE, unfortunately).
Just hand the commentary script to James Earl Jones...
Gotcha. Forgive my wise-assedness.
They were up on the 11th, at least in the morning. Try the 12th.
How so? If is box is running in standalone mode (no connection to the TiVo servers), he is fine. The box just takes in a video stream, encodes and stores it. It just works like a vcr, but with some of the cool TiVo features. There is no need to keep up with software upgrades, if you do not wish to.
If it works like their current direct advertising, the TiVo box will connect to their servers (through the phone line or via the internet), download the commercial (or image, or whatever it may be) during its normal content download timeframe and save it to a partition on the units' hard drive. The advertisers then send a bit of information along in either the closed captioning or the alternate language portion of the commercial broadcast (not sure which) that the TiVo recognizes as meaning "OK, time to display the ad". If the person happens to hit fast forward, they can then overlay the image for the product on the screen. They already do something similar with certain commercials. When the TiVo recognizes the flag, it overlays a little image that says "Hit the thumb's up button to learn more". This then takes you into a menu screen that allows you to view more detailed ads about the product.
I had the same machine. I upgraded the thing to 16MB RAM and eventually got Mindows ME running on it. What a POS.
Coming from Ted it would be more like "Mahk er-ah MuhGuiah, er-ah ah."