Cooperative Linux

On Friday 03 February 2006 14:50, Henry Nestler wrote:
> I'm searching condition for some problems in updating process of
> linux.sys driver.
>
> The first mysterious is, that I have a driver with name CoLinuxDriver
> and CoLinuxDriver0.7.1
>
> http://www.henrynestler.com/colinux/screenshoots/HardwareDeviceManager.p
>ng
>
> After manual uninstalling all CoLinux, the CoLinuxDriver0.7.1 never come
> back.  Have anybody see something to?

Nope.

> Second problem is, that the ImagePath to driver is not correct.  You see
> it in Hardware Device Manager, Properties of CoLinuxDriver, tapstop
> Driver and the grayed button "Driver details".
>
> Then I go into the registry
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CoLinuxDriver and
> changed the ImagePath from "\??\C:\colinux\linux.sys" into
> "\\?\C:\colinux\linux.sys" or "C:\colinux\linux.sys"
>
> After that, I can view driver details now:
> http://www.henrynestler.com/colinux/screenshoots/driver-details-grayed.p
>ng
>
> After reinstalling coLinux, the path is wrong again.
>
> 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 "\\??\" :-(

Bernd

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

On 2/3/06, Henry Nestler <Henry.Ne@...> wrote:
> I'm searching condition for some problems in updating process of
> linux.sys driver.
>
> The first mysterious is, that I have a driver with name CoLinuxDriver
> and CoLinuxDriver0.7.1
>
> http://www.henrynestler.com/colinux/screenshoots/HardwareDeviceManager.pn=
g
>
> After manual uninstalling all CoLinux, the CoLinuxDriver0.7.1 never come
> back.  Have anybody see something to?

You are probably seeing some leftover from a previous experiment I
made with a special build to show George it was easy to have a driver
with different names for each version.
The idea was to avoid version conflict problems and allow users to
have different versions installed side by side (but specially for
developpers).

I know I made no secret of that, maybe you just forgot about it?


Regards,
~Nuno Lucas

Henry Nestler wrote:
>
> 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  :-(
>
"\??\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.

- Hartmut