[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

2984.0. "Correct startup for DECwindows on PC ?" by KAOA12::DUFF (Peter Duff) Fri Jun 22 1990 15:59


	Hi,

	I have a customer who is trying to setup DECwindows on their
	PC that is in their network.

	The PC is running a third party Xwindow server software
	from HCL.

	Their VAX is running VMS 5.3 which is being used as
	the client for DECwindows. It is running the ULTRIX
	connection.

	In order to get things working at present we are logging
	into the VMS user's account and doing the following in the
	user's LOGIN.COM:

		1) SET DISP/CRE/TRAN=TCP
		2) Spawning with nowait the window manager.
		3) Spawning with nowait the file view.
	
	I wondering is there a proper procedure that I should be
	going thru to startup DECwindows on the PC ?

	Should I be placing symbol definitions for my PC in
	DECW$PRIVATE_SERVER_SETUP.COM and then invoke DECW$STARTUP again.

	DECW$STARTUP is already being executed at system startup.
    

	Regards,
		
	Peter
T.RTitleUserPersonal
Name		DateLines
2984.1Some side issuesSTAR::VATNEPeter Vatne, VMS DevelopmentFri Jun 22 1990 18:2616
Quick note on:

>		1) SET DISP/CRE/TRAN=TCP

This shorthand may be confusing to novices.  "TCPIP" may not be abbreviated.
Also, the node name is missing.  An example abbreviated command is:

		$ SET DISP/CREA/TRAN=TCPIP/NODE="uuuuuu"

where uuuuuu is the Internet node name.


>	Should I be placing symbol definitions for my PC in
>	DECW$PRIVATE_SERVER_SETUP.COM and then invoke DECW$STARTUP again.

What symbol definitions are you referring to?
2984.2the symbols are ...KAOA12::DUFFPeter DuffMon Jun 25 1990 22:3628
	Hi Peter,

	Thanks for the quick reply. Sorry for the shorthand but I 
	was winging it from what I could remember doing at the 
	customer site.

	The symbols I was referring to in DECW$PRIVATE_SERVER_SETUP
	are:

		DECW$SERVER_DENSITY
		DECW$COLOR	
		DECW$BITONAL	
		DECW$DEVICE	
		DECW$DEFAULT_KEYBOARD_MAP
		DECW$SERVER_TRANSPORTS

	I believe I can let some of the default values apply.


	Besides the method describe in note 2984.0 are there DCL 
	procedures for which I would need to modify/execute for 
	starting up the DECwindows on third party PC Xservers ?


	Regards,

	Peter
2984.3No symbols to define that I know ofSTAR::VATNEPeter Vatne, VMS DevelopmentTue Jun 26 1990 15:0716
Okay, of the symbols that you list, you will probably want to use the
defaults for all of them, except for DECW$SERVER_TRANSPORTS.

>		DECW$SERVER_DENSITY
>		DECW$COLOR	
>		DECW$BITONAL	
>		DECW$DEVICE	
>		DECW$DEFAULT_KEYBOARD_MAP
>		DECW$SERVER_TRANSPORTS

I believe the monitor density on our PCs is 75 dpi, which is the default.
DECW$SERVER_TRANSPORTS needs to include TCPIP, but from the sound of
your description, the customer must already know that.

I will leave it to the PC experts out there to answer the question
on proper startup of DECwindows applications displaying to the PC.
2984.4RANGER::PFEFFERTue Jul 17 1990 15:3418
    
    
     You may want to post this query in the RANGER::PCDECWINDOWS notes
     file.
    
     As far as I know, all 3rd-part PC X servers require the user to 
     start applications from another terminal (or to run a terminal
     emulator on the PC - TELNET - to invoke the application).
     The PC DECwindows team decided that this was too much of a 
     kludge so we invented the "remote startup protocol." It is 
     simply a DECnet task-to-task communication with a named DECnet
     task. The PC sends a request to start an application and also
     sends it its address. The remote task forks the application - 
     and it starts to the PC. The "protocol" is actually being
     enhanced by the MAC/X people.
    
     Mike