Thoughts about a Classiccmp private newsgroup

[Reliability of Windows NT] I get to play with NT now, as a part of work... IT STINKS! I forget who here worked at microsoft, but whomever, PLEASE tell R&D to find a way to make it require reboots less! Every time I make some minor change, I have to reboot the server. Thank God it's not production yet! If this was our dial-in server or something else important, I'd be toast by now. I call NT One-Eyed-Monster. The story: Customer calls, "I just built a 95 *monster* computer! I bet I can beat a server!" Me: "What've you got?" Customer: "Pentium II!" Me: "You lose. We have an Alpha. How's it run?" Cust: "Normal no-eyed-monster." Me: ?? Cust: "Walks into a wall too often"... I've come to the conclusion that NT has one eye, it knows where it's headed, but it still walks into a wall too often... [And to make it relevant...] Once the NCR SCSI driver for NetBSD is finished, (It's currently PIO-Only) I have a MicroVAX 3100 running NetBSD. Will that do as a server? It's up as long as I keep it up (24-7-365?) at the fast end of a T-1... -------