Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
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?
Page 1 of 1
req: possibility to cancel command.x-process
Rate Topic:
Back to top
#2
- Developer
-
- Group: Members
- Posts: 609
- Joined: 08-June 04
Posted 21 October 2004 - 11:42 AM
Quote
Another off-topic question: what about your changelog? is it still kept update?
But I don't modified wihu log file behaviour. Well do it may be on weekend.Quote
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
#3
- Developer
-
- Group: Members
- Posts: 609
- Joined: 08-June 04
Posted 22 October 2004 - 08:48 AM
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
Benjamin
#4
- Member
-
- Group: Members
- Posts: 260
- Joined: 31-May 04
Posted 22 October 2004 - 12:42 PM
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!
Ä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!
#5
- Developer
-
- Group: Members
- Posts: 609
- Joined: 08-June 04
Posted 23 October 2004 - 03:19 AM
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
Benjamin
#6
- Member
-
- Group: Members
- Posts: 260
- Joined: 31-May 04
Posted 24 October 2004 - 03:39 AM
Okay! :) 1 minute should be enough for most processes.
#7
- Member
-
- Group: Members
- Posts: 260
- Joined: 31-May 04
Posted 26 October 2004 - 08:10 AM
Hhm ... cancel button is shown but greyed out, can't click on it!
#8
- Developer
-
- Group: Members
- Posts: 609
- Joined: 08-June 04
Posted 26 October 2004 - 08:57 AM
Sorry, I fixed this.
Benjamin
Benjamin
Share this topic:
Page 1 of 1