"Stephane Dalpe" <da***@interfacing.com> wrote in message
news:21**************************@posting.google.c om...
Hi all,
I just want to know why when I'm installing jdk sometimes ask me to
reboot and sometimes he don't. As part of our installation, we launch
the jdk installation if it's not already installed, so it's important
to know when the user will be asked to reboot.
In most cases, when an install sometimes asks for a reboot and sometimes
it doesn't, it's because a file or directory (or other resource) was in use
and
locked. This can be a text editor, browser, etc. with a target file open in
it
(the file doesn't even have to be currently open if the tool failed to
unlock
the file when it was done).
If you've closed all applications (which you should), and it still happens,
it's likely that a service is accessing something in the target area. Check
the processes tab in the task manager and see if something looks likely.
(Obviously if you see 'java' running it's a likely candidate.)
Incidentally, email programs can sometimes have a serious impact on windows
installs - Outlook, especially, can make an install look like it has
stopped.
(Usually it hasn't, but it can take a LONG time to complete.) This doesn't
usually require a reboot, though.
Then next time it happens, you could try searching the registry for the key
"Runonce" (I think that's it) and see if you can discover what operation is
being blocked during the install. -Wm
