Dear Sir/Madam,
I downloaded the latest cvs of wine and compiled it. All went well but it seems that the regsvr32.exe.so file wasn't created properly. If check the dependency o f expand.exe.so, winver.exe.so, winepath.exe.so, I can see all the proper files that it needs but if I do it on regsvr32.exe.so, it says "regsvr32.exe.so: Not a dynamic executable". I have that his problem for the last 3-4 months. I used a text editor and it seems that the header is the regsvr 32.exe.so looks like an msdos .exe file (ex, first 2 characters have "MZ") but e xpand,winver, and winepath start with "^^". The reason I have notified it is when I run ie 5/6, It stops at the point saying
"/usr/local/bin/wine: cannot open builtin library for 'C:\windows\system\regsvr32.exe': /usr/local/lib/wine/regsvr32.exe.so: invalid ELF header".
would you please suggest me what I have to do
________________________________________________________________________ Yahoo! India Careers: Over 50,000 jobs online Go to: http://yahoo.naukri.com/
On Fri, 02 Jul 2004 12:26:05 +0100, Shiva Ram Krishna wrote:
would you please suggest me what I have to do
Basically, debug it. This has been an intermittent problem since at least Christmas of this year, but I was never able to nail it. Basically our regsvr32.exe.so file is being replaced with a native REGSVR32.EXE during the IE install because of the symlink put in place. I don't know what the solution is to this. Maybe preventing the Wine FS code writing to symlinks if they are inside the windows directory or something equally hackish - or just ensuring that the exe.so files are always readonly.
thanks -mike
Can't the wine installer chmod a-w all of those right when it sets things up?
It'd solve the problem more elegantly than having to add extra code that might break other programs.
On Fri, 2004-07-02 at 09:14, Mike Hearn wrote:
On Fri, 02 Jul 2004 12:26:05 +0100, Shiva Ram Krishna wrote:
would you please suggest me what I have to do
Basically, debug it. This has been an intermittent problem since at least Christmas of this year, but I was never able to nail it. Basically our regsvr32.exe.so file is being replaced with a native REGSVR32.EXE during the IE install because of the symlink put in place. I don't know what the solution is to this. Maybe preventing the Wine FS code writing to symlinks if they are inside the windows directory or something equally hackish - or just ensuring that the exe.so files are always readonly.
thanks -mike
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Jul 02, 2004 at 12:42:02PM -0400, Andrei Barbu wrote:
Can't the wine installer chmod a-w all of those right when it sets things up?
This won't work if the WINDOWS\SYSTEM directory is on a VFAT partition.
solution is to this. Maybe preventing the Wine FS code writing to
symlinks
if they are inside the windows directory or something equally hackish
- - or
just ensuring that the exe.so files are always readonly.
It'd solve the problem more elegantly than having to add extra code that might break other programs.
It might be simplest to simply reinstall Wine after installing IE. Or, if we can get Wine to run the native REGSRVR32.EXE with no trouble, it shouldn't be a problem when the Wine version gets overwritten with the native version. Someone who wants a Microsoft-free installation won't install IE anyway.