http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/ Switched Comments for http://www.switched.com/media/feedlogo.gif http://www.switched.com en-us Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only. Blogsmith http://www.blogsmith.com/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 4th 2009 9:33AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/ now i knw uat 2 do]]>May 5th 2009 5:31PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 4th 2009 4:40PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 9th 2009 5:36PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 4th 2009 7:07PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 5th 2009 11:00PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/
Yeah, if you want to impress actual power users, you'd stop playing with toys like Windows and install a *nix.]]>May 6th 2009 1:54PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/Jun 13th 2009 11:04AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/On several different PCs over the years, I've tried various Ubuntu and Fedora versions. All of them became unbootable after a major update. Only one supported any of my wireless cards. The video driver support was flakey. And finally, when I wanted to do anything efficiently and quickly (from developing software and testing it to simply updating my MTP compatible mp3 player), I had to boot back into Windows, or spend ages googling terminal commands for what should be everyday GUI tasks.

Windows breaks more often than Linux or Mac, but unlike them, it is usually quick and easy to fix...]]>Mar 29th 2010 10:42AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/
Linux does that too. It can even do that without actually DOING anything. It's called a separate /home partition. Another feature Windows never dreams of doing because it doesn't even have a unified file system that allows you to treat separate file systems as part of the whole. Only Windows forces you to back up your files/run a program to pull over old configuration or documents. Linux just remounts your /home partition and carries on. Tools like the migration tool Windows has are a symptom of an inflexible file system structure.

Also, it's quite easy to repair Linux compared to Windows because Linux provides you with more than a crippled DOS session for a recovery console like Windows does. Instead of offering you only 50 commands that are a major toss up over whether they'll fix your problem, Linux provides you with a single mode that won't activate network or daemons, and any LiveCD can do a lot more for even Windows on the same system than the Recovery Console Windows makes you put up with. Windows has you either try to find a magic combination with its severely crippled recovery tools to fix the problem, or its only guaranteed fix by way of reinstalling Windows a lot. Linux allows you to just fix the problem. And it's not that hard. At worst you Google it, which will be possible from most any LiveCD since it doesn't just install Linux like any Windows media does.

Your mistake was also using two of the WORST Linux distributions out there for stability or reliability: Ubuntu and Fedora. Ubuntu's built right off of Debian Unstable and has some of the least competent Linux devs working it. And Fedora is actually Red Hat's experimental branch.

Video driver support is only flakey if you're a sucker with an ATI card, and that's ATI/AMD's fault, not Linux's. All the others just plain work. nVidia cards require installation of a proprietary driver, but that takes five minutes tops and only an idiot would have any trouble with it. Actually, hardware support for Linux is loads better than Windows because it actually supports waaaaaaaaaaaaaaaaaaay more hardware out of the box, and has the more extensive driver base as well as what platforms it can run on. Try installing Ubuntu and XP on that same machine and see what works out of the box on your system compared to the two. You'll find that XP will have NOTHING working, where Ubuntu will have most, if not all, your hardware working without you having to set anything up. This is because most drivers you'll ever needa re installed as a part of the kernel package and udev modprobes them at boot. Your network problem would be easily solved had you actually rubbed two brain cells together and realized there was ndiswrapper that allows you to use drivers not explicitly written for Linux. You would have discovered that and easily fixed your wireless problem had you actually done some research. And unless you're using a laptop, wireless isn't really worth the slowness, insecurity, OR unreliability. Wireless just can't compare to a good ethernet connection. Speaking of networks, did you know Windows has a deliberately crippled IP stack that makes it operate on the network much slower than any other operating syetm you could use?

The only reason you had to boot into Windows was because you couldn't figure out how to set up your wireless card. That's your fault, not Linux's. And GUI tools? Yeah, you're not a competent software developer if you can only use GUI tools. Linux is *the* platform for software development. It offers, FOR FREE, and with a greater degree of reliability and flexibility way more compilers and development tools than you will EVER see Microsoft cough up for Visual Studio. In fact, Microsoft has DUMBED DOWN development with the advent of C# and .NET.

A CLI is always going to be faster, more powerful, and more efficient than a GUI. Windows and Microsoft have trained idiots like you into thinking that they're obsolete and useless. But GUIs are severely limited and slow at what they do, and are extremely generic procedures and can't be relied on for something mission critical.

There's also several damn good reasons why Linux is the better choice for a server There's a damn good reason why over 60% of the Internet, including this very web site, are run on Linux. There are several damn good reasons why Linux is most commonly chosen for embedded use. There is many damn good reasons why Android is beginning to overtake Windows Mobile AND OS X in the mobile market.

And the only reason Windows is used is because Microsoft forced it into a monopoly. Illegally. At least TWICE they were convicted of anti-competitive monopoly behavior. They can't even consider acquisition or expansion without clearing it with the DoJ and EU first.

Trust me. No one except those like you who can't seem to tolerate a learning curve uses Windows because they actually want to. Windows is only successful because it was artificially given a market by Microsoft

Stop blaming Linux for your inability to get a clue on how to actually use it.

And I reiterate, it's easier to fix Linux without having to use crippled recovery tools or reinstalling it the way Windows forces you to.]]>Mar 29th 2010 2:14PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 7th 2009 10:03PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 8th 2009 8:49AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/you a copy of the TASKKILL.EXE file. Save it to the "\Windows\System32\" folder and you're ready to try it. ]]>May 8th 2009 10:26AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/May 14th 2009 3:49PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/Aug 7th 2009 9:53AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/Nov 20th 2009 12:19AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/Feb 28th 2010 8:46PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/Apr 16th 2010 4:56AMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/Apr 6th 2010 4:10PMhttp://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/http://www.switched.com/2009/05/04/kill-frozen-programs-in-windows-with-a-shortcut/Dec 29th 2010 6:39AM