Shared folder error with long filename after snapshot restore

[vbdevtest]

• Snapshot created during running (WinXP) gast

• Snapshot restored (with vboxmanage startvm)

• Create an ordner on shared folders with more than 8 characters --> failes

• Access on files with more than 8 charcters in filenames failes

• Sometimes after a while (I don't know why and after which action), it is possible to access some longer filenames

• For Example:

• Start Windows Explorer an try to create an (default) ordner.

• It will be create "ordn" only, instead "Neuer Ordner".

• Hint:

• An other program tell, the shared folder support only 8 standard characters.

[vbdevtest]

Another sample:

• F: is a shared folder with full access

• call the winxp command line shell:

---

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\>dir f:

Falscher Parameter.

C:\>

---

"Falscher Parameter." What is a wrong parameter?

[vbdevtest]

Overview of Drive F: (connected Shared Folder), Display as RAW?

[vbdevtest]

If started the guest from a host account with admin rights, then it works fine. Instead "RAW" it displayed the filesystem as "VBoxSharedFolderFS".

But, if started the guest from a host account with limited rights, then there are problems, like described above.

Question: Which rights/settings on the WinXP Host systems are required, to solve this problems?

[FelixH]

I have a very similar issue, but for me it affects the administrator user as well. Same symptoms: when I have a mapped network drive corresponding to the shared folder, it shows filesystem type "RAW" in the properties dialogue, and filenames in it are limited to 8 characters.

I'm running VirtualBox open source edition, version 4.1.42_Debian.

I have found a workaround:

If I access the share using the path \ \ vboxsvr\sharefolder , everything works. It is only when I access the folder as a mounted network drive letter that the problem occurs.

[Socratis]

@FelixH

I don't think you have "a similar issue", I believe you have a completely different issue, I just can't find the appropriate bug report right now. I don't want to start diluting the original bug report, I could give you the explanation if you open a thread in the appropriate sub-forum of the forums (​https://forums.virtualbox.org/).