Fabian Cenedese wrote:
I know nothing about wineserver :) I was just wondering about thisMost of these ops takes place asynchroniously in Windows as well, so that's not the issue.
asynchronously. Of course it shouldn't get locked up. But who will be
faster then, wine or wineboot? I mean what if a program relies on these
actions being finished (they usually do), is it sure that wineboot has
finished when the app gets started?
I'm thinking that we should get the wininit.ini processed before the first Win32 program starts (and synchroniously, just like on Windows). Then, the delayed renames using RenameFileEx, also synchroniously. Next should come the RunServicesOnce, RunServices, RunOnce and Run, asynchroniously.
If we have the concept of "Explorer" in the future, we should defenitely seperate them a little (i.e. - get RunServices and RunServicesOnce over with before starting RunOnce and Run). We will also have to address the concept of Windows NT services at some point (in the future).
As for running things on ExitWindows - I don't think that's a good idea. It MAY work for wininit.ini stuff, but not the other stuff.
Shachar
