[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
2948.0. "HELP!!! No Windows..." by FSDEV1::KLEBLANC () Mon Jun 18 1990 14:33
<<< VWSENG::DISK:[NOTES$LIBRARY]VWS.NOTE;1 >>>
-< VWS - VMS Workstation Software (NOT DECwindows) >-
================================================================================
Note 609.0 HELP!!! No Windows... 1 reply
FSDEV1::KLEBLANC 28 lines 18-JUN-1990 12:11
--------------------------------------------------------------------------------
I'm experiencing a VERY frustrating and aggrevating problem...
Any help/suggestions will be GREATLY appreciated!!!
I have a VAXstation 3100 SPX/Model 38 (8MB memory) which boots
off a VAXstation 3100/Model 48 (16 MB memory). When the 'boot'
is completed, DECwindows does not come-up on my monitor. Instead,
I get about 30 lines of NCP output (ex. nonpriv user id = ,
alias incoming = , path split policy = , etc., etc.) and then
the following error:
% search-w-openin, error opening sys$common:[sysmgr]decw$ncp1.tmp
as input
- rms-e-fnf, file not found
To then get windows, I log into my system via the lat and simply
execute decw$startup. Then, the majority of times I do get DECwindows.
But not always!!!!!
BTW: We're running VMS 5.4... and I
Thanks,
Ken
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2948.1 | decw$ncp%.tmp | STAR::ORGOVAN | Vince Orgovan | Mon Jun 18 1990 19:10 | 10 |
| The file sys$manager:decw$ncp%.tmp is used a scratch file during
DECwindows startup. It is created in the sys$manager directory
"on the fly" during startup, and then parsed with the search
utility. (Yes I know it's a hack!) Search is complaining that it
can't open the file, which probably means that it wasn't written
correctly. Any chance that the system account doesn't have write
access to sys$manager during startup on your machine?
The relevant section of DCL is contained in
sys$manager:decw$startup.com following the label "decnet_running:".
|
| 2948.2 | I've seen the same problem... | PUGET::SCHEEL | Lee Scheel | Tue Jun 19 1990 00:19 | 9 |
| I recently had EXACTLY the problem that you are describing because
there was a command procedure invoked by systartup_v5 that created a
global symbol for DEFINE. The symbol was defined as
DEFINE :== DEFINE/SYS/EXEC which caused the DEFINE/USER in
DECW$STARTUP.COM that redirects NCP output to be a permanent system
logical assignment. Changing the symbol definition to local fixed the
problem. This was on another 3100 LAVC in the same building that you
are in. You didn't happen to pick up any startup command procedures
from node CADMIN did you?
|