.lbr files locked

If you can't see it in windoze explorer, either you are looking under the

wrong rock or the files are "hidden" and you don't have the option set in

folder options to show hidden files.  By default, one of the first things I

do when I do a windoze install on any of my stuff is to uncheck the option

to hide extensions of known file types and show hidden files.  I HATE being

"helped" -- see of one of those conditions applies here.

mikey

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

I have this identical problem and not only the  lbr file but its containing folder is hidden from File Explorer.  The containing folder shows up in Eagle > Libraries with the padlock. The containing folder for the hidden folder, which is Eagle-6.2.0/lbr, has its permissions set to display hidden files and folders - so that is not the problem.  What is going on here?

Francois, did you solve this problem?  I need to send this library to someone and I can't gain access to it. 

Well I finally gained access to the file.  I had to go to Eagle Control Panel, select the file, Choose Copy from the context menu and then saved it on my Desktop.  I still do not understand WTF is happening though.  I changed permissions so that I would have Full Control from the Eagle folder on down and that did not help.  I am perplexed.  But at least if others run into this, there is a workaround through the Copy command.

Just a thought - there are some additional bits in the files that windows

looks at - such as being able to tell that "the file xyz was downloaded

from the internet and is it OK to open it" - once you tell it OK, then it

seems to remember that, so somewhere is a bit being set that I never see in

"file properties".  May not be the issue, but it has that sort of feel.  I

wonder if copy/pasting it to the same location would also clear the issue

?

mikey

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

On 10/25/2012 2:14 AM, Mike Fields wrote:

Just a thought - there are some additional bits in the files that windows

looks at - such as being able to tell that "the file xyz was downloaded

from the internet and is it OK to open it" - once you tell it OK, then it

seems to remember that, so somewhere is a bit being set that I never see in

"file properties".  May not be the issue, but it has that sort of feel.  I

wonder if copy/pasting it to the same location would also clear the issue

?

 

mikey

 

Hi Guys,

Generally this issue arises when a user saves to EAGLE's library

directory inside Program Files (X86). Windows has placed some

restrictions on that folder and that's why you see the padlock.

The general recommendation is to not save any personal work in any of

EAGLE internal directories. Save you work to a less tampered with

location such as MyDocuments.

That's why the copy workaround was successful. He copied the file to a

non-restricted area.

Let me know if there's anything else I can do for you.

Best Regards,

Jorge Garcia

On 10/25/2012 2:14 AM, Mike Fields wrote:

Just a thought - there are some additional bits in the files that windows

looks at - such as being able to tell that "the file xyz was downloaded

from the internet and is it OK to open it" - once you tell it OK, then it

seems to remember that, so somewhere is a bit being set that I never see in

"file properties".  May not be the issue, but it has that sort of feel.  I

wonder if copy/pasting it to the same location would also clear the issue

?

 

mikey

 

Hi Guys,

Generally this issue arises when a user saves to EAGLE's library

directory inside Program Files (X86). Windows has placed some

restrictions on that folder and that's why you see the padlock.

The general recommendation is to not save any personal work in any of

EAGLE internal directories. Save you work to a less tampered with

location such as MyDocuments.

That's why the copy workaround was successful. He copied the file to a

non-restricted area.

Let me know if there's anything else I can do for you.

Best Regards,

Jorge Garcia

I'm having a similar issue opening a library. I created my device and I'm trying to upload it into a previous schematic. I saved the library into another folder like MyDocuments like you mentioned but I'm not sure how to navigate to this folder when trying to add the symbol to my old schematic.

I think you need to go to Library > Use in the Schematic window and then navigate to your new lbr file.

I was able to get it thank you.

Thank you so much for posting the solution to this irritating and baffling problem!  I had the same exact problem - my .LBR's were viewable from within the EagleCAD file explorer, but completely invisible from Windows explorer!  Copying/pasting to my desktop (from within the EagleCAD file explorer) allowed me to recover my lost/hidden/locked .LBR file.

Thank you thank you thank you!

So for anyone else that runs into this problem, I found that my .lbr file of interest was actually being stored in "C:\Users\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\EAGLE-<VERSION_NUM>\lbr\<file_of_interest>.lbr" even though Eagle was accessing the file via "C:\Program Files (x86)\EAGLE-<VERSION_NUM>\lbr\<file_of_interest>.lbr"

I used Microsoft SysInternals Procmon.exe and then added a filter to exclude all entries whose process wasn't eagle.exe, then used eagle to open "C:\Program Files (x86)\EAGLE-<VERSION>\lbr\<file_of_interest>.lbr" . from there it was a matter of scrolling through a few entries until I saw the real path for <file_of_interest>.lbr . ref: https://technet.microsoft.com/en-us/sysinternals/default

Yeah, that is that "virtual store" issue I have been bitten by before.  Microsoft has come up with this clever "scheme" whereby if you are not allowed to put something where you are trying to put it, then it puts it in the "virtual store" under your account and creates a link from where you thought you put it to where it is.  Not a bad idea EXCEPT they don't tell you they did it and if you come at it from a different direction, you can't find the file.  Do a bit of searching on the "virtual store" and you will have a better grasp of how it works (it has been a while since I managed to shoot myself in the foot with it).  I first ran into it with the CCS C compiler when I tried to drag the license file from the CD they had sent me to the install folder where it was supposed to be.  Kept getting a notice about "invalid license file".  Had CCS send me a new file.  Tried to drag that from the email to the install folder.  Turns out both the email and the CD are considered "suspect" for lack of a better word by M$ and they do the "virtual store" thing with them then the compiler could not find the right one.  The secret turned out to be to drag the file from the email to the desktop THEN drag it to the install folder and M$ decided that was safe enough I guess.  I really hate being "hepped" - especially when it doesn't bother to tell you it did it.  Either put the stupid file where I want it or tell me "permission denied" and let me work the problem, but don't put it somewhere else and tell me everything is OK !!!

<on soap box>

Another "invention" from the Bill Gates crowd! Duh, aren't some users smart enough to know better? You want to stop hackers

(maybe) stop giving "secret" interfaces. Ha Ha.

<off soap box>

Clem