I've seen XP crash a lot, but then I am a pro developer and I'm doing things that occasionally run amok - for instance, I crashed this machine here at work by running recursive Perl scripts over a file-system. It crashed the entire machine. That was only a couple of days back. A decent OS would have allowed me to recover, and actually to be fair to XP normally it'd have done so, but on this occasion the machine basically stopped responding entirely.
I've also found random crashes on all manner of PC apps, from Office to VS.NET to third party stuff like Photoshop. All on well-maintained machines (my company has almost 150,000 staff and an IT budget in > £1bn/year, so can't afford to and won't cut corners (i.e. everything is well supported and maintained), but is sadly locked into NT4 except for us priviledged dev lot who get XP. Comparing XP to NT4 makes one realise just how far Windows has come, but it's still a long way short of the stability of my OS of choice, OSX.)
On the other hand, I've personally found W2K/AS to be rock solid reliable, and haven't had a crash* in four years of 24/7 use for my own projects.
John
* that was attributable to a Windows problem as opposed to something I personally did, e.g. threading issues.
I've also found random crashes on all manner of PC apps, from Office to VS.NET to third party stuff like Photoshop. All on well-maintained machines (my company has almost 150,000 staff and an IT budget in > £1bn/year, so can't afford to and won't cut corners (i.e. everything is well supported and maintained), but is sadly locked into NT4 except for us priviledged dev lot who get XP. Comparing XP to NT4 makes one realise just how far Windows has come, but it's still a long way short of the stability of my OS of choice, OSX.)
On the other hand, I've personally found W2K/AS to be rock solid reliable, and haven't had a crash* in four years of 24/7 use for my own projects.
John
* that was attributable to a Windows problem as opposed to something I personally did, e.g. threading issues.