It isn’t a DOpus setting — you’d have to type it into the “Location” bar (also known as “Pathbar” under Toolbars).
[I use DOpus in Dual Horizontal + Details mode — I’m not sure how much of this would apply to you.]
If you have a Windows / Samba share that you normally access by (for example) typing “H:” in the Location bar, you should also be able to get to that same location by typing (for example) “\samba\h$” instead.
(The “\samba\h$” varies depending on your setup — “samba” is the name of the Windows / Samba file server, “h$” is the name of the drive share.)
Have you reported it to the people who make the NAS? Opus requests notifications the same way for UNC and drive letter paths so if the NAS behaves differently for each then it's probably a problem with the NAS.
I think it’s a ZFS thing. I’m at a new job now where we have a Sun ZFS Storage 7120 appliance, and Directory Opus has the same problem. I’m willing to bet you’ll see the same thing 100% of the time that DOpus connects to a ZFS SMB share, regardless of the NAS vendor / manufacturer. It’s not a particularly big deal (now that I’ve gotten used to hitting F5 all the time) but it’d be nice to get it cleared up.
Hmmmm I stand corrected. Does your NAS run a Solaris / OpenSolaris version of zfs? I haven’t really been keeping up on zfs development but from what I recall FreeBSD was on the verge of integrating zfs into the core OS and other flavors of Linux were looking into that as well. So I’ll hedge my bet a bit and surmise this is a Solaris–related zfs issue. (That said, this should soon not be an issue at all for me as we’re moving to EMC Isilon storage which uses a propietary OS called OneFS. It’s based on FreeBSD though.)
ZFS is chiefly a filesystem... the network stack and CIFS client/server interfaces that could affect this sort of issue don't have to be "ZFS" specific, and can differ from platform to platform upon which ZFS has been implemented by your device manufacturer. No?
Whatever the reason, the common thread seems to be Solaris / OpenSolaris zfs. I don’t know enough about the internals of Solaris or Directory Opus to have a clue why that would be. Granted, this is a very small sample, but I’ve seen it on two different installs — Nexenta (OpenSolaris) and Sun Storage (real Solaris). gauntlet is seeing it on an OpenIndiana server which is essentially OpenSolaris.
I agree with dsb it seems to be a Solaris/OpenSolaris ZFS and/or CIFS. I can also vouch for dsb on Nexenta and Solaris - tried both at work this last week, same issue. I still find it weird that Windows handles receiving updates to both UNC and mapped drive letters just fine.