I would like to add my experience with Cygwin/Opendx to this discussion as I
am a little further along the track.  However, I have come up against a new
problem.

1. I am running Cygwin/Opendx on a NT4 system.
2. I had problems with setting the path to include /usr/local/bin in Cygwin,
so I added this directory as C:\Cygwin\usr\local\bin in my NT path settings
and this solved the problem.
3. After this dx would run but dxworker failed.  dxworker needs csh.exe (not
included in the Cygwin distribution) to run, I found this and it worked.
4. Opendx needs the cygXpm-X4.dll library (not included in the Cygwin
distribution), I found this and I got dx, dxworker and the Opendx menu up
under Xfree86.
5. Now to the problem that has stopped me.  When I try to run any Opendx
process from the menu, edit, samples etc., I get the following error
message.

        timeout waiting for response from dx
        Internal error detected at "MacroDefinition.C":631.
        No files needed to be saved.
                0 [sig] dxui 371 open_stackdumpfile: Dumping stack trace to
dxui.exe.stackdump

I would appreciate some help with this one.

Michael Morse
Australian Geological Survey Organisation
Canberra
Australia

-----Original Message-----
From: David Starks-Browning [mailto:[EMAIL PROTECTED]
Sent: Thursday, 21 June 2001 21:06
To: [email protected]
Cc: Kevin Slover
Subject: Re: [opendx-general] newbie needs help


On Wednesday 20 Jun 01, Kevin Slover writes:
> Question then about the permissions...I have searched through the opendx
> mailing lists, and have
> found no documentation on what permissions should or ought to be.  Is
> there an issue with the
> owner of the file, or is it the read/write/execute permission??  Being
> new to the whole x-server
> world, I am still attempting to understand this concept of running Unix
> programs in a windows

On UNIX, the main dx "dispatch" script would have the proper
permissions and all you would have to do is make sure the command was
in your $PATH.  So I wouldn't expect it to come up in the opendx
mailing lists.

With Cygwin, it gets rather more complicated, because Win9x (in
particular) has no concept of "permissions".  Cygwin implements a
workaround for this.  OpenDX developers with no Cygwin experience are
not likely to know about these details.

I've not tried OpenDX on Cygwin myself, so I'm not sure what's gone
wrong.  I recommend you read the Cygwin FAQ entry "Why doesn't my
shell script work?", then look at your dx scripts and see if you can
spot the problem.

If this gets much more complicated (and is not otherwise relevant to
OpenDX in general), it might be more appropriate to take this to the
cygwin or cygwin-xfree mailing list.

Hope this helps.

Regards,
David (Cygwin FAQ maintainer)

 -------------------------------------------------------------------
  David Starks-Browning                  | [EMAIL PROTECTED]
  EMBL Outstation --                     |
  The European Bioinformatics Institute  |
  Wellcome Trust Genome Campus           | tel: +44 (1223) 494 616
  Hinxton, Cambridge, CB10 1SD, UK       | fax: +44 (1223) 494 468
 -------------------------------------------------------------------

Reply via email to