Is this a known issue?
I just says, that it can’t start the program, because the provided path doesn’t exist.
Could it be something with SeaDriveFS and NTFS permissions?
Currently SeaDrive only allows the current user to access the files. So if an executable requires admin permission to execute, it has to be run as administrator. So the administrator user cannot find the path. This is a limitation we plan to remove in later release, before 1.0.
Hi, any news on this issue? I’d like to use Seadrive to sync my developper folder, obviously not allowing executable to run is problematic in this use case…
SeaDrive is Beta. The only way is to create a simple bash script who indexes the files and make them executable. This shouldn’t be a problem.
The problem is not that simple. Chmod +x doesn’t affect files in latest Seadrive beta on the Mac (0.9.1). Can we have an official word on this?
same with 0.9.5
Any news on this? Is it a FUSE limitation?