Conference bulova::decw_jan-89_to_nov-90

You could make dxue run something like:
PATH='$PATH newpath' ; export PATH ; application

Then, application will have newpath in its search path.  I don't know if that's
exactly what you want, but it's the best interpretation of your question I 
can think of.

For the interactive prompting, you have a couple of possibilities.  You could
use the (undocumented) method that the file manipulation scripts use which 
pop up those little dialog boxes.  For your case, the script would look like:

#!/bin/sh

NODE=

echo 'Choose a node' 'Node:' `hostname` >& 2
# 'Choose a node' will be the title
# 'Node:' will be the contents of the text field label
# `hostname` will expand to the local host which will be the default contents
#    of the text field
#  All this is passed back to dxue on stderr, where it gets turned into a
#    dialog box
read NODE
#  $NODE will contain the contents of the text field if the user hit 'OK'
#  It will be empty if the user hit 'Cancel'
case $NODE in
  ?*) run command to $NODE
#  User hit 'OK', so do the command
      ;;
  *)
#  User hit 'Cancel', so exit without doing anything
esac

For this case, you have to set the 'Append selected files to command' bit in
the 'Edit Menus' db for the item that fires off this script.

The other method would be to fire up an xterm with a script running in it
that prompts for a node name and runs the command.

The command line would look like 'xterm -e do_app_on_node', and do_app_on_node
would look like:

#!/bin/sh

echo -n 'Node please? '
read NODE
run command to $NODE

				Jeff

For starters, RISC programs take up almost 3 times the space of VAX programs.
To be reasonable, I'd say that 300(risc) Mb = 100 (VAX) Mb. 

I believe that the NFS connection to the ultrix connection disk is related, and 
not related. What that means, is without the NFS files, mounted, I still have
the problem, even from a fresh boot.

However, the FIRST time I mounted the nfs file system into my PMAX, I mounted
it under /tmp. I then soon relized that that wasn't so swift, as the boot
procedure clears /tmp. In any case, my /tmp is now racking up the errors, and
the color map mapping as you can from .0, is not so good.

yeup, xsh is pretty good, but it doesn't run under VMS, unless VMS started 
supporting forks. I use xsh a little bit, but it would be a LOT better if
I could find the mandlebrot and other images that it was coded for, because I
don't have a UIL file that was used to create the xsh.uid that I currently use.
I would eliminate that section (since it hangs if it cannot find the image(s))
if I had the right uil file.

In any case, using xsh doesn't solve my path problem with dxue, and I'm sure
that someone has delat with this problem before. It's a problem with VMS too,
but can easily be solved (in my (vms) mind).

     This note was the first reply written, but I had to recall it
     to make some corrections.  Some other notes sneeked in.
     You can figure out the rest.   Sorry about that.
    RE .0
    
    I don't quite get it - why do you think the "RZ55 is just not enough
    space"?  This disk has about 325 meg!
    
    The XIO errors you get could be due to bad TCP/IP setup.
    "so I added he Ultrix Connection to it" (PMAX?) - How did
    you do that?  Is this your vehicle for inter-operating VMS
    and ULTRIX X11 applications?  If so, then good luck!
    Or are you using UCX as an NFS file server for ULTRIX
    executables?  
    
    Re. Ultrix File Viewer (UE).
    
    Using shell scripts and dxue could be quite cumbersome and resource
    consuming, so why not try something else?
    You will find an example program in /usr/demo/dwt called "xsh".
    This is a DECwindows application that will do exactly what you want. 
    The same Xshell program was customized for use in demonstrating
    the rolling PMAX applications.  Please check it out.
    
    BTW:  I thought Jeff Dike wrote the original xsh program. no?
    
    	   							kris..
                                                        

The ratio of MAX executables / VAX executables is about 1.3.  The COFF symbol
is a lot larger than its equivalent on VAX.  Strip your MAX executables and you
will be down to about 1.3.

What images are you talking about with respect to xsh?  If you're talking about
the same xsh that appears in /usr/demo/dwt, there are no images or anything else
except the uid file it reads.  The uil file that generated xsh.uid is xsh.uil
in that directory.  It is the same as one of the other uil files.  I forget
which one I made the default.
				Jeff

Nope, another one, that had come with a tape of some other various demos.
Apparently, it had been modified to include some of the mandlebrot images, 
as well as some nice looking .rgb images for xpaste. 

I'll look into strip. The UCX product is working quite nicely, actually, 
although it would be nice if it would give some more feedback as to WHAT I
might adjust should anything need tuning onthe VAX end.

I have also learned that export is in the bourne shell, so I'll have to try
running dxue under that shell, to use export. Is there a similar feature under
the c-shell?

Thanks,
-Ken

% set path = ( dir1 dir2 dir3 ...)

    Thanks all, and especially to Jeff Dike to helped me off-line. The
    biggest drawback to Ultrix dxue, is that there is currently no way to
    dynamically have a child process, created by dxue, to modify the
    DISPLAY variable, for subsequent child processes from the parent dxue.
    
    -Ken