|
![](/i/fill.gif) |
Le 21/04/2013 00:09, Patrick Elliott nous fit lire :
> It should probably be clear that Windows a) locks certain files, so you
> can't move them, **while it is running**, but b) it doesn't actually
> care if they are in those places, assuming you can find some way to move
> them later, and c) this is likely some sort of quirk in how it installs,
> where those files are "low priority, since they load once", allowing for
> a small improvement in the OS speed, by leaving the "faster" parts of
> the drive free, for all the OS components that get loaded/unloaded,
> swapped, and your own programs, etc.
And if you remember (for the old timers), Windows never got the
installation process right since its beginning: installing or removing
an application and you had to reboot.
So, nothing really news under the sun from Redmond.
(there is a joke: "mouse has moved, Windows must be restarted.", but
it's a slight exaggeration)
The classical file-locking of windows is: its DLL/SYS and the swap file.
Usually reducing the allowed swap to 0, or moving it explicitly to
another partition, can help... on the next reboot!
(compacting the file-system usually move the DLL/SYS at the start of the
partition, well, at least it does not put directory at the end of it...
oh compacting is de-fragmenting)
Post a reply to this message
|
![](/i/fill.gif) |