Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site oracle.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!petsd!pesnta!hplabs!oracle!bradbury From: bradbury@oracle.UUCP (Robert Bradbury) Newsgroups: net.unix Subject: Questions about running Ultrix (Unix) on uVaxII Message-ID: <130@oracle.UUCP> Date: Fri, 25-Oct-85 02:29:35 EDT Article-I.D.: oracle.130 Posted: Fri Oct 25 02:29:35 1985 Date-Received: Sat, 26-Oct-85 19:41:54 EDT Organization: ORACLE Corporation, 2710 Sand Hill Rd., Menlo Park, CA 94025 Lines: 27 Keywords: Ultrix, Vax, memory In the September 23 issue of Electronics there is a discussion of why Ultrix will not run on the uVaxII. Apparently there is a problem with the memory chips that writing into memory chips which have not been written into for 45 to 60 seconds causes the bits in the column adjacent to the one being written to change. The article fingered the NEC memory chips although DEC Corporate support would not confirm this. DEC did indicate that the problem would be fixed with a component swap. We have only been on the network for a short time, so pardon the questions if they were hashed over in September. 1) Will anyone who knows (presumably at DEC) confirm or deny the article? 2) If the NEC chips are bad, whose chips are they replacing them with? 3) Why does the problem not bother VMS on the uVaxII? (Hypothesis: is the VMS page handler so aggressive that pages get swapped out if they are not accessed for 30 seconds?) The article indicated that DEC had over 30 engineers working on the problem at one point, if so why aren't they willing to tell customers what the exact problem was? At least it would keep the negative comments about Ultrix on the uVaxII from floating around on the net. -- Robert Bradbury Oracle Corporation (206) 364-1442 {ihnp4!muuxl,hplabs}!oracle!bradbury