I'm writing an app that runs a batch of installation packages (vbscripts). Some of these packages require reboot, others do not. the user selects the apps they want from a list and clicks install. My app creates a list of installation paths in a file on the root of the c drive.
example:
\\server\share\app1\setup.vbs
\\server\share\app2\setup.vbs
etc...
Any packages that require reboot are moved to the end of the list. Each time a package is installed, it's path is removed from the ini file, and the next path is read and executed. If any package is selected that requires reboot, then automatic logon keys are added to the registry.
Okay, assuming all that jabber is clear, here is my problem. If a package requires reboot, the vbscript does the actual rebooting. My VB app is sitting there waiting for the script to finish, and when the script tries to reboot I get a msgbox that says "Cannot Quit", and the Vb app just won't seem let go unless I force it to end.
Any thoughts/feelings/questions/criticisms/unicorns will be greatly appreciated.
-Dan
example:
\\server\share\app1\setup.vbs
\\server\share\app2\setup.vbs
etc...
Any packages that require reboot are moved to the end of the list. Each time a package is installed, it's path is removed from the ini file, and the next path is read and executed. If any package is selected that requires reboot, then automatic logon keys are added to the registry.
Okay, assuming all that jabber is clear, here is my problem. If a package requires reboot, the vbscript does the actual rebooting. My VB app is sitting there waiting for the script to finish, and when the script tries to reboot I get a msgbox that says "Cannot Quit", and the Vb app just won't seem let go unless I force it to end.
Any thoughts/feelings/questions/criticisms/unicorns will be greatly appreciated.
-Dan