PDA

View Full Version : slimsvc not able to follow win32 shortcuts



Steve Baumgarten
2004-03-17, 18:56
My music directory has a single Win32 shortcut in it pointing to a real
directory containing lots of albums (each in its own subdirectory). Never
had a problem with this setup until this evening when I decided to run the
Slimserver (the 5.1.1 release) as a Windows service.

All my files are on my C: drive -- no Windows shares involved here (I know
that can be a problem when running as a service). But are there also
issues following simply Win32 shortcuts when running as a service?

Running as slim.exe things are just fine; running via "net start slimsvc"
and I get 0 albums. Whichever way I'm running I can see the music
directory path is the same (via the web page and the prefs file).

Oh, and also: if I do "Browse Music Folder" while running as a service I
get an error when clicking on the shortcut; if I do this while running as
slim.exe it works just as expected.

So it definitely seems to be something related to running as a service vs.
running as an application.

Has anyone else seen this?

SBB

Steve Baumgarten
2004-03-17, 20:01
> So it definitely seems to be something related to running as a service
> vs. running as an application.

One more datapoint: if I run slim.exe as a service via FireDaemon and set
it up so it runs under my login (vs. running as SYSTEM), then there's no
problem, the server is able to follow the shortcut just as if I had
started it from the command line.

So it's a user account vs. SYSTEM thing. Why should this be, though, for
a simple shortcut?

(I do have file sharing turned on, generally, on my laptop, but none of
the music directories involved are being shared -- for what that's worth.)

SBB

Roy M. Silvernail
2004-03-17, 22:02
On Wed, 2004-03-17 at 22:01, Steve Baumgarten wrote:

> So it's a user account vs. SYSTEM thing. Why should this be, though, for
> a simple shortcut?

Shortcuts are essentially remote mounts, same as network drives are.
The LOCAL SYSTEM account can't access non-local resources.

It's not so surprising, really. Way back in Win95 release 1, *all*
drives were treated as remote mounts. There weren't user accounts to
deal with, but try moving a file to a subdirectory with a rename.
--
Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
Never Forget: It's Only 1's and 0's!
SpamAssassin->procmail->/dev/null->bliss
http://www.rant-central.com

T
2004-03-18, 00:43
> > So it definitely seems to be something related to running as a service
> > vs. running as an application.

> So it's a user account vs. SYSTEM thing. Why should this be, though, for
> a simple shortcut?

It's a Windows thing. SlimServer must run in a user account, otherwise it
won't see the shared folders. Just create an account for SlimServer
(called, for example, SlimServer) and set the service to startup using that
account.

Tom

Steve Baumgarten
2004-03-18, 07:14
> Shortcuts are essentially remote mounts, same as network drives are.
> The LOCAL SYSTEM account can't access non-local resources.

Ugh. I'm a Unix guy with just a little Windows NT/2000/XP knowledge, so
thanks for the explanation.

Here's something interesting:

http://www.mydesktophelp.com/tips/win119.htm

I don't know whether that registry tweak applies to XP Home or not; but
given that I can use FireDaemon as a workaround it doesn't really matter
to me. (I actually prefer the FireDaemon approach since I can also
specify command-line options that way.)

SBB