Wise legacy setup reboot
Hi,
I've spent all my day trying to prevent a wise legacy setup from rebooting the PC. No luck.
Tried to do catch loop in vbs, monitoring the install log, and killing the process, does not work.
Do you guys have any other solution? a switch for wise ?, a C++ code that could catch a restart exception and cancel it ?
I've spent all my day trying to prevent a wise legacy setup from rebooting the PC. No luck.
Tried to do catch loop in vbs, monitoring the install log, and killing the process, does not work.
Do you guys have any other solution? a switch for wise ?, a C++ code that could catch a restart exception and cancel it ?
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
timmsie
13 years ago
do you have access to the wse file or only the exe?
If you have the wse then you could set the RESTART variable to nothing at the end of the script.
otherwise you could use the whyreboot tool to determine why it wants a reboot?
If you have the wse then you could set the RESTART variable to nothing at the end of the script.
otherwise you could use the whyreboot tool to determine why it wants a reboot?
Posted by:
package_aligator
13 years ago
I have only the exe, can't capture it cause it's doing hardware changes. Can't believe there is no system registry or something to prevent processes from rebooting the pc.
Posted by:
kardock
13 years ago
no command line option? usually it's /NoReboot or /NoRestart or something like that.
have you tried /? or /help to see if options are available?
have you tried /? or /help to see if options are available?
Posted by:
anonymous_9363
13 years ago
can't capture it cause it's doing hardware changesHuh? What difference does that make?
Posted by:
package_aligator
13 years ago
The snapshot doesn't catch all changes and the application will not work as expected. The worst part is that I can't test the package as it requires certain hardware and only the client can test it and give a feedback on the package - basically I'm blindfolded.
So the easy way out was to use the setup instead.
In order to solve the reboot i decompiled the exe in assembly code, searched for the win API "ExWindowsEx" and replaced it with dummy code.
Please don't judge to harshly, sometimes you have to get your hands dirty in order to do the job.
So the easy way out was to use the setup instead.
In order to solve the reboot i decompiled the exe in assembly code, searched for the win API "ExWindowsEx" and replaced it with dummy code.
Please don't judge to harshly, sometimes you have to get your hands dirty in order to do the job.
Posted by:
anonymous_9363
13 years ago
What are you capturing with? Wise Package Studio, I'm guessing? If so, try using Smart Monitor.
Alternatively, you could install using the MSI created from the capture, rename the relevant 'Uninstall' registry entry, start up a loghtweight snapshot tool like InstallWatch, then re-run the vendor install. That will identify the INF, CAT and so on and you can then use a CA to run that part of the install.
I think you'll find that approach a lot easier than trying to swallow and redirect Windows API messages!
Alternatively, you could install using the MSI created from the capture, rename the relevant 'Uninstall' registry entry, start up a loghtweight snapshot tool like InstallWatch, then re-run the vendor install. That will identify the INF, CAT and so on and you can then use a CA to run that part of the install.
I think you'll find that approach a lot easier than trying to swallow and redirect Windows API messages!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.