Bob,
Symptoms you report in 6 are the result of dx running without the environment
set up correctly (as would happen when you just double-click on dxexec, if files
are missing, or if the directory structure is perturbed.).  Suhaib is right...
the directory structure needs to be left intact for it to work.  I don't know if
you moved the files or if we have an error in the packaging, you might shed some
light on that.
Pete

Robert Schwartz wrote:

> Greg, Pete and others,
>
> Many thanks: I have now gotten closer. The user interface opens, but I get a
> "file not found" error when I try to start the executive via "dx -execonly&"
>
> However, dexec will start in a second DOS window if I double-click on
> /bin/dxexec.exe in windows explorer. (The start window that I had been
> getting doesn't come up.)
>
> The tutorial starts in the user interface but when I try to excute the
> "example1.net"  I can not execute the open program, for the "run" options
> under the Execute Menu are grayed out.
>
> So here's what I've done:
>
> > Replace the last line of opendx.bat with "dx %1 %2 %3 %4 %5 %6" so it will
> pass
> > command-line arguments to dx.
>
> 1. Did this
>
> > Run opendx -uionly and opendx -execonly at separate prompts.
> > Whether dxui and dxexec start should be evident.
>
> 2. From Dos Prompts at \usr\local\dx\bin: opendx -uionly  worked;
>
> 2a. opendx -execonly failed with error "cannot find file"
>
>  >If they do not start, fix the PATH in opendx.bat .
> 3.  What should be the PART to the executive?  Which I take to "dxexec.exe"
> , or is it just "dx.exe"  Both of these programs are in usr\local\bin
>
> > If they start, then through the ui's connection menu, connect to running
> server.
> >
> > Once that works, terminate them and try opendx -edit .  With this
> argument, the
> > ui should start, and in turn start the executive and connect to it
> > automatically.
> >
> 4. opendx -edit  works: it opens the user interface
>
> 5. I can start "dxexec.exe" in a second DOS window
>
> 6. Among the error messages I get is "Cannot open user's description module
> . . . "
>
> Many thanks for further suggestions,
>
> Bob
> [EMAIL PROTECTED]
>

Reply via email to