Setup.exe seems to hang

luke.kendall@cisra.canon.com.au luke.kendall@cisra.canon.com.au
Tue Sep 2 03:46:00 GMT 2003


One of the people here is trying to install Cygwin for the first time
ever on his Win2k PC.  We update a mirrored copy of Cygwin nightly, and
install from that on our local network.

The problem he's having is that when getting to the stage of trying to
change the installation type from "default" to "install", the machine
just goes very busy and doesn't complete (e.g. it was left running
overnight).

FWIW, this step in the setup process is always the most troublesome in
my experience - on some PCs here you click on Default or the icon and
you can cycle through the options with less than a second delay.  For
many other PCs, each click can take up to 3 minutes of intense CPU
activity before the state cycles on to the next (Default, Install,
Uninstall, Reinstall).

What *is* setup doing at this point?  I had assumed it was checking MD5
checksums of the files, but that wouldn't explain the huge variation in
responsiveness from PC to PC here, all on the same network.  I can't
say I've noticed any difference between Win2k and XP machines - I've
never been able to find a pattern in what makes one PC slow in this
regard.

BTW, the fact that setup.exe gives no visible indication (busy cursor)
to let you know that it's actually doing something, often leads to a
lots of counter-productive clicking.  It can also lead to accidental
uninstallation (you see Install, click on Next, but don't realise you
are 4 minutes and 2 clicks behind ...)

Anyway, any suggestion about setup.exe just going busy?  We're going to
try installing the Default stuff, then run it again and see if we can
choose to install everything after that.

luke


--
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/



More information about the Cygwin mailing list