I'm using Eraser 6.1.0.2946 and get a crash near the end of a pseudorandom free space wipe on a 4.69 GiB FAT32 partition (2.11 GiB free) on Windows 7 32-bit.
I could reproduce the crash several times.
When I try to access the partition in Windows Explorer after Eraser has crashed, I get "X:\ is...
Finally found time.
Tested with 6.1.0.2781 on the same hardware/OS/HDD as before
Here the results:
t: time the task started
t till t+90min: between 40 and 70 MiB (or whatever unit Windows' task manager uses)
t+92min till near the end of completion (t+105min): between 280 and 360 MiB
Definitely...
I'm sorry that I didn't reply sooner, somehow I didn't receive any e-mail notifications about the new posts.
That's why I asked if there's an option to just clean the "inodes" instead of overwriting the whole partition.
I'm not sure anymore. I only realized the high memory usage when the...
In the log there are about 10 messages, so definitely not something taking up 2GB of RAM.
I already ran dosfsck on Linux before using Eraser.
No, I didn't even find that ticket.
That's the reason why I tried Eraser. I filled up all the free space with zeros, but that didn't stop file recovery...
First of all thanks for this great open-source effort!
(I'm a Linux user and just used Windows to try Eraser)
System: Windows 7 Home Premium 64-bit, 4 GB RAM
I told Eraser to wipe the free space of a FAT32-partition on an (external/USB) HDD. The partition's size is about 206GiB from which...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.