March 2014 - Wine-Devel - list.winehq.org

Re: schedsvc: Add Task Scheduler service. Try 2.

by Dmitry Timoshkov

Alexandre Julliard <julliard(a)winehq.org> wrote: > >> >> It needs a more convincing argument. For instance, why do you need this > >> >> service > >> > > >> > I have an application that depends on this. > >> > >> Depends how? > > > > At installation time it schedules a task which should be executed when > > the installer exits, also it creates a task which checks for updates. > > Does it really call the service directly, or does it go through > taskschd.dll? It does this using taskschd.dll COM APIs, but the scheduled tasks are all separate processes. -- Dmitry.

March 6, 2014

Re: schedsvc: Add Task Scheduler service. Try 2.

by Dmitry Timoshkov

Alexandre Julliard <julliard(a)winehq.org> wrote: > > Well, I've been thinking of it, and a Wine session lifetime could be > > considered as a short-living Windows machine, with all the limitations. > > And there are a lot of various things that the task scheduler is able > > to do that I don't know how could be mapped say into cron for instance, > > like executing a COM handler, or supporting many kinds of triggers. > > > > There are many known use cases for the task scheduler like a task > > regularly checking for updates, or a task executed on user logon, > > or a task being executed on a network connection. For a list of > > various tasks you could check system32\tasks on any Vista+ system, > > there are pretty interesting examples in there. > > I still think this needs more thought. Having triggers that only happen > while some other random Windows app is running doesn't strike me as > particularly useful. Well, that's how it's supposed to work actually, just like a scheduled cron job for instance. > I also don't think that this limited usefulness justifies the cost of > running the service in every single Wine session. It should be started > only when there are actually tasks to schedule. The service also has a role of global xml task definitions storage, so that any client application could add or query task status, or check and change the task running state, and that's impossible to do without a service, similar to the functionality provided by services.exe. -- Dmitry.

March 6, 2014

Re: schedsvc: Add Task Scheduler service. Try 2.

by Alexandre Julliard

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Alexandre Julliard <julliard(a)winehq.org> wrote: > >> >> It needs a more convincing argument. For instance, why do you need this >> >> service >> > >> > I have an application that depends on this. >> >> Depends how? > > At installation time it schedules a task which should be executed when > the installer exits, also it creates a task which checks for updates. Does it really call the service directly, or does it go through taskschd.dll? -- Alexandre Julliard julliard(a)winehq.org

March 6, 2014

Re: schedsvc: Add Task Scheduler service. Try 2.

by Alexandre Julliard

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Well, I've been thinking of it, and a Wine session lifetime could be > considered as a short-living Windows machine, with all the limitations. > And there are a lot of various things that the task scheduler is able > to do that I don't know how could be mapped say into cron for instance, > like executing a COM handler, or supporting many kinds of triggers. > > There are many known use cases for the task scheduler like a task > regularly checking for updates, or a task executed on user logon, > or a task being executed on a network connection. For a list of > various tasks you could check system32\tasks on any Vista+ system, > there are pretty interesting examples in there. I still think this needs more thought. Having triggers that only happen while some other random Windows app is running doesn't strike me as particularly useful. I also don't think that this limited usefulness justifies the cost of running the service in every single Wine session. It should be started only when there are actually tasks to schedule. -- Alexandre Julliard julliard(a)winehq.org

March 6, 2014

Re: [PATCH 5/5] d3d9/tests: Use create_device() in more tests.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5434 Your paranoid android. === w2000pro (32 bit device) === device: unhandled exception c0000005 at 00407D13 === wxppro (32 bit device) === device: unhandled exception c0000005 at 00407D13 === wvista (32 bit device) === device: unhandled exception c0000005 at 00407D13 === wvistau64 (32 bit device) === device: unhandled exception c0000005 at 00407D13 === w2008s64 (32 bit device) === device: unhandled exception c0000005 at 00407D13 === w7pro64 (32 bit device) === device: unhandled exception c0000005 at 00407D13 === wvistau64 (64 bit device) === device: unhandled exception c0000005 at 0000000000407038 === w2008s64 (64 bit device) === device: unhandled exception c0000005 at 0000000000407038 === w7pro64 (64 bit device) === device: unhandled exception c0000005 at 0000000000407038

March 6, 2014

Re: schedsvc: Add Task Scheduler service. Try 2.

by Dmitry Timoshkov

Alexandre Julliard <julliard(a)winehq.org> wrote: > >> It needs a more convincing argument. For instance, why do you need this > >> service > > > > I have an application that depends on this. > > Depends how? At installation time it schedules a task which should be executed when the installer exits, also it creates a task which checks for updates. > >> where does the interface definition come from, > > > > It's documented in MSDN: > > http://msdn.microsoft.com/en-us/library/cc248435.aspx > > > >> why does it need a global header > > > > If you mean a global .idl then it follows what's already present > > for the services.exe service since it's also a service exporting > > public RPC API. > > If it's not used outside of the dll there's no reason to have a global > header. I'm planning to use it from taskschd.dll, and have already started this. > >> why does the service need to run constantly, etc. > > > > Task scheduler service needs to run constantly because it may need > > to handle various events like user login/logout, tasks starting when > > the system becomes idle, network connects/disconnects, tasks starting > > at any specified date and time, and many other types of triggers. > > That's not very convincing. If we really want that sort of support it > would have to be integrated with the OS, it can't be done from a Wine > service. Well, I've been thinking of it, and a Wine session lifetime could be considered as a short-living Windows machine, with all the limitations. And there are a lot of various things that the task scheduler is able to do that I don't know how could be mapped say into cron for instance, like executing a COM handler, or supporting many kinds of triggers. There are many known use cases for the task scheduler like a task regularly checking for updates, or a task executed on user logon, or a task being executed on a network connection. For a list of various tasks you could check system32\tasks on any Vista+ system, there are pretty interesting examples in there. -- Dmitry.

March 6, 2014

Re: [PATCH 3/5] d3d8/tests: Don't bother handling Direct3DCreate8() failures, we verified it works earlier.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5431 Your paranoid android. === w8 (32 bit device) === device.c:2533: Test failed: Expected foreground window 00030180, got 00010048. device.c:3207: Test failed: Expected wndproc 0x410390, got 0x410390.

March 6, 2014

Re: [PATCH 2/5] ddraw/tests: Verify that creating a ddraw object works before running any real tests.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://newtestbot.winehq.org/JobDetails.pl?Key=5430 Your paranoid android. === w8 (32 bit ddraw2) === ddraw2.c:5071: Test failed: Got unexpected refcount 3. ddraw2.c:5090: Test failed: Got unexpected refcount 3. ddraw2.c:5097: Test failed: Got unexpected hr 0. ddraw2.c:5100: Test failed: Got unexpected refcount 3. ddraw2.c:5102: Test failed: Got unexpected refcount 2. ddraw2.c:5108: Test failed: Got unexpected hr 0. ddraw2.c:5111: Test failed: Got unexpected refcount 2. ddraw2.c:5113: Test failed: Got unexpected refcount 1. === w8 (32 bit ddraw1) === ddraw1.c:3968: Test failed: Got unexpected refcount 3. ddraw1.c:3987: Test failed: Got unexpected refcount 3. ddraw1.c:3994: Test failed: Got unexpected hr 0. ddraw1.c:3997: Test failed: Got unexpected refcount 3. ddraw1.c:3999: Test failed: Got unexpected refcount 2. ddraw1.c:4005: Test failed: Got unexpected hr 0. ddraw1.c:4008: Test failed: Got unexpected refcount 2. ddraw1.c:4010: Test failed: Got unexpected refcount 1. === w8 (32 bit ddraw7) === ddraw7.c:5595: Test failed: Got unexpected refcount 3. ddraw7.c:5614: Test failed: Got unexpected refcount 3. ddraw7.c:5621: Test failed: Got unexpected hr 0. ddraw7.c:5624: Test failed: Got unexpected refcount 3. ddraw7.c:5626: Test failed: Got unexpected refcount 2. ddraw7.c:5632: Test failed: Got unexpected hr 0. ddraw7.c:5635: Test failed: Got unexpected refcount 2. ddraw7.c:5637: Test failed: Got unexpected refcount 1. ddraw7.c:5639: Test failed: Got unexpected refcount 6. ddraw7.c:5756: Test failed: Failed to set cooperative level, hr 0x8876023b. === w8 (32 bit ddraw4) === The test timed out

March 6, 2014

Re: schedsvc: Add Task Scheduler service. Try 2.

by Alexandre Julliard

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Alexandre Julliard <julliard(a)winehq.org> wrote: > >> It needs a more convincing argument. For instance, why do you need this >> service > > I have an application that depends on this. Depends how? >> where does the interface definition come from, > > It's documented in MSDN: > http://msdn.microsoft.com/en-us/library/cc248435.aspx > >> why does it need a global header > > If you mean a global .idl then it follows what's already present > for the services.exe service since it's also a service exporting > public RPC API. If it's not used outside of the dll there's no reason to have a global header. >> why does the service need to run constantly, etc. > > Task scheduler service needs to run constantly because it may need > to handle various events like user login/logout, tasks starting when > the system becomes idle, network connects/disconnects, tasks starting > at any specified date and time, and many other types of triggers. That's not very convincing. If we really want that sort of support it would have to be integrated with the OS, it can't be done from a Wine service. -- Alexandre Julliard julliard(a)winehq.org

March 6, 2014

Re: schedsvc: Add Task Scheduler service. Try 2.

by Dmitry Timoshkov

Alexandre Julliard <julliard(a)winehq.org> wrote: > It needs a more convincing argument. For instance, why do you need this > service I have an application that depends on this. > where does the interface definition come from, It's documented in MSDN: http://msdn.microsoft.com/en-us/library/cc248435.aspx > why does it need a global header If you mean a global .idl then it follows what's already present for the services.exe service since it's also a service exporting public RPC API. > why does the service need to run constantly, etc. Task scheduler service needs to run constantly because it may need to handle various events like user login/logout, tasks starting when the system becomes idle, network connects/disconnects, tasks starting at any specified date and time, and many other types of triggers. -- Dmitry.

March 6, 2014