I just wanted to let you know that we received your message, and we're looking into the problem. Using the current version of Cygwin I was able to duplicate your problem: crux fails, but doesn't provide any messages or warnings. I should have an answer for you tomorrow.
Thanks for letting us know about this problem!
Charles
On Aug 18, 2011, at 11:35 AM, Arie wrote:
>
> Did you have any luck fixing the issue? Thank you!
>
I'm not sure why the binary distribution of Crux 1.35 for Cygwin is failing. When I run any of the Crux tools from that distribution on a current version of Cygwin (1.7.9), I get exactly the results you found: no warnings, no messages, and no output. It is clearly failing almost immediately. However, when I build a fresh copy from the Crux 1.35 source, everything seems to work just fine. We definitely tested the Crux 1.35 distribution on Cygwin before putting it up on the web site, so my only guess is that there have been changes to the runtime libraries for Cygwin that keep Crux from working.
I built and tested a binary distribution of Crux 1.36 for Cygwin 1.7.9 and that is now available on the Crux web site. Could you download and install this new release and see if that resolves the problem?
Thanks for reporting the problem, and our apologies for the inconvenience.
Charles
On Aug 18, 2011, at 3:07 PM, Arie wrote:
> Yes, Crux 1.36 seems to work just fine with Cygwin, thank you very
> much!
Excellent!
> Do I understand correctly that with the version 1.36 I'll be able to
> search for post-translational modifications?
Well, Crux has supported post-translational modifications since about 1.20. Support for post-translational modifications is a new feature for the new release of Tide, but unfortunately Tide is not currently available for Cygwin.
Please don't hesitate to let us know if you have other questions.
Charles