[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

1697.0. "Problem with VMS 5.3 DECW$TAILOR" by BIGIST::ARDLEY () Wed Nov 08 1989 12:35

    I have just upgraded my workstation to VMS 5.3. As I didn't have the 
    decwindows kit in the same directory, I decided to use the DECW$TAILOR
    program to install decwindows.
    
    unfortunatly, all I get having selected all of the options is an error
    message:
    
    %RMS-E-DNR, device not ready, not mounted or unavailable
    %RMS-F-IFI, Invalid internal file identifier (IFI) value
    
    I have tried all sorts of combinations but I am having no joy. 
    
    The decwindows kit lurks on a disk.
    
    David Ardley

T.R	Title	User	Personal Name	Date	Lines
1697.1	A little more info ...	BIGIST::ARDLEY		`Wed Nov 08 1989 13:08`	10
	Just a little more info ... I select all the options I respond yes to "do you what to add the options" ... Then I get the error message . The procedure displays the message "creating temporary command procedure, but this is so quick, it appears not to really do anything.
1697.2	Seems to work now!	205GTI::ARDLEY		`Wed Nov 08 1989 16:57`	3
	well, after rebooting the system again the dcw$tailor seems to work ok, so I guess its problem solved. However I'd be interested if anyone knows what might have gone wrong.
1697.3	Just a guess...	IO::MCCARTNEY	James T. McCartney III - DTN 381-2244 ZK02-2/N24	`Sat Nov 11 1989 02:35`	7
	My guess is that you were still booted with startup_p1 == MIN and thus none of you devices were autoconfigured. Rebooting (after the installation of V5.3 which resets startup_p1) would have fixed this. James
1697.4	DECWINDOWS won't startup after DECW$tailor puts files "ON".	RUFREE::LAPERLE		`Thu Jun 07 1990 15:03`	23
	Hello, I too have a problem with DECW$TAILOR....... I have a standalone 3500. It has been upgraded from VMS 5.2 to VMS 5.3. The person doing the upgrade did not realize that he needed the DECW053 saveset to install decwindows.... In Phase 2 of the upgrade he chose the option to skip over the decwindows install. I attempted to correct the problem using DECW$TAILOR to put the files ON the disk. DECW$tailor "COMPLETED SUCCESSFULLY" and requested a system reboot. Upon reboot it would not start decwindows. The sysgen parameter Startup_p1 was not set to "MIN". I also attempted to start DECwindows interactivly. It would not startup the server process. Upon more investigation there seems to be files missing that DECwindows need to operate. We are going back to VMS 5.2 and upgrading over again To correct our problem. But I would still like to know what may have happen. If anyone can help me answer this questions I would be greatful. Thank You Richard Laperle.
1697.5	decw$tailor should work OK	STAR::ORGOVAN	Vince Orgovan	`Thu Jun 07 1990 19:06`	4
	DECW$TAILOR should have been able to do this, assuming that you asked for both "workstation device support" and "DECwindows application support". Are you sure you tailored both of these pieces onto your system?
1697.6	RE:decw$tailor should work OK	RUFREE::LAPERLE		`Mon Jun 11 1990 13:03`	13
	Hi Vince, Yes I did put those options back on in full. I put all options asked about back on in full. The strange thing was when I went to delete them using DECW$TAILOR "OFF" option all those files were not found. This was after a "Completed successfully" from the "ON" option. We have gone back to VMS 5.2 because the customer could not afford any more down time. We will upgrade properly in the near furtue. If you which to look into this further I would be willing to help you. Thanks for your reply Richard Laperle