On Sep 17 10:57, sven-eric.ber...@sanofi-aventis.com wrote: > Hi, > > I have windows 2008 R2 servers with cygwin 1.7 installed. > When i want to execute the cluster.exe command, I have : > seber...@flosapptest02 /cygdrive/c/windows/system32 > $ ./cluster res > bash: ./cluster: No such file or directory > > On a DOS prompt the command works.. > > Then I do a 'ls cluster*' in the bash session : > seber...@flosapptest02 /cygdrive/c/windows/system32 > $ ls cluster* > ls: cannot access cluster*: No such file or directory
You're on a 64 bit system and the cluster command only exists as 64 bit application in the 64 bit system32 directory. Due to the Windows file redirection for 32 bit processes, if you cd into /cygdrive/c/Windows/System32, you're actually in /cygdrive/c/Windows/SysWOW64. What you want to do is to cd into /cygdrive/c/windows/Sysnative. You'll find the cluster command there. Note that this is not a Cygwin problem, but one of the many weird properties of 64 bit Windows OSes. It would have been so much easier for everyone if the directory containing the 64 bit applications and DLLs would have been named /cygdrive/c/windows/System64, but here we are. See http://msdn.microsoft.com/en-us/library/aa384187%28VS.85%29.aspx for details on the file system redirector. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
