Conference bulova::decw_jan-89_to_nov-90

Is there a DECW$SERVER process running? If so what state is it in, HIB? LEF?
Is there decw$server*.log files in sys$manager?
						Bill

    Bill,
    
    Thanks for such a quick response...
    
�   Is there a DECW$SERVER process running? If so what state is it in, HIB? LEF?
    
    No, no DECW$SERVER process.
    
�   Is there decw$server*.log files in sys$manager?

    Yes,
    
    DECW$SERVER_0_ERROR.LOG
    
    $ ty decw$server_0_error.log
    Hello, this is the X server
    Dixmain address=22dfa
    $
    
    and DECW$SERVER_0_OUTPUT.LOG
    
    $ ty decw$server_0_output.log
    can not get input buffer
    $
    
    Hope this helps...
    
    Dan
    

Do a show device/full for all G* devices and TT* devices and post the
results here.
						Bill

	I have seen similar problems if you do not have enough GBLPAGES or
GBLSECTIONS for DECW$STARTUP to run properly.

Kevin

    Ok,
    
    $ sh dev/full G*
    %SYSTEM-W-NOSUCHDEV, no such device available
    $ sh dev/full TT*
    %SYSTEM-W-NOSUCHDEV, no such device available
    $
    
    Thanks,
    
    Dan
    

    re .4
    
    GBLSECTIONS = 300
    GBLPAGES    = 20700
    
    Do these look ok?
    
    Thanks,
    Dan

    
    $ sh dev/full G*
		Sorry, remove the * in the above

    $ sh dev/full TT*

   Sorry, remove the * in the above

    Ok,
    
    $sh dev/full G
    
    Device GCA0: is online, record-oriented device, carriage control, shareable.
  
    Error count                        0    Operations completed              0
    Owner process                     ""    Owner UIC                  [SYSTEM]
    Owner process ID            00000000    Dev Prot S:RWLP,O:RWLP,G:RWLP,W:RWLP
    Reference count                    0    Default buffer size              80
     
    $ sh dev/full TT
    
    Terminal RTA1:, device type VT200 Series, is online, mounted, record-oriented                   
        device, carriage control.                                                                   
    
    Error count                        0    Operations completed              0
    Owner process               "SYSTEM"    Owner UIC                  [SYSTEM]
    Owner process ID            20402AB0    Dev Prot            S:RWLP,O:,G:,W:
    Reference count                    2    Default buffer size              80

    $
    
    Hope this helps,
    Dan

Sorry, One more try. Could you do a show device/full tta0:
and a show device/full tta1:
					Bill

    Ok,
    
    $ sh dev/full tta0:
    
    Terminal TTA0:, device type LN03, is online, unit timed out, record-oriented
        device, carriage control, device is spooled through an intermediate device,
        operations being cancelled.
    
    Error count                2    Operations completed                      4
    Owner process             ""    Owner UIC                          [SYSTEM]
    Owner process ID    00000000    Dev Prot                    S:RWLP,O:,G:,W:
    Reference count            0    Default buffer size                      80
                                                           
    $ sh dev/full tta1:
    
    Terminal TTA1:, device type unknown, is online, record-oriented device, carriage
        control.
    
    Error count                0    Operations completed                      2
    Owner process             ""    Owner UIC                          [SYSTEM]
    Owner process ID    00000000    Dev Prot                    S:RWLP,O:,G:,W:
    Reference count            0    Default buffer size                      80
    
    $
       
    Right now I have the TTA0: port used for my LN03R printer, nothing on 
    TTA1: or TTA2:, and TTA3: is being used for an asynch DECnet connection.
    
    I hope this helps, I am really getting into a bind because I *must* get
    an imaging demo together very soon...thanks for your efforts.
    
    Still dead in the water with DECwindows,
    Dan

How did you attach the LN03R to the VS2000? The 2000 has a special comm
connector which replaces the normal serial lines and converts the ports 
for TTA0: and TTA1: into the workstation keyboard and mouse ports 
respectively. The console port is on TTA2: (i recall) and TTA3: is the 
full 25 pin comm connector. For more information see the DECW$DEVICE 
startup file where it configures this:

$ if VS2000
$ then
$   if (f$getdvi("GCA0","STS") .AND. 16) .eq. 0 then sysgen reload gcbdriver.exe
$   decw$device_type :==                VS2000
$   decw$keyboard :==                   tta0:
$   decw$pointer  :==                   tta1:
$   decw$xsize_in_pixels :==            1024
$   decw$ysize_in_pixels :==            864
$   decw$color :==                      FALSE
$ endif

In short, check your connections, and make sure you are specifying the correct 
ports in you setup files.

James

    Refer back to 226... The configuration for the BOOT NODE is
    a MicroVAX II with the SATELLITE NODES as VS2000. The LN03
    is connected to the TTA0: on the MICROVAX II and the
    communications line is on the TTA3: on the MICROVAX II.
    
    There are no printers or comm lines connected to the VS200s.
    Sorry if I misled you!
    
    Do the port definitions for the startup file for the BOOT node
    affect the way the SATELLITE  nodes are booted and configured?
    
    (DECwindows is STILL not up...)
    
    Dan

    hmmmm,
    
    So what is happening is, the SYSTARTUP_V5.COM file is executing
    when the satellite boots (because it resides in SYS$COMMON).
    Within this startup file I have attempted to set TTA0: on the
    boot node up for a printer port, not thinking that this will
    affect the corresponding port on the satellite nodes!!  This
    must be screwing up the DECW$DEVICE command procedure.
    
    Sounds like the port definitions should be node specific...right??
    
    Geez...I guess there is more to this system management stuff
    than I thought :')
    
    Not a system manager, but proudly becoming one,
    Dan

Use NODE::TTA0: instead of TTA0: (where NODE is the nodename of your bootname)
throughout your system startup files.

Kevin

    That works!!!!!!!
    
    Many, many, many thanks!!!!
    
    Feeling much relieved,
    Dan