Why didn’t you just look in the manual?To prepare an encrypted library, you need to invoke LTspice from the command line with the command line option "-encrypt". You will need to first backup the library because it will be replaced with the encrypted version. THERE EXISTS NO UTILITY TO CONVERT AN ENCRYPTED LIBRARY BACK TO CLEAR TEXT. Below summarizes the two steps:
1. Make a backup copy of the library. The version you encrypt is deleted.
2. From a command line, type \XVIIx64.exe -encrypt <filename>
The file <filename> will be replaced with an encrypted version. The encryption process will take a few minutes. One this process is finished, you have an encrypted ASCII file. It's possible to add a copyright notice above the "* Begin:" line, but the first 9 lines of the file must remain unchanged and each line of copyright notice you add must begin with the character “*”
I didn't know this because I have absolutely no use for encrypted files.
Of course, if you did have a use, well… RTFM, no?I didn't know this because I have absolutely no use for encrypted files.
Absolutely!Of course, if you did have a use, well… RTFM, no?
Yes, of course. My purpose is to hide details of my development and to keep on using a working file in a schematic.Are you asking how you can encrypt the file so that LTspice can use the file? If so, you might be out of luck if you don't know what algorithm LTspice uses to decrypt such files.
heh...that's silly.A pox on everybody that does have a use for encrypted LTspice library files. I won't use your files and I certainly won't use your products.
Maybe, but sometimes being an iconoclast can be difficult.heh...that's silly.![]()
Well post #3 gave you the magic key. Use it carefully.Yes, of course. My purpose is to hide details of my development and to keep on using a working file in a schematic.
Online research didn't bring any good idea on how to get it.