That's also good stuff to know. I'm escalating these issues to management, they will have to decide. Cygwin is a requirement of a new project. So something will have to give one way or the other! Many thanks guys. I really appreciate the assistance. -Frank
________________________________ From: cygwin-ow...@cygwin.com on behalf of Jeremy Bopp Sent: Fri 4/30/2010 12:23 AM To: cygwin@cygwin.com Subject: (nwl) Re: (nwl) Re: Installation problems - post install scripts all give "abnormal exit: exit code=128" Crow, Frank wrote: > But let's say that BLODA is the problem... and I'm not allowed to remove the > offending software. Can I do something like install Cygwin on a different > machine and then copy over the entire C:\Cygwin? I'm betting not, but I'm > asking just in case. Yes, even though it's not supported, you could copy an installation from one system to another, but you'll most likely run into failures as soon as you try to do much of anything with the installation. BLODA usually interferes with the general operation of Cygwin applications, not just setup.exe. If Cygwin addresses a business need, perhaps you'll be able to argue for an exemption from the BLODA on a handful of systems. Good luck! -Jeremy -- 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 -- 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
