Conference bulova::decw_jan-89_to_nov-90

	Set WINDOW_SYSTEM to 1 in Modparams.Dat and AUTOGEN and reboot.

							mike

    re: .1
    
    	I'm having the same problem as .0, and this is what I did:
    
    1) added a line to MODPARAMS.DAT 'WINDOW_SYSTEM=1'
    
    2) @sys$update:autogen
    
    3) rebooted
    
    	I still get an error saying there is no graphics device on the
    system.  Is there something else I need to do?
    
    			Tony
    

	Did you do a @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK  ???

							mike

    re: .3
>    	Did you do a @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK  ???
 
    No, should I? (I'm new to this system management stuff)
    
    				Tony
    

    By the way did you install graphic device support when asked by the DW
    installation?
    
    ���

RE: .4

	The correct answer to .5 and doing .3 should give you what you want.

							mike

    re: .5
    	I don't remember getting a question about graphic device support.
    The only question I got asked if I wanted to install the entire
    kit, to which I answered yes (can I assume that the graphic device
    support is included?)
    
    re: .6
    	I did what was in .3, and now I get the grey background up,
    and the pointer.  However, I don't get the login window, or Digital
    logo.  Is there something else that needs to be started in my
    systartup_v5 file (besides decw$startup)?
    
    			Tony               
    

    Graphics support will be there if you installed the whole kit.
    
    Really sounds like you are running out of some resource. Are your PQL
    values at the reccomended level? Is the SYSTEM account UAF record set
    up with sufficient BYTLM etc?
    
    ANdy

    	When I did as .3 instructed, the system gave a list of SYSGEN
    parameters that were set wrong, and gave me the option of letting
    it change them then rebooting, which I did.  Since then, it hasn't
    complained about any of these parameters.  As far as the SYSTEM
    account goes, it's BYTLM is 32768 (that is if BYTLM=buffered i/o byte
    count quota, otherwise I'm lost on how to find out what it's set
    to)
    
    
    				Tony
    

    I hope no one jumps on me for this, but I've found that I've had to
    increase several of the recommended SYSGEN param values to get things
    to work.  Of course, this always depends on the target system too.
    Here are the things that I've increased.  Not all of them are directly
    due to DECwindows requirements, but I don't think any of them are
    excessive either.  You might try autogening with these and see if they
    help.  Be sure to save a copy of your old MODPARAMS file.  This is on
    a 14MB VS2000 color system.

              Dave

	ADD_NPAGEDYN=200000
	ADD_GBLPAGES=6000
	ADD_GBLSECTIONS=50
	MIN_GBLPAGFIL=15000
	MIN_LOCKIDTBL=2048
	MIN_RESHASHTBL=512
	PQL_DWSDEFAULT=200
	PQL_MWSDEFAULT=200
	PQL_DWSQUOTA=300
	PQL_MWSQUOTA=300
	PQL_DWSEXTENT=400
	PQL_MWSEXTENT=400

    and my SYSTEM account has the following quotas

	Maxjobs:         0  Fillm:       100  Bytlm:       100000
    	Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
    	Maxdetach:       0  BIOlm:       100  JTquota:       2048
    	Prclm:          12  DIOlm:       100  WSdef:          500
    	Prio:            4  ASTlm:       400  WSquo:         1200
    	Queprio:         0  TQElm:        80  WSextent:      3100
    	CPU:        (none)  Enqlm:       600  Pgflquo:      20000

    	Well I set all the values, as stated in .10 (both SYSGEN and
    UAF parameters), but I still don't get the login window on my GPX, 
    any other suggestions? 
    
    
    				Tony
    

Are the DECW$ processes running? have you tried Ctrl/F2 ?

Andrew.

    Well, you've really exhausted all the easy ones and are now down into
    nitty gritty system manager territory.  You might check to see if your
    MAXPROCESSCNT parameter is high enough.  Since you can obviously log
    in from other sources, you probably don't have any file protection
    problems.  Look for any log or error files that show a modification date
    of when you tried to start DECwindows or log in, probably in the system
    manager directory since you never logged in.  After verifying from another
    terminal what DECwindows processes start or do not start, you might enable
    image accounting and see if there are any abnormal image termination
    statuses.

                Dave

    	Well, I got really frustrated with this so I re-installed VMS
    and the latest version of DECW (previously I was using V2 IFT1)
    And it now works ok.  Thanks all for helping me though.
    
    
    				Tony
    

    I've heard a couple of times now that I should increase LOCKIDTBL when
    running DECwindows.  I also know that VPA recommends that it be
    increased.  Why does it need to be raised?  What is using it on the
    client side?  What about on the server side?
    
    Thanks,
    
    Irene