There have been a couple of things in this thread - I'll try to add some input as I got to understand some of the working when tracking down a SlimTray problem.
The issue with the browser not opening up when Slimserver is started with SLimTray - that is a bug in SlimTray and a red herring to the other issues. I have built a modified SlimTray - details can be found in this post. http://forums.slimdevices.com/showpost.php?p=184445&postcount=93 One of the other issues with SlimTray was the fact it didn't shut the MySQLD service down when Slimserver was stopped. This might confuse some user into thinking MySQLD has started before Slimserver. Another issue is that Slimserver can be run * as a services under the "system" user if set to start on startup * under the user id if set to start on login * as a background process if service has been disabled (e.g. on installation unchecked the "start automatically" box. So when describing problems with startup, you should detail how your system is configured to start SlimServer. As part of the slimserver initialisation - slimserver will create the MySQLD service if it doesn't exist and then requests the startup of the MySQLD service - so there should be need to make dependencies. When there are problems with MySQLD - has the event log been checked to see if there are any entries from Slimserver or MySQLD. You can install the ProcessExplorer tool from www.sysinternals.com and it will display ownership of Slimserver & MySqld services clearer than task manager. -- bpa ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=31162 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
