Search results

Distilling the last few posts, I think the only thing outstanding is the system freezing during erasures. First: Where is your Firefox profile stored? Second: Have you tried disabling your anti virus? Depending on how many CPU cores you've got, I/O could be a real bottleneck.

Probably Eraser touched Firefox's program files as it was running, which it didn't like. Cluster tip erasure on Windows is always hit-and-miss, since we're opening file handles to files which normally won't be opened in that manner.

Re: unused space erasing failed to erase some undeleted file Yup, erasing cluster tips is a global option in Eraser 5.

Alright. Let's do something counterintuitive here: disable forced unlocking of locked files and see if these errors get reported again. Yeah, it's possible. Anti virus programs are rather pesky.

Your antivirus could just be "quarantining" the file. Check your AV settings/quarantine. This is weird. What file system is this drive? Eraser has its own unlocker. It should be able to release the files. Did you enable it? The rest of the messages are normal.

Yup, David got my point right.

No, defragmenters should be incapable of producing sparse files. It is an attribute that is set when the file is first created.

It does. You should try to run a recovery tool to see if the information that does remain (because it is hard to remove everything) is within your tolerance level.

I'm guessing those are files which the system uses on/off, like the HKLM registry hive.

From my observation, the most common program to make sparse files are BitTorrent clients - with good reason, since the stuff they are downloading off the network may not be immediately available, and it could be prudent to allocate space only when it is needed. Unfortunately moving and copying...

I'm more curious about the less obvious (probably, since I wrote most of the stuff in there), but what does Send To address that the context menu extension does not provide?

It is a bug. But it's a bug in the .NET Framework. I've reported this to Microsoft, and they've said they've fixed it, but...

I've got nothing to add. What you're doing here isn't really going to be found in any textbooks, either. It's probably best if you collected your own empirical evidence since if your purpose is to defeat Windows (which will try it's best not to let you succeed) it's pretty much a whole new ball...

Then in all likelihood it should be fine. Test first, though.

The diagnostic for encrypted/compressed/sparse files is very seldom wrong: what you'll have to do is to discard the Recycle bin folder on your drive (http://eraser.heidi.ie/forum/viewtopic.php?f=35&t=5708 para 3) and run an unused space erase.

Services, to a large extent, shares the ability to access anything when running under System. I know it's nothing exactly special that you're doing in your service program, and that while it is highly unlikely someone without the necessary technical skills be able to repeat the steps you...

Which is strange - the bootstrapper will clean up after itself before it exits. Hence I prescribed extracting the archive, since running it alone would not have been sufficient to get the MSI out. But anyway, glad it works.

The way you describe your server program is such that it will preemptively allocate extents on the disk ("preallocation.") How does it accomplish that? If you use the Windows APIs, then it should be fine. But if you're just keeping tabs within your program and nowhere else, you'll be running...

It's arguably the most dangerous thing anyone can be doing to a Windows install (I term it God Mode), so I'd recommend against this being shared this freely.

It sounds like the Windows Installer cache was purged (by a registry cleaner or the such). As David posted in the other thread, you can extract the MSI from the installer using 7-zip or WinRar.