On Sat, 2014-01-11 at 16:12 +0000, John Rose wrote:
> Martin,
>
> Output is white:
> john@JohnDesktop:~/.wine/drive_c/users/Public/Start
> Menu/Programs/Basic4android$ ls -l Basic4android.lnk
> -rw-rw-r-- 1 john john 611 May 31 2013 Basic4android.lnk
>
OK, that means this file is a hard link. and is pointing at a file that
is 611 bytes long. You can double check that its pointing to the correct
file, which I assume should be basic4android.exe, by seeing if that is
also 611 bytes.
Assuming that it is, the problem is that the hard link isn't marked as
executable. You can make it executable by changing its permissions with
Nautilus (use the permissions tab under Properties) or from the command
line with the "chmod ug+x Basic4android.lnk" command. As you'll probably
only be running it from the user its installed in, don't mark it as
world executable.
*** I don't think Basic4android.lnk is pointing at basic4android.exe but
*** its seeing what's inside the .lnk file to see what it is pointing
*** at.
*** I have a different suggestion. See below.
FYI, in Linux a symbolic link, AKA symlink, is exactly equivalent to a
Windows shortcut - a small file holding the name of the file or
directory its points to. Symlinks default to having all possible
permissions set because access is controlled by the permissions set on
the target.
However, a hard link is quite different. Creating a hard link adds
another name, with its own set of permissions, to an existing file. This
has two effects you need to know about:
(1) the hard link's permissions are the defaults for the user creating
it regardless of the permissions in the original name. This is
what you've seen: A Microsoft installer won't understand that
(2) A file with one or more hard links can only be deleted by deleting
all its hard links, which includes its original name: as long as
there is one of them left the file will continue to exist.
You can see this from the 'ls -l' output: the first number on the
line (just after the permissions) shows the number of links to the
file.
*** I notice that your Basic4android.lnk file has only one link, so it
isn't pointing at any other file. Have a look at its contents to see
what it is pointing to.
Here's what I'd do.
1) Make a safety copy
of /home/john/.local/share/applications/wine/Programs/Basic4android/
2) edit it, changing the "Exec" line so that the second argument:
/home/john/.wine/dosdevices/c:/users/Public/Start\\
Menu/Programs/Basic4android/Basic4android.lnk
becomes
/home/john/.local/share/applications/wine/Programs/Basic4android/basic4android.exe
3) Try running that. This type of fix will also solve your other
problems with the Windows version of the Android SDK.
But why are you playing with the Windows version of the SDK when there's
a Linux version available? Both versions of the SDK use Eclipse and the
Java 6 JDK.
Martin
