Hi - It has been noted that the problem might derive from a conflict with another application (BLODA - http://cygwin.com/faq/faq.using.html#faq.using.bloda).
But, I am using a clean install of: Windows Server 2003 Standard R2 X64 Windows Resource Kit Tools Cygwin That's all. Further, using the same VM (an exact block level copy), cygwin works on one set of hardware and not on another. It truly does appear to be a hardware dependent problem with bash. Stephen -----Original Message----- From: Stephen Quintero Sent: Wednesday, August 06, 2008 9:08 AM To: 'cygwin@cygwin.com' Subject: bash builtin "test" kills bash on Win 2003 Server R2 x64 (some hardware) This subject has been raised before in this thread: http://sourceware.org/ml/cygwin/2008-01/msg00579.html but I cannot find any resolution of the problem. In my case, I built a Win 2003 Server R2 x64 SP2 virtual machine under xen on one physical machine and cygwin worked fine. Copying the VM to another physical machine, with identical dom0 OS / Xen install results in the indicated failure. Using "bash -livx" the shell immediately exits when it hits the first test in the login script: [ ! -d /home/Administrator ] Removing cygwin and doing a clean install over the internet results in a broken install (postinstall scripts fail because of broken "["). You can now get a bash shell, since there is no login script, but without any environment. If you enter "[ -d /bin ]" the broken shell terminates. Attached is the output of cygcheck after the clean install on the machine which does not work. Any insight into this problem would be greatly appreciated.
