Bug 6474 - SC7 won't browse a music folder with a UNC path
: SC7 won't browse a music folder with a UNC path
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Service
: 7.0
: PC Windows Server 2003
: P2 normal (vote)
: ---
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-27 06:17 UTC by Craig Stevenson
Modified: 2008-12-18 11:12 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Stevenson 2007-12-27 06:17:00 UTC
Somewhere between SqueezeCenter 7.0 Build 13599 and 7.0 Build 15528 (Windows Server 2003 - EN - cp1252), the ability to browse the Music Folder appears to have been broken. I just did a scratch installation of Build 15528, and re-scanned my music. (SqueezeCenter shows 460 albums with 6680 songs by 441 artists, as it should, but nothing appears in the left pane when browsing the Music Folder.)

Further investigation revealed that this problem is caused when I enter a UNC path for my music folder.  (For example, in my case it is \\Guardian-20\Flac).  If I map a drive to that same folder, it works properly.

This behavior can even be seen when setting up SC initially. If you enter a UNC path into the Music Folder field, and hit the Browse button, you will see the folder, but you can't browse it. (A mapped drive to the same location is also there AND it is browsable.)

Here is a forum thread related to this topic:  http://forums.slimdevices.com/showthread.php?t=41372
Comment 1 Michael Herger 2007-12-28 07:44:40 UTC
change 15673 - only apply DriveInfo::IsReady() to drives, not to UNC paths

Feel free to re-open if this didn't fix this bug for you. Thanks!
Comment 2 Chris Owens 2008-03-07 09:04:30 UTC
This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.