The path for dxexec is based off of DXROOT. Here are some tests to
try. Try running dx by 1) Start the UI with dx -uionly & 2) start the
executive with dx -execonly & 3) connect the ui to the exec by going
to the connection menu, select connect to server, click options,
select already running server. I'd bet that if you're having
problems, you will not be able to perform step 2 and we may get more
info.
David
Hi,
I have serious troubles to run OpenDX on Solaris 2.5.
I downloaded the latest binary (opendx-4.0.10-solaris26.tar.gz) and
installed (gzip/tar)
the file in my home directory rather than /usr/local (due to restricted
permissions).
The DXROOT was set to $HOME/dx and the dx script was in the binary
search path.
The initial dx-windows came up including the Visual Program Editor
(according the procedure
described in the tutorial to load the example1.net file). Then, the
windows freeze and I got the
message 'unable to connect to dxexec'.
What can I do? Is the search path for dxexec 'hardcoded'?
The FAQs cover only the case to get a connection to the server in
general (FAQ D.3)
Thanks for any hints.
Regards
Sven
--
---------------------------------
Dr. Sven Hiller
Turbine Aerodynamics/CFD
Rolls-Royce Deutschland GmbH
Eschenweg 11
D-15827 Dahlewitz/Germany
Tel: +49-33708-6-1142
Fax: +49-33708-6-3292
e-mail: [EMAIL PROTECTED]
---------------------------------
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530