Printable View
Friends, I have installed wine in my system but I am having some problem with that. My problem is that, I am not able to start on Windows programs by means of wine and the reason behind this is that it is not allowing me to test out the executable bit within the properties. I am not having any idea that how this issue can be fixed. If you know anything regarding this then please let me know that. I will be thankful to all the replies.
So as you told that you are not able to launch any if the Windows program through wine. You can try one thing that try to run that as root and see if that can help you launch the program. If that is also not helping you then you can move that file to the home folder where you store all the things and try to start the program from there. Right click on that file and make that executable. See if that can be executed from there. I hope that this will help you to solve the issue for you.
Well this is only a consideration that someone may possibly drop extra light if I am incorrect but while you execute an executable files there are some programs that leave with that. The kernel expresses the entire configuration files to home directory. I am only guessing that from a Drive otherwise partition that is not home directory then kernel has not the space intended for the configuration files to go beings it perceive there is no home designed for it and won’t run. That is the most excellent I can carry out. Possibly someone can focus additional light on it and we together can be taught something with that.
I would like to tell you that the wine not at all desired the execute bit to be turned on in the initial place so I would tell you to do something. You just have to open the Nautilus and after that right click any *.exe file. Select properties that is the last option in that. Now go to Open with -> Add -> Use a custom command and there you have to type wine and mark this as the default for the file. Save the changed and close the property box. Once you are done with this then if you double click on any of the .exe file then that file will be opened with the wine.
There is dissimilarity in the default wine connection.If you want to confirm that then you can go to /usr/share/applications/wine and right click on that and choose properties. You will be able to observe something called "cautious-launcher" in the beginning of the Command. If you open /usr/bin/cautious-launcher as well as open that you can observe that it is the script that in point of fact confirms to perceive if the file is executable. The method suggested above will get rid of the cautious-launcher. So here is one other method that can confirm all this. So open Terminal and there you have to type:
Quote:
wine "/path/to/whatever.exe"
I would like to tell you that installer packages and normal runtime .exe files are not similar. Wine will execute the installer packages on or after anywhere, but it should get the installed .exe files that should be there in /home/user/.wine/drive_c, anywhere. The connected .dll files have got to be in the correct places if that is not there then the .exe will not able to locate them. It can be a slight complicated. I do not make use of wine to a great extent. It is typically just to experiment to observe what happens, so I am surely no specialist. It does seem that the newest wine edition is somewhat different in action as of the older ones.