26 Aug
2015
26 Aug
'15
11:25 a.m.
Just picked up a very complete MicroVAX 3800. I have very little experience
with VMS as this is my first VAX. Mostly a PDP-8 guy, I suppose.
I'm running through the change password procedure, which I had seen
mentioned previously on this list:
SET VAXCLUSTER 0
SET /STARTUP OPA0:
SET WRITESYSPARAMS 0
CONTINUE
SET NOON
SPAWN /NOWAIT SYS$SYSTEM:STARTUP.COM
SET DEFAULT SYS$SYSTEM
RUN AUTHORIZE
At this point, I get this:
%DCL-W-ACTIMAGE, error activating image SECURESHRP
-CLI-E-IMGNAME, image file
R7CY2A$DIA0:[SYS0.SYSCOMMON.][SYSLIB]SECURESHRP.EXE;2
-SYSTEM-F-PROTINSTALL, protected images must be installed
$
What would I need to do to correct it to login?
The eventual goal is to get this online, which should be feasible. I have
an AUI-to-10Base-T adapter (several, actually). I think that'll be a little
while away for now, though.
Here are some pictures: http://imgur.com/a/WYGra
Thanks,
Kyle
26 Aug
26 Aug
11:39 a.m.
Nice one! A big'un and fully loaded, too!
You tried this procedure? Always worked for me.
http://h71000.www7.hp.com/openvms/journal/v1/atw.pdf
Best,
Sean
On Wed, Aug 26, 2015 at 2:25 PM, Kyle Owen <kylevowen at gmail.com> wrote:
Just picked up a very complete MicroVAX 3800. I have
very little experience
with VMS as this is my first VAX. Mostly a PDP-8 guy, I suppose.
I'm running through the change password procedure, which I had seen
mentioned previously on this list:
SET VAXCLUSTER 0
SET /STARTUP OPA0:
SET WRITESYSPARAMS 0
CONTINUE
SET NOON
SPAWN /NOWAIT SYS$SYSTEM:STARTUP.COM
SET DEFAULT SYS$SYSTEM
RUN AUTHORIZE
At this point, I get this:
%DCL-W-ACTIMAGE, error activating image SECURESHRP
-CLI-E-IMGNAME, image file
R7CY2A$DIA0:[SYS0.SYSCOMMON.][SYSLIB]SECURESHRP.EXE;2
-SYSTEM-F-PROTINSTALL, protected images must be installed
$
What would I need to do to correct it to login?
The eventual goal is to get this online, which should be feasible. I have
an AUI-to-10Base-T adapter (several, actually). I think that'll be a little
while away for now, though.
Here are some pictures: http://imgur.com/a/WYGra
Thanks,
Kyle
12:01 p.m.
This is Sue Skonetski from VMS Software Inc. (www.vmssoftware.com)
Welcome to the world of VMS.
One of the huge advantages is the help so at the dead sergeant prompt >> you can
type in help show device, help cluster.
VMS is not case sensitive and is designed to be secure from the very start of the original
development almost 40 years ago. We still have customers who are still using this
version. As any FYI our longest record of up - time is 23 years so this is not a system
that you will be patching or fixing regularly.
If you are going to be using VMS regularly I would suggest signing up for the VMS Special
Interest Group (VMS SIG).
Here is the url to sign up, you can ask questions and folks will help. This is managed by
Connect (think DECUS) HP?s user group.
http://listserv.encompassus.org/scripts/wa-ENCOMPASS.exe?SUBED1=VMS-SIG&…
<http://listserv.encompassus.org/scripts/wa-ENCOMPASS.exe?SUBED1=VMS-SIG&A=1>
For current versions of VMS which is OpenVMS v8.4-1h1 just send me email.
Also if you need repairs done on PDP, VAX and Alphas? check out Nemonix Engineering. I
know the folks there and they can and do provide both hardware and software services, or
you can just send me mail and I will do what I can.
There will be a VMS/VAX/Alpha/DEC reunion at the OpenVMS Boot Camp in Sept you may just
want to see what kind of current VMS sessions there are. My guess is that there will be
more than you expected.
https://www.eiseverywhere.com/ehome/openvmsbootcamp2015/294678/
Hope this helps a little.
Sue
On Aug 26, 2015, at 2:25 PM, Kyle Owen <kylevowen
at gmail.com> wrote:
Just picked up a very complete MicroVAX 3800. I have very little experience
with VMS as this is my first VAX. Mostly a PDP-8 guy, I suppose.
I'm running through the change password procedure, which I had seen
mentioned previously on this list:
SET VAXCLUSTER 0
SET /STARTUP OPA0:
SET WRITESYSPARAMS 0
CONTINUE
SET NOON
SPAWN /NOWAIT SYS$SYSTEM:STARTUP.COM
SET DEFAULT SYS$SYSTEM
RUN AUTHORIZE
At this point, I get this:
%DCL-W-ACTIMAGE, error activating image SECURESHRP
-CLI-E-IMGNAME, image file
R7CY2A$DIA0:[SYS0.SYSCOMMON.][SYSLIB]SECURESHRP.EXE;2
-SYSTEM-F-PROTINSTALL, protected images must be installed
$
What would I need to do to correct it to login?
The eventual goal is to get this online, which should be feasible. I have
an AUI-to-10Base-T adapter (several, actually). I think that'll be a little
while away for now, though.
Here are some pictures: http://imgur.com/a/WYGra
Thanks,
Kyle
Sue Skonetski
VP of Customer Advocacy
Sue.Skonetski at vmssoftware.com
Office: +1 (978) 451-0116
Mobile: +1 (603) 494-9886
Mit freundlichen Gr??en ? Avec mes meilleures salutations
12:26 p.m.
Kyle Owen wrote:
Just picked up a very complete MicroVAX 3800. I have very little experience
with VMS as this is my first VAX. Mostly a PDP-8 guy, I suppose.
I'm running through the change password procedure, which I had seen
mentioned previously on this list:
SET VAXCLUSTER 0
SET /STARTUP OPA0:
SET WRITESYSPARAMS 0
CONTINUE
SET NOON
SPAWN /NOWAIT SYS$SYSTEM:STARTUP.COM
SET DEFAULT SYS$SYSTEM
RUN AUTHORIZE
At this point, I get this:
%DCL-W-ACTIMAGE, error activating image SECURESHRP
-CLI-E-IMGNAME, image file
R7CY2A$DIA0:[SYS0.SYSCOMMON.][SYSLIB]SECURESHRP.EXE;2
-SYSTEM-F-PROTINSTALL, protected images must be installed
$
What would I need to do to correct it to login?
You need an @ sign in front of SYS$SYSTEM:STARTUP.COM
(Sorry - I think I originally posted that procedure with the @ sign missing.)
Regards,
Peter Coghlan.
1:58 p.m.
On Wed, Aug 26, 2015 at 2:26 PM, Peter Coghlan <cctalk at beyondthepale.ie>
wrote:
You need an @ sign in front of SYS$SYSTEM:STARTUP.COM
(Sorry - I think I originally posted that procedure with the @ sign
missing.)
That seemed to do the trick! I'm now in the system. I'm struggling to
understand how to switch between making it conversational boot and not. I'm
assuming the lack of the NiCd battery will mean it won't necessarily
remember such preferences, but maybe I'm wrong. At this point, I think I'm
ready for it to boot non-conversationally.
Looks like it wasn't really wiped since it was last used in the mid-1990s.
I'll be reading up on VMS and learn how to do simple things like the
equivalent of "ls | less" in the *nix world. Not really sure how to read
the text printed to the terminal (VT320) one page at a time. In some OS/8
programs, you gave it the /P flag. Hmm...
It is complaining about DUB0:[RS1R4]RS1LOG.COM, DUB0:[ORACLES]ORAUSER.COM,
and DUB0:[ECMS4]LOGIN.COM after logging in. Not sure what that's all about.
%DCL-E-OPENIN, error opening [file]; as input
-RMS-E-DNR, device not ready, not mounted, or unavailable
How can I tell if it's an issue with the drive itself or something else? I
think this is one of the two 1.2 GB Sabre drives.
Thanks again for the tips!
Kyle
2:01 p.m.
Kyle Owen wrote:
That seemed to do the trick! I'm now in the system. I'm struggling to
understand how to switch between making it conversational boot and not. I'm
assuming the lack of the NiCd battery will mean it won't necessarily
remember such preferences, but maybe I'm wrong. At this point, I think I'm
ready for it to boot non-conversationally.
The way to do or not do a conversational boot is processor specific and I don't
know what the specifics are for a 3800. For some other types, something like
SET BFLGS 0 at the console prompt may reset it to non-conversational booting.
Typically putting 1 in the least significant bit of R5 enables conversational
booting and 0 disables it. As Sue said, there may be online help at the
console prompt which may provide some leads:
>> HELP
I would suggest removing the battery pack in case it leaks and causes damage
like some of mine have.
Looks like it wasn't really wiped since it was last used in the mid-1990s.
I'll be reading up on VMS and learn how to do simple things like the
equivalent of "ls | less" in the *nix world. Not really sure how to read
the text printed to the terminal (VT320) one page at a time. In some OS/8
programs, you gave it the /P flag. Hmm...
$ DIRECTORY /PAGE
Many other commands also accept /PAGE. Check the online help:
$ HELP
You might also get away with pressing holdscreen on the terminal, but probably
not on the console port.
It is complaining about DUB0:[RS1R4]RS1LOG.COM, DUB0:[ORACLES]ORAUSER.COM,
and DUB0:[ECMS4]LOGIN.COM after logging in. Not sure what that's all about.
%DCL-E-OPENIN, error opening [file]; as input
-RMS-E-DNR, device not ready, not mounted, or unavailable
How can I tell if it's an issue with the drive itself or something else? I
think this is one of the two 1.2 GB Sabre drives.
If one disk is DIA0 (a DSSI disk) and the two disks are similar types, it is
unlikely the other one is called DUB0 so you probably don't have the disk
it is trying to access. This should list the disks that you do have:
$ SHOW DEVICE D
Regards,
Peter Coghlan.
3406
days inactive
3406
days old
5 comments
4 participants
participants (4)
-
cctalk＠beyondthepale.ie -
kylevowen＠gmail.com -
scaron＠umich.edu -
Sue.Skonetski＠VMSSoftware.com