Eraser version 5 was used together with sandboxie with the following parameters :

"C:\WINDOWS\system32\Eraserl.exe" -folder "%SANDBOX%" -subfolders -method Random 1 -resultsonerror -queue

With Eraser version 6, eraserl.exe doesn't exist anymore, but eraser.exe has his own command line parameters. You can show the command line parameters from Eraser 6 with the following command :

"C:\Program Files\Eraser\Eraser.exe" help

The problem is that the command line parameters from Eraser 6 are not the same as Eraser 5. Which command line parameters should I use with Eraser version 6 ?

Eraser 6 can accept command line parameters, but it's still a Windows program.
It cannot run in DOS mode.

So I guess we first have to ask tzuk, if Sandboxie's Delete Command requires a DOS mode program or can it be a Windows program?

Were do we stand with using Eraser 6 in Sandboxie ?

No, there is no requirement for a console application. Obviously, if the application displays a window and waits for a click, then it's going to make the delete sequence more cumbersome. But it would still work. So the only issue is figuring out what the new command line should be.

I've tried to get Eraser 6 working with Sandboxie, but have had no luck.
So far, with parameters left to their default values (and with or without the "--quiet" parameter, as shown):
Using "USER" as the Windows logon name,
"C:\Program Files\Eraser\Eraser.exe" addtask --quiet --dir="%SANDBOX%"
gives an error:
Eraser Could not find a part of the path 'C:\Documents and Settings\USER\SandboxUSER__Delete_TestBox_01CAC9C6BFE69DF0'
Eraser seems to be looking in the user's %USERPROFILE% folder for the directory to delete, but is also appending a strange form of the actual name of the folder that is to be deleted.
Results: The sandbox was renamed by Sandboxie; the Eraser task fails with an error message; Eraser.exe stays in memory and in the system tray.
Eraser's log shows the failed task, as listed above.

If the complete path to the Sandbox folder is specified (with or without the "--quiet" parameter):
"C:\Program Files\Eraser\Eraser.exe" addtask --quiet --dir=C:\Sandbox\USER\"%SANDBOX%"
Results: Sandboxie renames the sandbox folder; Sandboxie's tray icon stays a red X; Eraser.exe stays in memory, although not in the system tray.
Eraser's log shows nothing.
--
Eraser 6 command line parameters, for those who may want to try it:

I also tried it now, testing some stuff from the command line, without involving Sandboxie at all, and I think the Eraser 6 command line interface is just buggy.

I was using a command prompt, working from the directory C:\TEST and typed:



I get the same error that Guest10 describes:

Session: Monday, March 22, 2010 7:39:13 PM
Monday, March 22, 2010 7:39:13 PM Error Could not find a part of the path 'C:\TEST\TESTTODEL'.

I then revised my command:



Which addresses two points: (1) The cd at the front is necessary because Eraser 6 seemingly takes the dir parameter and uses it as a suffix to the current directory. So I'm setting the current directory to the root directory. And (2) With the C:\ prefix of the dir parameter obviously ignored (as per point 1), any other backslash seems to be discarded unless it is repeated twice.

This works, but I think it might not be suitable for an automatic process.

Hi, if you use the command:
eraser addtask -d="c:\\Programmi\\Eraser\\EXTRA" -q
it works.

"D:\Programme\eraser\eraser.exe" addtask -m=1407fc4e-feff-4375-b4fb-d7efbb7e9922 -s=now -d=C:\\TEST

This command would delete the C:\TEST folder with the Gutman method.

The problem is, that Sandboxie renames the sandbox to some like "__Delete_SBOXNAME_01C..." before Eraser is started.

So you cant put in the path for your Sandbox, cause u dont know it.

If Tzuk could make another shortcut like "%Sandbox%" but with double slash, it would solve the problem.

Ok, I can do that. I will post an update here when it's done.

Thanks tzuk, we all appreciate your support.

In version 3.57.03, the Delete Command now accepts the variable %SANDBOX\\%. It expands in the same way as the old %SANDBOX% variable, except the backslashes are doubled.

But there is no need to mess with this directly, as I added an Eraser-6 button in the Delete Command settings page in Sandbox Settings in version 3.57.03, and this button sets a delete command based on the discussion in this topic.

What is the difference between Eraser5 and Eraser6? also how effective is the default delete settings? like if i had a virus in the sandbox and i used the default autodelete sandbox, would it totally erase all traces of the virus?

I am using Windows 7 64 bit, Sandboxie Beta ver. 3.57.03 (64bit)

I tried using the new built in Eraser 6 delete command...though the eraser part works fine the tray icon remains in delete mode even after erasing is complete! I can only get back the default sandboxie control mode (sandbox tray icon) by rebooting the computer!

Is anyone else seeing this problem?

Tzuk...could you please have a look...thanks!

What anti-virus are you using ? Likely a software conflict.

If the tray icon remains X it typically means that the process which is deleting the sandbox has still not ended. Which means a conflict with another program is not likely the cause of the problem. More likely, the command line is wrong in some way, and this causes Eraser to display some error window, which is hidden and inaccessible.

I won't be able to look into this immediately, it will take me a couple of days, but I'll post an update when I know some more about this.