Friday, December 16, 2005, 10:45:06 PM, Dan Kegel wrote:
On 12/16/05, Vitaliy Margolen wine-devel@kievinfo.com wrote:
$ rm -rf .wine $ wine/wine notepad.exe /home/dank/.wine updated successfully. $ find .wine -name regsvr32.exe -ls 4669487 0 lrwxrwxrwx 1 dank dank 40 Dec 17 03:35 .wine/drive_c/windows/system32/regsvr32.exe -> /home/dank/wine/programs/regsvr32.exe.so
Yup, exactly what I said.
? You were talking about something being overwritten with a native copy by an installer, but you can see from the log that no installer was run.
That file is not in your ~/.wine directory. When you removed it, you haven't touched the actual "regsvr32.exe.so" file.
Run 'file /home/dank/wine/programs/regsvr32.exe.so' to see what I'm talking about.
OK:
$ file /home/dank/wine/programs/regsvr32.exe.so /home/dank/wine/programs/regsvr32.exe.so: symbolic link to `regsvr32/regsvr32.exe.so' $ file /home/dank/wine/programs/regsvr32/regsvr32.exe.so /home/dank/wine/programs/regsvr32/regsvr32.exe.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
What does that tell you? The file looks like a perfectly good ELF file, as one would expect. How do you explain the next line from the log,
$ wine/wine .wine/drive_c/windows/system32/regsvr32.exe wine: cannot open builtin library for L"Z:\home\dank\.wine\drive_c\windows\system32\regsvr32.exe": /home/dank/wine/programs/regsvr32.exe.so: invalid ELF header
Yeah. The only time I have seen this message in relation to regsvr32.exe is only when Wine's builtin regsvr32.exe.so was overwritten with native PE executable. That could happen only of you have write access to the the place where you installed wine, or if you running it from the source tree.
In this case I don't know then what is going on. Could you follow all the symlinks and verify that it is in fact ELF? Also can you remove this file and remake it? If it is ELF it must be corrupted in some way.
Vitaliy.