Corruption preventing access to drivecrypt container mounted as drive

[dfatvb]

Host is Win7x64, booting Win7x32 (installed as drive X:) in the virtualbox, latest version of virtualbox and extensions as of this writing. Using shared folders to share local drives C:, D:, E:, F: where F: is a drive crypt 5.5.0 mounted container on a network mapped drive on the local host system. They are mapped to drive letters C:, D:, E:, and F: in the Win7x32 so all scripts needing to run 16 bit code still work under the virtual machine. Problem is after a short while, the drive crypt drive starts having problems with files not found, corruption, locked, etc.. I have to reboot the main machine once that occurs because it happens on that drive no matter what (host or guest). Thank goodness damage doesn't get saved to the drive crypt container. But, it's making it a pain to work with; XP mode is worse in that its shared folders doesn't work with the drive correctly from the start. However, I have a virtualbox machine with debian lenny and access that drivecrypt mounted drive via a shared folder with no problem (can work on it all day). So perhaps it has something to do with either Win7x32 in the virtualbox or the virtualbox Windows extensions for shared folders???

[vasily Levchenko]

Could you please attach the log file?

[dfatvb]

I don't believe there is a log file (the vm doesn't crash itself), or does a .log exist anyway?

[vasily Levchenko]

Replying to dfatvb:

I don't believe there is a log file (the vm doesn't crash itself), or does a .log exist anyway?

Please look at ​http://www.virtualbox.org/manual/ch12.html#idp9282608 for more details.

[dfatvb]

log file - started win7 x32 - went to drivecrypt drive - already problems on the host machine accessing it, shut down, this is the log

[dfatvb]

ok, log attached.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.