Permaent Shared Folders Problem in Solaris / Illumnos

Discussions related to using VirtualBox on Solaris hosts.
Post Reply
MikeWidmann
Posts: 5
Joined: 20. Jul 2011, 21:21
Primary OS: Solaris
VBox Version: OSE other
Guest OSses: Win7 32 / 64

Permaent Shared Folders Problem in Solaris / Illumnos

Post by MikeWidmann »

Hi

Mit 4.1.0 gibts ein massives Problem mit den Shared Foldern.
Ich legen den Folder an - kann ganz normal drauf zugreifen und durchblättern - aber sobald ich eine Datei weg kopieren / öffnen / bearbeiten will kommt folgendes:
im Windows:

Fehler: 0x80070057 Falscher Parameter ...

ähnliches passiert beim öffnen / schreiben etc....

Hat irgendjemand eine Idee dazu?

lg

Michael
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Permaent Shared Folders Problem in Solaris / Illumnos

Post by Perryg »

English please.
Are you using auto-mount?
MikeWidmann
Posts: 5
Joined: 20. Jul 2011, 21:21
Primary OS: Solaris
VBox Version: OSE other
Guest OSses: Win7 32 / 64

Re: Permaent Shared Folders Problem in Solaris / Illumnos

Post by MikeWidmann »

Hi

With 4.1.0 there's a problem with shared folders...

it operates flawless with all new folders and files - but with older files / folders i do have the problem that they are visible and could be navigated - but files couldn't be opened moved or something else.
windows error message:

0x80070057 Wrong Parameter / or sometimes :E\data\test\test.txt wrong parameter (see the : on the start)


And automount - means yes - if starting - the folder is permanent available


greetings

Michael
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Permaent Shared Folders Problem in Solaris / Illumnos

Post by Perryg »

Have you tried to un-mount the folders and remap them? un-mount in the guest and reboot before trying to mount again. If this is auto-mount you will then need to reboot after you mount them. Or you can NOT use auto-mount and select to use permanent and mount the share manually.
See Chapter 4.3.1 Manual mounting in your VirtualBox users manual.
MikeWidmann
Posts: 5
Joined: 20. Jul 2011, 21:21
Primary OS: Solaris
VBox Version: OSE other
Guest OSses: Win7 32 / 64

Re: Permaent Shared Folders Problem in Solaris / Illumnos

Post by MikeWidmann »

hi

Tried all the steps - unmounted / removed - rebootet - no change... couldn't access anymore old files....

Any Ideas?

Perryg wrote:Have you tried to un-mount the folders and remap them? un-mount in the guest and reboot before trying to mount again. If this is auto-mount you will then need to reboot after you mount them. Or you can NOT use auto-mount and select to use permanent and mount the share manually.
See Chapter 4.3.1 Manual mounting in your VirtualBox users manual.
MikeWidmann
Posts: 5
Joined: 20. Jul 2011, 21:21
Primary OS: Solaris
VBox Version: OSE other
Guest OSses: Win7 32 / 64

Re: Permaent Shared Folders Problem in Solaris / Illumnos

Post by MikeWidmann »

Reinstalled Virtualbox 4.0.12 - all works problemfree..

So it's a definit problem from VBox 4.1.0 ...
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Permaent Shared Folders Problem in Solaris / Illumnos

Post by Perryg »

These kinds of problems that are reproducible should be reported to bugtracker. You will need to setup an account there as it is on a different system.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.
pshrutpark
Posts: 24
Joined: 9. May 2010, 06:37
Primary OS: Mac OS X Leopard
VBox Version: PUEL
Guest OSses: Windows

Re: Permaent Shared Folders Problem in Solaris / Illumnos

Post by pshrutpark »

MikeWidmann wrote:Reinstalled Virtualbox 4.0.12 - all works problemfree..

So it's a definit problem from VBox 4.1.0 ...
I experienced the same problem and error code with Win 7 64 bit on OS X host (the Win 2000 client worked fine).

Reverted to 4.0.12 and all is well.

Definitely seems a 4.1 problem.
Post Reply