https://bugs.winehq.org/show_bug.cgi?id=50966
Bug ID: 50966 Summary: sc.exe create doesn't seem to create the service Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: falemagn@gmail.com Distribution: ---
Issuing
wine sc create my-server binpath= ""...""
Doesn't create any entries under
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
And certainly it doesn't create the "my-server" entry.
Then, issuing
wine net start my-server
Produces
Could not get handle to service.
However, if I use a program I made myself to create the service, then the entry in the registry is created and net start gives
The my-server service is starting. The my-server service was started successfully.
https://bugs.winehq.org/show_bug.cgi?id=50966
Fabio falemagn@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |falemagn@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=50966
--- Comment #1 from Fabio falemagn@gmail.com --- Hm, looks like the bug was in my command line: missing space between the '=' and the binpath proper, even though I was sure I had put it there.
It would be useful if sc gave an error about this, though.
https://bugs.winehq.org/show_bug.cgi?id=50966
Fabio falemagn@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Fabio falemagn@gmail.com --- Bug was not there in the first place.
https://bugs.winehq.org/show_bug.cgi?id=50966
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal
https://bugs.winehq.org/show_bug.cgi?id=50966
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Gijs Vermeulen gijsvrm@gmail.com --- Closing INVALID.