One more comment. It seems that MiKTeX 2.7 may instead place the texmf directory in the root of the hard drive. On my C drive, I find a texmf directory so located.
Hadn't noticed it previously. wrb > -----Original Message----- > From: Bob Lounsbury [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 16, 2008 6:59 PM > To: [EMAIL PROTECTED] > Cc: LyX User > Subject: Re: Layout and Class Files on Windows Distribution > > On Sun, Mar 16, 2008 at 3:31 PM, William R. Buckley > <[EMAIL PROTECTED]> wrote: > > Respecting what follows, your corrections of my > misunderstandings are > > solicited. > > > > OK. The digest goes like this: > > > > 1. It is the case that all installs to my single user computer are > > for use by all users. > > In this case it would be advisable to setup a localtexmf > directory to a shared location. > > > 2. MiKTeX has a requirement that the user maintain any *custom* > > class, style, include, other tex files, and layout files. One may > > choose to use any of the directories listed in MiKTeX Settings, > > though it would generally be better practice to add a new > path to the > > available roots, and store files in that root, thus obtaining an > > expected retention of setting in the face of MiKTeX upgrade. > > Of course, if the settings are lost, then the path will > need to be > > added to any upgrade. > > This is true of any tex distribution. > > > The *user config* directory is indeed not yet made, as in mkdir. > > I also note that the *user config* *user data* and *common* roots > > may not be altered, at least via MiKTeX Settings. > > Seems to be the case so far for MiKTeX 2.7 not for 2.6 (at > least the part that the 'user config;' directory is not made > by default). > > > 3. To be sure, when I mentioned following the given advice, I did > > follow all parts. Particularly, I refer to the notions of > > reconfiguration for both LyX and MiKTeX. Thus, when I added paths > > for the missing texmf subtree, I not only added a root and > subtree to > > MiKTeX, the FNDB was refreshed and Update Formats (thought this > > latter step may have no direct impact upon my current need) need), > > and also reconfigure and restart LyX. Both of these tasks > have been > > performed multiple times, and these times being subsequent to > > alteration of roots and addition of files thereto. > > Very good practice. :-} > > > 4. I did alter the layout file to read > > > > > > \DeclareLaTeXClass[llncs]{article (Springer LNCS)} > > > > Upon thereafter reconfiguring LyX, the class was recognised. > > So, now I am moving along. > > This is strange as I also installed llncs.cls and after > refreshing MiKTeX and LyX everything was fine. Meaning I did > not need to alter llncs.layout and 'article (Springer LNCS)' > was immediately available. > > > I had previously altered this statement, to include > [springer] and > > not [llncs], owing to some suggestion hinted by other > layout files. > > The correction to the bracketed label brought access to > the document > > class llncs. > > > > Thanks to all for all the help you have given. Perhaps > some of this > > information will find its way into the LyX documentation. > > This info is included in Section 5.2 of the Help->Customization file. > Although it is mostly written for *nix systems as LyX was > initially written for it. But the concepts are exactly the > same for Windoze :-}. > > As usual there are always resources available on the net: > > http://wiki.lyx.org/Layouts/CreatingLayouts > http://troubleshooters.a3b3.com/lpm/200210/200210.htm > http://www.etl.luc.edu/gkt/writing/how_to/lyx_ieee > http://www.nabble.com/forum/Search.jtp?query=adding+classes+to > +lyx&daterange=0&startdate=&enddate= > > > wrb > > > Cheers, > /Bob > >
