Henry Nestler wrote:
> Ah, thanks. So, it must be Windows specific problem, and not my system.
> If I watching more, I found more problems:
> We install driver with CreateServiceA "C:\colinux\linux.sys" (ASCII
> Path). Windows translate it into unicode path
> "\??\C:\colinux\linux.sys". This I can see via export the registry to
> text file.
> If I change it to "\\?\C:\colinux\linux.sys" (regedit), then can see
> the "driver details", but can not start colinux service. Hardware
> Control Manager fails with error "wrong path".
> If I change it back to "\??\C:\colinux\linux.sys", then "driver
> details" is grayed, and I can start colinux service.
> It's more mysterious. I let it grayed, that runs :-(
"\??\C:\colinux\linux.sys" is windows internal. The first "\" is the
root object name space. "??" is a link to the object directory
"\GLOBAL??". "C:" is a link to something like "\Device\HarddiskVolume2".
"\colinux\linux.sys" is a file on the specific volume. The driver image
path may be relative to the system root directory. In this case, the
path is something like "system32\drivers\linux.sys". I think, the grayed
button within the properties applet is a bug from windows.