Thanks for your response to my post:
>> I'm adding CW7 to a PC that's already got CW for an embedded target.
>> Lacking any other advice, I simple installed the new CW in the default
>> location, "over" the existing one, which I also put in the default location.
>> It should be clear, but I'll state it anyway: I really want to make sure
>> both installations function correctly and completely!
>> Will I regret this "over" installation? What are the ins and outs? Is
>> there a better way?
>> (I save a copy of the original installation just in case!)
> While we're working towards having completely mergable products, right
> now that isn't the case. Generally, you want to install CW Pro first,
> then install other products on top of it. If the products are using the
> same IDE, there's a good chance that will work, at least on Windows.
> The places where you could have problems are the license.dat files (make
> sure you merge those together manually) and any plugins that conflict
> between the two.
> Installing in different locations is safer, and should work fine for
> anything produced since Pro 6 was released.
As I said, I went ahead and did it...
There have been no problems so far. I've operated both IDEs
simultaneously. I checked that I can build a new plug-in in Pro and it
automagically appears in the other IDE when it's re-launched.
I haven't checked the versions of each, but I think they are about the same.
I had no problems with the license. There were no instructions regarding
licensing, so I didn't do anything, and CW Pro simply worked from the
get-go. The embedded CW wanted some data from the licensing czar at MW
headquarters, but I didn't see anything like that for CW Pro.
Auto-registration didn't return anything.
How would I know about which plug-ins conflict? Error messages? Crashes?
At this point, I don't see any point in fixing something that works. If I
get into problems, I guess the best thing is to remove both and re-install
starting with Pro.
I'm puzzled about the question of merge-ability. Why would the installers
put the stuff in the exact same default place if there were any problems
with this capability? Would it not be better to use different default
install directories until this is proven?
By the way, I have been bitten in the past putting other tools in
non-default directories, so I resisted doing this unless proven necessary.