virtualbox.org

I am using VirtualBox 4.0.8 on a Salix (Slackware 13.37) 64bit host with a Win7 64bit.

I tried both: to integrate the shared folder automatically or with Explorer.

All the files I create in Win7 or copy from my Linux host to the shared folder (\\vboxsrv\VBoxShared) have the attribute N (no access) so that my Tcl program gets the following answers:

file readable myfile -> 0
file writable myfile -> 0

Other odd symptoms:

• Computer administration for drives shows no drive with the (automatically E: or manually Z:) installed network drive
• Properties for the netdrive (E: or Z:) show: Not connected netdrive; Filesystem: VBoxSharedFolderFS
• icacls shows errors
• cacls says: "Not a ntfs drive"

But cat myfile works and it can be edited and saved. It seems to be (just) an ACL mess. But for developing and testing programs in VirtualBox correct attributes are important.

Does anybody have an idea?

Slackware does not seem to be a supported host OS (see section 1.4 of user manual).

Well, I have no installation problem:

It should be possible to use VirtualBox on most systems based on Linux kernel 2.6 using either the VirtualBox installer [...]

The access to a shared folder is provided by the guest addition which is offering a VBoxSharedFS driver for the Windows guest system. So not the Linux host but the installed Windows 7 does not recognize completely the offered filesystem and it seems rather to me that there is an issue between Windows 7 and the Windows guest addition.

As I am no Windows expert I don't know how to check acl file attributes in Windows unless using icacls in the Powershell.

And the issue seems not to be a Linux dependent issue because de facto the \\vboxsrv drive is connected though Explorer and Computer Administration say it were not.