Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site cmu-cs-wb1.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!rochester!cmu-cs-pt!cmu-cs-wb1!avie From: avie@cmu-cs-wb1.ARPA (Avadis Tevanian) Newsgroups: net.unix-wizards Subject: Re: what's wrong with microVax II? Message-ID: <234@cmu-cs-wb1.ARPA> Date: Thu, 22-Aug-85 23:28:55 EDT Article-I.D.: cmu-cs-w.234 Posted: Thu Aug 22 23:28:55 1985 Date-Received: Sat, 24-Aug-85 19:43:20 EDT Organization: Carnegie-Mellon University, CS/RI Lines: 15 >According to Electronics, DEC has stopped shipping microVax IIs >with Ultrix because of an unspecified problem with the operating >system. Are there any of you out there who know what the problem >is? As far as I know (and I may be completely wrong), there is no problem with Ultrix. The problem is the hardware. It seems that DEC has experienced some memory problems. As it turns out, the "bad" addresses usually show up in the lower ranges... right where Unix lives. Apparently, VMS runs in high memory, so the problem only affects poor little user processes (a situation that they are willing to live with). Supposedly, a significant number of beta sites have reported this problem. Our MicroVax II hasn't had this problem, though. In fact, in several months use, I've seen only one crash caused by hardware (a machine check).