WINEPREFIX and Invalid command line

Questions about Wine on Linux
Locked
docrob
Level 1
Level 1
Posts: 9
Joined: Mon Mar 04, 2013 4:36 pm

WINEPREFIX and Invalid command line

Post by docrob »

I seem to be having more trouble with WINE these days than formerly. I would love to understand better what is going on, but it can be hard for us non-programmers.

I have been trying to install Serif PagePlus X7 in its own WINEPREFIX. On first attempt, it seemed to install correctly:
env WINEPREFIX=~/.wine_pageplus winecfg
env WINEPREFIX=~/.wine_pageplus wine <path to CD>/setup.exe
This went through the installation, asked for the key code and completed the installation. As a note here, the program could install as a 32 or 64 bit application. I selected the default of 64 bit.
When run, the program crashed. In a terminal, the crucial error is:
"Call from 0x7b83c742 to unimplemented function msvcr100.dll._get_dstbias, aborting"
I have installed vcrun2010 with winetricks, but this had no effect.
Eventually I deleted the WINEPREFIX, recreated it and tried to reinstall. This time, all I got was an error message "Invalid command line". I would have thought that deleting the WINEPREFIX would erase all trace of the former installation.
Oddly, invoking the same setup.exe without the WINEPREFIX does not give the Invalid command line error and the program will install to the default WINEPREFIX (.wine). However, the error relating to msvcr100.dll is persistent and I cannot find a way to overcome it.
I would be very grateful for any pointers, as it is frustrating to have had a previous version working. I used to have Version X6 working well, but something happened a while back and it now crashes with a very similar error, albeit with msvcr90.dll.

OpenSUSE 12.3, KDE 4.10.3 release 1, WINE 1.5.23
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: WINEPREFIX and Invalid command line

Post by dimesio »

When the app crashed, it may have left processes still running in the background. Deleting the wineprefix would not stop them, and they would interfere with using the wineprefix you recreated with the same name.

Two things to try:
1. Upgrade Wine; the current development release is 1.5.31.
2. Install the 32 bit version of your app to a 32 bit wineprefix.
docrob
Level 1
Level 1
Posts: 9
Joined: Mon Mar 04, 2013 4:36 pm

Re: WINEPREFIX and Invalid command line

Post by docrob »

Thank you dimesio for your quick response. I did not think of processes running in the background. So presumably a reboot following removal of the WINEPREFIX should have fixed that.

I have upgraded wine to 1.5.31 and wine-gecko to 2.21.
I created a 32 bit WINEPREFIX: WINEARCH=win32 WINEPREFIX=~/.wine_pageplus winecfg
Attempting to install into this now gives a new error:
p11-kit: couldn't load module: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
- followed by the error message: Invalid command line.

In OpenSUSE 12.3 (64 bit) there is no directory /usr/lib/pkcs11; gnome-keyring-pkcs11.so sits in /usr/lib64/pkcs11. I assume this would be a 64 bit version of the file, so do I need to find a 32 bit version and place it where WINE is looking for it?
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: WINEPREFIX and Invalid command line

Post by dimesio »

docrob wrote: In OpenSUSE 12.3 (64 bit) there is no directory /usr/lib/pkcs11; gnome-keyring-pkcs11.so sits in /usr/lib64/pkcs11. I assume this would be a 64 bit version of the file, so do I need to find a 32 bit version and place it where WINE is looking for it?
That's what you need to do to get rid of that error message. I doubt it's the cause of your problem, though, as many people get it and it doesn't seem to affect anything.

You do need winbind.

I just noticed your original post mentioned you are installing from a cd. Make sure the cd is mounted in Linux and mapped to a drive in winecfg before trying to run the installer.

If you still get the "invalid command line" message after all that, post the full terminal output, including the command used to start the installer.
docrob
Level 1
Level 1
Posts: 9
Joined: Mon Mar 04, 2013 4:36 pm

Re: WINEPREFIX and Invalid command line

Post by docrob »

Thanks again for this. I did find a 32 bit version of gnome-keyring-pkcs11.so for OpenSuSE 12.3 using rpmsearch and installed it. That got rid of the error message whether or not it actually was a problem. I checked that samba-winbind (and samba-winbind-32bit) were installed.

The CD is automatically mounted in OpenSuSE 12.3, in /var/run/media/robin, so I mapped this to K: in winecfg.

As before, the installation starts, but only gets as far as choosing the installation language before crashing with the "Invalid command line" error. I have posted the terminal output below, but have cut about 25 lines where indicated, as I don't think it is relevant to the problem, although I do not know why WINE objects to the Path[$e] key.

robin@linux-svr1:~> env WINEPREFIX=~/.wine_pageplus wine "/var/run/media/robin/PPX7 17.0.0.21 ML/setup.exe"
fixme:shell:IQueryAssociations_fnGetString 00000004: unimplemented flags!
Could not parse file "/home/robin/.local/share/applications/Qsynth-2.desktop": Invalid key name: Path[$e]
< then about 25 lines similar to above>
fixme:clusapi:GetNodeClusterState ((null),0x33eb74) stub!
fixme:advapi:DecryptFileA ("j:\\c69eb1ea1049304a803434f05c53d1\\", 00000000): stub
fixme:advapi:RegisterTraceGuidsW (0x6cd15f38, 0x6cd20180, {e2821408-c59d-418f-ad3f-aa4e792aeb79}, 1, 0x33fc90, (null), (null), 0x6cd20188,): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:thread:SetThreadStackGuarantee (0x33fb58): stub
fixme:advapi:LsaOpenPolicy ((null),0x33f448,0x00000001,0x33f434) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:advapi:LsaOpenPolicy ((null),0x33f298,0x00000001,0x33f284) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:storage:create_storagefile Storage share mode not implemented.
robin@linux-svr1:~>
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: WINEPREFIX and Invalid command line

Post by dimesio »

Following these instructions for running apps from a terminal: http://wiki.winehq.org/FAQ#run_from_terminal.
docrob
Level 1
Level 1
Posts: 9
Joined: Mon Mar 04, 2013 4:36 pm

Re: WINEPREFIX and Invalid command line

Post by docrob »

Sorry for the delay in replying - I have been out all day.

Well, this is getting interesting - thanks for the link. I have tried everything I can think of to install PagePlus to a clean WINEPREFIX. It will install/reinstall to the default WINEPREFIX (~/.wine) without errors, but apart from the very first attempt, it always brings up the "Invalid command line" error in any other WINEPREFIX.

Having drawn a blank there, I looked further at the installation in ~/.wine and the undefined symbol _get_dstbias in msvcr100.dll, as per my first post. I tried switching to the native dll, which I have never got to work previously, but this time, it was happy and loaded the program. Unfortunately it will only do this once as it leaves the pageplus.exe process running when it shuts down, so to reload the program, I have to manually kill the process.

Much to my relief, the msvcr100.dll override also got DxO ViewPoint working, although there had been no clue as to the cause of this failure from the terminal output. ViewPoint works consistently and shuts down properly.

So, on the upside, I have two important programs working now under WINE. On the downside, they are both (at the moment) in the general WINEPREFIX ~/.wine, one needs to be manually shut down and I still do not have a clue as to why PagePlus will not install into a clean WINEPREFIX. I will continue to try to understand the issues here and I am exceedingly grateful for your time, which has yielded a result. At least the pressure is now off to a large extent, although I perhaps should not mark this thread as SOLVED until the original issue is explained.

Thanks again for all your help.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: WINEPREFIX and Invalid command line

Post by dimesio »

You should file a bug for the crash from unimplemented function msvcr100.dll._get_dstbias.
docrob
Level 1
Level 1
Posts: 9
Joined: Mon Mar 04, 2013 4:36 pm

Re: WINEPREFIX and Invalid command line

Post by docrob »

Thanks for the reminder. I'm about to go on holiday, but I'll do that when I return.
Locked