Library Problems

Best I can tell, Eagle 6.2.0, both 32 bit and 64 bit now conform to the

Windows 7 security mechanism, such that programs without administrator

privileges can not modify files in the Program Files area.  I find the

method that Microsoft used to enable this convoluted, and the (hidden)

location where it puts the modified files quite obscure.

Since I need to routinely move files between machines, particularly

when they are actively being built and tested, I would rather see Eagle

place the lib, cam, dru, scr and ulp files in the same location in the

eagle documents as the projects.  Any files that a user would normally

be expected to modify.  Everything except the binaries and Docs.

Nothing that a user would normally be expected to modify should be

located in the Windows system security protected area.

--- Graham

==

On 4/24/2012 2:36 AM, David Cotterill-Drew wrote:

Hi Graham

 

Thanks for the info, I am upgrading to 64 bit soon, so will at least know what to look out for!

 

Hi Graham

Thanks for the info, I am upgrading to 64 bit soon, so will at least know what to look out for!

I have sorted out the problem.

There are now two copies of the library file in the laptop.

The original unmodified copy of the library is (still) located at:

C:\Program Files\EAGLE-6.2.0\lbr

The modified copy of the library is located at

C:\Users\UsersName\AppData\Local\VirtualStore\Program Files\EAGLE-6.2.0\lbr

When Eagle modifies a library, it generates a changed copy, but

does not put the "lock" symbol on the file to warn you that it is using

the copy in the virtual store, rather than the original.  And it does

not remove or destroy the original, or tell you which one it is using.

I now have things working.

Thanks,

--- Graham

==

On 4/23/2012 12:53 PM, Graham wrote:

I have a library (lib file) that I am adding parts to. It was originally

created under Eagle 5.

 

I added a new IC to this library file, during a trip, using Eagle 6.1.0

Professional on a laptop running Windows 7 32 bit.

 

Now, when back at work, I copy the library file to my desktop computer

running Eagle 6.1.0 or 6.2.0 Professional, the new I.C. is not visible,

but all the older parts are still there in the library. The desktop

computer is running Windows 7, 64 bit.

 

When I look in 6.1.0 on the laptop, in the same file, the new part is

there. When I look in 6.1.0 or 6.2.0 on the desktop computer, the new

part is not there.

 

This is a large IC, that took several hours to create the footprint,

symbol, part, etc.

 

I have already spent several hours more going back and forth from the

laptop to the desktop to make sure that I have the correct version of

the file, and copying several times, to the lib file inside of the

Program files folder as well as trying to put it in the lib file in

the %appdata% folder.

 

How do I get my new part to be usable on my desktop Windows 7 64 computer?

 

--- Graham

 

==