   setting up subversion as windows service
  I am trying to setup my subversion to load on start as a window service.  I create the service with the following command:sc create svn binPath= "svnserve --daemon --root c:\repositories" DisplayName= "SVN" depend= Tcpipand this creates the service fine when when I try to load it throughsc start svnit seems like it loads and if i open up another command line window and typesvn ls svn://localhost/my_projectand it does list out the repository but after about 30 seconds in the window where i did the sc start ... it gives the following error[SC] StartService FAILED 1053:The service did not respond to the start or control request in a timely fashion.the thing is that is did start and was running for at least a little since the svn ls command did run fine, why would it just fail after 30 or so seconds or successfully running?  is my command for creating the service wrong or missing something?  When I runsvnserve --daemon --root c:\repositoriesit runs fine and stays running until i close the command line window, i just want it to be able to automatically start.   
  Run it as svnserve --service instead of --daemon and it should work. A quick google search turned this up:http://svn.collab.net/repos/svn/trunk/notes/windows-service.txtToolmaker   ;  Look up VisualSVN server.  It is an installer that sets up subversion as a Windows service, plus has some graphical interfaces to set up most of the normal configuration.   ;  Since this seems related, I'll chime in here:Is there an inherent problem with setting up subversion repositories as service on a mapped network drive?I can set it up as service as long as the repositories are local. If they're on network drives it fails (yes, I am setting the network stack as dependency).Anyhow, VisualSVN looks interesting!   ;  Ditch all that crap and install visual svn, youll be up and running in less than 5 mins. We used it at my last contract and its very reliable.   