Thanks Pete, that was educational *and* helpful. Here's how it went...
>Well, this looks similar to the dreaded import_ncdf problem believed fixed
March
>2 that did not appear to affect wintel ( my Feb 10 opendx-cygwin does not
show
>symptoms of this problem on NT and exceed 6.0.2). Maybe it does affect 98
and
>or Exceed 6.2 . What's the build date on your ui...help...product
information?
My ui build date is also 2/10/00.
>I'm not clear if all "watermolecule.dx"-type samples do not work for you
or if
>every conceivable visual program causes dxexec to die.
I am having this problem (can't execute vp's) with all the *.net files in
the samples/tutorial directory that I've tried.
>You might also try the following interactively:
>dx -script (actually you will type opendx -script to get the right
environment)
>dx> a=Import("/actualpath/watermolecule.dx");
>dx> b=Isosurface(a);
>dx> c=AutoCamera(b);
>dx> d=Display(b,c);
>type the equations in response to the dx prompt, remember the semicolons
>(cut-and-paste?), and you should get a display of an isosurface of
>watermolecule.dx .
And it works! I like this script stuff, very cool :)
OK, well I still have the problem I had before, but now I think I know that
this is simply a matter of getting the path right in the Import module
(because with the right path, the script method worked).
But why can't Import in example1.net find the data file?
The example1.net file is in
/usr/local/dx/samples/tutorial/
while watermolecule.dx is in
usr/local/dx/samples/data/
Also, my opendx.bat has
SET DXDATA = \usr\local\dx\samples\data
(I guess this is the relevant env variable?)
But apparently, Import can't find watermolecule.dx! The "name" string is
simply "watermolecule.dx", which apparently isn't working. Shouldn't opendx
automatically be appending the "name" string to the DXDATA path when it
looks for the data file? Why doesn't this work?
Another problem is that whenever I open the Import module in example1.net
(or any other *.net I've tried), I can't successfully edit the "name"
string. I change it, but next time I open the module, it has changed back
(I even hit "Apply"!). This appears to be a bug of some sort, but a
relatively trivial one.
(However, if anyone knows how to fix it, that would be great.)
So to get around all this, I edit the example1.net file directly, replacing
"watermolecule.dx" with the UNIX-style pathname
"/usr/local/dx/samples/data/watermolecule.dx".
Now I can load and execute example1.net successfully, and everything else
seems to be working. Can't wait to play with this some more, and put in
some of my own data!
Thanks a million!
-Noah
ps-- I still get a <can't open user's module description file "".> error,
though I'm not too worried about that. Should I be? To my knowledge, I
don't have a user's module description file.
