Actions
Forum Thread Details
  • Replies 14 replies
  • Subscribers 188 subscribers
  • Views 1252 views
  • Users 0 members are here
Related

v6 ignored Options Directories entries

e14 Contributor

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.

 

 

 

 

Parents

  • Hello Brett Holden !:

    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.

     

    .....

     

    The problem is really primitive and ... IMHO stupid. In fact all EAGLE

    instances use THE SAME eaglerc.usr file !!!!! Of course in v5 the libs

    are in v5 subfolders, in v6 - sure not the same. Of course the danger to

    make unwanted update of the libs is really high.

     

    I am afraid this stupis behaviour is not aa incident ... I guess CadCoft

    want to push more peopple to buy new v6. Why ? Because changing the name

    of the usr file is really primitive.

     

    My suggestion : if CadSoft still want to use same name of the usr file

    we have to use some workaround, f.i. batch file or ... use an hex editor

    and change the name of the usr file !!!! This is 1-2 minutes time and

    works perfectly.

     

    IMHo this is really a stupid problem ... and sure totally unnecessary.

     

    best regards

    --

    Grzegorz Zalot

     

    complex ltd.

    office tel/fax : +48 32 2505840

    mobil : +48 501 301515

     

    http://www.complex.org.pl/

     

Reply

  • Hello Brett Holden !:

    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.

     

    .....

     

    The problem is really primitive and ... IMHO stupid. In fact all EAGLE

    instances use THE SAME eaglerc.usr file !!!!! Of course in v5 the libs

    are in v5 subfolders, in v6 - sure not the same. Of course the danger to

    make unwanted update of the libs is really high.

     

    I am afraid this stupis behaviour is not aa incident ... I guess CadCoft

    want to push more peopple to buy new v6. Why ? Because changing the name

    of the usr file is really primitive.

     

    My suggestion : if CadSoft still want to use same name of the usr file

    we have to use some workaround, f.i. batch file or ... use an hex editor

    and change the name of the usr file !!!! This is 1-2 minutes time and

    works perfectly.

     

    IMHo this is really a stupid problem ... and sure totally unnecessary.

     

    best regards

    --

    Grzegorz Zalot

     

    complex ltd.

    office tel/fax : +48 32 2505840

    mobil : +48 501 301515

     

    http://www.complex.org.pl/

     

Children
  • in reply to e14 Contributor

    Am 03.01.2012 07:56, schrieb Grzegorz Zalot:

    Hello Brett Holden !:

    >> 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.

     

    .....

     

    The problem is really primitive and ... IMHO stupid. In fact all EAGLE

    instances use THE SAME eaglerc.usr file !!!!! Of course in v5 the libs

    are in v5 subfolders, in v6 - sure not the same. Of course the danger to

    make unwanted update of the libs is really high.

     

    I am afraid this stupis behaviour is not aa incident ... I guess CadCoft

    want to push more peopple to buy new v6. Why ? Because changing the name

    of the usr file is really primitive.

     

    My suggestion : if CadSoft still want to use same name of the usr file

    we have to use some workaround, f.i. batch file or ... use an hex editor

    and change the name of the usr file !!!! This is 1-2 minutes time and

    works perfectly.

     

    IMHo this is really a stupid problem ... and sure totally unnecessary.

     

    best regards

     

    Happy New Year everyone image

     

    The -U parameter  was imo created during Ver.5 testing. I didn't know

    how to use this parameter by that time but got an answer from cadsoft

    that it "sets" a new path for the "eaglerc.usr" file. To test that I

    gave it a new name too and that worked. image

    So since that time I use somethimg like "-U F:\Eagle-6.0.2\

    eaglerc602.usr" to place the file in the eagle Ver.6 dirctory.

    Same goes for my version 5.

    Warren Brayshaw has explained that more detailed.

    So if users place the -U parameter with "my" extention into the

    properties of the launcher they should change the name of the

    eaglerc.usr file first before starting eagle, otherwise they run against

    the wall again.

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag