Folder tree doesn't display network paths

When I access \server\share\directory, the lister shows all of the files and directories under the share, however, the Folder Tree does not.

Help?

If there isn't a My Network Places (may be named differently if not on XP) item in the tree at all, check Preferences / Listers / Folder Tree and verify that it's set to start at the Desktop level. If you start the tree at a lower level then you won't have a network item.

It does start at the desktop level.

I went through the docs and options 2-3 times already. It's just not working.

Bug? I'm using the latest build on x64.

Something interesting to add. When I map a drive letter to the path, it shows up in the folder tree (naturally, as it's perceived as a physical drive).

However UNC paths do not work. \server\share\directory doesn't show up.

All I see under networking is "Network" under which are box names and public shares. The UNC path I am browsing does not show up.

Which version of Opus are you using?

2 posts up: "Bug? I'm using the latest build on x64." As in, 8.1.1.5.3222.x64 - hope this helps.

I think the problem is that Opus won't insert computer names into the tree when you navigate to them, if the computer name was not included in the list returned by Windows when Opus asks for the list of network computers.

Opus can't do much about Windows not always returning the full list of computers -- something I've never been able to work out either; on my LAN it seems fairly random whether the list of computers will include all of mine or not :frowning: -- but it should do what Explorer does and automatically create an item for the computer in the tree if you navigate to it and it wasn't already in the tree.

A request for this change has already been sent to GPSoftware.

I thought this change had already been done but upon further investigation I was thinking of something else. (Recently Opus was changed to insert the names of hidden shares into the tree if you navigate to them, but the computer name still has to have been included in the list of network computers that Windows returns.)

I remember this working fine in previous versions..

Does the Windows Explorer add a link to the Network Places if you browse the path in Windows Explorer?

If not, you could try to reactivate it, for example with XP Antispy (Network->Avoid...):
xp-antispy.org/index.php/lang-en

[quote="leo"]I think the problem is that Opus won't insert computer names into the tree when you navigate to them, if the computer name was not included in the list returned by Windows when Opus asks for the list of network computers.

Opus can't do much about Windows not always returning the full list of computers -- something I've never been able to work out either; on my LAN it seems fairly random whether the list of computers will include all of mine or not :frowning: -- but it should do what Explorer does and automatically [/quote]

I can also confirm I have this problem of Folder Tree not updating for UNC file paths. I'm currently using version 9.1.1.8 but the problem was there in 9.1.1.7 and earlier.

To clarify further, I have 2 computers with Directory Opus installed: a Vista x64 and a Windows 2003 x32.

With a fresh Directory Opus install on Vista x64, the Folder Tree does not refresh when I type in UNC path such as \media1\mp3s\

However, on Windows Server 2003 32-bit, the Folder Tree updates for all UNC paths.

As a workaround, I noticed that Directory Opus often complained with the error message: "Network discovery is turned off. Network computers and devices are not visible. Please turn on network discovery in Network and Sharing Center."

So, I turned on "network discovery", exited completely out of Directory Opus and restarted it. The Folder Tree seems to work in Vista now.

However, I'm not sure why Directory Opus needs "Network Discovery" turned on but the built-in Windows Explorer does not. Windows Explorer correctly updates Folder Tree even if "Network Discovery" is explicitly turned off. What's special about the built-in Windows Explorer? Does Windows Explorer use different API function calls to retrieve folder names that Directory Opus does not?

Explorer doesn't enumerate the network unless you fully expand the Network part of its tree. If you just go to a network folder directly (e.g. by typing its path in) then Explorer adds a branch for it into the tree. It correctly assumes that if it can go to that computer then it exists and updates the tree accordingly.

On the other hand, the tree in Opus currently depends on being able to enumerate the network and then find the server within the list of results.

Making Opus do what Explorer does in this situation is on the feature request list.

Currently evaluating the trial version, and really like it.

But i spend the majority of the day on network shares, so this is probably gonna be a stoper for me until some version gets this in.

That aside, really really nice customizable little program you got there :slight_smile:

I do hope dopus will get around to having nework paths automatically dispalyed in the explorer tree.

However if it's too complicated for now, maybe there is an intermediate solution which in itself would be a pretty neat feature to dopus:

Instead of just displaying breadcrumbs in the listers file path, add an option to display the breadcrums in vista pathbar style. Like this even if the explorer tree does not update correctly, it is still possible to more or less easily navigate around the directory structure.

..possible ? :slight_smile:

Robert


If you enable Hot Paths in the File Display Border (not sure if it's on by default or not) then you can click on the path components, a bit like a breadcrumb bar but without the arrows that let you go to sibling folders.

At the moment the only place you can have a proper breadcrumbs bar is on the toolbar.

Yes thank you, the hot paths work perfectly fine and are very useful.

However at work i move through hundreds of folders every week, all of which are on various network paths, so i was trying to figure something out that would make life easier for these tasks.

Dopus is really great from a ergonomical & personalisable point of view, so kudos to that ! :slight_smile:

If you ever want to build upon some enterprise friendly feature here's some i see right away from what various admins at work always do:

Network path thingy (as everything is on network shares): ..already mentioned above :slight_smile:
ftp/sftp: already in dopus !!
Windows sys admins: always need to remote desktop to various machines, most use royalTS, however i can see tabbed remote desktop windows inside tabs, this would really rock!
Linux admins: always need to ssh to remote servers, could see the same scenario with ssh windows imbricked in tabs.

That and what dopus already does would really be the ultimate enterprise explorer replacement.

What really caught my eye on dopus vs other stuff like total commander & others is the multiple listers + multiple tabs (i used to use QTTabBar before this)

btw i'm on windows 7: 7057 64bit, both at home & at work & everything works just fine :slight_smile:

Thanks,
Robert

Just been rereading the posts a little..

From what i gather, if network sharing & discovery is ON, then the folder tree should be updating ?

Seems to be maybe x64 related issue the ? (on x64 here too)

The only way i can currently get the paths to show up fine is by manually mapping the network shares to drive letters & then accessing the shares via the mapped drives.

btw, turning on network discovery & file sharing or turning it off changes absolutely nothing ..except when off i get nagging popups asking me to turn it on, which is kinda useless if i have to map the drives manually anyways (a way to turn the popup message off?).

Thank's for any supplementary insight. Either way i will most likely be getting a copy with ftp/usb support soon :slight_smile:




I don't think machines that only show up as an IP Address are going to appear in the list of computers returned by network discovery. That probably explains what is different for you.

i.e. If I'm right, Explorer won't show the 10.0.0.231 node below Network until you navigate to it (by typing the path in or using a shortcut), which causes Explorer to insert the node into the tree even though it wasn't found. That's precisely what Explorer does which Opus doesn't currently do, and what this thread is about.

(The other thing Explorer does is not force the Network branch to expand fully when you go to something below it. So if you're on a network with 5,000 machines you don't get a tree that is cluttered full of machines you never want to go to; it only "partially" expands to show the computer you are on. It also means that you don't have to wait for those 5,000 machines to be enumerated before the network part of the tree works for the machine you are on.)

Excactly, explorer will only expand the tree when i navigate to a specific share, which is perfect, since it would be horrific it it started listing hundreds of machines on the network :blush:

Oh well, i guess i can live with having to map the shares to drive letters for it to work in dopus for now ..at least it does work and makes life much much easier, even if it's not the fanciest solution.

Thank's again,
Robert