Versions & mass-appeal

[Shachar Shemesh]

Andreas Mohr wrote:

>On Wed, Oct 30, 2002 at 12:21:51PM +0200, Shachar Shemesh wrote:
>  
>
>>Ender wrote:
>>
>>    
>>
>>>   - Getting the right set of dlloverrides and registry entries correct
>>>for a large portion of software is irritating. Most of this comes down to
>>>the lack of WINE being able to dynamically run RunOnce and wininit.ini
>>>entries. Doing this manually is far beyond your average user who just
>>>wants to install a reasonably complex program. Something like Crossover's
>>>reboot.so is needed.
>>>
>>>
>>>      
>>>
>>I'm willing to tackle that (the BiDi stuff is only slowly going, and 
>>there may be some unexpected development coming that is outside my 
>>hands, so I have SOME free resources available).
>>
>>Where do I get reboot.so to have a look? Either that, or can someone 
>>answer a few questions regarding it?
>>    
>>
>I've been having a finished implementation of wineboot in my tree for ages.
>I guess it's about time to get it submitted...
>  
>
I downloaded it once (you did the fatal mistake of mentioning it in one 
of your emails, and went and searched the archives for it). I couldn't 
get it to work, though, and I did not delve deep enough. If you have it, 
please submit it. I'm willing to take ownership of it if you don't want to.

>>- When are the boot time activities taking place? On wine start? On 
>>wineserver start?
>>    
>>
>Good question. I guess we once agreed on it being done on winelauncher script
>startup.
>
Not familiar enough - is that the first startup of wine?

>(or alternatively really on user desktop login, but I'm not sure whether this
>is what we want)
>
No, that would require nasty stuff we really don't want.

>winelauncher should probably check whether any of the places that register
>reboot activities need processing, and if this is the case, then first
>finish a wineboot process, *then* start regular wine apps.
>
That's the way Windows does that for SOME of the stuff (most noteably - 
wininit.ini). Also, NT does it differently (register in the registry 
etc.). I used to know all that stuff off the top of my head (I did the 
"GTFormat" system that installed all of Packard Bell's machines, and I 
believe still installs all of NEC's - moved on myself) (before 
mentioning that PB's systems were no good - that was before GTFormat was 
introduced).

>All this would have to be resistant against race conditions, of course :-\
>  
>
>>- When are login time activities taking place?
>>- How should a reboot request be treated? Should it be an indication 
>>that all these operations should start now, and let other wine programs 
>>carry on as usual?
>>    
>>
>IMO we need to make sure we only do this when no other wine process
>is running.
>
Either that, or start sending "WM_QUERYENDSESSION"s, the way the 
original does.

>Optionally there could be some way to tell Wine to do it immediately,
>even during a session, though.
>
>Sounds like nobody ever watched the wineconf2002 streams, since nobody ever
>knows about wineboot...
>  
>
I didn't watch the stream. I'm also having some hand problems as well 
(though am taking care of them, so far rather succesfully - Dimi, call 
me if you want some tips... ).

                Shachar