Don't delete operational installations on software update

On 1/9/2013 1:36 PM, Matt Compton wrote:

I just made the huge mistake of updating from 6.2 to 6.4 on my laptop at a customer site.

 

Unfortunately for me, the MacOS upgrade wipes the existing 6.2 installation and the 6.4 installation asks to relicense. This is problematic because I am in a remote location and don't have access to my original install information at this site. I am now twiddling my thumbs in front of a customer while I wait for Cadsoft USA to resend my licensing information having wiped the working installation from my machine. Cadsoft has always been great with customer support and I am sure it will be handled promptly, but it is annoying.

 

You need to either leave the working installtion in place or at very least pull the license info from the old directory. Wiping my working executables and leaving me high and dry is just not a cool thing to do.

 

Hi Matt,

     Unfortunately, this is a MAC issue and it's not something that exists

on Windows or Linux platforms. I have no idea why Apple would implement

such a feature, if there's a reason I would really like to hear it.

     It something MAC users using Mac 0S 10.7 and later should be aware of.

At the very least that has been my experience.

hth,

Jorge Garcia

Jorge Garcia wrote on Wed, 09 January 2013 15:53

On 1/9/2013 1:36 PM, Matt Compton wrote:

I just made the huge mistake of updating from 6.2 to 6.4 on my

laptop at a customer site.

 

Unfortunately for me, the MacOS upgrade wipes the existing 6.2

installation and the 6.4 installation asks to relicense. This is

problematic because I am in a remote location and don't have access to

my original install information at this site. I am now twiddling my

thumbs in front of a customer while I wait for Cadsoft USA to resend my

licensing information having wiped the working installation from my

machine. Cadsoft has always been great with customer support and I am

sure it will be handled promptly, but it is annoying.

 

You need to either leave the working installtion in place or at

very least pull the license info from the old directory. Wiping my

working executables and leaving me high and dry is just not a cool

thing to do.

 

 

Hi Matt,

 

     Unfortunately, this is a MAC issue and it's not something that exists

 

on Windows or Linux platforms. I have no idea why Apple would implement

 

such a feature, if there's a reason I would really like to hear it.

 

     It something MAC users using Mac 0S 10.7 and later should be aware of.

 

At the very least that has been my experience.

 

hth,

Jorge Garcia

I just installed V6.4 on my Mac (10.8) and I still have V6.2 installed as

well, though I install to different directories so I keep old versions--I

need different versions for different projects.  But if you install into

the old directory it isn't a surprise that it replaces the binaries.

However, I do agree that in either case (installing to old directory or to

a new one) the installer should not need to ask for .key and install code

if a previous version of EAGLE has been installed on the same machine.  It

should be able to scan for the old .key file, copy it where it needs to,

and use that one without the need to re-enter the license info.

Cheers,

James.

--

James Morrison  ~~~  Stratford Digital

Specializing in CadSoft EAGLE

• Online Sales to North America

• Electronic Design Services

• EAGLE Enterprise Toolkit

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.