As in the 3rd paragraph of my last post - don't erase the cluster tips. This does not compromise security to a significant extent for most people.usoferaser said:What can I do to finish my tasks "wipe unused disk space"?
Eraser uses .NET 3.5. Version 4 is also backwards compatible.usoferaser said:What Framework version does Eraser use(compiled with)? Is it 2.0?
But if I need to erase cluster tips how can I set up .NET Framework that it worked properly and garbage collection could work properly?As in the 3rd paragraph of my last post - don't erase the cluster tips. This does not compromise security to a significant extent for most people.
I still have problems, have done the above you wrote.DavidHB said:Just to check, please delete the Task List; details of how to do this are in the FAQ topic 'Common Eraser Questions'. Then, re-start Eraser.
1. Wiping file. All is ok.Use Task Manager to check how much memory Eraser is using when idle; open Task Manager, and click on the Performance tab. Leave it open for all tests. Then, do a test erase of actual files, and see if you get the same results. . Please tell what results you get, so that Joel can do a diagnosis
I have Windows 7 professional with latest updates and all .NET Framework was install with Windows and Windows Update:Without other information, my guess is that you have a problem with your .NET installation. If it were the Eraser code (though, as I said, I don't know how it could be), the chances are that we'd all be getting this problem.
This is too much! Do you disagree, David? Why it needs so much memory and this is without erase cluster tips. Why it can't erase clusters tips direct with no-buffering IO?DavidHB said:By way of comparison, on my quad core Windows 7 machine with 8GB of RAM, memory usage during a free space erase (which runs without problems) is about 1.05GB, and CPU usage is 1% to 4%, with spikes of very short duration going up to 20%. As we know that free space erasing moves a great deal of data, these figures do not surprise me.
What .NET Framework version I must install manually?DavidHB said:If .NET has been installed and updated with Windows, there is often no uninstall entry in the 'Programs and Features'. But you can install a manually downloaded build of .NET on top of the one already there, and this will create an uninstall entry, allowing you to uninstall and reinstall .NET in the usual way.
I'll try and will write you here.DavidHB said:One other thought. Try disabling your antivirus while the free space erase is running. Does that make a difference?
If you mean that the memory usage on my machine is too much, no, I don't think so. I should have made it clear that the memory usage I was quoting was the total, including everything running in the background (antivirus etc.). I forget the Eraser proportion of that, but it wasn't huge. The reason I quoted the total figure was to compare with the 5GB+ figures that were apparent from your screenshots. Unless I've missed something, discrepancies like that point to an installation issue of some sort. And, as the Eraser code does not manage memory, attention has to turn to .NET.usoferaser said:This is too much! Do you disagree, David? Why it needs so much memory and this is without erase cluster tips. Why it can't erase clusters tips direct with no-buffering IO
3.5usoferaser said:What .NET Framework version I must install manually?
So, there is no support for Windows 7 directly. And if your program based on .NET Framework 3.5 it can't properly work on Windows 7!1.2. Supported Operating Systems
Microsoft Windows XP
Microsoft Windows Server 2003
Windows Server 2008
My comes with 4.0Joel said:Windows 7 comes out of the box with .NET 3.5.
There is no any .NET Frameworks in <Programs and Features> except for .NET 4.0. There is a checkbox for .NET 3.5 in Windows Components and it is checked.Joel said:You'll need to go to Programs and Features to uninstall and reinstall .NET 3.5 for Windows 7.
For Windows 7 .NET 4.0 is default.Joel said:It would be a nightmare if .NET 3.5 didn't work on Windows 7