EAGLE upgrade impossible  .....

On 12/20/2011 2:00 PM, Grzegorz Zalot wrote:

Dear all, especially CadSoft team ...

 

From your site :

 

>> Upgrade system under maintenance

>>

>> Upgrade system is currently under maintenance and will be available

>> shortly.

 

since few days.

 

And my question : how to test Eagle 6.0 without upgrading ?????

 

br

Hi Grzegorz,

Use EAGLE 6.0 in freeware mode, and make a simple board that's if you

want to test it.

If you want to upgrade it, for the moment you have to call it in since

as you've noticed the upgrade site is down due to technical difficulties.

hth,

Jorge Garcia

Hello Jorge Garcia,

Use EAGLE 6.0 in freeware mode, and make a simple board that's if you

want to test it.

I cant use Eagle in freeware mode - my projects are too complex .....

If you want to upgrade it, for the moment you have to call it in

since as you've noticed the upgrade site is down due to technical

difficulties.

Interesting .... this is for many days !!! I cant imagine the upgrade

prices are not known ! Of course I can call the German CadSoft, I speak

German, but ...

Thanks and best regards

--

Grzegorz Zalot

complex ltd.

office tel/fax : +48 32 2505840

mobil : +48 501 301515

Another WARNING / CAUTION that they do not warn you about:

DO NOT OPEN ANY PROJECTS OR LIBRARIES WITH V6.0 without first saving

BACKUPS of ALL FILES, since V6.0 will "UPGRADE" all files to new XML

format AND YOU CANNOT REVERT them back to V5.11 or earlier versions.

On 12/20/2011 11:43 AM, Grzegorz Zalot wrote:

Hello Jorge Garcia,

 

>> Use EAGLE 6.0 in freeware mode, and make a simple board that's if you

>> want to test it.

 

I cant use Eagle in freeware mode - my projects are too complex .....

 

>> If you want to upgrade it, for the moment you have to call it in

>> since as you've noticed the upgrade site is down due to technical

>> difficulties.

 

Interesting .... this is for many days !!! I cant imagine the upgrade

prices are not known ! Of course I can call the German CadSoft, I speak

German, but ...

 

Thanks and best regards

Another WARNING / CAUTION that they do not warn you about:

DO NOT OPEN ANY PROJECTS OR LIBRARIES WITH V6.0 without first saving

BACKUPS of ALL FILES, since V6.0 will "UPGRADE" all files to new XML

format AND YOU CANNOT REVERT them back to V5.11 or earlier versions.

On 12/20/2011 11:43 AM, Grzegorz Zalot wrote:

Hello Jorge Garcia,

 

>> Use EAGLE 6.0 in freeware mode, and make a simple board that's if you

>> want to test it.

 

I cant use Eagle in freeware mode - my projects are too complex .....

 

>> If you want to upgrade it, for the moment you have to call it in

>> since as you've noticed the upgrade site is down due to technical

>> difficulties.

 

Interesting .... this is for many days !!! I cant imagine the upgrade

prices are not known ! Of course I can call the German CadSoft, I speak

German, but ...

 

Thanks and best regards

Marvin Dawson wrote on Tue, 20 December 2011 20:39

Another WARNING / CAUTION that they do not warn you about:

DO NOT OPEN ANY PROJECTS OR LIBRARIES WITH V6.0 without first saving

BACKUPS of ALL FILES, since V6.0 will "UPGRADE" all files to new XML

format AND YOU CANNOT REVERT them back to V5.11 or earlier versions.

I couldn't reproduce this.  I just opened an EAGLE 5 design (both by

opening the project and the schematic/pcb directly).  Closing without

saving had no effect on the files that were there.

Now if you went ahead and saved the files then yes, they will write the

files in V6's XML format and there's no easy way to get back.  I don't

think it should be a surprise that EAGLE would do this.

I have argued for awhile that EAGLE should have a "Save As" option to save

into old formats.  I understand there are complications with this, but as a

design house we have to deal with files in all sorts of formats.  This

would give everyone the benefit of the new features of the program and

still be able to support clients on older versions.

However, I do agree that CadSoft should have handled this better.  A

warning when changing the format of the file would be sufficient.  There is

a warning when the .epf file is rewritten from version to version so at

least that should be done.

I would argue that the best option would be to change the file extension

itself.  EAGLE V6 should no longer use .sch and .pcb, just like Microsoft

Word doesn't use .doc anymore.  The extension should be changed to .schx

and .pcbx or something similar.  That way, this is a moot issue since the

new files will be different and the user will still have the old version of

the files around if they want them.

As an aside, I have all my files stored in revision control so I can play

with them freely and not worry about corrupting the local copy and I highly

recommend this for anyone doing serious design work.  You will get whatever

time it takes you to setup back ten-fold when issues occur--and they will

occur.

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.

Hello Warren Brayshaw !:

....

You need to have v6 use its own location for eaglerc.usr. If you don't it

may use the v5 eaglerc and with common project names between the versions

you can accidently load and save your v5 design as v6. Ouch!

Yes ! I am wondering why CadSoft is NOT able to change the name of the

config file and this workaround is really necessary !!!

Change the desktop icon that launches v6 so that it starts eagle with the -U

switch so it will look something like eagle.exe -Ufilepathforeaglerc.usr

It may take a bit of patience to get the file name string correct if it

contains spaces. Mine looks like so:

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

and Settings\Warren\NewEagle2\eaglerc.usr'

Eagle will now place the  eaglerc.usr  file into the folder 'NewEagle2'

instead of where the $HOME environmental variable says to.

Good advice but .... CadSoft please think about this problem seriously !!!

Another possibility is to change the name of the eaglers file by editing

the exe with a HEX editor. But the question WHY is still here ...

best regards

--

Grzegorz Zalot

complex ltd.

office tel/fax : +48 32 2505840

mobil : +48 501 301515

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

Marvin Dawson wrote:

Another WARNING / CAUTION that they do not warn you about:

DO NOT OPEN ANY PROJECTS OR LIBRARIES WITH V6.0 without first saving

BACKUPS of ALL FILES, since V6.0 will "UPGRADE" all files to new XML

format AND YOU CANNOT REVERT them back to V5.11 or earlier versions.

 

It is said in places but it is not "in your face" and it should be.

It's to early to use v6 for production. Just to many fixes needed at present

but  the more people that try it out and report issues the sooner it will

become solid.

Work on a copy of your libraries, ulp, scripts and design files so you dont

have to restore the backups if you wish to revert to v5.

V6 will install in its own folder which is the first step in isolating the

versions.

There are  more things you should do and change immediately after installing

v6.

Do these things before ever opening a file.

I'll talk windows here.

You need to have v6 use its own location for eaglerc.usr. If you don't it

may use the v5 eaglerc and with common project names between the versions

you can accidently load and save your v5 design as v6. Ouch!

Change the desktop icon that launches v6 so that it starts eagle with the -U

switch so it will look something like eagle.exe -Ufilepathforeaglerc.usr

It may take a bit of patience to get the file name string correct if it

contains spaces. Mine looks like so:

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

and Settings\Warren\NewEagle2\eaglerc.usr'

Eagle will now place the  eaglerc.usr  file into the folder 'NewEagle2'

instead of where the $HOME environmental variable says to.

Set the directories in Control Panel. They need to point to different

folders than v5.

Remember they should point to the COPIES of your personal libraries, ulp,

script etc.

The  $eagledir paths should be OK as in theory they point to the path of

this installed instance of Eagle (v6)

There could be a $Home path in the project path when you load v6 (I saw it

but I may have caused it ) so removing that path would be a good idea.

That should do it. Others can comment if I missed something.

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de