John W. Sheppard, PhD wrote:
To answer your questions, yes they were latex packages, and yes I am using
MiKTeX.
I had only looked at the textclass.lst file in the C:\Program
Files\LyX\Resources\lyx directory. You are correct that the one that I did
not check (in C:\Documents and
Settings\your_id_here\Application Data\lyx) is 0-length. I copied the global
one to the local one but that didn't work.
That's a bit curious. I take it that you still got the "unable to find
layout description/check textclass.lst" message after you copied the
global textclass.lst file over the broken local one?
Other than comments, the contents of the textclass.lst file is a list of
LaTeX document classes, each line culminating with true or false
according to whether a layout was found. Is anybody in the (global)
list flagged true? In particular, you should have the following line:
"article" "article" "article" "true"
which signals that the basic article class has a layout. If nobody is
flagged true (don't know if that's even possible), it might signal a
fundamental problem with MiKTeX.
Speaking of MiKTeX, have you verified that it's working post-update?
When I try running sh configure, it doesn't run because paths don't appear
to be set up right. I decided not to try to fix that because I wasn't sure
it would get me anywhere.
LyX 1.3.6 contains a "path prefix" that it prepends to your system path.
The path prefix contains (should contain?) the path to the MinSYS bin
directory, where sh and related programs live. So you don't need that
on your system path for LyX to work.
In any case, the main purpose of running the configure script would be
to generate the global textclass.lst file, which you already have. The
secondary purpose would be to verify that latex works (and that LyX can
find it).
So the immediate mystery is why LyX won't settle for the global
textclass.lst file. Best guess from here would be that something is
amiss with the file (corrupted, or doesn't show any usable layouts).
Paul
