![]() *You will have to download a previous version of Heidi Eraser, version 5 for the Sandboxie command to work. If you're not already using Heidi Eraser to secure delete your sandboxes - I recommend it. With the secure deletion of Eraser you get the peace of mind knowing at least it will wipe out any non deletions of sandboxes that may have occured - I am guessing the Queue command see's to it that any failed deletions will be stacked up and booted out the next time deletion is evoked. ![]() I have always bumped into problems with the default Sandboxie deletion. And I prefer the secure deletion using Heidi Eraser over to the default RMDIR command. Like J_L, I think the deletion of sandboxes when you close the leader application is a good policy. ![]() I use a ramdrive/disk for my browsing, but only because I've switched to a SSD drive, just to cut down a load of HD writes. If you have admin privileges and the RAM disk still fails, lower the size of the RAM disk and try again. First and foremost is that you need to have administrative privileges for this to work. Note: There are a few reasons why a RAM disk will fail to start. I can't say I notice any speed increases, TBH. The installation of the drivers is part of the RAMDisk start-up. Maybe if you're looking to ensure browsing tracks are going to be dumped at reboot, maybe there is a privacy benefit to browsing in one?. I don't think there are any security benefits for ram disk/drive browsing.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |