Printable View
I just newly learn Linux but here I really not understood what to do. I mean how can I enable executable bit? I cannot start on Windows programs with Linux wine because it cannot permit check the executable bit in the properties. How do I repair this? Anyone have any idea regarding this or anyone ever heard about this? Please someone help me or someone suggest me some information about my problem.
Well this is only an idea somebody could shed more light if I am incorrect but while you run an executable files there are programs which go with that. The kernel expresses all configuration files to the home directory. I am just estimating that from a Drive or panel that is not the home directory after that kernel has not put for the configuration files to go beings it observes there is no home for it and won’t sprint. That is the most excellent I can do. Possibly somebody can shed more light on it and we both can discover something.
I possibly should not be affectation in this subject since it is been so extended since I have utilized wine that I am astonished I memorize how to spell it. First, there has been altering to how Ubuntu or Mint auto mounts an NTFS or FAT32 partition on the soar. It utilized to rise with every folder and files set at 0700 meaning the whole thing was executable. Now it rises with folders at 0700 and files at 0600, the 0600 means the implement bit has been twisted off. Second, as I remember wine not at all required the implement bit to be twisted on in the primary place so I would like you to attempt something: unlock Nautilus and right click on *.exe file. After that choose Properties- Open with- Add- utilize a custom command and after that enter in wine.
Actually there is dissimilarity in the default wine association and the one you recommended. You can confirm this by going to /usr/share/applications/wine, right click and choosing properties. In the Command you will perceive at the extremely start somewhat called "cautious-launcher". If you go to /usr/bin/cautious-launcher and unlock it you will observe that it is a script which actually checks to perceive if the file is executable: programs cannot be executed while they lack the implement bit. My technique eliminates the careful launcher. Here is one more way to confirm all this. Unlock a Terminal and enter:
They as well inflict this on a java jar file even though a jar file is not an executable body, it is a records.Code:wine "/path/to/anything.exe"
There is dissimilarity between installer packages and usual runtime .exe files, IME. Wine will sprint installer packages from anyplace, but it likes the installed .exe files to be in /home/user/.wine/drive c, someplace. The linked .dll files have to be in the appropriate places, too, or the .exe won't locate them. It can be a slight tricky. I don't utilize wine for much, generally just for experimenting to observe what occurs, so I am definitely no specialist. It does appear that the most recent wine version is faintly dissimilar in action from the older ones.