Read/Write Files on Windows XP

[BillA1016]

Hi,

I am trying to run a program on Windows XP on a Mac OS X host and need a folder to be read and write. When I uncheck the little green "Read Only" box, everything seems to work, but it resets itself to Read Only again. This is causing major problems with the program I'm running and will not allow for the "Autosave" feature to function (and you cannot manually save in this program). Any help in making this file Read & Write permanently would be a great help.

Thank you.

[ChipMcK]

Are you asking about Shard Folders, by chance?

If so, when you define the folder as shared, you may specify Read-Only access and if to be auto-mounted (VB r4.116).

[BillA1016]

Thanks for your reply! This is not a shared folder. I installed a piece of software and need to make its program folder read/write. Any ideas?

[ChipMcK]

Beyond my knowledge of Windows.
Perhaps a Microsoft forum?

[BillA1016]

From what I understand, it's not a Windows problem. I talked to a friend who is into computers, and he said that a native Windows machine wouldn't do this and it has to do with VirtualBox, which is why I'm posting here.

Thanks again for your help!

[Perryg]

Sorry but if you are strictly talking about an app on the guest that can not set the folder (on the guest) to read write, it is the guests issue.

[mpack]

The only time I've seen symptoms kinda similar to what the OP describes is when the folder concerned is on a read-only media, or is inherently read-only for other reasons, e.g. it's a metafolder showing you a view of some kind of data, or e.g. because the folder belongs to another user who has granted you read permission (but not write). AFAIK Windows has no way to represent folder permissions, so it'll present them as permission ticks in the properties dialog of each file in the folder. While you can display the dialog and untick the checkbox, the underlying permission can't really be modified and it will reappear when you show the dialog again.

As others have said, this doesn't sound like a VirtualBox issue. It sounds like someone doesn't understand Windows.

[BillA1016]

I looked into it more and it turns out that this is a Windows issue. There is apparently a similar issue dealing with shared folders on Windows systems in VBox and I got confused.