Hi Charles,

> Unfortunately the bug seems to still be there in the custom uninstall
> scripts.
>
> I've sent you the scripts (which worked fine in the SetupBuilder version
> that supports Clarion 10).
>
> Let me know if I need to test anything or give you any other information.

IMO, it's not caused by the previously mentioned (and fixed) uninstall bug.
This was only a bug in "standard" uninstaller projects - caused by the new
"Disable CR/LF Handling" flag in the "Display Message Box" function. I
forgot to add this new flag to the standard uninstall script. As a result,
the uninstaller did not work at all. In a custom uninstaller, the compiler
added it automatically.

So there must be another cause for it. IMO, the compiler does not resolve
one of your compiler variables which holds the name of your product.

Friedrich