Since Version 24 came it appears that I am supposed to keep my user defined models in a different place than the factory models, However I have not yet made the switch from the file structure I had previously.  I keep my models in subdirectories in the factory lib and sym folders.

That has been the advice from here for many years prior to V24.

I edited the Pin locations in the TI supplied OPA891_Model_V1p1.lib and renamed the edited version to OPA891_Model_V1p1SAH.lib.  I presume that I must copy that entire file to a directory where the symbol can call it.

I have made 2 symbols: OPA891 and OPA2891 which should both call the same Model.

I edited the Attributes as follows:

Prefix X

SpiceModel   TSS/OPA891.sub  (my customized models are in a TSS subdirectory)

Value     OPA891 

Remaining attributes are blank

It seems that the SpiceModel attribute should be OPA891_Model_V1p1SAH.lib  rather than .sub. along with directions for the symbol to find it.

The SpiceModel attribute is optional. But if you assign a value to it, that should be exactly the name the of the model file. Whether this has a "sub", "lib", or any other suffix makes no difference. If you leave it blank, you need to inform LTspice of the name of the model file some other way. I prefer adding:

.lib ModelFileName

..as a SPICE directive. This is visible on the schematic and unambiguous. It is also easy to view this file file by Right-clicking on the directive > Open.

There is a whole lot of other stuff in that file other than the opamp model itself.  Should the symbol call the whole .lib file and it will figure out which part to use?

That is exactly what the .lib directive does.

Sorry for the newbee questions, but figuring out the directory structure in version 24 isn't easy for me.

I'm still smarting from when an attempted install of version 24 erased my entire Win 7 LTSpice installation without warning

That's strange, as I'm not sure V24 will run on Win7, according to the ADI website.

You would be wise to back up critical files before making any major changes to your system. I would imagine you have heard that advice before. I recommend you have a regular backup regime in place, preferably an automatic schedule. You never know when disaster will strike - don't make it any worse by not having backups.

--