1 INFO-VAX	Sun, 09 Jul 2006	Volume 2006 : Issue 379       Contents:+ Re: DEC 2000 AXP fails system power up test + Re: DEC 2000 AXP fails system power up test + RE: DEC 2000 AXP fails system power up test + Re: DEC 2000 AXP fails system power up test  Re: Hoffman Labs' Re: setting uafalternate 1 doesnot work ' Re: setting uafalternate 1 doesnot work ' Re: setting uafalternate 1 doesnot work ' Re: setting uafalternate 1 doesnot work ' Re: setting uafalternate 1 doesnot work ' Re: setting uafalternate 1 doesnot work   F ----------------------------------------------------------------------   Date: 9 Jul 2006 06:36:30 -0700  From: dooleys@snowy.net.au4 Subject: Re: DEC 2000 AXP fails system power up testA Message-ID: <1152452190.002778.95710@75g2000cwc.googlegroups.com>   
 Tom wrote:L > I came into possesion of an Alpha system labeled as a DEC 2000 axp system.G > It had no video card so I stuck an old Paradise 8 bit VGA card in it, = > connected a PC keyboard to the PS2 port, and powered it up.  > K > I get a screen telling me it has ROM version 1.3 and SRM firmware version E > 309 followed by system power up tests. All componets, including the B > keyboard, pass except the NVR which fails with a "00 0004" code. > / > These tests are followed by a message saying: D > "Power-on self-test errors were detected. Continue NT boot (Y/N)?" > H > I thought this system had VMS on it but, whatever. The system does notI > appear to be able to read from the keyboard. When I press Y or N or any L > other key, I get no response. I get no response when I press the space barD > during the memory test, either, and I get the same results using aM > different KB. If I remove the keyboard all together, I get a message saying K > "Console on serial line port 1 active. Keyboard not detected." So, I know " > the system DETECTS the keyboard. > L > I'm not sure where to go from here. Does the NVR failure have something toL > do with the inability to read the KB? How do I recover from that? Any help > would be appreciated.  > . You should probably replace the battery first., These were one of the first alphas released,( they could run Windows NT, VMS, or Tru64' This model was also known as the jensen ) This page explains how they are different ( http://www.alphalinux.org/faq/FAQ-9.html) There is also a list of graphics cards at 4 http://moon.hanya-n.org/comp/alpha/hct/graphics.html& It looks like yours is set to boot NT,% your first objective is to hit ctrl-C   until you get the SRM prompt >>> Phil   ------------------------------  # Date: Sun, 09 Jul 2006 16:10:34 GMT # From: Tom Dockray <dockray@acm.org> 4 Subject: Re: DEC 2000 AXP fails system power up test+ Message-ID: <_T9sg.16750$LS6.7892@trnddc03>    dooleys@snowy.net.au wrote:    >  > Tom wrote: [snip]0 > You should probably replace the battery first.. > These were one of the first alphas released,* > they could run Windows NT, VMS, or Tru64) > This model was also known as the jensen + > This page explains how they are different * > http://www.alphalinux.org/faq/FAQ-9.html+ > There is also a list of graphics cards at 6 > http://moon.hanya-n.org/comp/alpha/hct/graphics.html( > It looks like yours is set to boot NT,' > your first objective is to hit ctrl-C " > until you get the SRM prompt >>> > Phil  G Thanks for the links. Unfortunately, I get no response to ctrl-C or any  other KB input.    ------------------------------  # Date: Sun, 09 Jul 2006 16:13:27 GMT # From: Tom Dockray <dockray@acm.org> 4 Subject: RE: DEC 2000 AXP fails system power up test* Message-ID: <HW9sg.16752$LS6.605@trnddc03>   Main, Kerry wrote:   >> -----Original Message----- C >> From: Alan Adams [mailto:alan.adams@orchard-way.freeserve.co.uk]  >> Sent: July 8, 2006 3:31 PM  >> To: Info-VAX@Mvb.Saic.Com7 >> Subject: Re: DEC 2000 AXP fails system power up test  >>  , >> In message <KGQrg.2895$bd4.1039@trnddc01>) >>           Tom <tfd@verizon.net> wrote:  >>   [snip] > 6 > Check that the following console parameters are set: >  >>>> set console serial 0 >>>> set server on (if off, assumes workstation)  K Thanks for the reply. If I ever get ever get to the point where I can enter  a command, I'll check that out.    ------------------------------  # Date: Sun, 09 Jul 2006 16:08:51 GMT # From: Tom Dockray <dockray@acm.org> 4 Subject: Re: DEC 2000 AXP fails system power up test, Message-ID: <nS9sg.16749$LS6.15744@trnddc03>   Alan Adams wrote:   + > In message <KGQrg.2895$bd4.1039@trnddc01> ( >           Tom <tfd@verizon.net> wrote: >  [snip] >>  0 >> These tests are followed by a message saying:E >> "Power-on self-test errors were detected. Continue NT boot (Y/N)?"  > @ > Could it be waiting for input from the serial consloe - i.e. a& > terminal connected to a serial port? >  >>   [snip] > @ > I think this means it is using a serial port because it hasn't= > detected the keyboard of the graphical console setup. Try a 
 > terminal...  >  [snip]  I Well, the only VT device I have is a VT420 with an MMJ cable. Anyone know ( where I can get an MMJ to DB9 converter?   ------------------------------  $ Date: Sun, 9 Jul 2006 08:18:07 -0400) From: "Neil Rieck" <n.rieck@sympatico.ca>  Subject: Re: Hoffman Labs ; Message-ID: <44b0f366$0$6113$9a6e19ea@news.newshosting.com>   ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:44B0503B.51B111ED@teksavvy.com...# > "johnhreinhardt@yahoo.com" wrote: : >> The whole site certainly has that "Hoff" feel about it. > L > But who is "kkh" the second entity listed in the "Lab Rats" after "Hoff" ?  8 Since the last initial is "H", probably a family member.  
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada." http://www3.sympatico.ca/n.rieck/    ------------------------------  % Date: Sun, 09 Jul 2006 09:25:25 +0200 3 From: Wilm Boerhout <w5OLD.boerhout@PAINTplanet.nl> 0 Subject: Re: setting uafalternate 1 doesnot work6 Message-ID: <44b0af66$0$13543$ba620dc5@nova.planet.nl>  " on 9-7-2006 4:31 JF Mezei wrote...  G > Another way to bypass authentication is to set the startup file to be H > OPA0: instead of SYS$SYSTEM:STARTUP.COM (this can be set from SYSBOOT I > (SET/STARTUP).  The system will then expect commands to be entered from A > OPA0:. The systems will be very barebones at that stage becayse G > STARTUP.COM will not have executed. But from there you have access to E > DCL and can fix things and manually invoke varous procedures to get + > enough of the system up to do your fixup.   F When doing this, use $SPAWN as your first command. The second command E may then be @SYS$SYSTEM:STARTUP.COM, which includes a $LOGOUT at the  B end. This will give you a somewhat "familiar" system, with system 9 logicals defined etc., whilst staying logged in on OPA0:.    /Wilm    ------------------------------   Date: 9 Jul 2006 08:15:34 -0700  From: tomarsin2015@comcast.net0 Subject: Re: setting uafalternate 1 doesnot workB Message-ID: <1152458133.943716.245490@75g2000cwc.googlegroups.com>   Wilm Boerhout wrote:$ > on 9-7-2006 4:31 JF Mezei wrote... > I > > Another way to bypass authentication is to set the startup file to be I > > OPA0: instead of SYS$SYSTEM:STARTUP.COM (this can be set from SYSBOOT K > > (SET/STARTUP).  The system will then expect commands to be entered from C > > OPA0:. The systems will be very barebones at that stage becayse I > > STARTUP.COM will not have executed. But from there you have access to G > > DCL and can fix things and manually invoke varous procedures to get - > > enough of the system up to do your fixup.  > G > When doing this, use $SPAWN as your first command. The second command F > may then be @SYS$SYSTEM:STARTUP.COM, which includes a $LOGOUT at theC > end. This will give you a somewhat "familiar" system, with system ; > logicals defined etc., whilst staying logged in on OPA0:.  >  > /Wilm A Thanks for the help but when ever I put startup "opa0"  I get the F parameter opa0 is invalid and the keyboard stops working. This is on a VAX 4000-200 with VMS 7.2 and a & RF73 drive if that makes a difference.   ------------------------------  $ Date: Sun, 9 Jul 2006 11:55:01 -0400) From: "Ken Robinson" <kenrbnsn@gmail.com> 0 Subject: Re: setting uafalternate 1 doesnot workH Message-ID: <7dd80f60607090855t2d01b6a9gff3cfbdb213234ce@mail.gmail.com>  6 On 9 Jul 2006 08:15:34 -0700, tomarsin2015@comcast.net! <tomarsin2015@comcast.net> wrote:  > C > Thanks for the help but when ever I put startup "opa0"  I get the H > parameter opa0 is invalid and the keyboard stops working. This is on aH > VAX 4000-200 with VMS 7.2 and a RF73 drive if that makes a difference.  C What is the exact comand you're typing and the exact error message? = SYSBOOT is very unforgiving, so all commands must be typed in 
 correctly.   Ken    ------------------------------   Date: 9 Jul 2006 09:02:38 -0700 / From: "Volker Halle" <volker_halle@hotmail.com> 0 Subject: Re: setting uafalternate 1 doesnot workC Message-ID: <1152460958.392856.272640@b28g2000cwb.googlegroups.com>   5 > boot -flags=0,1 (or whatever gets you into SYSBOOT)   
 Make this:   >>> B/1 device orH >>> B/n0000001 device - if you boot from a root other than SYS0 (n=root)  
 for your VAX.    Volker.    ------------------------------   Date: 9 Jul 2006 09:12:45 -0700  From: tomarsin2015@comcast.net0 Subject: Re: setting uafalternate 1 doesnot workC Message-ID: <1152461565.763606.216610@p79g2000cwp.googlegroups.com>    Volker Halle wrote: 7 > > boot -flags=0,1 (or whatever gets you into SYSBOOT)  >  > Make this: >  > >>> B/1 device > orJ > >>> B/n0000001 device - if you boot from a root other than SYS0 (n=root) >  > for your VAX.  > 	 > Volker. % Thanks for the help - I was typing in  sysboot>set startup "opa0"9 after typing in set/startup=opa0: it worked like a charm-  thanks for all the help.   ------------------------------  % Date: Sun, 09 Jul 2006 12:50:14 -0400 - From: bradhamilton <bradhamilton@comcast.net> 0 Subject: Re: setting uafalternate 1 doesnot work* Message-ID: <44B133C6.4050604@comcast.net>   tomarsin2015@comcast.net wrote:  [...] C > Thanks for the help but when ever I put startup "opa0"  I get the H > parameter opa0 is invalid and the keyboard stops working. This is on a! > VAX 4000-200 with VMS 7.2 and a ( > RF73 drive if that makes a difference.   Hi -   The full command is:   SET/STARTUP OPA0:    and the full command sequence:   SET/STARTUP OPA0:  SET WINDOW_SYSTEM 0  SET WRITESYSPARAMS 0 CONTINUE    can be found at the OpenVMS FAQ:  " <http://www.hp.com/go/openvms/faq>F (look for the section labeled "5.6  Emergency (Conversational) System 
 Startup?")J which contains a good discussion of the methods used to bypass the sysuaf.   ------------------------------   End of INFO-VAX 2006.379 ************************