home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.sysmgt:346 comp.os.vms:18032
- Path: sparky!uunet!ukma!wupost!usc!news.service.uci.edu!beckman.com!dsroberts
- From: dsroberts@beckman.com
- Newsgroups: vmsnet.sysmgt,comp.os.vms
- Subject: Re: Error accessing SYSUAF file
- Message-ID: <1992Nov16.135421.1042@beckman.com>
- Date: 16 Nov 92 13:54:21 PDT
- References: <1992Nov16.115823.1041@beckman.com>
- Organization: Beckman Instruments
- Lines: 23
-
- In article <1992Nov16.115823.1041@beckman.com>, dsroberts@beckman.com writes:
- > "Error accessing system authorization file"
- > "Error in device name or inappropriate device type for operation"
- > "SYSUAF" = "BII$SYSTEM:SYSUAF.DAT"
- > "BII$SYSTEM" = "$1$DUA1:[BII.SYS]"
-
- Well, more information, as pointed out, is needed to eliminate some
- possibilities. From the log of the startup in question:
-
- $ define /system/exec/nolog bii$system $1$dua1:[bii.sys]
- $ define /system /exec /nolog sysuaf bii$system:sysuaf.dat
-
- So, as all can see, it was indeed defined in executive_mode.
-
- Any other thoughts? Thanks for the replies so far.
-
- --
- Don Roberts Internet: dsroberts@beckman.com
- Beckman Instruments, Inc. Phone: 714/961-3029
- 2500 Harbor Bl. Mailstop X-12 FAX: 714/961-3351
- Fullerton, CA 92634 Disclaimer: Blame me, not Beckman.
- This was probably the most disastrous election result for the American
- people since James Buchanon became president. Heaven help us.
-