From: CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 19-JUN-1989 14:53 To: MRGATE::"ARISIA::EVERHART" Subj: Installing VMS on VS3100s Message-Id: <8906191848.AA12507@crdgw1.ge.com> Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Mon, 19 JUN 89 10:46:16 PDT Received: from stc10.ctd.ornl.gov by KL.SRI.COM with TCP; Mon, 19 Jun 89 10:24:36 PDT Date: 19 Jun 89 13:13:00 EST From: "OCU::LPZ" Subject: Installing VMS on VS3100s To: "info-vax" Hi: I have installed VS3100s on two LAVCs now, and on both of them I encountered a problem. When you install VMS for the first time, Sys$Update:Lmf$Config.Com is run to configure the initial VMS license. It has a list of CPU types which excludes the VS3100. To fix it, change the following line by adding "/59": $type_4 = "/9/10/19/21/26/27/34/36/38/40/44/46/48/50/55/56/97/98/99/" --- $type_4 = "/9/10/19/21/26/27/34/36/38/40/44/46/48/50/55/56/59/97/98/99/" --- If you don't do this, you will have to install the VMS license before you add DECWindows, or you will not be able to log in without killing DECwindows first (which means you have to reboot). This is especially annoying when you add a VS3100 to an existing LAVC, and not too bad if you are installing VMS on the VS3100 itself. Lawrence ~ ----------------------------------------------------------------------------- ARPA: LPZ@STC10.CTD.ORNL.GOV LPZ%OCU.DECNET@STC10.CTD.ORNL.GOV MFE: MACINTYRE@ORN BITNET: LPZ@ORNLSTC Bell-South: 615.576.0824 US-Snail: Lawrence MacIntyre Martin Marietta Energy Systems Bldg 9103 MS 8214 P O Box 2009 Oak Ridge, TN 37831