It sounds to me like it couldn't find the dx script in the path when dxstartupi tries to exec other OpenDX executables. What happens if, in a DOS window in some arbitrary directory, you run Opendx.bat, then try to execute dx from the command line? I bet it fails, which means that the dx script isn't in the path Opendx.bat sets up, and which the StartupUI uses when it tries to spawn other OpenDX executables. Thats where this is failing - when you try to open the tutorial from the StartupUI (or any other part of DX), it formats up a command line to cause the dx script to start the requested executable (something like "dx -tutorial") and then execs the command line, expecting the dx script to be found . The message you are getting is because the dx script isn't found.
Greg "Robert Schwartz" <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 03/24/2000 08:05:44 AM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: <[email protected]> cc: Subject: Re: [opendx-users] trouble with 4.0.10 Hello, I am having the same problem that Noah describes: DX opens with the window showing Tutortorial and other buttons, but an attempt to open the Tutorial fails, as does an attempt to open a sample file *.net. The error is DXLStartChild: Could not connect using 'dx' (in my DOS window) and "Cannot connect to dxec" in a DX error message. Here is my Opendx.bat file, to which I added the line SET DXMACROS after reading the last message from Suhaib in response to Noah. Does any one see the error in that file that makes it impossible to connect to DEXEC? Thanks, Bob Schwartz Mount Holyoke College REM @ECHO OFF SET DISPLAY=127.0.0.1:0.0 SET PATH=C:\usr\local\dx\BIN;C:\usr\local\dx\BIN_CYGWIN;C:\usr\X11R6.4\bin;C\usr \local\dx\etc\ %path% SET DXROOT=\usr\local\dx SET DXDATA=\usr\local\DX\SAMPLES\DATA SET XKeysymDB=C:\usr\local\DX\bin\XKeysymDB SET XErrorDB=C:\usr\local\dx\bin\XErrorDB SET DXMACROS=C:\usr\local\dx\java\server\dxmacros REM BY RS SET DXexec=C:\usr\local\dx\bin\BIN_CYGWIN\DXEXEC REM BY RS SET DXUI=C:\usr\local\dx\bin\BIN_CYGWIN\DXUI REM SET LC_ALL=C:\usr\share\locae REM SET LC_CTYPE=en_us REM SET LANG=C REm SET XLC_LOCALE=C:\usr\share\locale REM SET XNLSPATH=C:\usr\share\locale\iso8859-1 REM Leave the / (forward slash) as it is. It is not a typo. Cygwin needs it to set your $HOME SET HOME=C:/ SET HOMEDIR=C:\usr\local\dx SET USERDIR=c:\usr\local\share SET BitmapDir=C:\usr\local\share\bitmaps rem cls dx ----- Original Message ----- From: "Suhaib M. Siddiqi" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, March 23, 2000 1:25 PM Subject: RE: [opendx-users] trouble with 4.0.10 > > > > Hi, after experiencing multiple problems with OpenDX versions > > 4.0.6-9 on my > > Win98 laptop (a Quantex I-1511), I am delighted to find that I am having > > only one problem with 4.0.10 (besides numerous XtWarnings which > > Suhaib said > > to ignore). > > Depends which Xt warnings to ignore. If the Xt warnings relates to > XkeysymDB then > your keyboard will not work. Exceed itself has problems withits own > XKeysymDB. Checkout their Knowledge base database at > http://www.hummingbird.com, for a work around. > > > > > This one problem is, however, prohibitive. > > Whenever I try to open a *.net file, I receive an "Unable to connect to > > DXexec" error. > > Have you made sure that your DXROOT and DXMACROS etc are set properly in > Opendx.bat. > > Regards > Suhaib > > > > > I have tried all the transport settings in Exceed, and am having no other > > problems opening X-windows, either locally or from remote servers. I can > > ping localhost and localpc fine, and Exceed is configured as suggested. > > > > Am I missing something? Has anyone else had this problem? > > Thanks again to the list for your help. I hope to contribute more than > > questions some day. > > > > -Noah > > [EMAIL PROTECTED] >
