Comments inline... > -----Original Message----- > From: DMelczer@xxxxxxxx [mailto:DMelczer@xxxxxxxx] > Sent: 12 June 2003 16:08 > To: thin@xxxxxxxxxxxxx > Subject: [THIN] Re: Rebooting Win2k Terminal servers > > I don't think any of this is a "botched assertion" as you > say...yes MS can do some things better. Their ring structure > for the NT4 kernel was terrible... There was a compromise, there, for the graphics subsystem, true enough - but outside of that, I hardly think there's reason to question or doubt the stability or integrity of the OS for dealing with privileged / non-privileged stuff. > Again, my point was simply that it isn't a Microsoft problem > OR a vendor problem. Rather, that it's BOTH simultaneously. I simply think it's rather unfair to tarnish one, based on the fault possibly being elsewhere. Sure, as an administrator, as a user, you can gel them altogether - but that doesn't truly help in being accurate, or identifying where the problem truly lies. > Those who have experienced more problems tend to become a > little more jaded than the rest of us. I still don't mind > using MS products, even with their security risks and > occasional stability issues. They're better than anything > else out there right now (again, in my opinion only). > Someone who's vendor won't cooperate and whose software > causes their NT4 Server to crash 5 times a day might disagree > with me. Again, que sera sera. Blame MS for not gracefully > trapping the errant code, How, exactly, is the OS *supposed* to trap stuff, if it's going to be privileged and run in kernel rings? > or blame the vendor for the errant > code. 6 of one, half-dozen of the other. No it's not, that's merely zoned-out, undetailed analysis. > And, just for the record, I'd also throw hardware vendors > into the mix as well. Sometimes (and I had this happen just > recently with a vendor who will remain nameless -- check the > archives on TheThin.net if you're interested) a poorly coded > SCSI array bios crashes the box as well, even though the > vendor swears there is nothing wrong with their code. > Upgrade the BIOS and the problem goes away...hmmm...again, > another stability issue not OS related that could be avoided. Yebbut - people who simply want to blame corporation X, already have ammunition ;-) As I said - there's nothing new under the sun. Application and hardware vendors have been crashing OSs since before Microsoft became prevalent - but it's only this thread, where people seem to be sitting in judgement of *one* vendor. And besides all that, it's rather redundant. Without the problems to solve, most of the list would probably be out of work ;-) Be careful what you wish for... Neil *********************************************************************** This e-mail and its attachments are confidential and are intended for the above named recipient only. If this has come to you in error, please notify the sender immediately and delete this email from your system. You must take no action based on this, nor must you copy or disclose it or any part of its contents to any person or organisation. Statements and opinions contained in this email may not necessarily represent those of Littlewoods. Please note that email communications may be monitored. The registered office of Littlewoods Limited and its subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB. Registered number of Littlewoods Limited is 262152 *********************************************************************** ******************************************************** This weeks sponsor - Emergent Online 99Point9.com Designed to facilitate efficient resolution of your technical server-based questions, issues and incidents, technical support is a few mouse-clicks away: you submit your incident-specific support requests via our online support helpdesk, our certified engineers resolve them while you monitor the progress, and your systems get back to 99.9% up-time in no time. http://www.99point9.com ********************************************************** Useful Thin Client Computing Links are available at: http://thethin.net/links.cfm For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thethin.net/citrixlist.cfm