Vista - Shared folders - guest mixes up folder hierarchy after save /restore

Hello *,

I have a recurring issue with the shared folders in MS VPC, occurring on
various hosts (Windows 2000 SP4, XP SP2/3) with VPC 2004 and 2007 and
various guests (Windows NT 4.0 SP6a, Windows 2000 SP4, Windows XP SP3).
When I access shared folders on the host exceeding a certain depth from
the guest, the wrong folder content is displayed (seems to be the
content from the previous or next folder in the parent directory, but I
didn't check thoroughly). The problem occurs only after restarting a
saved guest, but not consistently.

What I do right now to fix this issue is (1) remove shared folder in
client, (2) close guest(s), close VPC console, (3) restart VPC console,
(4) restart guest(s), (5) add shared folder in guest. This is a bit
awkward, especially if more than one client is running.

Does anybody know a simpler workaround for this problem?

Regards,
Andreas

--
"Thou know'st we work by wit, and not by witchcraft;"

On Sat, 10 Oct 2009 12:58:58 +0200, Andreas Ziegler
<news09@newsgroup> wrote:
As has been frequently discussed here, shared folders as handled by
the virtual machine additions in VPC2007 is *very* lacking and really
only useful for transfering small number of files between host and
guest.
If you want solid performance you should *never* use this feature,
instead you should do as you normally do to access files between two
PC:s on a network:

Set up file/folder sharing over the network instead!
This is rock solid for any number of files or folder tree depth.

--
Bo Berglund

Bo Berglund wrote:Hi Bo,

Yes, you are right, the reliability of a network share is greater than
the shared folders, but since I use my virtual machines on a lot of host
machines and mostly in NAT mode, a virtual network is not easy to set
up. Also the shared folders have become a lot more stable since the
first time I used them. I just hoped someone might have the ideal
workaround ...

By the way, sharing a directory tree at a greater depth eases the
problem; the fault is entirely dependent on the hierarchy depth seen by
the client.

Thank you anyway,
Andreas

--
"Thou know'st we work by wit, and not by witchcraft;"