>> ...Plus the netware server can run 2 to 3 years (or more) with out needing to reboot. We would have gone longer but we downed the servers to upgrade them to new versions. Part of this success is due to a crack team of CNEs that we have here.
>
>I added emphasis to what I believe to be the key to success -- competent people in all areas. The problem I see is hardware people, MSCEs, CNE, etc., do not necessarily have to know anything about application development or software. Unfortunately, developers must have knowledge in both to be successful, at least with respect to defending themselves when hardware providers and system administrators are too quick to blame the software. For some reason, with a multi-user application, end-users will believe a bogus story from a hardware person even if the problem can only be duplicated on 1 machine but not on someone elses running the same app and following the same steps.
>
>Just venting because this happened to me again today. I got a 2-page fax from a customer blaming me for a Windows fatal exception error [NOT a C...5 error] along with an Unable to write to disk in drive C error. It took me 10 minutes to convince them this was hardware and to call me back if this same problem occured on a different machine. Funny thing, it is going on 3 hours now since I talked to them about this and not a word I have heard from them. But then again we are just slacker developers according to another thread here and are clueless about hardware and OSs.

I have definitely been in that boat too. :-|

P.S. When I compare Netware and NT server, I like to think back to a MS tech presentation that boasted that an NT 5 Server had been running for 90 days straight. (sheesh!)