Hi - I am reasonably clued up on PC’s, but not too much on the network stuff. I have a piece of software (from NCH Swift Sound) that runs on users PCs and records telephone calls through the sound card. The recordings are saved as .wav files on a remote (networked) PC. This works fine running it as a normal application However, there is box that can be checked so it “runs as a service” which should have the advantage that the recording software still runs even when no one is logged on to the PC. The problem is that if I “run it as a service” it will not save anything to the remote PC (cannot access the remote folder) regardless of whether anyone is logged on or not. I have done quite a bit of experimenting with various bits of software and as far as I can see nothing starting automatically and running as a service seems to be able to ‘see’ shared folders on a remote (networked PC) I wondered if someone out there has any experience of running applications as a service, and can possibly point me in a direction to investigate further – I have a feeling that I am overlooking something blindingly obvious here – just can’t see it Here’s hoping

firedaemon is about the best off-the-shelf solution I've seen for running applications as services. If your app already has the ability to run itself as a service, firedaemon might not solve your particular problem though. Do you know why your app won't save to the remote folder? I'm wondering if it needs a user session to establish a connection to the remote pc. Are you using a mapped drive, or a UNC path for this?

I am using a UNC path. "needs a user session to establish a connection" would certainly fit with all the playing around I have done, because if you restart the app not as a service it will work ok and then stay working even if you re-start it again as a service. It is only when you re-start the PC with it running as a service that it can't see the remote PC. This suggests that it can't actually make a connection until it is run under the control of a user. Not sure how to get round that. I will try mapping a drive & post back tomorow Thanks

I think you have the right idea. It does seem like the UNC connection is what's failing. Maybe you can create a batch that will map a drive (or at least authenticate to the remote computer...IPC maybe?) and then start the app? Although mapping a drive should work too. Good luck, and please do post back. I'd be interested to know how you finally solve the problem.