Ticket #135 (closed defect: wontfix)

Opened 6 years ago

Last modified 6 years ago

Eraser not deleting very long (and weird) filenames (from Sandoxie)

Reported by: Ozo Owned by:
Priority: major Milestone:
Component: Core Version: 5.8.6a
Keywords: long filenames sandboxie Cc:
Processor Architecture: Blocked By:
Blocking: Operating System:

Description

When using Eraser (v5.86 on Vista 32-bit) to delete files in my Sanboxie sandboxe (http://www.sandboxie.com/), some files will usually be left behind. The error I get from Eraser is always the same: "Error: There was nothing to erase".

These files that Eraser can't see are kind of weird: their filename is very long, and Explorer himself has troubles dealing with them (ex: Explorer's right-click contextual menu will not show all the options you would expect). So there are some options like "Open" that may not be available from Explorer, but the Delete option is always there. Since Eraser can't see these files, I have to delete them with Explorer (unsafe).

I am having this problem with Eraser since I first tried Eraser, i.e. release v5.84. Upgrading to v5.86 didn't help. Note that some other applications can delete these files, such as East-Tec Eraser 2008.

Note:

Here is the DIR output of a folder with one of such files that Eraser can't erase. Please note the very weird filename:

Volume in drive C has no label.
Volume Serial Number is XXXX-XXXX

Directory of C:\Users\XX\AppData?\Roaming\sandboxes\Sandbox\DefaultBox?\user\current\AppData?\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\JEYM66JP

2008-01-15 23:13 <DIR> .
2008-01-15 23:13 <DIR> ..
2008-01-15 23:09 265 main_31;sz=480x70;!c=31;kvid=Ro5apjAjzDA;kpu=NHLVideo;ko=p;kpid=31;kr=H;u=Ro5apjAjzDA%7C31%7C468E5AA63023CC30;tile=1;dcopt=ist;ord=61611[1].asx
1 File(s) 265 bytes
2 Dir(s) 88ÿ830ÿ775ÿ296 bytes free

Change History

comment:1 Changed 6 years ago by Joel

  • Status changed from new to closed
  • Resolution set to wontfix

It's to be expected. Long filenames like these can't be deleted with Eraser 5 nor Eraser 6. We use the standard kernel functions which accept only 260 characters in the path. Other applications may use the extended format (which supports 32767 characters) but I've judged it to be too risky to use. Furthermore, the extended format is not supported in .NET which is what v6 uses. I'll have to give this bug a miss, unfortunately.

If you want to use Eraser anyway you could rename the file to a shorter length and execute Eraser on it. Renaming to the same drive shouldn't create multiple copies.

comment:2 Changed 6 years ago by Joel

  • Version set to 5.8.6a
Note: See TracTickets for help on using tickets.