Congratulations!
That might just be the most odd installation result ever reported in the last decade of our using this installer script!
Unfortunately you are a victim of a combination of managing to confuse the installer as to where the root folder for the install is and Windows deciding to “protect” your system and shoving everything into C:\ProgramData.
It’s not your fault, but rather just a combination of trying to override some patterns built into a very complex installer.
We use a single SetupBuilder installer script driven by Arnor’s Build Automator and a rigid file structure and some control files to build ALL of the templates we have.
That said the script is the most complex that Friedrich has ever seen (about 4000 lines) and it does have one nuance (explained below).
First off, recovery is easy.
Just run the uninstall and the installer will remove the files and shortcuts from where they ended up.
Now the fix.
Our installer using the standards agreed upon for 3rd party vendors back when C7 came out.
It also uses SetupBuilder’s ability to “detect” where to put things based on actual installs of Clarion (one ran from the installer - not just copied to a drive or location).
So when the installer runs it lets you know what “legit” installed (meaning it has Registry entries) versions of Clarion it sees and offers you the chance to just pick one.
It also offers a chance to pick a version of Clarion supported in the installer even if SetupBuilder was unable to detect it.
In both cases, the installer uses that to establish a “root” folder for the install.
In trying to change the root to “C:\Clarion11\accessory\LANSRAD” when no normal set of Clarion directories exist under that location you inadvertently set off a cascade of “bad or non-existent” paths in the installer.
Then Windows got involved and … well here we are !!!
So that’s the bad news.
The good news is that you can still put any file where ever you want it.
Just install again and tell the installer to Uninstall the old files, or run the uninstaller first.
Then just start the installer again and select the Custom install option.
Then VERY IMPORTANT click the button to BROWSE for a target folder (don’t just type it in - SetupBuilder does things internally after the BROWSE). Create the LANSRAD target folder as shown:
You should end up with this:
Then when you go to select the location for the examples, select this option and specify this folder (again using the BROWSE button). Note that you do NOT select the LANSRAD folder as it will be created for you by the installer.
Then select these options (as desired)
Your install will go here:
Note that you will see references below the LANSRAD folder regarding 3rdParty, etc because this custom option was intended to “dump” the files into a location such as C:\vuFileTools and let you move them where you want them and it shows the old C5.5/C6 style folders too.
But they do end up where you put them and the do work. If you chose to register the templates they are ready to use and the shortcuts on the IDE menu open the examples folder and the help.
If you open a solution from the examples, it compiles and runs as expected.
Note that for templates that have classes your RED file needs to “see” the new location so Clarion can find them during a compile.
The bug in having to BROWSE for the changed folders instead of type it in is some nuance of our complex script and how the LOOP inside the installer works.
Friedrich and I have talked about it and it is probably something I am doing slightly off.
But I can hardly ask him to debug a 4000+ line script and since 99 of 100 developers install to the default locations it just hasn’t ranked high on my list of things to spend a week fixing.
At any rate, I’m sorry you had a bad experience with it, but this will fix it if you follow the steps shown.
Charles
