my2001 Posted October 21, 2004 Posted October 21, 2004 Sometimes a program called by command.x directive doesn't end itself properly. Instead it waits endlessly for something to happen which isn't going to happen. Conclusion: WIHU won't continue its work because the sub-process isn't finished yet ... and never will be. Only way to continue with Windows installation is to abort WIHU and leave out the remaining installations.Is there a possibility to give the user in WIHU the chance to abort the processing of a crashed installation program and let WIHU continue with the remaining installations?Another off-topic question: what about your changelog? is it still kept update?
BenjaminKalytta Posted October 21, 2004 Posted October 21, 2004 Another off-topic question: what about your changelog? is it still kept update?No not really. But I don't modified wihu log file behaviour. Well do it may be on weekend.Is there a possibility to give the user in WIHU the chance to abort the processing of a crashed installation program and let WIHU continue with the remaining installations?I could add this. May be on weekend.Benjamin
BenjaminKalytta Posted October 22, 2004 Posted October 22, 2004 I changed this, please download new WIHU version. There is a "Cancel" button near the progress bar which may be pressed to cancel current running process. Please note, interrupting currently running software installation may cause serious system errors!Benjamin
my2001 Posted October 22, 2004 Author Posted October 22, 2004 Auch hier recht netten Dank, ich brauch' des wirklich, des hilft mir Probleme mal kurz ausm Weg zu räumen und dennoch den Rest der Installation zu erleben. *hihi*Ähm ... just a further proposal, of course, it's up 2 u 2 implement it: maybe not activate the cancel button immediately, maybe after a timeout period of perhaps 5 minutes per each installation step to avoid misuse. I think this isn't unimportant because many use WIHU to perform a completely unattended installation and don't want to offer the user any possibilities to interfere. So a timeout could help here. And maybe you could even add an ini setting like Timeout=<Sek> or timeout.x=<Sek> ... but as I said: up 2 u!
BenjaminKalytta Posted October 23, 2004 Posted October 23, 2004 Yes nice idea ... I also tought about this. I changed it this way that Button will be showed after 1 minute for each process. (timout is 1 minute)Benjamin
my2001 Posted October 24, 2004 Author Posted October 24, 2004 Okay! 1 minute should be enough for most processes.
my2001 Posted October 26, 2004 Author Posted October 26, 2004 Hhm ... cancel button is shown but greyed out, can't click on it!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now