|
Stupid installers. | by Phoon | 2007-07-01 01:40:39 |
|
Or that they don't want to restart at all? | by Michiel | 2007-07-01 02:00:07 |
|
A simple, "It won't work until you restart", | by Phoon | 2007-07-01 02:02:28 |
|
I love it when they say that... | by shadowsystems | 2007-07-01 02:25:11 |
|
tsk tsk tsk | by pitje | 2007-07-01 03:16:17 |
|
*LART* | by shadowsystems | 2007-07-01 03:44:58 |
|
... Sigh. | by bwkaz | 2007-07-01 05:27:08 |
|
a simple halt process apply fix then restart | by joecrouse | 2007-07-01 09:42:32 |
|
Yes, true, it woudn't be hard. But: | by bwkaz | 2007-07-01 09:47:36 |
|
If the process halts does the replace | by joecrouse | 2007-07-01 10:12:46 |
| The system doesn't have to restart. |
by bwkaz |
2007-07-01 10:25:01 |
But the process does; if the process doesn't want to (say, because it's the DCOM process), then the system will have to.
But I have a feeling I'm not getting what you're trying to say...
Are you suggesting getting some help from the process that has the file open? That'd be nice, but nothing that I know of will do it. Certainly not MS office: you can't ask any office program "please close all your handles to gdi32.dll so I can replace it".
Or are you talking about some kind of SIGSTOP type of thing, which would halt the process temporarily? That'd be nice too, but nothing like that exists on Windows that I'm aware of. And even if it does exist, halting the process doesn't close the file; the kernel would still stop you from replacing it. You'd have to kill the process (and lose any unsaved work) or get the user to shut it down gracefully (and save their work themselves).
Or did you mean something else? |
|
[ Reply ] |
|
Exactly what I was meaning. | by joecrouse | 2007-07-01 10:39:21 |
|
Hmm, maybe. | by bwkaz | 2007-07-01 13:24:07 |
|
He never said he didn't shut down his apps. | by Phoon | 2007-07-01 12:57:38 |
|
Allow me to quote: | by bwkaz | 2007-07-01 13:44:20 |
