Re: How to handle windows installers that need processing after a reboot?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for the suggestion, but I'm not sure it's working as expected.  What would be the "normal" usage of that command, just "wineboot", or "wineboot -e"?  'wineboot' just returns to the terminal line after a few seconds, while 'wineboot -e' gives me:

Err:process:__wine_kernel_init boot event wait timed out

Is this a problem?  And if so, how do I correct it?

D
 

> -----Original Message-----
> From: David Gerard [mailto:dgerard@xxxxxxxxx] 
> Sent: Tuesday, November 10, 2009 11:11 AM
> To: David C. Kerber
> Subject: Re:  How to handle windows installers that 
> need processing after a reboot?
> 
> 2009/11/10 David C. Kerber <dkerber@xxxxxxxxxxxxxxxxxxxxxxxxxx>:
> 
> > I've got the latest wine (from WineHQ this morning) 
> installed and running on Debian Lenny.  Two of our apps 
> (which we wrote) work fine.  The third one is from a 3rd 
> party and has an installer that wants a reboot, and then (on 
> windows) does some additional processing after the reboot.
> > How do I arrange for wine to do that additional post-reboot 
> processing?  I looked in the RunOnce registry key to see if I 
> could run the command manually, but there was nothing there.
> 
> 
> The command "wineboot" is supposed to simulate a reboot. Does 
> that do the job for you?
> 
> 
> - d.
> 


[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux