I should also add that after a setup.exe crash at 9:38am after being left running overnight, later attempts to install that day (with the VM size steadily increasing, and setup.exe appearing to "stick" at the stage where it is installing the zip package), that setup.log was not updated by the later installation attempts.
Shouldn't setup.log be getting opened in append mode? We examined it at various times during a later installation attempt, and the contents didn't change and the file modification time stayed at 9:38am.
At the moment, the log files are written to disc in one bulk write when setup.exe completes. That's probably not a great design feature.
Max.
-- 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/
