Some shared folders cannot be accessed after some time

[dabiel.kabuto]

I use VirtualBox 2.2.2 and I have 3 shared folders.

After some minutes or hours, I cannot open a shared folders in the guest OS (Windows XP). Other shared folders work fine. The message is "you do not have access to \\VBOXSVR\UnitF".
Usually it happens when I am using Builder C++ 6.0 in the guest in debug mode but I do not know why.

The only thing that I can do is to restart the guest and then everything works fine again for some time more.

Do you have a clue about the reason?

Thanks

[vbox4me2]

Does it happen after about 20min? can you use the VM control buttons to re-share them? what if you leave an explorer open inside the share? try debugging a small hello world thing set brakepoints on every call, to see at what specific point it happens.

[dabiel.kabuto]

I do not know exactly the time, sometimes 20 minutes, sometimes more.
Yes, I can use the VM control buttons, but I am not clear what you mean with "re-share". I can go to Devices / Shared Folders and all folders are there.
If the explorer is opened, I can see the shared folder, but when I double click, it shows me an error like "you do not have access..."
Other shared folders work fine, I do not know the reason.
Then, I need to shutdown the guest system to have access to the unit again.
It seems that it happens that the software that I am debugging is opening a text file placed in the shared folder. The shared folder has been mapped via NET USE ....

Thank you

[vbox4me2]

The behaviour of vbox shared folders is different then a normal share, you might have to play with the attributes of the fileopen function or maybe zero out access rights bit mask.

[dabiel.kabuto]

The thing is that it works fine at beginning and for some time before the unit is not accessible. Also, some procedure in the guest provokes that the entire system, including Windows Explorer, does not have access to the shared folder. It only happens (until now) when I am debugging my application with Builder C++, never executing the software. It seems that there are something in VBOX that does not support the debug mode.

In any case thank you for your time.

[vbox4me2]

It seems more likely there are some calls made from debug mode that interacts with the GA api, you'd have to investigate the ose source to find out how.