Richard Heck wrote:
[EMAIL PROTECTED] wrote:
Hey guys, how are you today?
Well, I've tried to install the Lyx 1.4 and old versions, but I can't.
Actually I tried from many ways to do it on Windows XP SP2:
- from "lyx-144-4-bundle.exe" - complete (74mb);
- from "lyx-144-4.exe" - (8mb); and...
- from the "LyXPackageComplete-3-08.rar" - berilOS Developer (73mb).
All this ways seems to be good installation, but when I run the program, I only see the same error:
RuntimeError: Can not locate 'w9xpopen.exe' which is needed for pope
th your shell or platform.
LyX: Ready!
LyXTextClassList::Read: unable to find textclass file `'. Exiting.
And then, the program abort! I have the same error with old versions. Can
somebody help me please? I'm an old Lyx user, but now I need to abandon this
software if this can't be solved... :(
I don't know what the first error is. That file has to do with python.
Do you have a working python installation? As for the second, it has
been discussed on the list several times. Have a look at the archives.
The errors are likely to be related: if Python is broken, the
installation script is probably doomed, hence the null textclass.lst file.
As Richard said, w9xpopen.exe is a Python file. (Apparently Jasc uses a
file of the same name in Paint Shop Pro, but the bit about "shell or
platform" coupled with the fact that LyX uses Python and not PSP
strongly suggests Python here.) Googling around indicates that Python
uses w9xpopen.exe on Win 95/98 systems. You indicated you are using XP
SP2, so you don't need that file. (I have both a full installation of
Python 2.3 and the 'thin' installation that LyX does on its own, and
neither has that file.) Any chance you upgraded this machine from 9x to XP?
If you have Python installed someplace, you might try uninstalling it
(or at least moving it off the Windows command path momentarily) and see
if that cures the bug. It might also be a good idea to uninstall any
LyX installations, and delete the user data folder(s) they created.
Then reinstall LyX, cross fingers and hope for the best.
If you're not sure about whether there is a "ghost" installation of
Python floating around, you could try searching the entire hard drive
for python*.exe. That should (eventually) point to any and all Python
installations.
/Paul
