[Bug 60479] New: CloneCD shows

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=60479

            Bug ID: 60479
           Summary: CloneCD shows
           Product: Wine
           Version: 11.19
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
  Target Milestone: ---
      Distribution: ---

Driven by the experiments with other kernel mode drivers in bug #60466
I tried to start CloneCD, which unfortunately shows again the same behaviour
as in bug #51998.


0074:err:ntoskrnl:ZwLoadDriver failed to create driver
L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\ElbyCDIO": c0000142
003c:fixme:service:scmdatabase_autostart_services Auto-start service
L"ElbyCDIO" failed to start: 1114
0024:trace:msgbox:MSGBOX_OnInit L"Unable to load the CloneCD device
driver!\nAfter Installation of CloneCD Windows has to be restarted!"

This shows up with a 64-bit prefix, and a regression test leads me to
wine-11.8 as last version, which gets over this message.


A git bisect shows this commit:
2231b967d9e7f9712764c40aac235465d2890a1c is the first broken commit
commit 2231b967d9e7f9712764c40aac235465d2890a1c
Author: Dmitry Timoshkov <[e-mail]>
Date:   Wed Oct 29 21:23:51 2025 +0300

    wineboot: Run services.exe from c:\windows\system32 directory.

    A .Net based service detects that it's running as a service by checking if
its
    current directory is system32, otherwise the service runs in some debugging
    console based mode. Service processes created by services.exe inherit its
    current directory, so it's enough to make sure that services.exe runs from
    c:\windows\system32.


Comparing the files I could not find a difference to
a native installation within a 64-bit windows 11:
drive_c/windows/system32/drivers/ElbyCDIO.sys
drive_c/windows/system32/drivers/ElbyCDFL.sys
drive_c/windows/syswow64/Drivers/ElbyCDFL.sys


$ wine reg query 'HKLM\System\CurrentControlSet\Services\ElbyCDIO' /v ImagePath
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ElbyCDIO
    ImagePath    REG_SZ    System32\Drivers\ElbyCDIO.sys


Reverting 3f4fde0038 and 2231b967d9 makes this error go away.
CloneCD fails then with another error, but UI stays open.
  0024:trace:msgbox:MSGBOX_OnInit L"No CD-Rom found!"

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 60479] CloneCD shows ntoskrnl:ZwLoadDriver failed to create driver ... ElbyCDIO: c0000142

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=60479

Bernhard Übelacker <[e-mail]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    Regression SHA1|                            |2231b967d9e7f9712764c40aac2
                   |                            |35465d2890a1c
            Summary|CloneCD shows               |CloneCD shows
                   |                            |ntoskrnl:ZwLoadDriver
                   |                            |failed to create driver ...
                   |                            |ElbyCDIO: c0000142
           Keywords|                            |download, regression
       Distribution|---                         |Debian
                URL|                            |https://archive.org/downloa
                   |                            |d/generic-SetupCloneCD5340/
                   |                            |SetupCloneCD5340-SetupClone
                   |                            |CD5340.exe

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 60479] CloneCD shows ntoskrnl:ZwLoadDriver failed to create driver ... ElbyCDIO: c0000142

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=60479

--- Comment #1 from Bernhard Übelacker <[e-mail]> ---
Created attachment 82325
  --> http://bugs.winehq.org/attachment.cgi?id=82325
relative-path-get_binary_type.patch

I found with current git the winedevice.exe is a 32-bit process, which is
therefore not able to load the 64-bit driver.

In the registry the Service entry is marked with WOW64=1.

Removing this WOW64 entry makes it a 64-bit process
and the driver can be loaded successfully.

A installation within a native Windows also does not have this WOW64 entry.
Also, other services with this WOW64 mark contain a value of 0x14c,
which matches IMAGE_FILE_MACHINE_I386.

Is the problem here in svcctl_CreateServiceWOW64W, which seems to assumes
a service created via this WOW64 API is always is_wow64=TRUE?

In the past this may have worked because in get_winedevice_binary_path
a call to GetBinaryTypeW succeeded, because winedevice.exe's
current directory was "c:\windows".
But this fails now as the current directory is "c:\windows\system32".

Attached patch tries to cover relative paths by adding a prefix "..\\".

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.