[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | POLYCENTER Console Manager | 
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: | 
| Moderator: | CSC32::BUTTERWORTH | 
|  | 
| Created: | Thu Aug 06 1992 | 
| Last Modified: | Fri Jun 06 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 1541 | 
| Total number of notes: | 6564 | 
548.0. "Prblms installing V1.5" by SWETSC::EKLUND (Cheer up, the worst is yet to come) Wed Jan 11 1995 11:15
    Hi,
    
    I have a customer who has problems installing on a 4700 
    running V6.1 of VMS.
After invoking Vmsinstal he gets:
    
%SYSTEM-W-NOSUCHDEV, no such device available
 \CONSOLE$ROOT:[DATA]\
%CREATE-E-DIRNOTCRE, CONSOLE$ROOT:[DATA] directory file not created
-SYSTEM-W-NOSUCHDEV, no such device available
%VMSINSTAL-E-INSFAIL, The installation of CONSOLE V1.5 has failed.
        VMSINSTAL procedure done at 19:51
He then defines CONSOLE$ROOT (to STA1:[CONSOLE.]) just to try and he now get's:
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-E-BADSPEC, File spec  CONSOLE$CONFIG.PORT  cannot be parsed
%VMSINSTAL-E-INSFAIL, The installation of CONSOLE V1.5 has failed.
        VMSINSTAL procedure done at 19:56
                                                                                
    
    I know that defining CONSOLE$ROOT should not be done.
    Is there anybody who have seen something like this ?
    
    Johan
| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 548.1 |  | OPG::SIMON |  | Wed Jan 11 1995 13:50 | 9 | 
|  | What did the customer answer to the question:
Please specify the disk for Console Manager files?
The install uses the answer to this to build the logical names for the 
files to be accessed. This should be a disk volume or a logical name for
a disk volume.
Cheers Simon....
 | 
| 548.2 | VMSINSTALL did not find the logical name table | SWETSC::EKLUND | Cheer up, the worst is yet to come | Thu Jan 12 1995 09:37 | 6 | 
|  |     Hi,
    
    You where on the right track, the problem was a redefinition of 
    lnm$file_dev on that system.
    
    Johan
 |