Angus Leeming wrote:
Paul A. Rubin wrote:
If so, maybe I can hack the script to pause
right at the top, so that (maybe) I could see what if anything was
painted in the DOS window that spawned (and died).
It is. Try adding something like:
$ cat trial.sh
#! /bin/sh
while true
do
echo "Hello!"
done
Whoops, silly me. I forgot that the installer will overwrite the hacked
script before running it, so no joy there.
Meanwhile, the plot thickens. I created a plain user account (no admin
privileges) on my laptop and installed successfully, multiple times with
variations in the installation path. No manifestation of the bug. The
only change was that the plain user cannot install to C:\Program Files.
Ok, fine, back to my regular admin account, try installing someplace
other than C:\Program Files. No joy, the bug is still there. So it
would seem to be something specific to the administrator account.
Still logged in as administrator, I tried shutting down every background
application I could, then retried installation. No joy, same bug. The
details windows in the installer shows nothing, the system log files
show nothing, the process viewer does not show sh.exe spawning. I
*think* a small window opens just before the error message pops up, but
if so it closes too fast to really see, and in any case it's behind the
error message.
Note that, unlike Ekkehart, I get a successful installation in the sense
that LyX runs when I start it, and does a "local" configuration. The
textclass.lst file and its siblings don't exist in C:\Program
Files\LyX\Resources\lyx, but I can open a shell there and run the
configuration script manually with no problem. I'm not sure what to try
next.
BTW, I discovered that a user without admin privileges can install LyX
but can't run the uninstaller. (I got a message that the uninstaller
requires admin privileges.) However, the plain user can delete all the
files.
Paul
