As far as getting the GUI to load if you are running this from UNIX I belive you will need to be in a x-window environemnt.
Sounds like you figured that out by running the console mode that is probably textual and not graphical.
I’m not sure if this extra information helps any but I stopped hanging my hat on a stable directory structure when I had to go from Cloverleaf 3.5.5 to 5.2.
Since then I’ve been palcing the cloverleaf install into a files system unkown to the install_dir environment variable used by cloverleaf.
What I did this time while upgrading from cloverleaf 5.2 to 5.6 was:
– create an /upgrade filesystem
– mkdir /upgrade/cloverleaf
– create a symbolic link for the currently used base directory name which was /quovadx this time but might be /healthvision next time
Here is my steps for creating the quovadx symbolic link
cd /
ln -s /upgrade/cloverleaf /quovadx
Then I install cloverleaf and it thinks it is in $HCIROOT
/quovadx/qdx5.6/integrator
but physically resides in
/upgrade/cloverleaf/qdx5.6/integrator
We also adopted a similar pratice for all the cloverleaf sites using symbolic links for each site that points to where they are physically located in our /sites file system
Russ Ross
RussRoss318@gmail.com