Bug 6119 - SC doesn't autostart after install
: SC doesn't autostart after install
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Installer
: 7.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-10 06:59 UTC by Doug Williams
Modified: 2007-11-12 04:48 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 Doug Williams 2007-11-10 06:59:57 UTC
11/10 version
Uninstalled prior 7.0 version.
Deleted SC folders
Did NOT manually search/clean registry

Installed 11/10 build.
Left the View Readme checked.
Looked at the readme.
The SqueezeTray started and indicated that SC was stopped.
Checked Windows Task Manager - no SC tasks running

Ran ServiceEnabler.exe and set option to run as a service.
SC started and popped up the wizard page.

Michael indicated that this is a bug so I thought that I would write it up.  It does, however, make it easier to run the serviceenabler.exe...
Comment 1 Michael Herger 2007-11-10 07:27:12 UTC
Before you ran the ServiceEnabler(c) - what was the setting in the SqueezeTray menu?
Comment 2 Doug Williams 2007-11-11 07:02:23 UTC
OK
Uninstalled 11/10 version using program.
Manually deleted both diretories (program files and Doc/Settings)
Searched/deleted all registry entries found (using "logitech", "squeeze", "slim" as search keywords)
   NOTE: Logitech Harmony Remote entries not deleted, LEGACY_* entries not deleted (unable to for some reason)

Downloaded and installed 11/11 build.

After the installation finished the readme came up but SC was not started by the install.  The SqueezeTray indicated that it was stopped and I had the options to Start SqueezeCenter (Bold) and Automatically run at login.  No ticks by either option.

This is as clean an install as I know how to do without formatting the box and reinstalling the OS from disk (something I'm not going to be able to do).

You have stated that it should startup by itself right after the install is complete - it is not doing so.  I can manually start it or run the serviceenabler.exe program just fine but it doesn't startup without some manual action on the user's part after the install.  Personally, I kind of like it this way since I'm always going to want to run the serviceenabler.exe program after install anyway, but this is your call.
Comment 3 Michael Herger 2007-11-12 04:48:39 UTC
change 14631 - the startup behavior was indeed not correctly initialized when there was no setting in the registry. Thanks!