v6 ignored Options Directories entries

Brett Holden wrote:

I think that when somebody installs v6 alongside v5 that v6 should run

exclusively and not use v5 libraries.

 

I say this because when I installed v6 it wanted to use my old v5

libraries.

 

I copied my projects and libraries to entirely new directories so

that my old ones would not get fouled up and I made the appropriate

changes to the control panel "Options Directories", but Eagle IGNORED

my changes that pointed to the v6 libraries. Instead of using my v6

libraries, Eagle v6 continued to use my old v5 libraries from a

non-specified directory.

 

Fortunately I realized that my old libraries were in use and

proceeded to fix the problem.

 

"Use -*" (enter) and then "Use *" took care of the problem, but WHY

should that rigamarole be necessary??.

 

This is not a suggestion so much as it is a bug report. It's an

accident waiting to happen. I remember the exact thing happening as I

upgraded from v4 to v5.

This has been highligted a few times since the v6 betas were initially

released and I agree that Cadsoft need to mitigate the potential for these

inter-version traps.

It's just bad customer relations and there are many early adopters of v6

sufferring.

Although it is a trap, it could be argued Eagle works reasonaibly and it is

a user issue. That said, I feel that a document could have been made

available that guided their customers around these 'gotcha's'.

In your case Brett, when you replicated your projects, the eagle.epf files

were replicated and they contain the paths to that projects libraries used

to that point which are the v5 paths.

So you opened the project in v6 and the epf file made available the v5

libraries listed within it. The .  Thats why  "Use -*" (enter) and then "Use

*" worked..It closed the v5 libs and opened those you specified in (v6)

Options/Directories. Subsequently the eagle.epf reflected those paths to the

v6 libraries.

There is a second trap related to this one. If, in v5, you closed Eagle with

a project open, then the eaglerc.usr file will remember this project.

When you open v6 and provided you did not establish a different place for

the v6 eaglerc.usr file to reside  then v6 will read the eaglerc.usr file

(written with v5) and open your v5 project as it contains te full path. If

you dont realise this and subsequently 'save', you  have  now converted the

v5 file to v6.

I feel if CadSoft diverted some of its current support effort to getting

these upgrade issues publicised the number of support calls would reduce and

make more time available for other pressing issues.

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

Am 31.12.2011 02:30, schrieb Warren Brayshaw:

Brett Holden wrote:

>> I think that when somebody installs v6 alongside v5 that v6 should run

>> exclusively and not use v5 libraries.

>>

>> I say this because when I installed v6 it wanted to use my old v5

>> libraries.

>>

>> I copied my projects and libraries to entirely new directories so

>> that my old ones would not get fouled up and I made the appropriate

>> changes to the control panel "Options Directories", but Eagle IGNORED

>> my changes that pointed to the v6 libraries. Instead of using my v6

>> libraries, Eagle v6 continued to use my old v5 libraries from a

>> non-specified directory.

>>

>> Fortunately I realized that my old libraries were in use and

>> proceeded to fix the problem.

>>

>> "Use -*" (enter) and then "Use *" took care of the problem, but WHY

>> should that rigamarole be necessary??.

>>

>> This is not a suggestion so much as it is a bug report. It's an

>> accident waiting to happen. I remember the exact thing happening as I

>> upgraded from v4 to v5.

 

This has been highligted a few times since the v6 betas were initially

released and I agree that Cadsoft need to mitigate the potential for these

inter-version traps.

It's just bad customer relations and there are many early adopters of v6

sufferring.

 

Although it is a trap, it could be argued Eagle works reasonaibly and it is

a user issue. That said, I feel that a document could have been made

available that guided their customers around these 'gotcha's'.

 

In your case Brett, when you replicated your projects, the eagle.epf files

were replicated and they contain the paths to that projects libraries used

to that point which are the v5 paths.

So you opened the project in v6 and the epf file made available the v5

libraries listed within it. The .  Thats why  "Use -*" (enter) and then "Use

*" worked..It closed the v5 libs and opened those you specified in (v6)

Options/Directories. Subsequently the eagle.epf reflected those paths to the

v6 libraries.

 

There is a second trap related to this one. If, in v5, you closed Eagle with

a project open, then the eaglerc.usr file will remember this project.

When you open v6 and provided you did not establish a different place for

the v6 eaglerc.usr file to reside  then v6 will read the eaglerc.usr file

(written with v5) and open your v5 project as it contains te full path. If

you dont realise this and subsequently 'save', you  have  now converted the

v5 file to v6.

 

I feel if CadSoft diverted some of its current support effort to getting

these upgrade issues publicised the number of support calls would reduce and

make more time available for other pressing issues.

 

Warren

 

>

Unfortunately this problem exists since a very long time. There have

been a lot of discussions about the eaglerc.usr und .epf files but

nothing has changed. In win OS the eagle -U parameter helps a little but

once you forget the eaglerc.usr originally created in your user

directory you run into the same problem again.

I must run different versions of eagle installations in parallel and the

versions are in different directories or even different disks but one

must watch hell if opening a file just with a double click.

Eagle V6 has a new structure but imo this issue needs a new structure as

well.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Yup I originally had problem with only the wrong libraries being used. Now I

can't seem to get Eagle to use the v6 project folders I established. It

wants to open the old schematic files and I don't see an obvious fix.

This sucks. Well, I'll probably spend a couple of hours trying to work my

way around this minefield.

This is just the free version I'm using. At least I did not have to pay for

this headache.

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

news:jdmqq0$prg$1@cheetah.cadsoft.de...

Am 31.12.2011 02:30, schrieb Warren Brayshaw:

>> Brett Holden wrote:

>>> I think that when somebody installs v6 alongside v5 that v6 should run

>>> exclusively and not use v5 libraries.

>>>

>>> I say this because when I installed v6 it wanted to use my old v5

>>> libraries.

>>>

>>> I copied my projects and libraries to entirely new directories so

>>> that my old ones would not get fouled up and I made the appropriate

>>> changes to the control panel "Options Directories", but Eagle IGNORED

>>> my changes that pointed to the v6 libraries. Instead of using my v6

>>> libraries, Eagle v6 continued to use my old v5 libraries from a

>>> non-specified directory.

>>>

>>> Fortunately I realized that my old libraries were in use and

>>> proceeded to fix the problem.

>>>

>>> "Use -*" (enter) and then "Use *" took care of the problem, but WHY

>>> should that rigamarole be necessary??.

>>>

>>> This is not a suggestion so much as it is a bug report. It's an

>>> accident waiting to happen. I remember the exact thing happening as I

>>> upgraded from v4 to v5.

>>

>> This has been highligted a few times since the v6 betas were initially

>> released and I agree that Cadsoft need to mitigate the potential for

>> these

>> inter-version traps.

>> It's just bad customer relations and there are many early adopters of v6

>> sufferring.

>>

>> Although it is a trap, it could be argued Eagle works reasonaibly and it

>> is

>> a user issue. That said, I feel that a document could have been made

>> available that guided their customers around these 'gotcha's'.

>>

>> In your case Brett, when you replicated your projects, the eagle.epf

>> files

>> were replicated and they contain the paths to that projects libraries

>> used

>> to that point which are the v5 paths.

>> So you opened the project in v6 and the epf file made available the v5

>> libraries listed within it. The .  Thats why  "Use -*" (enter) and then

>> "Use

>> *" worked..It closed the v5 libs and opened those you specified in (v6)

>> Options/Directories. Subsequently the eagle.epf reflected those paths to

>> the

>> v6 libraries.

>>

>> There is a second trap related to this one. If, in v5, you closed Eagle

>> with

>> a project open, then the eaglerc.usr file will remember this project.

>> When you open v6 and provided you did not establish a different place for

>> the v6 eaglerc.usr file to reside  then v6 will read the eaglerc.usr file

>> (written with v5) and open your v5 project as it contains te full path.

>> If

>> you dont realise this and subsequently 'save', you  have  now converted

>> the

>> v5 file to v6.

>>

>> I feel if CadSoft diverted some of its current support effort to getting

>> these upgrade issues publicised the number of support calls would reduce

>> and

>> make more time available for other pressing issues.

>>

>> Warren

>>

>>

Unfortunately this problem exists since a very long time. There have been

a lot of discussions about the eaglerc.usr und .epf files but nothing has

changed. In win OS the eagle -U parameter helps a little but once you

forget the eaglerc.usr originally created in your user directory you run

into the same problem again.

I must run different versions of eagle installations in parallel and the

versions are in different directories or even different disks but one must

watch hell if opening a file just with a double click.

Eagle V6 has a new structure but imo this issue needs a new structure as

well.

 

>

--

Mit freundlichen Grüßen / With best regards

 

Joern Paschedag

"Warren Brayshaw" <warrenbrayshaw@paradise.net.nz> wrote in message

news:jdt3r8$d95$1@cheetah.cadsoft.de...

Brett Holden wrote:

 

>> ..............Here is text from the manual, page 113:

>> "It is possible to start EAGLE with the command line option -U which

>> can be used to define the location of the eaglerc file."

>>

>> That does not explain anything to me. I can't use -U if I don't know

>> how. If this goes on much longer I will feel obliged to re-ask this

>> question in the support forum, but maybe somebody can answer me here

>> to get this over with:

>>

>> What is the proper syntax and application for starting Eagle with the

>> -U parameter? (I'm using Windows XP.)

 

Hi Brett

Mario's reference is good.

 

Some further clarification.

1) When you use the  -U option you can name the 'user file' anything as it

does then not have to remain as eaglerc.usr. In the example Richard

provided

it is named 'myeaglerc.usr'.

2) If there are spaces in your path to the file then double quotes are

needed. I launch from a desktop icon so modified its target (in

properties)

so that it contains the -U option and location of the eaglerc.usr file.

As I have spaces here is my path.

"C:\Documents and Settings\Warren\NewEagle2\bin\eagle.exe" -U"C:\Documents

and Settings\Warren\NewEagle2\eaglerc.usr"

3) Note there is no space after the U

4)If you have multiple Eagle version installs, double clicking a design

file

outside of Eagle cannot be used to launch Eagle as only one version of

Eagle

can be associated with the file type.  You can set up Windows so that if

you

right click on the file (viewed in, say, explorer) then the context menu

lists the multiple Eagle versions you have set up. In this way  you can

launch the appropriate Eagle version from the file but I have not found a

way to make none of them the default. You want no defaults as a double

click, in error, on the file may launch the wrong Eagle version. It is

best

to disable file associations from brd, sch,  lib, usr files.

 

Hope this helps

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

 

That's it, Warren.

I thought Mario's references would be the fix but I was still getting kicked

in the teeth with various error messages, either trying to use the RUN box,

or trying to launch from a desktop icon with modified icon target

properties.

So, thank you for that explicit example, that is exactly what I needed. I

was having trouble because there is a space in my directory path and I had

forgotten the need for double quotes.

The -U option is working now (and no thanks to Cadsoft's documentation).

Cadsoft apparently expects somebody using their product to be a computer

guru, or else suffer.

Thank you to all who responded.

Brett Holden wrote:

..............Here is text from the manual, page 113:

"It is possible to start EAGLE with the command line option -U which

can be used to define the location of the eaglerc file."

 

That does not explain anything to me. I can't use -U if I don't know

how. If this goes on much longer I will feel obliged to re-ask this

question in the support forum, but maybe somebody can answer me here

to get this over with:

 

What is the proper syntax and application for starting Eagle with the

-U parameter? (I'm using Windows XP.)

Hi Brett

Mario's reference is good.

Some further clarification.

1) When you use the  -U option you can name the 'user file' anything as it

does then not have to remain as eaglerc.usr. In the example Richard provided

it is named 'myeaglerc.usr'.

2) If there are spaces in your path to the file then double quotes are

needed. I launch from a desktop icon so modified its target (in properties)

so that it contains the -U option and location of the eaglerc.usr file.

As I have spaces here is my path.

"C:\Documents and Settings\Warren\NewEagle2\bin\eagle.exe" -U"C:\Documents

and Settings\Warren\NewEagle2\eaglerc.usr"

3) Note there is no space after the U

4)If you have multiple Eagle version installs, double clicking a design file

outside of Eagle cannot be used to launch Eagle as only one version of Eagle

can be associated with the file type.  You can set up Windows so that if you

right click on the file (viewed in, say, explorer) then the context menu

lists the multiple Eagle versions you have set up. In this way  you can

launch the appropriate Eagle version from the file but I have not found a

way to make none of them the default. You want no defaults as a double

click, in error, on the file may launch the wrong Eagle version. It is best

to disable file associations from brd, sch,  lib, usr files.

Hope this helps

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

Brett Holden wrote:

..............Here is text from the manual, page 113:

"It is possible to start EAGLE with the command line option -U which

can be used to define the location of the eaglerc file."

 

That does not explain anything to me. I can't use -U if I don't know

how. If this goes on much longer I will feel obliged to re-ask this

question in the support forum, but maybe somebody can answer me here

to get this over with:

 

What is the proper syntax and application for starting Eagle with the

-U parameter? (I'm using Windows XP.)

Hi Brett

Mario's reference is good.

Some further clarification.

1) When you use the  -U option you can name the 'user file' anything as it

does then not have to remain as eaglerc.usr. In the example Richard provided

it is named 'myeaglerc.usr'.

2) If there are spaces in your path to the file then double quotes are

needed. I launch from a desktop icon so modified its target (in properties)

so that it contains the -U option and location of the eaglerc.usr file.

As I have spaces here is my path.

"C:\Documents and Settings\Warren\NewEagle2\bin\eagle.exe" -U"C:\Documents

and Settings\Warren\NewEagle2\eaglerc.usr"

3) Note there is no space after the U

4)If you have multiple Eagle version installs, double clicking a design file

outside of Eagle cannot be used to launch Eagle as only one version of Eagle

can be associated with the file type.  You can set up Windows so that if you

right click on the file (viewed in, say, explorer) then the context menu

lists the multiple Eagle versions you have set up. In this way  you can

launch the appropriate Eagle version from the file but I have not found a

way to make none of them the default. You want no defaults as a double

click, in error, on the file may launch the wrong Eagle version. It is best

to disable file associations from brd, sch,  lib, usr files.

Hope this helps

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

"Warren Brayshaw" <warrenbrayshaw@paradise.net.nz> wrote in message

news:jdt3r8$d95$1@cheetah.cadsoft.de...

Brett Holden wrote:

 

>> ..............Here is text from the manual, page 113:

>> "It is possible to start EAGLE with the command line option -U which

>> can be used to define the location of the eaglerc file."

>>

>> That does not explain anything to me. I can't use -U if I don't know

>> how. If this goes on much longer I will feel obliged to re-ask this

>> question in the support forum, but maybe somebody can answer me here

>> to get this over with:

>>

>> What is the proper syntax and application for starting Eagle with the

>> -U parameter? (I'm using Windows XP.)

 

Hi Brett

Mario's reference is good.

 

Some further clarification.

1) When you use the  -U option you can name the 'user file' anything as it

does then not have to remain as eaglerc.usr. In the example Richard

provided

it is named 'myeaglerc.usr'.

2) If there are spaces in your path to the file then double quotes are

needed. I launch from a desktop icon so modified its target (in

properties)

so that it contains the -U option and location of the eaglerc.usr file.

As I have spaces here is my path.

"C:\Documents and Settings\Warren\NewEagle2\bin\eagle.exe" -U"C:\Documents

and Settings\Warren\NewEagle2\eaglerc.usr"

3) Note there is no space after the U

4)If you have multiple Eagle version installs, double clicking a design

file

outside of Eagle cannot be used to launch Eagle as only one version of

Eagle

can be associated with the file type.  You can set up Windows so that if

you

right click on the file (viewed in, say, explorer) then the context menu

lists the multiple Eagle versions you have set up. In this way  you can

launch the appropriate Eagle version from the file but I have not found a

way to make none of them the default. You want no defaults as a double

click, in error, on the file may launch the wrong Eagle version. It is

best

to disable file associations from brd, sch,  lib, usr files.

 

Hope this helps

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

 

That's it, Warren.

I thought Mario's references would be the fix but I was still getting kicked

in the teeth with various error messages, either trying to use the RUN box,

or trying to launch from a desktop icon with modified icon target

properties.

So, thank you for that explicit example, that is exactly what I needed. I

was having trouble because there is a space in my directory path and I had

forgotten the need for double quotes.

The -U option is working now (and no thanks to Cadsoft's documentation).

Cadsoft apparently expects somebody using their product to be a computer

guru, or else suffer.

Thank you to all who responded.