RK wrote:

Thanks Adi (and Neil) for the quick reply. I have tried to run reconfigure, but
it fails to launch. I did not install Miktek as a part of the installation
because it was already installed on my machine. But I will try to reinstall it
to see if it helps.


Reinstalling MiKTeX probably won't help if MiKTeX currently works. Try the following:

1. Make sure MiKTeX's bin directory is on your system command path. If LyX can't find latex.exe, all bets are off.

2. Locate your LyX user directory. Usually it's C:\Documents and Settings\<your login>\Application Data\lyx15, but if not Help -> About LyX will tell you where to find it. ('~' expands to your Windows home directory.) Delete that directory (e.g., ...\Application Data\lyx15) and open a command prompt in its parent directory (e.g., ...\Application Data).

3. Make sure MiKTeX is properly installed and visible by running 'kpsewhich article.cls' from the command prompt. It should cough up the path to article.cls. If DOS says it doesn't recognize kpsewhich as a command, MiKTeX's bin directory is not on the command path. If you get a null response, the MiKTeX installation may be hosed.

4. Assuming the previous step went ok, either use MiKTeX's Settings applet to set on-the-fly package installation to "no" or "ask me first", or else ensure you have a live Internet connection and MiKTeX is pointed to a valid repository, then make some popcorn and a pitcher of your favorite beverage. Then run

  <path to LyX>\bin\python.exe <path to LyX>\Resources\configure.py

and watch the fireworks. In particular, look for a message fairly early that latex.exe was found, and then messages that key classes such as article.cls were found. (You'll get a lot of not founds on inessential stuff, which is no worry.)

5. Assuming that went ok, try to start LyX and see if things are working better. If not, there should be a file named configure.log in the (reconstructed) user directory. Look for indications of a problem and, if you can't figure it out, post it here.

Good luck,
Paul

Reply via email to