Remove old versions of Eagle???

For the short term, at least, I will be running both the old version 5 along

with the new version 7.5.

It confused me a bit as I was configuring the directories for V7.5.

All files except the binaries and documentation are mapped to the network

for backup.

A separate directory of \EAGLEDATA7 is created for the Eagle 7.5

files.

The old [network\EAGLEDATA is left for use only by Eagle V5.

Pointed the directories for V7.5 to use \EAGLEDATA7 and then went

back to V5 and checked that. Found that all the directories were pointing

now to \EAGLEDATA7 .

Reset them to [network\EAGLEDATA , exited and opened V7.5 to be certain that

nothing had changed there. All good it seems.

Hopefully this is a one-time hiccup.

"Oppie" <oppie@saynotospam.com> wrote in message

news:n4et5m$c1e$1@baboon.cadsoft.de...

I had been using Version 5.11 and had loaded a trial of 6.0 (but never

registered).

 

Yesterday I installed and registered version 7.5 and went to do some

clean-ups. I wanted to uninstall version 6 since it was never fully set up

anyway but I noticed that in Windows XP Pro, that the Add/Remove programs

list only shows version 7.5. There are no entries for either version 5 or

version 6. Both of those will run from the start menu.

 

I looked in C:\Program Files\EAGLE-6.0.0\bin and see that there is a file

"uninstall.bat"

Is this safe to run and will not destroy any of my other data?

Evidently, this is not a one-time hiccup.  Closed both editors and restarted

V5 the directories for the V7.5 came back. Looks like one set of environment

variables are used for all eagle versions.

Is there any work-around for this? I am currently using an absolute network

address and not a variable.

"Oppie" <oppie@saynotospam.com> wrote in message

news:n4evu6$dha$1@baboon.cadsoft.de...

For the short term, at least, I will be running both the old version 5

along with the new version 7.5.

 

It confused me a bit as I was configuring the directories for V7.5.

All files except the binaries and documentation are mapped to the network

for backup.

A separate directory of \EAGLEDATA7 is created for the Eagle 7.5

files.

The old [network\EAGLEDATA is left for use only by Eagle V5.

 

Pointed the directories for V7.5 to use \EAGLEDATA7 and then went

back to V5 and checked that. Found that all the directories were pointing

now to \EAGLEDATA7 .

Reset them to [network\EAGLEDATA , exited and opened V7.5 to be certain

that nothing had changed there. All good it seems.

 

Hopefully this is a one-time hiccup.

 

Hi Oppie,

I hope you're doing well. You have discovered that the eaglerc file can

be shared by multiple versions of EAGLE. The workaround is use a bat

file to start EAGLE and tell it where you want EAGLE to store the

eaglerc file. This is how I keep the last members of V4-V7 installed on

my machine without interaction.

I've attached my example file. Change the extension to .bat and adjust

the paths in the file to match your system. To start EAGLE just double

click on the .bat file.

Let me know if there's anything else I can do for you.

Best Regards,

Jorge Garcia

Am 11.12.2015 um 18:18 schrieb Oppie:

Evidently, this is not a one-time hiccup.  Closed both editors and

restarted V5 the directories for the V7.5 came back. Looks like one set

of environment variables are used for all eagle versions.

 

Is there any work-around for this? I am currently using an absolute

network address and not a variable.

 

"Oppie" <oppie@saynotospam.com> wrote in message

news:n4evu6$dha$1@baboon.cadsoft.de...

For the short term, at least, I will be running both the old version 5

along with the new version 7.5.

 

It confused me a bit as I was configuring the directories for V7.5.

All files except the binaries and documentation are mapped to the

network for backup.

A separate directory of \EAGLEDATA7 is created for the Eagle

7.5 files.

The old [network\EAGLEDATA is left for use only by Eagle V5.

 

Pointed the directories for V7.5 to use \EAGLEDATA7 and then

went back to V5 and checked that. Found that all the directories were

pointing now to \EAGLEDATA7 .

Reset them to [network\EAGLEDATA , exited and opened V7.5 to be

certain that nothing had changed there. All good it seems.

 

Hopefully this is a one-time hiccup.

 

Check the eagle information about the "-U" parameter.

I (must) have different versions of eagle running.

Each version is in its own directory. With the -U parameter you can also

give a different name for the "eaglerc.usr" file. In the following

example eagle version 6.6.0 is in the

F:\eagle-6.6.0 directory and the eaglerc.usr file is named

"eaglerc-660.usr" (easier for me) and stored in the same directory.

F:\EAGLE-6.6.0\bin\eagle.exe -U F:\Eagle-6.6.0\eaglerc-660.usr

It works since years (windows)

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

OK, Took me a while to find what the -U switch was. I thought the switches

were only used with Eaglecon but appears that they work with eagle.exe too.

-

Copied my eaglerc.usr and saved the copy as eaglerc5.usr

Edit the eaglerc5.usr to change the Directories.n arguments to the ones I

dedicated for eagle V5.

Create Eagle5.bat in notepad with (XP Pro):

Rem Start Eagle 5 with a special eaglerc to force directories to

N:\Eagledata

"C:\Program Files\EAGLE-5.11.0\bin\eagle.exe" -U"C:\Documents and

Settings\bob\Application Data\CadSoft\EAGLE\eaglerc5.usr"

-

I'm not partial to the fact that the dos window stays open but doing this in

silent mode it more of a big deal. The DOS window can be closed manually at

any time or left to autoclose when the eagle session is ended.

Thank you again for your assistance.

-

"Jorge Garcia" <jorge@cadsoftusa.com> wrote in message

news:n4f84n$hkd$1@baboon.cadsoft.de...

Hi Oppie,

 

I hope you're doing well. You have discovered that the eaglerc file can

be shared by multiple versions of EAGLE. The workaround is use a bat

file to start EAGLE and tell it where you want EAGLE to store the

eaglerc file. This is how I keep the last members of V4-V7 installed on

my machine without interaction.

 

I've attached my example file. Change the extension to .bat and adjust

the paths in the file to match your system. To start EAGLE just double

click on the .bat file.

 

Let me know if there's anything else I can do for you.

 

Best Regards,

Jorge Garcia

 

 

 

Thank you! Jorge got me started on this and was able to get it running.

    Cheers!

"Joern Paschedag" <jpaschedag@t-online.de> wrote in message

news:n4ff0t$l47$1@baboon.cadsoft.de...

Am 11.12.2015 um 18:18 schrieb Oppie:

Evidently, this is not a one-time hiccup.  Closed both editors and

restarted V5 the directories for the V7.5 came back. Looks like one set

of environment variables are used for all eagle versions.

 

Is there any work-around for this? I am currently using an absolute

network address and not a variable.

 

"Oppie" <oppie@saynotospam.com> wrote in message

news:n4evu6$dha$1@baboon.cadsoft.de...

For the short term, at least, I will be running both the old version 5

along with the new version 7.5.

 

It confused me a bit as I was configuring the directories for V7.5.

All files except the binaries and documentation are mapped to the

network for backup.

A separate directory of \EAGLEDATA7 is created for the Eagle

7.5 files.

The old [network\EAGLEDATA is left for use only by Eagle V5.

 

Pointed the directories for V7.5 to use \EAGLEDATA7 and then

went back to V5 and checked that. Found that all the directories were

pointing now to \EAGLEDATA7 .

Reset them to [network\EAGLEDATA , exited and opened V7.5 to be

certain that nothing had changed there. All good it seems.

 

Hopefully this is a one-time hiccup.

 

 

Check the eagle information about the "-U" parameter.

I (must) have different versions of eagle running.

Each version is in its own directory. With the -U parameter you can also

give a different name for the "eaglerc.usr" file. In the following example

eagle version 6.6.0 is in the

F:\eagle-6.6.0 directory and the eaglerc.usr file is named

"eaglerc-660.usr" (easier for me) and stored in the same directory.

 

F:\EAGLE-6.6.0\bin\eagle.exe -U F:\Eagle-6.6.0\eaglerc-660.usr

 

It works since years (windows)

 

--

Mit freundlichen Grüßen / With best regards

 

Joern Paschedag

Am 11.12.2015 um 22:33 schrieb Oppie:

I'm not partial to the fact that the dos window stays open but doing

Don't you have a link to start your EAGLE already (start menu, desktop)?

If not, create one. Then, right-click it -> properties and edit the

command line here: No bat-file, not console window.

Rene

Thank you Rene. Your recommendation to do this without a batch file

definitely simplifies things.

The original eaglerc.usr was renamed to eaglerc5.usr and left in the same

location as the original.

Start menu properties are changed for the Eagle5.11.0

Target: changed from

"C:\Program Files\EAGLE-5.11.0\bin\eagle.exe"

to the following

"C:\Program Files\EAGLE-5.11.0\bin\eagle.exe" -U"C:\Documents and

Settings\bob\Application Data\CadSoft\EAGLE\eaglerc5.usr"

Quote marks are exactly as copied from the properties window.

Where -U is a switch that tells where the desired eaglerc is located.

eaglerc5.usr has directories.xxx entries changed to use a set of legacy

directories. Those should not be accessed by any eagle version after V5 to

avoid compatibility issues.

Note that this is in Windows XP.

    Oppie

"René König" <rk@tbkoenig.de> wrote in message

news:n4m10b$jt$1@baboon.cadsoft.de...

Am 11.12.2015 um 22:33 schrieb Oppie:

I'm not partial to the fact that the dos window stays open but doing

 

Don't you have a link to start your EAGLE already (start menu, desktop)?

If not, create one. Then, right-click it -> properties and edit the

command line here: No bat-file, not console window.

 

Rene