Holger Krull schrieb:
I am not the one who asked, but having the same problem
> Which version of colinux do you use?
> If you can't connect with nt-terminal,
I can't connect. No error message at all. Using
"colinux-console-fltk.exe" there is a windows drawn, but it is
deleted right after without any readable message. The same for
> can you connect with ssh?
Yes, but since I do not know when Linux was ready booting, this is
sometimes a bit difficult.
> Is there an error message if you try to connect?
No, or better if there is one, I can't read it, because the window
drawn is deleted faster than I can recognize what may be printed within.
>> I've done what you said but, no way, it's still not working.
>>>> I gave the right to write on the differents files used as partitions
>>>> by coLinux. I checked with sysinternals tools filemon and regmon but
>>>> I get no access violation neither on NTFS tree nor on registry.
>>>> Is there a way to get it works ?
>>> The user needs the right to start a service. This can be given with
>>> the subinacl command.
>>> If you have no resource kit it can be fetched here:
>>> subinacl /SERVICE "Colinux" /GRANT=username=TO
>>> Meaning of TO
>>> F : Full Control
>>> R : Generic Read
>>> W : Generic Write
>>> X : Generic eXecute
>>> L : Read controL
>>> Q : Query Service Configuration
>>> S : Query Service Status
>>> E : Enumerate Dependent Services
>>> C : Service Change Configuration
>>> T : Start Service
>>> O : Stop Service
>>> P : Pause/Continue Service
>>> I : Interrogate Service
>>> U : Service User-Defined Control Commands
This was a good tip! This way I am able to have coLinux run by users
without admin-rights. BTW: it was usefull not only giving those
users "TO". "TOEQSP" was a better choice.