>>>> "Ashley" == Ashley Carder
<wacarder(a)usit.net> writes:
Ashley> If you're able to get into 1,2 you can do whatever you want.
Ashley> I don't know what kinds of changes happened from v7 to v9,
Ashley> but you should be able to do anything you need to do if
Ashley> you're on 1,2 (except POKE, which you can only do from 1,1).
Ashley> For example, if you can break the startup sequence and get a
Ashley> READY prompt while logged into 1,2, you can do
Ashley> UT CHANGE [1,2] xxxxxx
Ashley> where xxxxxx is the new password for 1,2. Unless $MONEY was
Ashley> changed between v7 and v9, you should also be able to print
Ashley> passwords from 1,2.
Ashley> The passwords are stored in account [1,1], also known as the
Ashley> MFD (master file directory). $MONEY uses SYS() function call
Ashley> SYS(CHR$(6%)+CHR$(14%)) to retrieve the accounting info,
Ashley> including passwords, from the MFD. You could also write a
Ashley> program to open [1,1] as a file and get all this info
Ashley> yourself, bypassing the SYS() call and going directly to the
Ashley> MFD. Of course, all of this would require you to be logged
Ashley> on as a privileged user (1,*).
All this is quite different as of V9.0. For one thing, there's a GFD
(group file directory), and account attributes are stored there.
Second, MONEY is history as is UTILTY -- these things changed to DCL
command like "set account" or "set password".
Finally, though it wasn't used all that widely, V9.0 and later have
multiple privilege flags very much like what VMS has (somewhat better,
in my opinion, but I'm biased...). The defaults are like they were
before, but you can make 1,* accounts that are not privileged, or
non-1,* accounts that are. Or you can have accounts that are somewhat
privileged. For example, you can set up an account that can do
backups -- but not restores, so that user can read files but not
change files.
paul