Page 1 of 1

Bug: Shared Folder: Cannot clear Read-Only Attribute

Posted: 15. Nov 2008, 16:33
by Ohmu
VirtualBox 1.5.6_OSE
Host: Ubuntu Heron
Guest: Vista SP1
Guest Addns installed

In Ubuntu host I've created /my/share/ and done chmod a+rwx /my/share

In VirtualBox settings, I've set this to my shared folder & ensured 'Read Only' attribute is unset.

In Vista SP1 client, I have mapped this to my Y: drive

I point Windows Explorer to Y:, right click, Create New Folder
(Minor)Problem: It's invisible. Needs a rightclick+refresh to see it.

Major Problem: Right click on it, Properties: its 'Read Only' attribute is set. I clear it, Apply, ok. Now I bring up the properties again. It has reverted!!!

Total mystery. I can write files into this folder. I can create an empty doc, type into it, save it.

This problem is affecting me because I need to set Visual Studio to build into the shared folder: Y:\ReleaseBuild\ and Visual Studio is not allowing it, presumably as it sees it as readonly.

Please someone fix!!!

Sam|Ohmu

Bug filed

Posted: 16. Nov 2008, 13:55
by Ohmu
http://www.virtualbox.org/ticket/2592

One has already been filed, so I've simply added my post to this.

Sam|Ohmu

Posted: 16. Nov 2008, 16:22
by Sasquatch
Is the box ticked or filled? If it's filled, it means that there might be some read-only files in the folder.

As for Visual Studio, there is a known limitation of the SF. Compilers can't build on it. This is with every compiler, Windows, Linux, you name it.

Posted: 16. Nov 2008, 18:48
by Ohmu
Is the box ticked or filled? If it's filled, it means that there might be some read-only files in the folder.
Box is filled.
By clicking I cycle ->clear->ticked->filled->clear->...
I clear it & ok
then do properties again
and it is again filled

Now I create a new (hence empty) folder (I've checked ls -la from linuxhost. There's no hidden file being created inside the new folder) ...and do the same process, right-clicking on this folder -> properties -> ....
it re-fills the box each time

Creating a new file, the file behaves ok. It's just folders that play up.
As for Visual Studio, there is a known limitation of the SF. Compilers can't build on it. This is with every compiler, Windows, Linux, you name it.
It may be that the compiler refuses to attempt to write to a read-only folder.

Would this approach fail even without this read-only complication?

If it's a definite nono, I'll have to find some other way. Do you know why this is the case?

Posted: 17. Nov 2008, 16:44
by Sasquatch
Take your avarage Windows folder, e.g. create one on your desktop. It will have that box filled too. It's not ticked, so it's not marked as read only.

I'm locking this one, it's not a bug, nor an issue specific on Shared Folders. VS probably has a problem with network resources. Else set up Samba on your Host and use that instead.