Strange Library behavior under Windows 7

On 11/19/2011 6:37 PM, Graham wrote:

I am running Eagle 5.11.0 under Windows 7 (64 bit)

 

Normally, under Windows 7, program files, such as the CadSoft supplied

".lbr" files are stored in

 

C:\Program Files (x86)\EAGLE-5.11.0\lbr

 

If a user creates a new library, then Windows 7 puts it in

 

C:\Users\<Name>\AppData\Roaming\CadSoft\EAGLE\lbr

 

I have my own custom libraries, so I put them in the appropriate AppData

folder.

 

Everything works fine until I download the latest SparkFun Eagle library.

 

If I put the SparkFun.lbr in the appropriate AppData folder then

Eagle can not see it.

 

If I put it in the appropriate lbr folder inside Program Files (x86)

then Eagle can see the library and all works fine.

 

What is different between all my other libraries and SparkFun.lbr that

it is not visible from the %appdata% folder?

 

I can override the Windows 7 security as a workaround, but why

does it not work like it is supposed to?

 

--- Graham

 

==

 

Hi Graham,

Windows 7 came out after the release of 5.11. At this moment Windows 7

security features and EAGLE don't play very nice. The recommendation

we're giving is to allow EAGLE to run in administrative mode,

effectively over riding the security settings.

This will be corrected for the release of version 6.

Best Regards,

Jorge

Jorge Garcia wrote:

Hi Graham,

 

Windows 7 came out after the release of 5.11. At this moment Windows 7

security features and EAGLE don't play very nice. The recommendation

we're giving is to allow EAGLE to run in administrative mode,

effectively over riding the security settings.

 

This will be corrected for the release of version 6.

 

Best Regards,

Jorge

--

Come on Jorge get your information right.

Windows 7 was General availablity October 22, 2009

Eagle 5.11 was released  December 2010

On that basis I would expect the Windows 7 problem to be fixed now for the

final version of v5 (5.12) and the initial version of v6

The excuses we are being subjected to have become  tiring.

Warren

Viewed / responded via the newsgroup at

news.cadsoft.de

Jorge Garcia wrote:

Hi Graham,

 

Windows 7 came out after the release of 5.11. At this moment Windows 7

security features and EAGLE don't play very nice. The recommendation

we're giving is to allow EAGLE to run in administrative mode,

effectively over riding the security settings.

 

This will be corrected for the release of version 6.

 

Best Regards,

Jorge

--

Come on Jorge get your information right.

Windows 7 was General availablity October 22, 2009

Eagle 5.11 was released  December 2010

On that basis I would expect the Windows 7 problem to be fixed now for the

final version of v5 (5.12) and the initial version of v6

The excuses we are being subjected to have become  tiring.

Warren

Viewed / responded via the newsgroup at

news.cadsoft.de

On 11/21/2011 5:58 PM, Warren Brayshaw wrote:

Come on Jorge get your information right.

 

Windows 7 was General availablity October 22, 2009

Eagle 5.11 was released  December 2010

 

>

On that basis I would expect the Windows 7 problem to be fixed now for the

final version of v5 (5.12) and the initial version of v6

 

The excuses we are being subjected to have become  tiring.

I'm only human Warren.

Best Regards,

Jorge