Rebooting during installation

doctordruidphd · Post by **doctordruidphd** » Sat Feb 21, 2009 9:39 pm

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?

austin987 · Post by **austin987** » Sat Feb 21, 2009 10:51 pm

On Sat, Feb 21, 2009 at 8:39 PM, doctordruidphd
<[email protected]> 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

doctordruidphd · Post by **doctordruidphd** » Sat Feb 21, 2009 11:32 pm

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.

austin987 · Post by **austin987** » Sat Feb 21, 2009 11:41 pm

On Sat, Feb 21, 2009 at 10:32 PM, doctordruidphd
<[email protected]> wrote:

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.

Maybe in C:\windows\temp ?

--
-Austin

doctordruidphd · Post by **doctordruidphd** » Sun Feb 22, 2009 10:45 pm

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.

DaVince · Post by **DaVince** » Mon Feb 23, 2009 7:48 am

Have you tried rerunning the original setup file right after? It might actually detect to "resume".

But yeah, apps that require a reboot to continue installation suck. Luckily there aren't many of them - and maybe you can find a hack for this on the net somewhere.

austin987 · Post by **austin987** » Mon Feb 23, 2009 10:29 am

On Mon, Feb 23, 2009 at 6:48 AM, DaVince <[email protected]> wrote:

Have you tried rerunning the original setup file right after? It might actually detect to "resume".

But yeah, apps that require a reboot to continue installation suck. Luckily there aren't many of them - and maybe you can find a hack for this on the net somewhere.

You could look in the registry for the 'Runonce'/'Run' keys and
execute those manually.

'wineboot -r' is supposed to simulate a reboot, but I'm not sure if it
works for this or not. We had Runonce/Run keys being executed for a
short while, but it caused a big mess and was disabled...

--
-Austin

doctordruidphd · Post by **doctordruidphd** » Mon Feb 23, 2009 12:02 pm

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.