From: Mark M. <mie...@gm...> - 2012-04-02 00:34:20
|
On Sun, Apr 1, 2012 at 7:46 AM, Mike Cowlishaw <mf...@sp...> wrote: > Not really a bug, and for the next release probably ... I just tried the RC > install, and do like the "quick install, don't change anything" option. > Unfortunately it didn't work for me -- I'd closed all my command windows (which > run Rexx as the shell), but forgot web servers and Wikis (which run Rexx as > filters). Hence, although the uninstall appeared to work fine, the install > failed with 'unable to replace Rexx.dll' dialog (repeated x 5, I think). > > Cancelling the install and closing those things that were using Rexx worked, but > I wasn't offered the 'quick install' options on the next try. Hi Mike, Yeah, that would happen. In NSIS the install and uninstall programs are completely separate. For the quick install option, the installer reads the ooRexx registry entries into memory. If the registry entries indicate a quick install is an option, then the current path and PATHEXT are also read into memory. Then the uninstall program is called. The uninstall program uninstalls everything, including removing the installation directory from the path and .rex from PATHEXT. It has to because it is the same program that is run when the user wants to completely uninstall. When the uninstaller finishes, the instatller regains control and starts installing. The new ooRexx registry entries are written to the registry after the files are all installed okay. So, in your case the new registry entries would not have been written. When the installer was run the next time, there would be no registry entries to indicate a quick install was an option. And, really it would not be an option. Part of what the installer would need to know is exactly what directory the old ooRexx was installed in, which is completely unknown at this point. I'm not really sure if there is a good way, or even any way, to handle this case. I'll have to think about it. -- Mark Miesfeld |