Errors by creating a 32 bit prefix

Questions about Wine on Linux
Locked
User avatar
gatoso
Level 1
Level 1
Posts: 8
Joined: Sat Dec 07, 2013 9:03 pm

Errors by creating a 32 bit prefix

Post by gatoso »

Hello

When I try to create a 32 bits prefix, I am getting this errors:

Code: Select all

> WINEARCH=win32 WINEPREFIX=/home/gatoso/Office2007 winecfg
wine: created the configuration directory '/home/gatoso/Office2007'
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:storage:create_storagefile Storage share mode not implemented.
p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio
fixme:iphlpapi:NotifyAddrChange (Handle 0x10fe8b0, overlapped 0x10fe8bc): stub
wine: configuration in '/home/gatoso/Office2007' has been updated.
I have read that error:

err:mscoree:LoadLibraryShim error reading registry key for installroot

is due either to that I am trying to create the prefix as root (this is not the case), or I have installed the 64 bit version of WINE for running a 32-bit application.

I am on OpenSUSE 64 bits, winecfg is included in a package called: wine, it also provides wine64, not wine 32 bits (or, just, wine), it is packaged into another package called: wine-32bit, that is to say:

wine-32bit (1.7.10) package:
/usr/bin/wine

wine (1.7.10) package:
/usr/bin/wine64
/usr/bin/winecfg

Perhaps is this related?
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Errors by creating a 32 bit prefix

Post by dimesio »

Except for the p11-kit message, which isn't coming from Wine, that console output is perfectly normal for creation of a wineprefix. The p11-kit message is harmless, but you can get rid of it by either installing 32 bit p11-kit or uninstalling it, if you don't need it.

Wine prints a lot of messages in the console. If your app is working, don't worry about them.
User avatar
gatoso
Level 1
Level 1
Posts: 8
Joined: Sat Dec 07, 2013 9:03 pm

Re: Errors by creating a 32 bit prefix

Post by gatoso »

That is the issue, I am having troubles with Microsoft Office Word 2007, it has been installed from the Microsoft Office Plus 2007 CD. I can install it with no problems. These appears by launching the application.

I am on OpenSUSE 64bits

Here the terminal output when I create the 32bits prefix:

Code: Select all

$ WINEARCH=win32 WINEPREFIX=/home/gatoso/Office2007 winecfg
wine: created the configuration directory '/home/gatoso/Office2007'
Application tried to create a window, but no driver could be loaded.
The explorer process failed to start.
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:storage:create_storagefile Storage share mode not implemented.
p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio
fixme:iphlpapi:NotifyAddrChange (Handle 0x10fe8b0, overlapped 0x10fe8bc): stub
wine: configuration in '/home/gatoso/Office2007' has been updated.
Here the terminal output when I install Office:

$ WINEPREFIX=/home/gatoso/Office2007/ wine Descargas/Office\ 2007\ Español/SETUP.EXE

http://yadi.sk/d/ILU8JOa5FoVHL

Here the terminal output of the first launch of Word:

$ WINEPREFIX=/home/gatoso/Office2007/ wine Office2007/drive_c/Program\ Files/Microsoft\ Office/Office12/WINWORD.EXE

http://yadi.sk/d/vC4jBdOgFoVcf

After of this, when I launch the program, I get the configuration window, again. Here a screen capture of the window that I am referring: image

Here the terminal output of the second launch of Word:

$ WINEPREFIX=/home/gatoso/Office2007/ wine Office2007/drive_c/Program\ Files/Microsoft\ Office/Office12/WINWORD.EXE

http://yadi.sk/d/uzZ4mQAkFoVoi

The window configuration appears over and over, each time I launch word, this is very annoying. Also, I can't move the window of Word, I mean I can't drag, hold and leave it in another position.

Please, help =/
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Errors by creating a 32 bit prefix

Post by dimesio »

Code: Select all

Application tried to create a window, but no driver could be loaded.
The explorer process failed to start.
That's definitely a problem.
After of this, when I launch the program, I get the configuration window, again.
The usual cause of that is that you have installed to a 64 bit wineprefix. However, the commands you say you used are correct for a 32 bit wineprefix.

What I think may be happening is that you are restarting Word with processes still left running from the previous attempt. Find and kill them.
User avatar
gatoso
Level 1
Level 1
Posts: 8
Joined: Sat Dec 07, 2013 9:03 pm

Re: Errors by creating a 32 bit prefix

Post by gatoso »

dimesio wrote:

Code: Select all

Application tried to create a window, but no driver could be loaded.
The explorer process failed to start.
That's definitely a problem.
I have got that error, just once, in that oportunity
dimesio wrote:
After of this, when I launch the program, I get the configuration window, again.
The usual cause of that is that you have installed to a 64 bit wineprefix. However, the commands you say you used are correct for a 32 bit wineprefix.

What I think may be happening is that you are restarting Word with processes still left running from the previous attempt. Find and kill them.
I already had thought that, I made what you say, but wine was not running. Anyway, I have tried out it again, after launching and close Word:

Code: Select all

ps -aux | grep wine
gatoso    2749  0.0  0.0  10540   928 pts/1    S+   21:23   0:00 grep --color=auto wine
As you see wine was not running.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Errors by creating a 32 bit prefix

Post by dimesio »

Looking for "wine" isn't enough. The command I usually use to kill everything Office might have left running is:

Code: Select all

killall wineserver ose.exe services.exe plugplay.exe winedevice.exe rpcss.exe explorer.exe
But if that's not it, then the only other thing I know of that could make Office setup restart every time you start Word is that is wasn't properly installed in the first place. So reinstall to a clean wineprefix following the instructions in the AppDB.
User avatar
gatoso
Level 1
Level 1
Posts: 8
Joined: Sat Dec 07, 2013 9:03 pm

Re: Errors by creating a 32 bit prefix

Post by gatoso »

dimesio wrote:Looking for "wine" isn't enough. The command I usually use to kill everything Office might have left running is:

Code: Select all

killall wineserver ose.exe services.exe plugplay.exe winedevice.exe rpcss.exe explorer.exe
does not work. After launching and to close Word:

Code: Select all

> killall wineserver ose.exe services.exe plugplay.exe winedevice.exe rpcss.exe explorer.exe
wineserver: no process found
ose.exe: no process found
services.exe: no process found
plugplay.exe: no process found
winedevice.exe: no process found
rpcss.exe: no process found
explorer.exe: no process found
dimesio wrote:But if that's not it, then the only other thing I know of that could make Office setup restart every time you start Word is that is wasn't properly installed in the first place. So reinstall to a clean wineprefix following the instructions in the AppDB.
I swear I have tried by using a clean wineprefix at least ten times, before starting this thread. Each time, I have used:

> WINEARCH=win32 WINEPREFIX=/home/gatoso/Office2007 winecfg

I have tried out overriding riched20.dll globally and only for the prefix, none has worked.

On Mint and Archlinux, I also installed Office 2007 and with no problems. Now on OpenSUSE I have troubles, to this is due I think is a problem in the opensuse wine package or something, related to wine, is different in this distro.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Errors by creating a 32 bit prefix

Post by dimesio »

On Mint and Archlinux, I also installed Office 2007 and with no problems. Now on OpenSUSE I have troubles, to this is due I think is a problem in the opensuse wine package
I'm on 64 bit openSUSE 12.3, using their 1.7.10 packages, and Office 2007 works fine. But if you really think it's the package, the way to test that is to compile Wine yourself and see if you still have the problem.
User avatar
gatoso
Level 1
Level 1
Posts: 8
Joined: Sat Dec 07, 2013 9:03 pm

Re: Errors by creating a 32 bit prefix

Post by gatoso »

Wine of what repository do you use?
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Errors by creating a 32 bit prefix

Post by dimesio »

Locked