wine users - Oct 2009 - Do UNC paths actually work or not?

I'm assuming most people are familiar with this:
http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure#AEN415

which indicates that symbolically linking a Linux-accessible path, such as a
remote server mountpoint, to ~/.wine/dosdevices/unc/SERVER/path will cause
Windows applications running under Wine to see files enclosed under the standard
UNC path \\SERVER\path\to\file.ext

The open question is: does this really work?

On the one hand, you have bug threads such as these:

http://bugs.winehq.org/show_bug.cgi?id=425
http://bugs.winehq.org/show_bug.cgi?id=14501

which seem to indicate that support is incomplete, and that some (unspecified)
things don't work.

On the other hand, you have threads posted in this forum which indicate that UNC
paths work perfectly.

I have an application, Autodesk Combustion 2008, which will write output files
encoded in UNC format while running in Wine, but will not open any file
specified manually by typing in a UNC pathname, nor will it browse files in any
directory prefixed with \\SERVER\dir pathnames.

Is this a question of "It does work, just not really..."? 

Also, since Wine File doesn't appear to be able to browse UNC paths, is
there any other basic, universal method of testing that UNC paths work from
within a Windows application running on Wine?

Thanks in advance

scottburton wrote:
> Iwhich indicates that symbolically linking a Linux-accessible path, such as
a remote server mountpoint, to ~/.wine/dosdevices/unc/SERVER/path will cause
Windows applications running under Wine to see files enclosed under the standard
UNC path \\SERVER\path\to\file.ext
> 
> The open question is: does this really work?
Yes and no. Browsing of network shares is not implemented in Wine that's why
you can't browse UNC paths. But if application tries to directly open / save
a file using a UNC path it should work.