Thanks Achim and Larry for your responses and pointing out that setup.exe should be ran in a ms-windows console. But, another point I was making, is that in my opinion, setup.exe should not get into an infinite loop goobling up to 100% cpu usage, that setup.exe is out of control and indicates a design or coding flaw. So when ran with administrators priveledges, unexpected bad side effects might occur. Ideally, it would detect what ever is wrong and exit gracefully. If there anyway I help spot the e rrant code, please let me know and I would try to find a point where it breaks.
Regards Achim Gratz <strom...@nexgo.de> wrote: > > setup hangs in a tight loop when I try the following command from a cygwin > > console: > > You should start setup.exe from a cdm window, not a Cygwin console. > Once you do this, setup.exe does take a few seconds (or up to two > minutes if the package repository is on a network drive) from the time > the windows pops up and the packages are listed on the console and the > window becomes responsive again. > > > Regards, > Achim. > -- ... -- 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
