home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!ux1.cso.uiuc.edu!usenet.ucs.indiana.edu!master.cs.rose-hulman.edu!rosevc.rose-hulman.edu!mgrthh
- From: mgrthh@rosevc.rose-hulman.edu (Thomas H. Hopson)
- Newsgroups: comp.os.vms
- Subject: Re: Boot VAX3800 problem, help please!
- Date: 5 Jan 1993 18:37:44 GMT
- Organization: Rose-Hulman Institute of Technology
- Lines: 30
- Distribution: world
- Message-ID: <1ickhoINNn3k@master.cs.rose-hulman.edu>
- References: <1993Jan5.175824.4035@proton.llumc.edu>
- Reply-To: mgrthh@rosevc.rose-hulman.edu
- NNTP-Posting-Host: hydra.rose-hulman.edu
-
-
- In article <1993Jan5.175824.4035@proton.llumc.edu>, lin@primus.llumc.edu (P. James Lin) writes:
-
- >When I boot VAX3800 VMS5.3-1 which recovered for power supply failured,
- >message
- > Error opening primary input file SYS$INPUT
- > Error in device name or inappropriate device type for operation
- >
- >What is it? How Should I take care of it?
-
- Usually this means either:
- 1. the startup file is set incorrectly --
- - boot conversationally and do a SHOW/STARTUP to check
- and maybe a SET/STARTUP SYS$SYSTEM:STARTUP.COM to fix
- 2. or the SYSBOOT process could not read your VAXVMSSYS.PAR file
- - boot conversationally and do a SHOW NPAGEDYN to see if it
- has a value--to fix try USE DEFAULT and then AUTOGEN
- repeatedly
-
- As a last resort you might try SET/STARTUP OPA0: to get a DCL shell to fix
- the problem, though it is tricky at best to get things to work for you at
- such an early point in the startup.
-
- - Tom
-
- --
- Thomas H. Hopson work: mgrthh@rosevc.rose-hulman.edu
- VMS Manager / CS geek mgrthh@rhit
- Rose-Hulman Institute of Technology play: hopsonth@cs.rose-hulman.edu
- Terre Haute, Indiana
-