"Every bit of fossil fuel CO2 we've used since Watt built his steam engine has contributed to the progression of global warming" is likely true, but probably only in a pedantic sense (because emissions have gone up so fast, the impact of the decades prior to 1950 is tiny compared to those since).
As the U.S. 'decays', our labor becomes more and more cost effective. Things will not get terrible.
(of course, our multiplier over average world consumption will probably go down, making a bunch of people think things are terrible (where 'slightly uncomfortable' would probably be a better description))
Do note that it is simply a self extracting archive containing a batch file and some other tools (and it isn't clear that the tools have been licensed for redistribution).
WinRar and 7-Zip can both extract the file, the main program is 'C.bat'. It contains this entertaining text:
:: It's okay if you want to take a peek at the script but......:: please bear in mind that if you have to copy, that means you can't script it on your own.:: Copying means you don't understand enough. Also means you're not ready to make tools.:: Do yourself & everybody else a favor. Don't release anything that you dont fully understand.:: Chances of trashing a machine is high. Bide your time. If you work hard, your time shall come.
I've also seen it where the 'helpers' on malware sites say that they don't want to reveal how (their batch script) works, as it would help the malware writers (you know, the guys writing low level rootkits).
It also seems to use the 'probably won't break anything' approach to testing.
Definitely a buyer beware type of situation (but it has been used to help loads of people...).
Examining the disk from an independent system (the software, so a boot cd works) is the only way to be sure that it is possible to see the rootkit, but most rootkits can be detected by several of the tools that exist for the purpose (from what I gather, the tools look for differences between what system file routines return and what lower level file system routines return).
Sure, a powerful enough rootkit will be hidden from both, but we (seemingly) haven't gotten to that point yet.
Yeah, sure, learning how to use a different system will take 10 minutes. And figuring out which apps to run to do various tasks will only take 5 more.
The root problem was a file corrupted by malware, so calling the update broken is a bit much; certainly, the fact that malware can trample system files is a bummer.
Certainly doesn't absolve Microsoft (they are the ones that released XP with Administrator accounts being the norm, making it easy for malware to alter system files), but it isn't that crazy that a hacked up low level driver is causing some issues.
As I alluded to in my comment, all you need is the I386 folder. It is mostly likely present at C:\I386.
(I am typing this on a computer that did not come with an installation disc; I used the I386 folder to build one (with SP3 slip-streamed in). I have used that CD to install Windows into a VM.)
That solution shouldn't really cause any additional problems, I imagine it was unmarked because it is overzealous, uninstalling all of the updates instead of a single update (presumably the problem is related to a single update).
Slashdot Mirror
Your characterization of what he says won't stand up to people reading the interview, so i would suggest that they go ahead and do that.
"Every bit of fossil fuel CO2 we've used since Watt built his steam engine has contributed to the progression of global warming" is likely true, but probably only in a pedantic sense (because emissions have gone up so fast, the impact of the decades prior to 1950 is tiny compared to those since).
Read the article for yourselves. Do not take my or jvillain's word for it.
There is no bus involved, and Phil Jones says that yes, warming since 1950 is probably anthropogenic.
Perhaps they will provide an impartial assessment of the current state of climate science, rather than a pronouncement on global warming.
Then you need to explain which channel it was:
http://www.history.com/content/ufohunters/
http://www.bautforum.com/small-media-large/85688-history-channel-program-ancient-aliens.html
Was it before, after or between shows about aliens?
Firefox does not get in my way. I therefore have no interest in trying out other browsers (I have never tried any of Chrome, Safari or Opera...).
Maybe I am missing out, but I don't know it, so it doesn't bother me any.
As the U.S. 'decays', our labor becomes more and more cost effective. Things will not get terrible.
(of course, our multiplier over average world consumption will probably go down, making a bunch of people think things are terrible (where 'slightly uncomfortable' would probably be a better description))
~6.5 billion, not 5.7 billion.
http://gnuwin32.sourceforge.net/packages/findutils.htm
http://gnuwin32.sourceforge.net/packages/grep.htm
They work fine (as far as I have exercised them).
"Use Firefox Keyboard Shortcuts" wouldn't be a completely absurd option to include.
It is only plagiarism if he misrepresents the source of the work.
And, for instance, Rolling Stone doesn't seem to be real reluctant to 'call him on it':
http://www.rollingstone.com/reviews/album/16700035/review/16720051/rockandrolljesus
Exiv fits your description:
http://www.exiv2.org/index.html
(I find the already mentioned ExifTool better for command line stuff)
You should be able to look at the most interesting details in most up to date image software.
The buzzsaw is ExifTool:
http://www.sno.phy.queensu.ca/~phil/exiftool/
Do note that it is simply a self extracting archive containing a batch file and some other tools (and it isn't clear that the tools have been licensed for redistribution).
WinRar and 7-Zip can both extract the file, the main program is 'C.bat'. It contains this entertaining text:
:: It's okay if you want to take a peek at the script but ...... :: please bear in mind that if you have to copy, that means you can't script it on your own. :: Copying means you don't understand enough. Also means you're not ready to make tools. :: Do yourself & everybody else a favor. Don't release anything that you dont fully understand. :: Chances of trashing a machine is high. Bide your time. If you work hard, your time shall come.
I've also seen it where the 'helpers' on malware sites say that they don't want to reveal how (their batch script) works, as it would help the malware writers (you know, the guys writing low level rootkits).
It also seems to use the 'probably won't break anything' approach to testing.
Definitely a buyer beware type of situation (but it has been used to help loads of people...).
The update isn't providing a new atapi.sys file, it is changing something that the rootkit (present in atapi.sys) depended on.
Examining the disk from an independent system (the software, so a boot cd works) is the only way to be sure that it is possible to see the rootkit, but most rootkits can be detected by several of the tools that exist for the purpose (from what I gather, the tools look for differences between what system file routines return and what lower level file system routines return).
Sure, a powerful enough rootkit will be hidden from both, but we (seemingly) haven't gotten to that point yet.
The rollback fix and the possible malware link were both discussed in the story posted yesterday.
(I realize that getting a recovery console on a netbook with no optical drive is a bit of a chore)
Yeah, sure, learning how to use a different system will take 10 minutes. And figuring out which apps to run to do various tasks will only take 5 more.
The root problem was a file corrupted by malware, so calling the update broken is a bit much; certainly, the fact that malware can trample system files is a bummer.
This post, a little ways below, indicates that the crash is due to malware altering a file:
http://tech.slashdot.org/comments.pl?sid=1546966&cid=31108534
Certainly doesn't absolve Microsoft (they are the ones that released XP with Administrator accounts being the norm, making it easy for malware to alter system files), but it isn't that crazy that a hacked up low level driver is causing some issues.
Compared to the Nuke it and reinstall advice above it, it is a walk in the park.
That's covered by the expecting them to look after their own interests.
As I alluded to in my comment, all you need is the I386 folder. It is mostly likely present at C:\I386.
(I am typing this on a computer that did not come with an installation disc; I used the I386 folder to build one (with SP3 slip-streamed in). I have used that CD to install Windows into a VM.)
That solution shouldn't really cause any additional problems, I imagine it was unmarked because it is overzealous, uninstalling all of the updates instead of a single update (presumably the problem is related to a single update).
You can install the recovery console as a boot option:
http://support.microsoft.com/kb/307654
(You should have an I386 folder somewhere)
It is more complicated for Vista and later:
http://blogs.msdn.com/winre/archive/2007/01/12/how-to-install-winre-on-the-hard-disk.aspx