Page 1 of 1

Office 2007 saves files in my linux host as read-only

Posted: 6. Jul 2009, 23:28
by carosas
Hi everybody!

I have a problem with my virtualbox (MS server 2003 R2) since I upgraded it to 3.0.0 because when I'm working with office and I save the file into my linux file system (Ubuntu 8.10) it saves the file in read-only mode and when I try to save it again I can't because it is in read only. This only happens with MS Office. I already tried to delete the shared folder and create it again and nothing happens, I still having the same problem, can anybody help me to find out if the problem is with the virtualbox or office suite? This didn't happen with the previous version of wirtualbox (2.2.4).

Thanks in advance!

Regards!

César Rosas.

Re: Office 2007 saves files in my linux host as read-only

Posted: 7. Jul 2009, 03:46
by Perryg
I have been studying this for a few days and think it has to do with the way that Office saves the files as well as permissions between Windows and Linux.
Points of interest are:
  • 1. I do not have this problem.
    2. I use the same login on the Windows VM as I do in the Host.
    3. I see that the permissions are read only but I am still allowed to edit, save, and even delete.
    4. Office and Visual C++ are just about the only thing that I have read about that does this.
    5. I can use notepad and so far others can and this problem does not affect them as far as I can tell from reading posts.
Are you interested in testing this theory? You can try to add the Windows login name to your Linux and be sure to add them to the VBox users group to see if this will solve the problem.
Of course this would just be a work-a-round but you could keep working while the Dev's figure this out.

Re: Office 2007 saves files in my linux host as read-only

Posted: 7. Jul 2009, 16:37
by klirik
It doesn't work, unfortunately.

I also have the same problem: since upgrading from 2.2 the regression with ro attribute came.
It is possible to save a file from notepad or wordpad, but possible only once from VisualStudio, since it became ro (permission 400 on host).
And there was NO such problem at all on 2.2.

I have the same login name on host and on guest. So, it is the case you describe as a workaround.
However, it doesn't work.

Apart from VisualStudio, it is also impossible to work with Mercurial repository on a shared folder, using TortoiseHG. Trying to commit, you will get "'module' object has no attribute 'is_exec'" error. However, if you copy the whole folder with repository onto the disk inside VM, there is no problem with Mercurial.