can I deny permissions for SYSTEM for $recycl

Packard bell / Dot se/r-110uk
January 27, 2011 at 15:35:45
Specs: Windows 7 Starter/Linux i686, Atom N450/1GB
As Administrator, I wish to override SYSTEM control of certain small NTFS partitions with limited sizes - a swap or pagefile partition, for instance, which I cannot hide. I don't want irrelevant (in this case) folders such as $RECYCLE.BIN or System Volume Information to store files there. Can I do this, and would it be safe to do so? I have to say that I know how it can be done, but will there be problems from the system if it is done? Access control help has little specific information on taking over system objects.

Otherwise, is there a registry hack to stop these folders from being there?

This is on a netbook, Packard Bell dot se (mfg. Acer) Intel Atom N450 1.66Ghz, 1GB RAM 160GB hdd, dual booting with Mint Linux. My intention is to use it as an ultra portable tool to assist users in their own homes with system problems.

See More: can I deny permissions for SYSTEM for $recycl

Report •

January 27, 2011 at 16:15:03
Don't really understand. Pagefiles don't go into separate partitions unless you specifically set it up that way (and you can tell system size to use). You can adjust the mount of space system restore uses on a partition/drive basis (so system volume information can be controlled) or turn it off. You can also restrict recycle bin size or set it to delete rather than use the bin. So basically what's the fuss about?

Report •

January 27, 2011 at 16:56:40
In Windows there is no such thing as a pagefile partition. You can create a separate partition for the pagefile (a bad idea) but the pagefile will always be a file. A pagefile anywhere but on the system volume is always explicitly created by the user, not by the system.

Why do you have these small partitions at all? Without knowing the purpose of these partitions it is impossible to answer your question.

In my view you should be very sure of what you are doing before changing system permissions to anything.

Report •

January 28, 2011 at 01:24:39
Thanks for the replies. I intend to have several Windows versions multibooting, e.g. XP, Vista, & 7. Running in VMs is not yet acceptable on these little machines (nor in some real-world scenarios). A single swapfile in the same place for all systems would be favourite,

A single, small boot partition too would be good for easy backup and restore or editing. System Reserved boot partitions are already being implemented for Windows 7, as well as EFI booting volumes, which have remarkable speed benefits.

While they remain hidden, they are accessible only to the System, which is good for Windows 7, but not earlier versions. I may need to get these to cohabit nicely with unsupported XP, Win2k and Vista for several years yet to come.

System Volume Information folders do not only contain system restore data. Chkdsk folders and logfiles appear there, in Win7 at least. Heaven knows what else, I hadn't looked before - there's loads of data, logs, metadata. Is it different in Vista or XP?

If we are still needing to multiboot in a few years time, and still supporting people with legacy systems, who need to do the same because they have much invested in working legacy hardware and software, the possibilities need exploring. Just as there are databases with DOS origins still running core business activities, the Microsoft model of "more-or-less the same but better" cuts both ways - "if it ain't broke, don't fix it" springs to mind. Microsoft want the "better", whereas many users want "the same", and unfortunately "better" equates to "broke", and my job is to "fix it". There are many ways of doing the same thing. Thanks for the remarks, Steve, no fuss just wanted to know if anyone had recent experience of this type of thing.

I've since found this old discussion:
Swap partitions are standard practice for Unixes, I can't understand why LMiller7 thinks it's a [u]bad[/u] idea, it has just never been implemented well in MS OSs. If the swapfile volume is located in the first few GB at the beginning of the disk, it will be much faster than the default location, as in Windows installations. It can never get in the way of other files being written, or cause excess disk activity when data is being written on either side of the pagefile. You also know the true size of your system disk files, without having to check and subtract the page file size.

Report •
Related Solutions

Ask Question