|
I agree Walden, except for the: <"I know that there is 3rd party hardware (EMC jumps to mind) but unless I'm wrong these look and smell like IBM hardware at the interface level." > part :-) that is what they are SUPPOSED to do but don't always do that in reality (I speak from experience - MC on the 3rd party drives at conflict with the system...), so that just FURTHER illustrates what you say ;-) ! Chuck "Walden H. Leverich" wrote: > Chuck, > > I'd say that the OS and MI have a lot to do with it, but the reason IBM can > control these so well is that they control the hardware. If IBM had to > support hardware _designed_ by 3rd parties I think the OS and MI would be > less stable. I know that there is 3rd party hardware (EMC jumps to mind) but > unless I'm wrong these look and smell like IBM hardware at the interface > level. > > -Walden > > -----Original Message----- > From: Chuck Lewis [mailto:clewis@iquest.net] > Sent: Tuesday, August 01, 2000 7:19 AM > To: MIDRANGE-L@midrange.com > Subject: Re: Windows BSOD vs. AS/400 > > Walden H. Leverich wrote: > > --- Snip --- > > <while NT's main design constraint is stability, > > > And the reason FOR that stability is the CORE of NT is OS/2... > > <I've seen many NT/2000 machines on Compaq and Dell equipment that have > uptimes > of well over a year between reboots and then they are rebooted to install > software upgrades.> > > In my experience, Novell servers (running MORE than one app) are MUCH more > stable > than an NT Server (running one...). Don't have any experience with 2000, > yet... > But with Novell Servers, NT Servers and AS/400's sitting in the same room, > they > all had problems in a given time span. AS/400 was disk drive issues, Novell > was > hardware related and NT was software, drivers AND hardware in that order... > > <The 400 is a stable machine BECAUSE IBM controls the hardware. Period!> > > Come on Walden, there is a LITTLE more to it than that :-) don't you think ? > I am > NOT disagreeing that controlling everything hurts but the OS and MI are VERY > important too :-) ! > > Chuck > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.