NewsArchive
04-07-2009, 01:51 AM
I created a custom uninstall script for the first time. Great feature!
The manual has a very good description of how to start up the customized
uninstall .sbi script. I had that initialized within a few seconds.
However, the manual is silent on the subject of what information (from
the install script) is available to the uninstall .sbi script at
uninstall time.
Realizing the uninstall script is compiled into a separate program from
the install, the first thought that came to mind was to use only
compiler variables. However, compiler variables can be
I set up a compiler variable [FILEPATH] in the .sbi. In the #include
directive, I configured [FILEPATH] with the value %FILEPATH%, which at
the point in the script where the #include is coded, contains a path to
a file my script wishes to delete. To my surprise, [FILEPATH] was
compiled into the .sbi as the string "%FILEPATH%". Not very useful at
uninstall time. <g>
Conclusion: This technique does not work with an uninstall .sbi.
Some words in the manual would be helpful as to when and how to use
"Include Script Compiler Variable configuration". (Something more than
"[in]") I don't know enough at present to know whether the above is a
bug or is working as intended.
I next removed the #set directive from the .sbi, reopened the project
and defined the [FILEPATH] compiler variable in the project definition
section. (With the value %FILEPATH%) With limited testing, this seems
to work. However, it occurs to me that the actual path in [FILEPATH] is
not known until installation time, so am curious how this actually worked!
The most certain method appears to be to store paths under keys in the
system registry, which my script will interrogate and use just before
the uninstaller removes the keys.
BTW, I am testing on 64 bit Windows 7. Your 2558 release message says"
> There is still one tricky Win64 uninstall bug to be fixed in SB6.
My Win 7 64 bit uninstalls seem to work fine with Clarion 7, except,
unless I first manually unregister all templates belonging to the
install I get an error message for each of the registered templates.
OTOH, responding "ok" to each error message is quicker and easier than
manually unregistering in Clarion 7! <g>
What should I be looking for wrt 64 bit uninstall?
--
Phil Carroll
http://www.enablingsimplicity.com
The manual has a very good description of how to start up the customized
uninstall .sbi script. I had that initialized within a few seconds.
However, the manual is silent on the subject of what information (from
the install script) is available to the uninstall .sbi script at
uninstall time.
Realizing the uninstall script is compiled into a separate program from
the install, the first thought that came to mind was to use only
compiler variables. However, compiler variables can be
I set up a compiler variable [FILEPATH] in the .sbi. In the #include
directive, I configured [FILEPATH] with the value %FILEPATH%, which at
the point in the script where the #include is coded, contains a path to
a file my script wishes to delete. To my surprise, [FILEPATH] was
compiled into the .sbi as the string "%FILEPATH%". Not very useful at
uninstall time. <g>
Conclusion: This technique does not work with an uninstall .sbi.
Some words in the manual would be helpful as to when and how to use
"Include Script Compiler Variable configuration". (Something more than
"[in]") I don't know enough at present to know whether the above is a
bug or is working as intended.
I next removed the #set directive from the .sbi, reopened the project
and defined the [FILEPATH] compiler variable in the project definition
section. (With the value %FILEPATH%) With limited testing, this seems
to work. However, it occurs to me that the actual path in [FILEPATH] is
not known until installation time, so am curious how this actually worked!
The most certain method appears to be to store paths under keys in the
system registry, which my script will interrogate and use just before
the uninstaller removes the keys.
BTW, I am testing on 64 bit Windows 7. Your 2558 release message says"
> There is still one tricky Win64 uninstall bug to be fixed in SB6.
My Win 7 64 bit uninstalls seem to work fine with Clarion 7, except,
unless I first manually unregister all templates belonging to the
install I get an error message for each of the registered templates.
OTOH, responding "ok" to each error message is quicker and easier than
manually unregistering in Clarion 7! <g>
What should I be looking for wrt 64 bit uninstall?
--
Phil Carroll
http://www.enablingsimplicity.com