#1
When installing Slick (B1 ... Rc1), it modifies the system PATH - adding the new version of Slick as the first thing in the path.
After installing, use Explorer (start->Run) to create a new CMD window.
Notice that the PATH inherited by CMD doesn't include the new Slick version.
Normally when you use the control panel -> Advanced system settings to change env-vars, the change is noticed by Explorer and will be inherited by new processes started by Explorer.
This should also happen when the Slick install updates the Path.
#2
On Windows 10, I have several betas installed and now the RC1 version.
After just installing a new version, it is surprisingly hard to find it in Start (Oh, how I wish for the Win7 version of start!).
Tap the windows key, type "Slick", and I see the previous versions.
I have to type "Slickedit Pro 2016" before I finally see the RC version (maybe just waiting a little longer would have been enough??).
It would be good if the new install would surface in Start a little easier.
(Does an installer have any influence on this? Or any ability to give hints to Windows about it?)
I don't know if this is an issue if you don't have so many beta versions installed of course.
