Re: error msg: Eraser cannot connect to the running instance
The Eraser download page specifies that the program should be used with Windows XP SP3.
If you're referring to "http://eraser.heidi.ie/download.php", then no, it does not. It specifies Build Name, Version, Release Date, and Downloads, but no target/supported OS. (Edit: Ah, I found it on the index.php page--somewhat oddly reported as a feature. It should probably be added on the Download page as well, no?). As for running it on SP2: I really don't see why there would be any issue in doing so; it runs quite well beyond the issue noted above.
Thank you for linking the thread; it explains nicely the plans to run it as a service. However, it doesn't really answer my question as to a reason why
Eraser now runs at startup--that is, why this was planned for 6.x to the exclusion of running it normally? If it was purely a Vista/7 response, was there no way to avoid forcing the background process? As I said, beyond the task scheduler, I can't see why it needs to run, and even the scheduler could be done by the OS.
And Version 6.0.7 works perfectly well (including the shell extension) for me on XP, though I am using SP3.
Does it work without running on boot?
The main thing you're reporting here is that you've disabled the starting up of Eraser by default. Try enabling it for starters.
I'm reporting that the behavior of this utility is not functioning as expected (based on previous versions). While I appreciate that the background process/future-service is kept to minimal system resource use, I think many people nevertheless would rather not have that process present on a day-to-day basis.
The fact that Eraser doesn't work after the program has been exited and re-run from the context menu is a known bug, but without any conclusive means of finding where the problem is.
Well, that decides it for me then, unfortunately; I'll have to revert to the 5.x series. It's good to know, however, that there are no known major (particularly security) issues in 5.8.8. I look forward to when the 6.x series fixes this bug / restores the "run on demand" functionality.
As for the current versions: it might be wise to put some sort of information bubble in the installation that describes the current installation scenario: "As of Eraser 6.x, a background process is required and will be registered to run on startup. This is in anticipation of converting the background process to a service. For more information, see here." This could then be expanded to "For information on running Eraser portably / without a service, see here" if and when that functionality is introduced.
Again, I appreciate your efforts on this program. I mean no offense; I am simply trying to run the recent versions of this program in the same way I have run previous versions for years. Obviously it is not to be, yet, but I look forward to it being a possibility in future versions. Thank you again.