v6 ignored Options Directories entries

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/

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

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.

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

Hello Joern Paschedag !:

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.

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.

Brrrrrr, workaround again ....

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.

Exactly here is the problem.

BR

--

Grzegorz Zalot

complex ltd.

office tel/fax : +48 32 2505840

mobil : +48 501 301515

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

Am 04.01.2012 06:52, schrieb Grzegorz Zalot:

Hello Joern Paschedag !:

 

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

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

 

Brrrrrr, workaround again ....

 

Yes, but I have to run 3 Versions of eagle, 4, 5 and 6 and so this is at

least a little way out...

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

 

Exactly here is the problem.

 

BR

Well one must know what one is doing (hopefully)

I have to watch out carefully since some clients send version 4.x files

and insist of return in this version.

Right now I'm working still with v5, because of the many reported

troubles in v6, which was imo released too early.

If there is time I test with v6 or try to follow reports but so far I

had none of the so many reported crashes on my windows xp.

Unfortunately many people reporting errors witout mention the machine

and software they use. That makes it even more difficult for cadsoft to

locate errors.

Sorry but I am drifting OT.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Am 04.01.2012 06:52, schrieb Grzegorz Zalot:

Hello Joern Paschedag !:

 

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

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

 

Brrrrrr, workaround again ....

 

Yes, but I have to run 3 Versions of eagle, 4, 5 and 6 and so this is at

least a little way out...

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

 

Exactly here is the problem.

 

BR

Well one must know what one is doing (hopefully)

I have to watch out carefully since some clients send version 4.x files

and insist of return in this version.

Right now I'm working still with v5, because of the many reported

troubles in v6, which was imo released too early.

If there is time I test with v6 or try to follow reports but so far I

had none of the so many reported crashes on my windows xp.

Unfortunately many people reporting errors witout mention the machine

and software they use. That makes it even more difficult for cadsoft to

locate errors.

Sorry but I am drifting OT.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag