1 INFO-VAX	Sat, 15 Oct 2005	Volume 2005 : Issue 576       Contents: Re: Alpha last order date  Re: ES40 MODEL NUMBER F$GETSYI Re: File marked for deleteF Re: fork() (Was: Re: Will "COM for OpenVMS" be ported to Itanium ?) ?) HP marketing Re: HP marketing JAVA for telephone handsets ? ! Re: JAVA for telephone handsets ? 1 Re: Newbie trying to get foreign commands working & OT: AMD 64-way SMP about to hit market* Problem getting to SRM from AlphaBIOS 5.70. Re: Problem getting to SRM from AlphaBIOS 5.70. Re: Problem getting to SRM from AlphaBIOS 5.70. Re: Problem getting to SRM from AlphaBIOS 5.70. Re: Problem getting to SRM from AlphaBIOS 5.70. Re: Problem getting to SRM from AlphaBIOS 5.70. Re: Problem getting to SRM from AlphaBIOS 5.704 Re: Red Hat trying to steal trucluster for linux ... Re: VMS support strategy?  Re: VMS support strategy?   F ----------------------------------------------------------------------  % Date: Sat, 15 Oct 2005 18:33:09 +1000 6 From: "O'Brien Paddy" <Paddy.O'Brien@transgrid.com.au>" Subject: Re: Alpha last order dateX Message-ID: <8BAD914A0B8CA84C9E94187103A1AB9E05BEC3@EX-TG2-PR.corporate.transgrid.local>  , This is a multi-part message in MIME format.  ' ------_=_NextPart_001_01C5D163.BA300AB4 . Content-Type: text/plain; charset="iso-8859-1"+ Content-Transfer-Encoding: quoted-printable          -----Original Message-----L From: Phillip Helbig---remove CLOTHES to reply [mailto:helbig@astro.multiCL= OTHESvax.de] Sent: Fri 10/14/2005 4:36 PM To: Info-VAX@Mvb.Saic.Com " Subject: Re: Alpha last order date =20 F In article <_bB3f.23947$U9.4632@fe3.news.blueyonder.co.uk>, Alan Greig" <greigaln@netscape.net> writes:=20  H > I've been under the impression it was end 2006 but I can't remember=20J > where I saw that. A last order date of Oct 27 probably implies a last=20E > ship around December 2006 (excepting some special cases I suppose).  >=20 > Six years previously...    > Just for information:  >=20 >   < % >    Last order dates for VAX systems  >=204 >    VAX 4000, MicroVAX 3100 - 88 and 3100-98 models >=20= >    VAX 4000, MicroVAX 3100-88, and MicroVAX 3100-98 systems 2 >    and all associated options are being retired.6 >    Limited supply will be supported on a first come, >    first serve basis.  >=20( >    Last order date: September 30, 2000 >=20& >    Last ship date: December 31, 2000  F Of course, 6 years ago, ALPHA had been out in the field for at least 6H years and had been recognised as the performance leader in its field forD essentially all of that time.  That's not the situation with ItaniumI now.  IIRC, VAXes were sold until they ran out of chips; perhaps there=20 " are no ALPHA chips sitting around.     *****   L Hmm, since I'm paying for maintenance, I would expect there to be chips aro=L und whilst I have an Alpha.  We're not big consumers, but I have a DS10 for=(  development and an ES40 for production.   Regards, Paddy    G *********************************************************************** ; Please consider the environment before printing this email.   C "This electronic message and any attachments may contain privileged @ and confidential information intended only for the use of the=20D addressees named above.  If you are not the intended recipient of=20C this email, please delete the message and any attachment and advise D the sender.  You are hereby notified that any use, dissemination,=207 distribution, reproduction of this email is prohibited.   C If you have received the email in error, please notify TransGrid=20 C immediately.  Any views expressed in this email are those of the=20 ? individual sender except where the sender expressly and with=20 C authority states them to be the views of TransGrid.  TransGrid uses > virus-scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************     ' ------_=_NextPart_001_01C5D163.BA300AB4 - Content-Type: text/html; charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">  <HTML> <HEAD>L <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-= 1"> K <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7226.0"> ( <TITLE>Re: Alpha last order date</TITLE> </HEAD>  <BODY>) <!-- Converted from text/plain format -->  <BR> <BR> <BR>  0 <P><FONT SIZE=3D2>-----Original Message-----<BR>L From: Phillip Helbig---remove CLOTHES to reply [<A HREF=3D"mailto:helbig@as=G tro.multiCLOTHESvax.de">mailto:helbig@astro.multiCLOTHESvax.de</A>]<BR>   Sent: Fri 10/14/2005 4:36 PM<BR> To: Info-VAX@Mvb.Saic.Com<BR> & Subject: Re: Alpha last order date<BR> <BR>L In article &lt;_bB3f.23947$U9.4632@fe3.news.blueyonder.co.uk&gt;, Alan Grei= g<BR> ) &lt;greigaln@netscape.net&gt; writes:<BR>  <BR>L &gt; I've been under the impression it was end 2006 but I can't remember<BR>L &gt; where I saw that. A last order date of Oct 27 probably implies a last<= BR> L &gt; ship around December 2006 (excepting some special cases I suppose).<BR> &gt;<BR>  &gt; Six years previously...<BR> <BR> &gt; Just for information:<BR> &gt;<BR> &gt;&nbsp;&nbsp; &lt;<BR> ; &gt;&nbsp;&nbsp;&nbsp; Last order dates for VAX systems<BR>  &gt;<BR>J &gt;&nbsp;&nbsp;&nbsp; VAX 4000, MicroVAX 3100 - 88 and 3100-98 models<BR> &gt;<BR>L &gt;&nbsp;&nbsp;&nbsp; VAX 4000, MicroVAX 3100-88, and MicroVAX 3100-98 sys= tems<BR>H &gt;&nbsp;&nbsp;&nbsp; and all associated options are being retired.<BR>L &gt;&nbsp;&nbsp;&nbsp; Limited supply will be supported on a first come,<BR>- &gt;&nbsp;&nbsp;&nbsp; first serve basis.<BR>  &gt;<BR>> &gt;&nbsp;&nbsp;&nbsp; Last order date: September 30, 2000<BR> &gt;<BR>< &gt;&nbsp;&nbsp;&nbsp; Last ship date: December 31, 2000<BR> <BR>J Of course, 6 years ago, ALPHA had been out in the field for at least 6<BR>L years and had been recognised as the performance leader in its field for<BR>L essentially all of that time.&nbsp; That's not the situation with Itanium<B= R>L now.&nbsp; IIRC, VAXes were sold until they ran out of chips; perhaps there= <BR>& are no ALPHA chips sitting around.<BR> <BR> <BR>	 *****<BR>  <BR>L Hmm, since I'm paying for maintenance, I would expect there to be chips aro=L und whilst I have an Alpha.&nbsp; We're not big consumers, but I have a DS1=1 0 for development and an ES40 for production.<BR>  <BR> Regards, Paddy<BR> </FONT>  </P>   <FONT SIZE=3D3><BR>  <BR>K ***********************************************************************<BR> ? Please consider the environment before printing this email.<BR>  <BR>G "This electronic message and any attachments may contain privileged<BR> B and confidential information intended only for the use of the <BR>F addressees named above.  If you are not the intended recipient of <BR>G this email, please delete the message and any attachment and advise<BR> F the sender.  You are hereby notified that any use, dissemination, <BR>; distribution, reproduction of this email is prohibited.<BR>  <BR>E If you have received the email in error, please notify TransGrid <BR> E immediately.  Any views expressed in this email are those of the <BR> A individual sender except where the sender expressly and with <BR> G authority states them to be the views of TransGrid.  TransGrid uses<BR> B virus-scanning software but excludes any liability for viruses<BR>  contained in any attachment.<BR> <BR>@ Please note the email address for TransGrid personnel is now<BR>( firstname.lastname@transgrid.com.au"<BR> <BR>K ***********************************************************************<BR>  </FONT>  </BODY>  </HTML> ) ------_=_NextPart_001_01C5D163.BA300AB4--    ------------------------------    Date: 15 Oct 2005 00:09:01 -0700/ From: "Volker Halle" <volker_halle@hotmail.com> ' Subject: Re: ES40 MODEL NUMBER F$GETSYI C Message-ID: <1129360141.689863.100950@g43g2000cwa.googlegroups.com>    John,   " have a look into the STARLET file:  % $ SEARCH SYS$LIBRARY:STARLET.REQ ES40   D and you'll find the HW_MODEL definitions for all known and supported variants of all systems.   Volker.    ------------------------------  % Date: Sat, 15 Oct 2005 12:51:49 +0200 & From: Paul Sture <paul.sture@decus.ch># Subject: Re: File marked for delete + Message-ID: <3rc5a6Fib3s7U1@individual.net>    Alan Greig wrote:  >  >  > Paul Sture wrote:  >  >>E >> Do the startup files use MOUNT/NOREBUILD for this disk, perchance?  >  > - > Nope, the mount during boot does a rebuild.  >  >>  From your initial post:  >>. >>  >Versions of VMS are VAX 6.2, Alpha 7.2-1. >>F >> The versions sound a bit far apart to me. ISTR quite a few ECOs in ; >> this period relating to F11BXQP.EXE  and related images.  >  > F > Yes, I suspect the mix is not formally supported. A monitor cluster H > doesn't work properly for example. I seem to recall there was a patch E > for VAX VMS 6.2 that fixed the mon/clus problem and probably other  1 > things too, but no patches have been installed.  > E Hmm. The VAX V6.2 ECOs are online at ftp.itrc.hp.com/vax/v6.2 if you   want to peruse them.  4 I might be safer to let sleeping dogs lie though :-)   ------------------------------  % Date: Sat, 15 Oct 2005 09:43:56 -0400 * From: "FredK" <fred.nospam@nospam.dec.com>O Subject: Re: fork() (Was: Re: Will "COM for OpenVMS" be ported to Itanium ?) ?) * Message-ID: <4351079b@usenet01.boi.hp.com>  9 "JF Mezei" <jfmezei.spamnot@teksavvy.cm> wrote in message % news:43504F72.811B193F@teksavvy.cm...  > FredK wrote:K > > write1, write2, MB, read1 will never return from read1 until write1 and 
 > > write2L > > are visible to a second CPU, and committed to on a device bus (and reads > > will > > not pass writes -  >  > I > How is this implememted ? Does the CPU clock simply stop until a signal H > is received from the memory subsystem to indicate that all writes have > been completed ? > F > Or does the MB instruction just consume a fixed number of CPU cyclesG > that gives the memory system time to complete all write operations in 
 > its queue ?  > D > I take it those instructions really throw a monkey wrench into CPU > performance optimisations ?    Time is warped.   L I'm not a CPU designer, but I'm pretty sure the "clock" isn't stopped.  WhenE you do a memory read, there is *always* some amount of time needed to L get it to the CPU - it is not instantanious - it might be coming from cache,I or memory, or from memory on the other side of a crossbar.  The delay for L a memory read that needs an MB to complete is just... longer - but I imagine# pretty much the same type of logic.   J Yes, MB can be a performance killer.  It is very, very bad on EV4 and EV5.E It's not so bad on EV6 and EV7 where they had by then learned lots of  tricks.    ------------------------------  % Date: Sat, 15 Oct 2005 04:53:43 -0400 ' From: Dave Froble <davef@tsoft-inc.com>  Subject: HP marketing 0 Message-ID: <11l1gh256lac3cd@corp.supernews.com>  G Was visiting that favorite rumor rag, The Inquirer, and ran across the  
 following:  ) http://www.theinquirer.net/?article=26899   I It's too big to post the whole article here, but the short of it is, the  I writer is complaining about HP's marketing of gaming systems.  Seems the  ? AMD systems trounce the Intel systems in just about all gaming  I benchmarks, but on the HP web site, the Intel systems seem to get pushed  : much harder.  Enough so that the writer thinks that HP is  mis-representing it's products.   I While reading the article, two things occured to me.  VMS isn't the only  H HP product that seems to get the short end of the stick, and, there may E be people in HP marketing that push what they like, not what is best.   H Read the article if you want to get all frothy at the mouth again about 
 HP marketing.    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Sat, 15 Oct 2005 07:44:37 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: HP marketing , Message-ID: <4350EB79.9F8FA4E6@teksavvy.com>   Dave Froble wrote:+ > http://www.theinquirer.net/?article=26899  > / > It's too big to post the whole article here,      H And has HTML errors that cause netscape to miss out on all the text. Had( to save the source to read what i could.    @ > writer is complaining about HP's marketing of gaming systems.   E Anyone who has read the AMD legal suit against Intel would understand G exactly why HP is pushing intel machines and is just reluctant to admit  it also has some AMD systems.   F The AMD systems are a bit like VMS: there are there if you ask for it,D but HP won't be pushing them because it has obligations to Intel andD microsoft shareholders to increase profitability of thsoe companies.  G However, when you look at HP's global 8086 advertising budgets, whethet F Intel or AMD, they are huge. And this is one of the reasons VMS really? needs to be ported to the 8086. On the 8086, it can ride the HP F advertising wave. And it can scale from laptop to data centre, whetherG on AMD or Intel chip, whichever HP decideds it is allowed to market. HP D will either market Intel's 8086 only (because it needs to help IntelG shareholders), or market both Intel and AMD (once it has fullfilled its F obligatiosn towards Intel shareholders, it can then spend extyra money on AMD marketing).  F Remember that Intel heavily contributes to 8086 advertising. So again,C with VMS on the 8086, VMS would benefit from direct Intel marketing F money. It would be a LOT harder for HP to ignore VMS in its marketing.    E If there is no covert secret porting of VMS to the 8086 operated as a G "special project" in ZKO's basement lead by someone who had managed the C port from Alpha to that IA64 thing, my hope is  that some engineers D might take it upon themselves to port just enough of VMS to the 8086H during their spare time  to show management that it is feasable and helpC them make the pitch to HP that it is worth porting VMS to the 8086.    ------------------------------  % Date: Sat, 15 Oct 2005 01:48:18 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> & Subject: JAVA for telephone handsets ?, Message-ID: <4350980B.DDF90201@teksavvy.com>  B Is it possible to write java programs that can be pre-compiled (orG whatever the term is) on an Alpha and then have the jar file moved to a  handset and run on it ?   G Or is the Java "compiler" on Alpha generate very specifalised JAVA code   that can only run on VMS/Alpha ?  F Has anyone succesfully written JAVA code on ALPHA and then executed it on a handset ?  G (I realise that Handset manufacturers provide proprietary windows based C application development environments, but I assume that the handset ( still support basic JAVA functionality).   ------------------------------  % Date: Sat, 15 Oct 2005 08:55:00 +0200 6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>* Subject: Re: JAVA for telephone handsets ?< Message-ID: <4350a7c3$0$99991$edfadb0f@dread16.news.tele.dk>   JF Mezei wrote: D > Is it possible to write java programs that can be pre-compiled (orI > whatever the term is) on an Alpha and then have the jar file moved to a  > handset and run on it ?  > I > Or is the Java "compiler" on Alpha generate very specifalised JAVA code " > that can only run on VMS/Alpha ? > H > Has anyone succesfully written JAVA code on ALPHA and then executed it > on a handset ? > I > (I realise that Handset manufacturers provide proprietary windows based E > application development environments, but I assume that the handset * > still support basic JAVA functionality).  0 The Java compiler on VMS is a real Java compiler2 meaning that it generates standard Java byte code.  1 Standard Java byte code is portable. I frequently 0 upload jar files from my Windows PC and run them on my VMS system.   7 If the handset is JSE (Java Standard Edition) compliant  then it will just work.   0 But there are a JME (Java Micro Edition) version2 in two flavours CLDC (for devices with very little/ memeory) and CDC for devices with more memory).   - My guess is that JME tools will be written in 4 portable JSE and therefor in theory run fine on VMS,1 but that you would have to collect things and get  it to work yourself.  . Start on http://java.sun.com/j2me/index.jsp if
 it is JME.   Arne   ------------------------------  % Date: Sat, 15 Oct 2005 11:19:58 -0600 + From: Mark Berryman <mark@theberrymans.com> : Subject: Re: Newbie trying to get foreign commands working% Message-ID: <4350d7cf$1@mvb.saic.com>    Mark Round wrote: I > On a related note, is this normal procedure for a large site ? Say, for C > instance, I have downloaded a large number of 3rd party tools and G > binaries and plonked them in a shared "utils" directory. Would I have E > to set up foreign commands for each and every one ? How do you guys  > handle this on your sites ?   . I'm surprised no one has mentioned this yet...    E In later versions of VMS (and you said you were running V7.3-1 which  H counts as a later version) there is a much easier way than defining all  of those symbols.   0 Create a directory that has World RE protection.E Place your utilities such as tar, zip, unzip, etc. in this directory. < Define the logical name DCL$PATH to point to this directory.  D If you want the utilities to work only for you, define the DCL$PATH : logical name only for your process (usually in Login.com).  G If you want the utilities available for all users, define the DCL$PATH  ! logical name in the system table.   	 Examples:   < $ CREATE/DIR/OWN=SYSTEM/PROT=WO:RE DISK$FREEWARE:[UTILITIES]2 $ DEFINE/SYSTEM DCL$PATH DISK$FREEWARE:[UTILITIES] $ COPY -C _$ ZIP.EXE,UNZIP.EXE,TAR.EXE,GZIP.EXE,GUNZIP.EXE,DFU.EXE,PERL.EXE -  _$ DCL$PATH:*.*;/PROT=WO:RE   F (Obviously this is just an example.  The disk name and directory name I can be whatever you choose and the executable images you choose to place  ( in that directory will probably differ).  F At this point, VMS first checks the VMS way of doing things.  If that < fails, it follows the DOS/UNIX way of doing things.  To wit:   User types a command:   B $ tar -tf file.tar  !This user has SET PROC/PARSE=EXTENDED enabled  6 VMS checks to see if TAR is a DCL command.  It is not.E VMS checks to see if TAR is defined as a foreign command.  It is not. G If the logical name DCL$PATH is defined VMS searches the directory (or  D directories) pointed to by that logical for a file named TAR.COM or A TAR.EXE (the case of the filename doesn't matter unless you have  I explicitly enabled that feature on the disk where these files reside and  G a .COM file will be found before a .EXE file if both are present).  If  H the file is found, it is executed the same as if it had been referenced  in a foreign command.   G This way, you simply place your utilities in the appropriate directory  C and you don't have to worry about defining symbols to execute them.   
 Mark Berryman    ------------------------------  # Date: Sat, 15 Oct 2005 12:03:24 GMT ( From: Alan Greig <greigaln@netscape.net>/ Subject: OT: AMD 64-way SMP about to hit market = Message-ID: <ge64f.28104$ey6.19425@fe1.news.blueyonder.co.uk>   ) http://www.theinquirer.net/?article=26948   
 Say's that --- ! "AMD Horus to arrive very shortly   . Next generation will scale into big iron space  0 By Klaus Fehrle: Saturday 15 October 2005, 08:40  H IN A chatter over a cup of coffee this morning, Phil Hester, AMDs newly B assigned Chief Technology Officer, spilled some beans about Horus.  B That's the concept he and Rich Oehler inititated and developed at 6 Newisys before they both joined AMD earlier this year.  H In brief, Horus is alive, it works and will hit the market very shortly B in its current version which scales AMD64 to 32 sockets (64cores).  C This will not be the end of Horus development, Phil said: Its next  G version is planned to scale way beyond this. However this version will  6 depend on support of upcoming generations of AMD64. " ---   I I am guessing that Microsoft have been using Horus internally to certify  H   recent beta releases (Windows Server 2003 R2 and SQL Server 2005) for F 64 way  SMP on X86-64 as prototype Horus systems have been around for I some time. I doubt even Microsoft would certify software releases for 64  E way SMP without actually testing such a configuration. They may also  I have a 64 way IBM X3 chipset Intel dual core Xeon system in the test mix  . as well as I doubt that can be far off market.  I It becomes even clearer now why Microsoft are downplaying future Itanium  F support. They know how well the X64 scales and they don't need Itanic 	 any more.      --  
 Alan Greig   ------------------------------    Date: 15 Oct 2005 08:47:49 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) 3 Subject: Problem getting to SRM from AlphaBIOS 5.70 3 Message-ID: <pw6fsAG7$PHY@eisner.encompasserve.org>   ; I got a call from an employee of a former consulting client > whose home PWS500-AU was the victim of a power failure and now= is coming up into AlphaBIOS instead of SRM.  Does anyone have = any hints on how to get it back into SRM mode ?  I don't have  that model of machine.   AlphaBIOS 5.70 July 20, 1999   ------------------------------  # Date: Sat, 15 Oct 2005 14:32:53 GMT ( From: Alan Greig <greigaln@netscape.net>7 Subject: Re: Problem getting to SRM from AlphaBIOS 5.70 = Message-ID: <pq84f.28850$ey6.20670@fe1.news.blueyonder.co.uk>    Larry Kilgallen wrote:  = > I got a call from an employee of a former consulting client @ > whose home PWS500-AU was the victim of a power failure and now? > is coming up into AlphaBIOS instead of SRM.  Does anyone have ? > any hints on how to get it back into SRM mode ?  I don't have  > that model of machine.  E I think it's a setting in the BIOS itself. Something like a "Boot to  H SRM" setting which should be fairly obvious if you run through the BIOS < options. Change the option, save the BIOS update and reboot.   > AlphaBIOS 5.70 July 20, 1999   --  
 Alan Greig   ------------------------------  # Date: Sat, 15 Oct 2005 14:43:54 GMT ( From: Alan Greig <greigaln@netscape.net>7 Subject: Re: Problem getting to SRM from AlphaBIOS 5.70 + Message-ID: <435115AC.1000803@netscape.net>    Larry Kilgallen wrote:  = > I got a call from an employee of a former consulting client @ > whose home PWS500-AU was the victim of a power failure and now? > is coming up into AlphaBIOS instead of SRM.  Does anyone have ? > any hints on how to get it back into SRM mode ?  I don't have  > that model of machine.  F Further to my first response based on my dodgy memory a google groups ( search back suggests it is this sequence  E "CMOS Setup,followed by an Advanced (setting), followed by a Console  	 Selection  to Digital Unix (SRM) console."      from: ) From: j...@sophia.inria.fr (Janet Bertot) < Subject: Console Selection (SRM) lost after PWS500 power off Date: 1999/03/240 Message-ID: <7dat58$cga$1@news-sop.inria.fr>#1/1 X-Deja-AN: 458398300 Content-Transfer-Encoding: 8bit * Organization: INRIA, Sophia-Antipolis (Fr), Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0  Newsgroups: comp.sys.dec  : While trying to add some memory to a PWS500au, our machine: found itself with the factory defaults.  The AlphaBios who: tells you it can't find an OS and so you've but one choice "F2 for setup".   = We go in and after a certain combination of arrow keys, tabs, ; enters, F6, F10, and ESCs ... basically we do a CMOS Setup, B followed by an Advanced (setting), followed by a Console Selection= to Digital Unix (SRM) console.  You save the stuff and slowly = resurface.  A "reset" of the machine and you see the familiar : console for unix/vms (ea.e9.e8... >>>).  In fact using the; reset button things look great.   But using the power cycle 9 button and you find yourself back in AlphaBios with no OS 	 found ...          > AlphaBIOS 5.70 July 20, 1999   --  
 Alan Greig   ------------------------------  % Date: Sat, 15 Oct 2005 17:02:04 +0200 & From: Paul Sture <paul.sture@decus.ch>7 Subject: Re: Problem getting to SRM from AlphaBIOS 5.70 + Message-ID: <3rcjvdFibhr8U1@individual.net>    Larry Kilgallen wrote:= > I got a call from an employee of a former consulting client @ > whose home PWS500-AU was the victim of a power failure and now? > is coming up into AlphaBIOS instead of SRM.  Does anyone have ? > any hints on how to get it back into SRM mode ?  I don't have  > that model of machine. >  > AlphaBIOS 5.70 July 20, 1999  E See the latest VMS FAQ, section 14.3.7.3. In AlphaBIOS a menu driven   system is used.   G Although I don't recall this being necessary, note the key translation  0 table on pages 14-20/21 if using an LK keyboard.   ------------------------------    Date: 15 Oct 2005 07:50:28 -0700; From: "johnhreinhardt@yahoo.com" <johnhreinhardt@yahoo.com> 7 Subject: Re: Problem getting to SRM from AlphaBIOS 5.70 C Message-ID: <1129387828.176546.179910@z14g2000cwz.googlegroups.com>    Larry Kilgallen wrote:= > I got a call from an employee of a former consulting client @ > whose home PWS500-AU was the victim of a power failure and now? > is coming up into AlphaBIOS instead of SRM.  Does anyone have ? > any hints on how to get it back into SRM mode ?  I don't have  > that model of machine. >  > AlphaBIOS 5.70 July 20, 1999   Larry,  F   It should be about the same for any system with the AlphaBios.  This is what it is on my AS1200:   G 1) Either while booting or at the OS selection screen press F2 to enter " the AlphaBios configuration screen  E 2) Use the arrow keys to move the selection to "CMOS Setup" and press  the Return/Enter key.   F 3) On the "CMOS Setup" screen press F6 to go to the "Advanced" screen.  D 4) Use the Tab key to navigate to the "Console Selection" option andF then use the arrow keys to scroll through the choices.  There are 3 onD mine.  "OpenVMS Console (SRM)", "Unix Console (SRM)" and "Windows NT- Console (AlphaBios)".  Pick the one you want.   2 5) Press F10 to save your choice or Esc to cancel.  F 6) Press F10 again at the "CMOS Setup" screen and then presse Enter to, continue saving the setting or Esc to abort.  F 7)  Power cycle the machine to reboot.  Do NOT Alt-Ctl-Del or you will# just come back up in the AlphaBios.   C If your friend's system still has one of the SRM choices showing in 8 step 4 then there is some other problem.  Hopefully not.     John H. Reinhardt    ------------------------------    Date: 15 Oct 2005 11:58:23 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) 7 Subject: Re: Problem getting to SRM from AlphaBIOS 5.70 3 Message-ID: <A8OPvpEIHcHh@eisner.encompasserve.org>   V In article <dir41l$npv$02$1@news.t-online.com>, Bill Bennett <no.spam@plea.se> writes:  H > Here is a little checklist I made for myself once (for a group of PWS  > 433au machinesJ > running Tru64 UNIX; for some reason, the 433au tended to loose the CMOS  > backup3 > battery much more often than the 500au or 600au):   F Thanks to all who responded.  It turns out the in-house support personD is out of the country on vacation.  The affected individual was ableD to follow Bill's checklist (modulo OS choice) and is up and running.   ------------------------------  # Date: Sat, 15 Oct 2005 17:00:38 GMT A From: "Colin Butcher" <colin_DOT.butcher_AT@xdelta_DOT.co_DOT.uk> 7 Subject: Re: Problem getting to SRM from AlphaBIOS 5.70 > Message-ID: <WAa4f.129762$G8.49880@text.news.blueyonder.co.uk>  L Must be that time of year. Mine just did exactly the same - complained about0 the clock being invalid and cam up in AlphaBIOS.  B Most likely a dead CMOS battery. Get a new CR2032 lithium battery.  J Seup > CMOS setup > Advanced > Console > OpenVMS SRM console, then re-initJ (or power-cycle). Then reset all the CMOS settings you had. The clock will@ get set when you first boot VMS and it asks for the time & date.   See here for Miata docs:N http://h18002.www1.hp.com/alphaserver/workstations/retired/auseries/index.html   --     Hope this helps, Colin. ) colin DOT butcher AT xdelta DOT co DOT uk E It's not mine, but I like this definition: Legacy = stuff that works.    ------------------------------  % Date: Sat, 15 Oct 2005 04:41:17 -0400 ' From: Dave Froble <davef@tsoft-inc.com> = Subject: Re: Red Hat trying to steal trucluster for linux ... 0 Message-ID: <11l1fpm6drftl9a@corp.supernews.com>   bob@instantwhip.com wrote:. > but NO ONE will ever best vms clustering ... > it was designed for it ... >    Question for you boob.  D You talk about entry level systems.  Do you currently run a cluster?   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Sat, 15 Oct 2005 01:45:06 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> " Subject: Re: VMS support strategy?, Message-ID: <4350974B.40A6317D@teksavvy.com>   Pete wrote:  > D > Is there a forum to discuss support strategies for VMS?  Given theG > current concerns about HP's committment to supporting VMS I'd like to H > hear from other concerned netizens.  If there is a better forum please > feel free to inform.    H By support, do you mean getting telephone support, or do you mean activeJ development ? Or do mean active marketing ? Do you mean platform support ?  H HP has little credibility in its statements about VMS (the few that they@ make). The VMS management tries hard to make up for HP's lack ofF involvement in VMS, but in the end, they are not very powerfull within* HP and generally just do as they are told.   ------------------------------    Date: 15 Oct 2005 07:34:16 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) " Subject: Re: VMS support strategy?3 Message-ID: <RyPOQZitKZFm@eisner.encompasserve.org>   ` In article <43508885.3C09CB59@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes:
 > Pete wrote:  >>  E >> Is there a forum to discuss support strategies for VMS?  Given the H >> current concerns about HP's committment to supporting VMS I'd like toI >> hear from other concerned netizens.  If there is a better forum please  >> feel free to inform.  > 3 > Well, there's a lot of "discussion" of that here.  > H > Generally, the feeling is that VMS needs to be bought away from HP and  C No, _generally_ the feeling is that a bunch of loudmouths spend all C their time grousing about non-technical issues rather than creating  great software on VMS.   ------------------------------   End of INFO-VAX 2005.576 ************************                                                                                                                                                                                  <n7W}vʦe'lvA|+{7AK#.lÓϵb+	FCkfv	U9t~ .b&a(N!e ۦI)i6`򢾠,@#}Axz =S M89_04֍Fa|_ ]Ow-_ zW4mYv_Y|}I_mo 3gnq_:n5-Qo)cG-ﱫނgKٜSLw;wg9$$.96Zo~[A>:B@ԻF3ZLs9Q;^zUeso%BÍohqVx߃\!pGzuun]
{fjouy_5E#I]λkݚ=e[+ۘk{x{MXG{\ӹ)Tv-hS:6rԉ劳}$Ͼ D?1OJ`lX(⴯ŻT*^1TbAuuanSvmk0Wsû}w]]5qfxG}e.`x1nVX:(VQZ
j9tP/l܍\N}0Yo!Ne?Vh}E]kFSu+eGaKz~0cmr7>(0t_5x6l}M~]ET~/Hߣ<^ZCCIMe:C~Ũ:z!f('qub0&{q`}sCW})~|?(="uL[|J[#n}L֐x-*,o
jkViQO#biyq.yؕ8
yf`Yaa@	*BB2_=ֻ;3xjKnvڭudK

mBj#nݤb~ZM%8@׫uq:.d?fA_0o^U9nT,-7{߱U6q%}蟜f]U䟞a6_;cgfQ(/P9
wP5oo~g
4@"GZ5ŹwwEA:,z1nŵQ=YPq|zٵq~q\ncWBF)]f]Vh7Jߵ۱bp6	}hL|>,A9plF#b1xƧ4wEI蠸r)XT{%ϨN̘w~}媟
?;*__q]y]hvŋ|`sOq8Y]9<syޣ<N8,bN)h}a#v̊r߸}W2