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?
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.
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 .
If there's a fatal bug in Import, an alternate net is CappedIso.net or an
alternate script derived therefrom is
dx> a=Construct({[-1 -1 -1]} , {[ 0.1 0.1 0.1 ]} , {[21 21 21]});
dx> b=Replace(a,a,"positions","data");
dx> c=Compute2("mag(abs(a) - [0.5 , 0.5 , 0.5 ])","a",b);
dx> d= Isosurface(c);
dx> e=AutoCamera(d);
dx> g=Display(d,e);
(quit exits).
Hope this helps, or is at least educational.
Pete
Noah Knowles wrote:
> Hi, I should point out that Bob and I are having different problems,
> actually...
>
> since installing 4.0.10, I am now able to start the tutorial, edit visual
> programs, etc just fine. It is only when I try to *execute* a visual
> program that I get the "Unable to connect to dxexec" error, with
> ACCESS_VIOLATION then stackdump and disconnected server. With 4.0.9, I was
> getting the problems Bob describes (ie tutorial won't start), but not any
> more.
>
> Nonetheless, I tried one of your suggestions, changing opendx so it will
> pass arguments to dx. "opendx -execonly" seemed to work, generating the
> following...
>
> ******************
> Starting DX executive
>
> Memory cache will use 24 MB (2 for small items, 22 for large)
>
> port = 1900
> ******************
>
> However, when I try to execute a visual program (ie, "Execute Once") I get
> the errors mentioned above and in my previous post.
>
> I am using Exceed 6.2 under Win98. Any more insights?
> Thanks.
> -Noah
>
