🚀 go-pugleaf

In article <1ggvu1INNoqi@sacomm.schulz.unisa.edu.au> cowleym@sacomm.schulz.unisa.edu.au writes:
>
>I'm reposting this item here, as I got no response from comp.windows.x:
>
>Server System: DECstation 5000, running Ultrix 4.3, Motif Windows, Pathworks for
>		Ultrix v1.2 and DECnet
>
>Using eXcursion V1.? on a PC, we're trying to run an Xapplication (dxclock) 
>over DECnet on the Ultrix server and get the error message:
>
>Application not found in host "dxclock"
>
>Defining the application as /usr/bin/dxclock produces the same error.
>The "User's Guide" suggests we check application startup command, host and user
>information which all looks OK to us.
>
>Using MacX on a Mac LC, we try to run the same Xapplication (dxclock) over
>DECnet an the Ultrix server and get the error message:
>
>remote command "Clock (DECnet)" (this name is defined as dxclock) could not be
>executed via the tool "DECnet Tool". Creation of the remote command stream
>failed.
>
>Yet, if we log on to the Ultrix server from either the Mac or PC and type:
>
>setenv DISPLAY <nodename>::0.0
>
>we can run dxclock and the application is re-directed to the Mac or PC
>successfully.
>
>Is there something else we must do on the Ultrix server to make eXcursion or
>MacX run X applications successfully?
>
>Any help appreciated,
>
>Margaret
>--
>AusMail: Margaret Cowley, UniSA, Schulz Building, Kintore Ave.,Adelaide,SAust.
>E-Mail : cowleym@schulz.unisa.edu.au, Phone:+61 8 301 1617, FAX:+61 8 301 2602

Yes, you are missing something... on a VAX, there is a command file which 
is being fired first (transparently) called msax$client.com (I think it 
is in msa$root:[msa]... it might be useful for you to look at it).  It 
accepts your 'remote command' and manages the display environment for 
it.  For pc's, there is an equivalent file, but I cannot recall its name.  
Neither of these will exist on Ultrix, or on any system other than a VAX 
running PathWorks.  (BTW, if you decide to translate 
msax$client or the PC equivalent to a script file, please mail me a 
copy...)

Try the following:

o try having the 'remote command' be 'dxclock -display <pc_node_name>::0'
  (I believe this is how we handle it...)
  
o Instead of trying to run the application directly, have the PC fire a 
  script file which does: dxclock -display <pc_node_name>::0

bob
--
RW Salnick, Spokane,WA  |  Home: salnick@dejavu.spk.wa.us
  Amiga 1000, WB 1.3    |  Work: mfgsys!salnick@kaiser.spk.wa.us
      WA9BVE            |