11 Oct
2007
11 Oct
'07
12:48 a.m.
Allison schrieb:
It's "run $acntres" on this beastie. However any attempt to modify
the accounts or add accounts causes a illegal instruction trap and
return to prompt.
Yes, this is a "shared library" version of the ACNT program which can
be
built with sysgen to
save some space in memory. IIRC, it is linked against some RMSRES.TSK or
FCSRES.TSK
library loaded into memory.
Look into the [1,2]STARTUP.CMD file what is done there. It is possible
that some TSKs have to
be installed first (INS cmd).
Was [7,*] also privileged? I am not sure anymore after several years.
The point may be though that
the password file is actually owned by [1,2] - in this case you might
not be able modify it from [7,21].
Subject: Re:
DEC RSX-11
From: Holger Veit <holger.veit at iais.fraunhofer.de>
Date: Wed, 10 Oct 2007 13:19:57 +0200
To: General Discussion: On-Topic Posts Only <cctech at classiccmp.org>
Ethan Dicks schrieb:
RUN $SHUTUP
That works.
On 10/9/07, Allison <ajp166 at
bellatlantic.net> wrote:
It is probably @[1,2]SHUTUP.CMD, or better RUN $SHUTUP
>
> > TO
change admin password how, and which account again?
>
>
RUN $ACNT
and then modify the UIC [1,2].
Could it be the files are protected? I did insure the
disk write
protect was disabled and working.
Things that can happen are:
- the ACNTRES.TSK is not contiguous (PIP [1,2]ACNT*.TSK/LI does not
contain a 'C' in the line
- some of the resident libraries are missing/not INStalled (because on
that turn-key application there were not required)
- the ACNTRES comes from a different OS version
- there are several versions of ACNTRES.TSK in the system dir, and only
an older one works.
Basically, any account [1,x] is privileged, so
you might create a new
account in this range before
fiddling with the old one and maybe accidentally disabling it (happened
to experience this myself :-))
Fortunately when the system boots the startup.cmd also logs in account
7,21.
Very helpful, save for Acrobat say the files are corrupt for any of the more
useful ones and crashes for manuals over 25MB.
I had downloaded them, as well as the ones at John Dundas's site, and
did not find corruptions. The files
at the Australian computer museum are large, though; the first thing I
did was to compress them with an
Adobe Acrobat. There it should have been detected if they were corrupt.
So I guess its you having some
transfer problem.
I'm not sure anything useful other than a
"Pregen"ned system is on
the disk as I havent found any languages.
Hmmm, to sysgen a new system, the installation set is required. One
indicator you might have sysgen stuff
on the system is the presence of some [200,200]SYSGEN*.CMD scripts, and
the current configuration
should be in [200,200]SYSSAVED.CMD;*
--
Holger