-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://cygwin.com/acronyms/#PPIOSPE
According to Sarcar, Shourya C (GE Healthcare) on 10/27/2005 1:29 AM: >>Now it looks like you have two copies of cygwin installed, >>and that c:\insite\bin is still trying to compete with >>c:\cygwin\bin. Cygwin does not work well if you have two >>copies of cygwin1.dll, even if the two copies are the same >>version. I don't know what insite is trying to provide, but >>it is probably the source of your problems. > > > > Thanks for the help. I am struggling with a legacy system, so do not > have the answers right away. > I will try to establish some sanity and then ask some more questions if > I am still stuck. > > Is there a specific reason why two versions of Cygwin do not coexist > well ? Yes. cygwin1.dll shares memory between all cygwin processes, and if you have two versions of the .dll, the shared memory region is incompatible between them and you are practically guaranteed a crash or other unexpected behavior. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDYMGd84KuGfSFAYARAn5bAJ9u8WMyrpCjklzgcJI0NDrIkzU3sQCaApBH XJNop1P8HlRghpIE/SjPW0g= =BkZl -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
