Hi,

Thanks for the reply.

I'm running coLinux 0.7.1-hn16 on Windows XP. Here is the output from colinux-daemon.exe --status-driver:

C:\coPlanet\coPlanet>colinux-daemon.exe --status-driver
Cooperative Linux Daemon, 0.7.1-hn16
Compiled on Sun Jul  9 16:35:25 2006

checking if the driver is installed
current state: 4 (fully initialized)
current number of monitors: 0
current linux api version: 10
current periphery api version: 20

so it looks like the CoLinuxDriver driver is installed properly.

To install a coLinux service I run the following:

colinux-daemon.exe "@C:\coPlanet\coPlanet\pl.conf" ro root=/dev/sda1 --install-service "coPlanet"

I tried running with the debugger but I only got the same information that is dumped to stdout when I try and start the service from the console with:

colinux-daemon.exe --run-service "coPlanet"

Cheers,
Mark.

On 11/16/06, Henry Nestler <Henry.Ne@arcor.de> wrote:
Mark Zaloumis wrote:
> Hello,
>
> I'm wondering what the coLinux installer does in the install process
> that lets coLinux daemons be run as services. If I copy the files from a
> coLinux install on one computer onto a computer that coLinux has never
> been installed on, coLinux will run fine but if I try and run it as a
> service I get the error:
>
> The service process could not connect to the service controller
>
> However, if I then go install coLinux somewhere else on the computer I
> copied the coLinux install onto I can then start the copied version as a
> service. This leads me to think that the coLinux installer is setting up
> something to do with the service controller? I was wondering if anyone
> could shed some light on this.

The installer does a "colinux-daemon.exe --install-driver" and setthe
path for the uninstaller, but does nothing with the system services.

What version of coLinux you are running?
What Windows (XP or W2K)?

Is the coLinux right installed and unused?
Check this, if service is not running:
   colinux-daemon.exe --status-driver

Try to start the debugger:
   colinux-debug-daemon.exe -d -p -s prints=31,misc=31 > file.log
Than run the service from a second prompt, stop debugger with CTRL-C
after the error passed.  Than grep into the output, search the error
line and read detailed error messages some lines before.

What steps do you runs to "install the service"?
Please list your inputs on windows command line.

--
Henry Nestler