Conference bulova::decw_jan-89_to_nov-90

1834.0. "DECwindows bombs at startup" by WFOV12::COBB () Sat Dec 02 1989 11:07

                      
    
    Maybe someone can help me with this problem.  I have a Vaxstation
    II/gpx (Microvax with 8 plane modules).  I just loaded the new VMS
    5.3 and decwindows 2.0.  The instalation went well and Vms loads
    ok.
    
    My question is when the startup procedure tries to initialize
    decwindows, it comes up with the following error:
    
    %DECW-W-VWS, VWS graphics drivers already loaded
    %DECW-W-NODECW, DECwindows graphic drivers will not be loaded.
    
    The disk I upgraded had VWS on it, but I removed all the files
    that could possibly load in.  The version of VMS was 5.0 . 
    
    In the file DECW$DEVICE.COM,
    the procedure bombs out about here:
    
    $if f$getdvi("GAA0","exists") then goto gaa0
    $if f$getdvi("GBA0","exists") then goto gba0
    $if f$getdvi("GEA0","exists") then goto gea0
    $if f$getdvi("GFA0","exists") then goto gfa0
    $if f$gerdvi("GCA0","exists") then goto gca0
    $if f$getdvi("VAA0","exists") .or. f$getdvi("VCA0","exists"))
    $then
    $write sys$output "%DECW-W-VWS, VWS graphics drivers already loaded"
    $write sys$output "%DECW-W-NODECW, DECwindows graphic drivers will
    not be loaded"
                  
    
    Looking at this, it looks as though VAA0 and VCA0 are not valid
    graphic adapters or are associated with VWS.  A SHOW DEVICES shows
    no GAA0-GFA0 devices, only VAA0 shows up.  What is necesary to fix
    this problem?  Can I unconfigure the graphics adapter to look like
    a GAA0 device?  
    
    By the way, when the startup procedure completes, a mouse arrow
    appears on the screen.  It moves around but no windows appear or
    anything.  Could this be a clue?
    
    Any help will be very much appreciated.
    -Thanks in advance
                                                              

    Try:
    
    >>>B/1
    
    SYSBOOT> SET WINDOW 1
    SYSBOOT> EXIT
    
    You have the window system set to 2 and the VA video driver is being
    loaded.  You might look in modparams.dat to see if it's bee hardwired
    into your autogen.
    
    _Fred

    
    Thank you Fred,
    
        That did it.  Modparams.dat looked ok when I looked at it. 
    Is there a way I can put that in modparams.dat so that I can eliminate
    the SYSBOOT> set window 1  all the time.  

    
    The SET_WINDOW in SYSBOOT and a EXIT burns that sucker in :-)  But you
    might do a search of all the autogen files in sys$system for the
    window_system parameter... so that when you do an autogen with feedback
    (you do want that DECwindows system to run 'reasonably' right?) you
    won't get bit by autogen.
    
    _Fred

>    The SET_WINDOW in SYSBOOT and a EXIT burns that sucker in

Almost true.  If the WRITESYSPARAMS parameter is 0, then it wont 
``stick''.  The approved way is to modify MODPARAMS.DAT, add the
WINDOW_SYSTEM=1, and then do an autogen.

    
    modparams changes in a word: suck.
    
    9 out of 10 people who complain that they cannot install VWS or
    DECwindows have a modparams that has screwed them.
    
    It's also *real* messy when you frequently switch windowing systems.
    
    I guess when you set writesysparams to 0, you deserve what you get :-)
    
    

>             <<< Note 1834.6 by SSPENG::KLEINSORGE "So sue me." >>>
>
>    
>    modparams changes in a word: suck.
>    
>    9 out of 10 people who complain that they cannot install VWS or
>    DECwindows have a modparams that has screwed them.

	Kinda gives a different angle on all the support-for-XDEFAULTS
	arguments, doesn't it?  :-)

RE: .7

So give us a supported, reliable, convenient, and robust way to do
customization.

--PSW