On Mon, Dec 23, 2013 at 3:38 PM, Art Heimsoth <artstore@artheimsoth.com> wrote:
 
> It looks like there is some registry redirection involved here that
> I'm not aware of.

I don't have that key on my system (a 32 bit Win7 system), so I think
it may be something more/different.

I think it is essentially the same.
 
 
If I uninstalloosqlite, then install ooRexx including to remove the oorexx
folder content on the uninstall, then run oosqlite install, all works okay.

The ooSQLite installer writes some uninstall information to a registry key.  The uninstaller deletes it.
 
If I do not first run the uninstalloosqlite, then the subsequent oosqlite install
(after ooRexx uninstall/install) fails immediately after the Welcome panel
and before the normal License panel.  It appears there is something being
tested before that Nsi section that is failing.

Yes, the installer reads the the uninstall information from the registry key.  If it exists, it assumes ooSQLite is installed.  Then, if ooSQLite is installed, it tries to test that there is no ooSQLite program running and that the PDF doc is not open.  It does that by copying the two files and then trying to delete the originals.  If the files do not exist this fails

So, when you uninstall ooRexx by deleting the whole tree, the registry key is not removed.  The files are deleted and when you go to install ooSQLite it fails as described above.
 
 
BTW, where is the ooSQLite nsi script in svn?

Here:

svn+ssh://miesfeld@svn.code.sf.net/p/oorexx/code-0/incubator/ooSQLite/install/platform/windows/

--
Mark Miesfeld