I need to run OpenDX, and the Linux binaries for Redhat 6 don't seem to be available on opendx.org anymore (only 7.1), so I decided to go the Cygwin route:
I used the instructions for 'Windows 95/NT based on OpenDX v4.1.3' (http://opendx.npaci.edu/bin/README.windows). I installed: Cygwin (1.3.2, I think - this was barely on Aug. 16, 2001), using 'setup.exe', then: Cygwin/XFree86 (4.1.0?) (same day), using the instructions in the 'Cygwin/XFree86 User's Guide' (http://xfree86.cygwin.com/docs/ug/), then: opendx-4.1.3-cygwin.tar.gz (same day), using WinZip (oops, I know - see below). At the bash prompt, I typed 'dx', and got: 'exec: /usr/local/dx/bin/dxworker: not found' (hereafter, the 'exec:' error), even though the file was clearly there (I could list it with 'ls /usr/local/dx/bin/dxworker'). I began looking for help in the E-mail List Archives from the Support page on the opendx.org site. I found some references to this error and tried those fixes (which obviously didn't work), with my results and the original posting links listed below: ANNOUNCE list - no help DEV list - no help GENERAL list - no help USERS list: * I don't think it's a text vs binary problem - or at least 'dxworker' doesn't have '\r\n' at the end of each line (cf. Jean-Luc Vay's problem - http://opendx.npaci.edu/mail/opendx-users/2000.08/msg00029.html) * I originally unzipped 'opendx-4.1.3-cygwin.tar.gz' using WinZip, but I went back (after finding out that was bad) and re-unzipped it using 'tar xvzf opendx-4.1.3-cygwin.tar.gz' from /usr/local ('opendx-<etc.>' was there), with no difference - same 'exec:' error. (I was considering clearing the files that were created and doing it again, in case files were left from the WinZip operation, but I don't know what's supposed to be in '/usr/local/', and thus what to remove and what to leave.) (I'm not sure where I read that using WinZip was a problem) * I have both /usr/X11R6/bin and /usr/local/bin in my PATH (using 'export PATH=/usr/X11R6/bin:$PATH'; /usr/local/bin was already there) * I think I have binary mount points, but here's the result of the 'mount' command, verbatim: C:\cygwin\bin on /usr/bin type system (binmode) C:\cygwin\lib on /usr/lik type system (binmode) C:\cygwin on / type system (binmode) c: on /cygdrive/c type user (binmode,noumount) * Both 'dx' and 'dx -edit' give the same results (the 'exec:' error) (cf. Yang Wang's problem - http://opendx.npaci.edu/mail/opendx-users/2001.07/msg00001.html) * I have both 'dx' and 'dx.exe' in /usr/local/dx/bin, as well as 'dx' in /usr/local/bin (identical to the other 'dx'); moving 'dx' from /usr/local/bin (to an inaccessible Windows folder) then typing 'dx' (from /home/default) produced: 'BASH: /usr/local/bin/dx: No such file or directory'; after moving it back (typing 'dx' now produces 'exec:' error above), moving either or both of 'dx' and 'dx.exe' from /usr/local/dx/bin and typing 'dx' produced the same 'exec:' error as before. (Note: typing the full path name, i.e., /usr/local/dx/bin/dx (or dx.exe) produces 'error: No such file or directory', while the same path but a garbage filename like 'dxgrlf' produces 'BASH: /usr/local/dx/bin/dxgrlf: No such file or directory'. I don't know why the difference, or if it's even relevant. Just an observation.) (cf. Cameron Huddlestone-Holmes's problem - http://opendx.npaci.edu/mail/opendx-users/2001.08/msg00005.html) * I have 'csh.exe' (in /usr/local/dx/bin/csh.exe - though I noticed that /usr/local/dx/bin is not in my PATH - which is as follows: /usr/X11R6/bin:.:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/WINDOWS:/cygdrive/ c/WINDOWS:/cygdrive/c/WINDOWS/COMMAND:/cygdrive/c/TEXMF/MIKTEX/BIN:/cygdrive /c/GSTOOLS/GS5.50). I wasn't sure if I should do the 'ln -s tcsh csh' thing (see link, below), since I don't really understand the intended effect of the suggestion (i.e., I already have csh; should I just put that folder in my PATH? Should I link tcsh to csh instead? Or something else altogether?). (cf. Cameron Huddlestone-Holmes's problem - http://opendx.npaci.edu/mail/opendx-users/2001.08/msg00006.html) So that's where things stand right now. Sorry this is so long, but I didn't want to waste anyone's time on suggestions I could have done (and did do) on my own. Any ideas, please let me know. Thanks! -Robert Bruntz [EMAIL PROTECTED]
