Re: Use RAM for NTFS security permission changes

So what happens, in your happy scenario, if:

1. A file changes, is deleted, or moved during the process?
2. A stack overflow allows a hacker to access or expose memory contents?
3. Power fails on the workstation during the process?

Frankly I expect that any such process that touches several hundred thousand files will take a while and have no interest in shortcuts to try to speed it up at the risk of failure.


"John Peterson" <JohnPeterson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:25FA9456-581D-49B4-B885-8422C73C1D5A@xxxxxxxxxxxxxxxx
I want to suggest that you alter the way NTFS permission settings are applied
in Windows XP, Vista and 7 with the goal of minimizing the number of HDD
queries that are made when changing security settings for many files at a
time (for example for large directory or a drive with many files).


.

Quantcast