<< I wasn't talking about lame forum responses, I was talking about the fact that people consider stability based on a standard that windows set. They consider certain things windows does as accepted where Linux wouldn't put up with them, thus why I brought up BSOD and Dr Watsons. >>
Are you talking about stability based on Win9x, or NT/W2K??? You act as if the two platforms are the same. They're as different as night and day.
<< The downtime was exactly the same as replacing any piece of hardware. Their old machines were removed - their new Linux machines were installed. Done! The interface was setup very nicely so that even those without any Unix background could grasp it. >>
It's good to know that some companies can accomplish this. It's not they same everywhere, unless you want to be called every 5 minutes by a user asking "how do I print to xxx", "how do I save this file to xxx", etc. Most end users cannot handle to much change without being a serious burden on administration.
<< I never said Win2K was a bad OS, don't put words in my mouth - I actually gave praise to Win2K in another thread. >>
You always seem to think it doesn't measure up, and you find it hard to believe that it can be stable. Wouldn't that make it a bad OS in your eyes???
<< Also, like good ol mom useda say - if NASDAQ jumped off a bridge, would you do it too? >>
Maybe, depending on how much my stocks fall.
<< Yes, you must assume that because I like Linux I am retarded or something because you then stated, "or you were using a Presario as a server". >>
I just wondered why you're the only person I've heard trash Compaq's servers. I woun't give their home line the time of day but I've heard a lot of praise about their server. However even if the server sucks that really isn't the fault of the OS now is it???
<< Since windows copies profiles down from the server - instead of just reading the data from the server - it is prone to multiple problems. Example: someone logs in while the servers are down and it tells them it is using their local profile, since their profile is no longer on the network - several things break. Shortcuts get remapped if the client tries to run a network app, Netscape will create a new profile on the local machine since it cannot reach the network, people will get frustrated and log out. Now the earlier things were to be expected, here is the suprise, when they log back in windows will ask THEM which profile they want because the one on the local machine will be newer. The default choice is to use the local one. Most people choose the default even after being advised not to, once they have chosen the default it will continue using all the changes it made when the network wasn't down and when they log out it will save those changes to the network. Even worse is when a profile becomes to big - Windows won't wait to save the profile it will just log out with it half saved. >>
I haven't seen this, but I will have to admit that the server has never crashed during the time anyone is using it, and if I've had it down it wasn't during working hours. So I really can't elaborate on this.