- Posted on
Sat Mar 11, 2017 6:00 am
-
DaveL17
offline
-
- Posts: 6741
- Joined: Aug 20, 2013
- Location: Chicago, IL, USA
-
Older versions of Indigo should not interfere with newer versions in any way. On my development machine, I have Indigo 6 and Indigo 7 installed and routinely go back and forth between the two (for testing purposes.)
You should not have Indigo as a startup item for any user account, and instead select "Start and connect to Indigo Server on this computer" when you first start the server. On the server machine (you can't do it from another computer) select Stop Server and then select Start Local Server... to see this option and ensure it's checked.
Next, if you access your server from multiple machines with the Indigo client, you should always ensure that the version is the same on all. It doesn't necessarily have to be the newest version--they just all should be the same.
Lastly, each build of Indigo is stand alone. It doesn't rely on older versions in any way (that is, for Major releases like from 6 to 7.) Dot releases definitely do rely on older versions (like from 7.0.2 to 7.0.3). But a word of warning--your "custom" files are not automatically copied over (like custom images or script files) during major upgrades. You're on your own for those. I'd recommend leaving the older version installed for a while. Depending on what you have for custom files, prior versions don't take up that much space and you may find that you need to go back and get something that you missed after upgrading. My Indigo 6 and Indigo 7 installs together are only 150MB. You could back them up someplace else, but in my opinion, if you have Indigo properly configured at startup, there's no immediate need to get rid of the older versions.
I came here to drink milk and kick ass....and I've just finished my milk.
[My Plugins] - [My Forums]