Re: [coLinux-devel] mysterious ImagePath for linux.sys

[Henry N. <Henry.Ne@Arcor.de>]

Bernd Brandstetter wrote:
>>src/colinux/os/winnt/user/daemon/driver.c:
>>I traced colinux source and see that the function CreateService() was
>>called with right name "C:\colinux\linux.sys".  Function was called with
>>non UTF name (without prefix "\\?\") for lpBinaryPathName (see
>>http://msdn.microsoft.com/library/en-us/dllproc/base/createservice.asp).
>>
>>Is that a bug in CreateService?
>>Have anybody same grayed button?
> 
> 
> Yes, same thing here. And I just noticed that Google and Yahoo are not very 
> helpful when searching for something like "\\??\" :-(

Ah, thanks.  So, it must be Windows specific problem, and not my system.

http://msdn.microsoft.com/library/en-us/fileio/fs/naming_a_file.asp


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  :-(

-- 
Henry Nestler