Philip A. Viton wrote:
I accepted all the suggestions except that I put Lyx into
c:\ProgramFiles\Lyx instead of "c:\Program Files\Lyx" (with a space).
1.3.6pre17 can be installed to C:\Program Files and (mostly) works fine
from there.
This time the installer posted a message "Failed attempting to execute
the configure script". On clicking OK, the main thread resumed, saying
that Lyx had been successfully installed. But when the program tried to
start it reported "LyX wasn't able to find its layout descriptors" and
closed.
Is it possible that python and/or mysys were not installed correctly?
Neither is in my path - should they be?
Python is not needed for the installation script to run. Msys is, but
it does not need to be on the Windows command path. On my machine,
Python is on the path but Msys is not.
May I say that the experimental all-in-one installer seems to me to be
preferable, certainly to a new user. I understand the problems with
including everything; still, in the piecemeal installer, I think that
perhaps it should be more obvious that you need to interrupt the Lyx
installation routine to retrieve and install the various packages.
If there are things I can report that can help diagnose the problem(s),
please let me know.
Do you have a C:\Documents and Settings\<your logon id here>\Application
Data\lyx directory? If no, open a DOS console, cd to
C:\ProgramFiles\LyX\bin, and run lyx -dbg 3. Hopefully near the top of
the output will be a message telling you where LyX is looking for
lyxrc.defaults.
Now take a look inside lyxrc.defaults (in the aforementioned directory).
There should be a line near the bottom that looks like
\path_prefix "C:\Program
Files\msys\1.0\bin;C:\PROGRA~1\Python23;C:\TeX\MiKTeX\miktex\bin;C:\gs\gs8.13\bin;C:\Program
Files\ImageMagick-6.0.3-Q16"
If it's not there, or incorrect, it may signal a problem with the
installation of msys.
One other question (bit of a long-shot): do you have admin privileges
on your machine? People get so used to Windows having limited security
that occasionally they're ambushed when a write-permissions problem occurs.
-- Paul
- Re: the new install for win32 Paul A. Rubin
-
