From:	SMTP%"carl@SOL1.GPS.CALTECH.EDU" 16-JAN-1995 13:42:46.96
To:	EVERHART
CC:	
Subj:	Re: HELP! -- UAF file damaged

From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
X-Newsgroups: comp.os.vms
Subject: Re: HELP! -- UAF file damaged
Date: 15 Jan 1995 10:37:18 GMT
Organization: HST Wide Field/Planetary Camera
Lines: 66
Distribution: world
Message-ID: <3fatsu$2lq@gap.cco.caltech.edu>
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu
To: Info-VAX@Mvb.Saic.Com
X-Gateway-Source-Info: USENET

In article <3f5g78$qvd@raffles.technet.sg>, ratrain@technet.sg (ratrain@technet.sg) writes:
=
=	You may still remember a few days ago I got help from 
=you on SYSTEM password.
=	I did managed to recover it with your help.
=	But now the situation is even worse.
=
=	Even after I SET UAFALTERNATE 1
=I still cannot login SYSTEM. It always says "unautherorized user".

The most common reason for this is:
	1)  Somebody already forgot the SYSTEM password on your machine.
	2)  They used the UAFALTERNATE technique to boot the system and log in.
	3)  They then used AUTHORIZE to set the password for SYSTEM, without
	    deassigning the logical name SYUAF.
This means that there are both both the normal and an alternate SYSUAF, and you
don't know the password for the SYSTEM account stored in eitheer.

=I then remember that, I was in SYSTEM, trying to create
=a new user with the same provilege of SYSTEM. I left the
=terminal half way without logout. (What a mistake a new system
=adminstrator has made!)
=	Somebody might key in some wrong commands and massed up
=the UAF file.
=
=	We do have another working MicroVAX 3100.
=Someone told me by using another VAX, I should be able to recover
=it.

Only if it's part of an homogenous VAXCLUSTER, or can be configured (without
using privs on the machine that's giving you trouble) to be part of such a
cluster.

If you can't manage that, then try a conversational boot, then when you get the
SYSBOOT> prompt, try the following:
	SYSBOOT>  SHO/STARTUP
	SYSBOOT>  SET/STARTUP _OPA0:
	SYSBOOT>  CONTINUE
{wait for the $ prompt}
	$ SPAWN
	$ DEFINE/USER SYS$INPUT SYS$MANAGER:VMSIMAGES.DAT
	$ MCR INSTALL
	$ MCR AUTHORIZE
	UAF> MOD SYSTEM/PASS=whateveryouwant
	UAF> EXIT
	$ MCR SYSGEN
	SYSGEN>USE CURRENT
	SYSGEN>SET/STARTUP whatever_you_found_in_the_first_step_above
	SYSGEN>WRITE CURRENT
	SYSGEN>EXIT
	$ @SYS$SYSTEM:SHUTDOWN 0 1 0 1 0 1 NONE
When the system comes up again, log in as SYSTEM and locate and delete the
alterenate SYSUAF.

Note:  I'm not 100% sure of the syntax on all of the above commands, and I'm
not willing to shut down one of the systems I manage to confirm the syntax. 
Check the manuals to make sure my syntax is correct, or ignore this message,
whichever you prefer.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.