| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
I installed VMS T5.3-462 on my VS2000 from scratch. The installation
seemed to go smoothly but it seems that whenever I try to create a user
account I can only start DECterms and can't start clock or calendar,
calculator,... When I try to start them by typing RUN SYS$SYSTEM:DECW$CLOCK
from one of the DECterms I keep getting the following error:
X Toolkit Warning: DRM: I18NOpenFile: Couldn't open file DECW$CLOCK -
DRMFailure
X Toolkit Warning: Drm__OpenHierarchy: - DRMFailure
Can't open hierarchy
If I use the Application menu to try and start it I just get to "Starting
appl. (date time)" message in the session manager window but the application
never starts.
It seems that the only accounts that work right are the accounts that were
created when the installation was done (SYSTEM, SYSTEST, FIELD,...).
One thing I noticed is that the user accounts don't have the logical
name table DECW$LOGICAL_NAMES. If I log into the system account and do a
SHOW LOGICAL DECW$* this is what I see:
(LNM$PROCESS_TABLE)
(LNM$JOB_8039D190)
"DECW$DISPLAY" = "WSA1:"
(LNM$GROUP_000001)
(LNM$SYSTEM_TABLE)
"DECW$DECTERM_MAILBOX_TWINKE::0.0" = "_MBA52:"
"DECW$SERVER_MBX_000013B3_0" = "MBA16:"
"DECW$TERMINAL_MAILBOX_TWINKE::0.0" = "_MBA52:"
(DECW$LOGICAL_NAMES)
"DECW$BOOK" = "SYS$COMMON:[DECW$BOOK]"
"DECW$EXAMPLES" = "SYS$COMMON:[SYSHLP.EXAMPLES.DECW]"
"DECW$INCLUDE" = "SYS$COMMON:[DECW$INCLUDE]"
"DECW$KEYMAP" = "DECW$SYSCOMMON:[SYS$KEYMAP.DECW.USER]"
= "DECW$SYSCOMMON:[SYS$KEYMAP.DECW.SYSTEM]"
"DECW$SYSCOMMON" = "SYS$COMMON"
"DECW$SYSTEM_DEFAULTS" = "SYS$COMMON:[DECW$DEFAULTS.USER]"
= "SYS$COMMON:[DECW$DEFAULTS.SYSTEM]"
= "SYS$LIBRARY:"
"DECW$USER_DEFAULTS" = "SYS$LOGIN:"
"DECW$WINMGREXE" = "SYS$SYSTEM:DECW$WINMGR.EXE"
"DECW$XLIBERRDB" = "SYS$MESSAGE:DECW$XLIBERRDB.DAT"
and if I log into the user account and do the same thing, this is
what I see:
(LNM$PROCESS_TABLE)
(LNM$SPECIFIC)
(LNM$JOB_8039BC40)
"DECW$DISPLAY" = "WSA1:"
(LNM$GROUP_000300)
(LNM$SYSTEM_TABLE)
"DECW$DECTERM_MAILBOX_TWINKE::0.0" = "_MBA73:"
"DECW$SERVER_MBX_000013B3_0" = "MBA16:"
"DECW$TERMINAL_MAILBOX_TWINKE::0.0" = "_MBA73:"
I also did an upgrade from an VMS V5.2 system and that has the same
problem.
Any ideas? I'm new to DECwindows so I not even sure where to start
looking.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1626.1 | STAR::ORGOVAN | Vince Orgovan | Mon Oct 30 1989 18:05 | 4 | |
The DRM error messages mean that the applications can't open their
UID files. Did you check the file protections on the
decw$system_defaults:decw$*.uid files? They should have world:read
access.
| |||||
| 1626.2 | Still no applications | BAGELS::GIBEAU | Wed Nov 01 1989 11:54 | 5 | |
I did a dir/prot sys$sysdevice:[*...]*.uic and every .UID file on
the system is protected (RWED,RWED,RWED,RE).
I just update to V5.0 and still have the same problem. No
DECW$LOGICAL_NAMEs table defined.
| |||||
| 1626.3 | correction to .2 | BAGELS::GIBEAU | Wed Nov 01 1989 16:24 | 5 | |
The directory was on *.UID files not .uic and the new upgrade was
to V5.3. It's tough typing when you have 3 people in your office.
I guess if I could figure out why the DECW$ logicals are not defined
it might tell my why my user accounts aren't working.
| |||||
| 1626.4 | Try the create command file | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Thu Nov 02 1989 22:03 | 10 |
It gets created in SYS$MANAGER:DECW$LOGICALS.COM. Try putting a set
verify in that command file during system startup and see if you can
tell why your other processes don't see it.
Note: I did not check thoroughly. This may be called several times
to create several different tables, not all of which are supposed to
become part of LNM$FILE_DEV etc.
Burns
| |||||
| 1626.5 | SKIME::VEZINA | Tue Nov 07 1989 14:25 | 9 | ||
I had a user with a similar problem and found that his LOGIN.COM was the culprit. Is it possible that users LOGIN.COMs or SYLOGIN.COM could be doing something similar ? I had the user rename his login.com to .SAV and had him fire up Windows and his problem was solved. He is trying to isolate the problem within his login procedure. I don't know if this will help but it may be worth a try. | |||||