I am going out on a limb here, but I was thinking . We have had X1 with 4 or 5 different updates, X2 with a Quick Fix and one update and now we have X3 with three updates at the moment. I think there is a real possibility that the programs are interacting with each other as far as the updates and therefore causing these little problems. You fix one in X3 and you get a twist of something else again from another X version. Just thinking...................... Ouch , IT HURTS

Many of us have kept old versions on our systems unless we had to do either a new computer build or OS.  This goes back to Pro Audio days and no one has reported a problem. 

John
Many of us have kept old versions on our systems unless we had to do either a new computer build or OS.  This goes back to Pro Audio days and no one has reported a problem. 

Hi John
What I am trying to say is that we all report problems by nature of the New program that came out. Nobody thinks of what happens with the interaction of the computer with the old X and the new X.
When we install the new program , plugins, shared plugins, shared utilitys and a bunch of other things get shared by the new installed program.
Now if you get a bug in X3 , the bakers try to reproduce this bug and sometimes cannot. What if the bug came from something that was saved and then transfered with the new installation on your computer that causes the problem and cake only tests the recent version.
 
I hope this makes sence.
 
Danny 

Danny yes it makes sense but that doesn't mean much. I was trying to point out that I for one had four different versions on my Vista setup with X1 and didn't have any of the problems some others had. Right now I don't have any version other then X3 c Producer on my system and can report one crash that I believe is due to opening an old file that was created in X1. It crashed with X2 and now it will crash in X3 if I do the same things with it. 
 
What CW does with its dlls and plugins is upgrade those but that wont interfere with old versions. How many times have you for example gone back and opened a project in an older version and had not problem? I have on occasion and can report no issue as long as the project is compatible with the old version. That is I haven't saved it in the new version and made it incompatible. The point is that often plugins and some dlls maybe new but don't stop one from opening or accessing that project in an older version. 
 
We know that the linear phase 64 EQ was reworked and it works in the older versions. 
 
However as an idea its not a bad one but as I implied in my post above it would seem that it would have been mentioned by now if it were known to cause problems.
 
Don't forget that most if not all of the critical files associated with a given version are placed into their own folders. Only those files that by their very nature are benign are in fact shared.
 
A plugin shouldn't cause any problem even if its been updated for a newer version for example.     
 
 

Thanks for the answer John
 
I do not know how they make the updates to fix bugs . I was just thinking that maybe an update to fix a bug in X2 could maybe cause problems in a new X3 as far as programming goes. I dont know what they make new as far as programming and what they use from an older program to save programming time.
 
As I said, It was just a thought, and very hard to explain.
 
Danny