In a recent message <[EMAIL PROTECTED]>, Paul A. Rubin
<[EMAIL PROTECTED]> wrote.
[...]
I'm sure Uwe will want to fix the updater, but the question now is
whether we can isolate what caused the problem. This is always an
adventure, particularly on Windows systems, because differences in
system configuration often turn out to be the difference.
This I can believe. I shouldn't worry about it too much at this stage,
it might just be an isolated glitch. No one else seems to be having this
problem by the look of it.
Did you ascertain before reinstalling IM that IM itself was damaged (as
opposed to simply being lost from the path)?
I didn't, Paul.
Also, before the upgrade, was IM on the LyX path prefix or on the
system command path (or both), and after the upgrade was it missing
from those paths?
After the upgrade the LyX path pointed to the version of IM that gets
installed within the LyX hierarchy. I'm not sure where the pointer was
pointing (I can't believe I wrote that) before the update. I've now set
the path within LyX to point to my new IM installation.
I'm not sure this matters, but do you have a full version of Python
installed? (I don't know if the updater uses Python, but the regular
installer does, and apparently I avoided a known bug in an earlier
installer because I have Python 2.3 rather than 2.5 installed.)
I have the full version of Python 2.5 installed, which LyX finds and
adjusts the path accordingly.
Just an afterthought, does installing LyX make changes to the registry?
I didn't think it did, but I do have software installed that is supposed
to protect the registry from changes.
Regards,
Nick.
--
Nick Hopton and Anne Hopton
Caversham, Reading, England
<[EMAIL PROTECTED]>
