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] > > R Schwartz wrote: > > > Suhaib, > > > > Many thanks: I'm using DX 4.0.10. Yes, and Exceed 6.2. I'll try another > > X server, I guess. > > > > Bob > > [EMAIL PROTECTED] > > ----- Original Message ----- > > From: "Suhaib M. Siddiqi" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Friday, March 24, 2000 9:20 AM > > Subject: RE: [opendx-users] trouble with 4.0.10 > > > > > > > > > > > > DXLStartChild: Could not connect using 'dx' (in my DOS window) > > > > > > > > > Which version of DX? if it is one of those experimental, with Xceed > > > ;libs, then you have no luck, Xceed 6.2 libs are very buggy. After > > > a lot of argument Hummingbird ackowledged the problems and said they will > > > fix it - do not know when. > > > > > > Suhaib > > > > > > > > > > > > > > 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] > > > > > > > > >
