XYplorer Beta Club

Hi,

Vmware Workstation has a great feature called shared folders.
Basically, it creates a virtual network server on the host computer that gives access through a share (\\vmware-host\Shared Folders) to any declared folder on the host.
On the guest side, Windows(7) (Explorer) shows \\vmware-host\Shared Folders as just one more share and it's possible to browse it directly or though a mapped drive letter. XY shows the server (\\vmware-host) in the tree, but is unabled to browse it : Now if I map \\vmware-host\Shared Folders\Dir to a drive letter, XY works perfectly with it.
But... as soon as a tab points to a location on this drive letter, Menu|View|Suspend Auto-Refresh gets automatically ticked and... no more auto-refresh. This doesn't happen when the drive letter points to a "normal" server share.

Is there something I missed?

I should have labelled this thread "location currently not available".

After spending some time on this support forum, I came up with a way to look into this : Exist
Here are 2 screen captures: There's obviously a difference.

When using Windows Explorer there is absolutely no difference between the 2 servers.
Xyplorer displays the " location currently not available" screen.

Is there a way to make this work ?

Look at your second screenshot, the path is \\vmwar-host but your first post is asking about \\vmware-host

You're right , I'm sorry I mispelled for the screen shot...
The screen shot in the first post was ok though.
I'll try again...

Until the dev gets a chance to review this, a suggestion if you're interested is that you could try enabling this:

Configuration | General | Safety Belts, Network | Network | Assume that servers are available

restart XY afterwards.

Thank you for you suggestion.
Unfortunately it didn't change anything : location still not available.

Hi all
I wonder if anyone got a new idea about this "location currently not available" issue.
Having to press F5 after every file copy or move is very annoying.

@Don, screenshot in english: The interesting thing is:
By default XY doesn't expand the \\vmware-host, it doesn't see any shares in it
But when you enter that full path to the share in the address bar, it becomes visible and all shares underneath it as well (although you can't access them (location not available)...

\\vmware-host\Shared Folders

Error 53 (BadNetPath) is returned. A possible solution would be to ignore the error and see what happens. But under which conditions? Does this only affect VmWare? If yes, do they always start with "\\vmware-..."?

Haven't tried any other Hypervisors to test that but out of the box and iirc: VMware is probably the only one that has this internal sharing

\\vmware-host\ is by default the hostname for this sharing mechanism

Let's give this a try (ignore the error)? I can test it on monday again...

Hi thank you both for taking the time to investigate this... inconvenience.

I have no means here to test this and I'm not totally sure which is the best point in the code to tweak this. I'll start with one point in the next beta, and then will see...

It got a little worse with 0201

\\vmware-host\Shared Folders
Doesn't even list all the shares in it any more (in the tree) as in previous versions...

Okay, I'll try again.

Sorry! It was late yesterday...

The shares are visible in the tree once I enter \\vmware-host\Shared Folders
Even with 201

I can access shares in that version^^

\\vmware-host\Shared Folders\storage [games]
Works fine!

What doesn't work is: Getting to the list of shares by using the tree. I can't expand \\vmware-host, there are no entries visible in it as long as I didn't go to (at least) \\vmware-host\Shared Folders via the address bar.
202 doesn't change that.

Sorry again!