OSNews

No, is not a magic box.

(Trollmode ON)
But Windows is like an American car, which need tune up every 3 months or it breaks appart, while Linux/BSD are European cars which runs without tuneup for 6+ months, lol
(Trollmode OFF)

No, is not a magic box.

(Trollmode ON)
But Windows is like an American car, which need tune up every 3 months or it breaks appart, while Linux/BSD are European cars which runs without tuneup for 6+ months, lol
(Trollmode OFF) "

Which European cars? If they are french cars or Italian Motorcycles expect them not to work if it rains (I don't even joke, I have owned a Harley Sportster 1200 and a Aprilia RS-250, one is European and one is an American/Euro engine and it doesn't start easily if it is raining).

Actually Windows since Windows 7 is more like a Honda CB-125 motorcycle engine. You can abuse it as much as you want and it will keep on working ... it might limp along and not get you there as fast ... but it still works

:-P

When did I say that, I simply said that with Windows that problems can be solved using those tools ... and things can be solved without a reinstall with a little understanding of the underlying system.



True.

My comment is more about the fact that people tend not to look for the root cause of the solution.

A lot of Linux users "distro hop" because they can't solve their problems using <distro X> and try using <distro Y> in hope it will solve their problems.

When in fact there is an underlying issue that needs to be addressed.

Either way reinstalling or installing another operating system is not the way to solve problems. It is better to scrutinize the root cause of the problem.

In short it is better to understand why you are having problem first before deciding a strategy to deal with it.

Edited 2012-11-27 20:17 UTC

lucas_maximus,

"When did I say that, I simply said that with Windows that problems can be solved using those tools. Nothing more."

Fair enough, I was just reading your statement in context of the previous windows/linux generalisation.

Another tool everyone on windows should have is the sysinternals process explorer. Shows processes, resources, open files, etc. It allows you to forcefully kill hidden processes that are otherwise difficult to kill and responsible for locking files.

http://technet.microsoft.com/en-us/sysinternals/bb896653


Edit:
" ... and things can be solved without a reinstall with a little understanding of the underlying system."

This is assuming you can track down the problem of course. I've had many people come to me for help in fixing something or other on windows. Usually it's something pretty trivial, but other times I have to recommend restoring or reinstalling because it's less work than trying to find out what's wrong. Sometimes just re-creating a user account is enough.

Mind you, linux can be the same way, but it's usually easier to diff the files and/or look at timestamps there. In windows you've got the whole registery to deal with.

Edited 2012-11-27 20:38 UTC