OK, I know I've seen the answer somewhere, but I can't find it. How does one handle the situation when an installer asks you to reboot during an install? Wineboot does nothing, or maybe it does, but I can't figure out what to do next. Are there generic instructions for doing this?
On Sat, Feb 21, 2009 at 8:39 PM, doctordruidphd <wineforum-user at winehq.org> wrote:> OK, I know I've seen the answer somewhere, but I can't find it. How does one handle the situation when an installer asks you to reboot during an install? Wineboot does nothing, or maybe it does, but I can't figure out what to do next. Are there generic instructions for doing this? > > > > > >Just click reboot. It won't affect your OS. -- -Austin
Yeah, it didn't accomplish anything, either. Wine just died, and I don't know if there is a way to restart it so that it resumes the installation.
Nope, nothing there except residue from other applications. There is a directory tree ~/~MSSETUP.T/~mdac.t which has a couple of files in it, one of them acmsetup.exe, but when I run it, it says it is missing several files. This is MS Works that I am trying to set up, and it just may not work at all. Was worth a try, though.
OK, I tried wineboot -r; didn't do anything. There is a Runonce key, which points to the original SETUP.EXE. Running that, both with and without a previous wineboot -r, did nothing. The setup program is apparently not writing all of the files it needs to its temporary directory. No telling why, but that seems to be the problem. So I think we'll just have to chalk this up to one that isn't going to work.