element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Best way to upgrade
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Suggested Answer
  • Replies 25 replies
  • Answers 13 answers
  • Subscribers 190 subscribers
  • Views 4278 views
  • Users 0 members are here
Related

Best way to upgrade

jsantosrico
jsantosrico over 9 years ago

Hi,

 

The default behaviour of Eagle is to keep old versions of eagle when you update. Is not really a problem, as it is not hughe program, but it's a tad annoying when I click an old link pointing to an old version or I double click on a file and it opens in the old version because the file association has not updated. Why is this the default behaviour? I also noted that in my projects there is a file called Eagle.epf, which lists the libraries in use in my project, and the default libraries still point to old versions of them, as in for example:

 

....

UsedLibrary="C:/EAGLE-7.6.0/lbr/19inch.lbr"

UsedLibrary="C:/EAGLE-7.6.0/lbr/40xx.lbr"

UsedLibrary="C:/EAGLE-7.6.0/lbr/41xx.lbr"

UsedLibrary="C:/EAGLE-7.6.0/lbr/45xx.lbr"

....

 

Do I have to check all my projects every time I upgrade and update to the new paths? Is that the way this is intended to be? I was wondering if there is a less cumbersome way to update.

 

Thanks for taking the time to check my problem.

 

regards,

 

Joel

  • Sign in to reply
  • Cancel
Parents
  • autodeskguest
    0 autodeskguest over 6 years ago

    Am 13.10.2016 um 15:55 schrieb Joel Santos Rico:

    Hi,

     

    The default behaviour of Eagle is to keep old versions of eagle when you update. Is not really a problem, as it is not hughe program, but it's a tad annoying when I click an old link pointing to an old version or I double click on a file and it opens in the old version because the file association has not updated. Why is this the default behaviour? I also noted that in my projects there is a file called Eagle.epf, which lists the libraries in use in my project, and the default libraries still point to old versions of them, as in for example:

     

    ...

    UsedLibrary="C:/EAGLE-7.6.0/lbr/19inch.lbr"

    UsedLibrary="C:/EAGLE-7.6.0/lbr/40xx.lbr"

    UsedLibrary="C:/EAGLE-7.6.0/lbr/41xx.lbr"

    UsedLibrary="C:/EAGLE-7.6.0/lbr/45xx.lbr"

    ...

     

    Do I have to check all my projects every time I upgrade and update to the new paths? Is that the way this is intended to be? I was wondering if there is a less cumbersome way to update.

     

    Thanks for taking the time to check my problem.

     

    regards,

     

    Joel

     

     

    Unfortunately you didn't mention your version of eagle nor your OS.

    Talking of win. There is an U-parameter that one can use to point to the

    eagle.exe file, i.e.

    E:EAGLE-5.12.0\bin\eagle.exe -U E:\Eagle-5.12.0\eaglerc-512.usr

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

     

    The file can have any name. I put them into the correspondent eagle

    version and name it i.e. "eaglerc-660.usr" instead of the original

    "eaglerc.usr" which is the name normally in EVERY eagle version (and

    causes problems).

    First part is the pointer to "eagle.exe" which is located in sub

    directory "bin", second part is the location of xxx.usr, in my case in

    the eagle main directory.

     

    I don't use the AD versions but think that this parameter still exist.

    Check documentation.

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • autodeskguest
    0 autodeskguest over 6 years ago

    Am 13.10.2016 um 15:55 schrieb Joel Santos Rico:

    Hi,

     

    The default behaviour of Eagle is to keep old versions of eagle when you update. Is not really a problem, as it is not hughe program, but it's a tad annoying when I click an old link pointing to an old version or I double click on a file and it opens in the old version because the file association has not updated. Why is this the default behaviour? I also noted that in my projects there is a file called Eagle.epf, which lists the libraries in use in my project, and the default libraries still point to old versions of them, as in for example:

     

    ...

    UsedLibrary="C:/EAGLE-7.6.0/lbr/19inch.lbr"

    UsedLibrary="C:/EAGLE-7.6.0/lbr/40xx.lbr"

    UsedLibrary="C:/EAGLE-7.6.0/lbr/41xx.lbr"

    UsedLibrary="C:/EAGLE-7.6.0/lbr/45xx.lbr"

    ...

     

    Do I have to check all my projects every time I upgrade and update to the new paths? Is that the way this is intended to be? I was wondering if there is a less cumbersome way to update.

     

    Thanks for taking the time to check my problem.

     

    regards,

     

    Joel

     

     

    Unfortunately you didn't mention your version of eagle nor your OS.

    Talking of win. There is an U-parameter that one can use to point to the

    eagle.exe file, i.e.

    E:EAGLE-5.12.0\bin\eagle.exe -U E:\Eagle-5.12.0\eaglerc-512.usr

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

     

    The file can have any name. I put them into the correspondent eagle

    version and name it i.e. "eaglerc-660.usr" instead of the original

    "eaglerc.usr" which is the name normally in EVERY eagle version (and

    causes problems).

    First part is the pointer to "eagle.exe" which is located in sub

    directory "bin", second part is the location of xxx.usr, in my case in

    the eagle main directory.

     

    I don't use the AD versions but think that this parameter still exist.

    Check documentation.

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • rachaelp
    0 rachaelp over 6 years ago in reply to autodeskguest

    autodeskguest  wrote:

     

    I don't use the AD versions

     

    It's a shame more of the long time users of the original EAGLE like yourself aren't using the newer AD versions, your experience and support on the main AD forums would be very valuable and I'm sure if you could look past the licensing (which I assume is your reason for not using it), it's actually really really good now. It's like old EAGLE on steroids, the last few releases in particular have been big jumps up in functionality.

     

    Best Regards,

     

    Rachael

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • autodeskguest
    0 autodeskguest over 6 years ago in reply to autodeskguest

    On 31/08/2019 08:35, Joern Paschedag wrote:

     

    I don't use the AD versions but think that this parameter still exist.

    Check documentation.

    Yes, it still exists, and is very useful for having V9, V8, V7 and V5

    all available on the same PC, in case I need to work on an old design

    and don't want to convert it.

     

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube