Ticket #210 (accepted enhancement)

Follow-up to #41 and #135

I understand that handling of NTFS long filenames is not available in .NET, however, so it can't be fixed+forgotten, but the problem it creates is major _and_ there might be a workaround.. so please re-consider :)

Additions to the problem:

• MSN file sharing and IE can easily create too long filenames, so the problem may be pretty common
• On my PCs, erasing around too long filenames actually crashed Eraser, with only indirect hint (fragment of current filename string)
• Even free space deletion crashes
• The crash closes the parent process - even if it was explorer.exe
• Crashing is not a way for a GUI programme to respond to an issue in the wild, IMO :)

Suggestion:

• Catch exceptions around the erasing, (optionally?) skip on error and report it in the end
• Even better, check for filename length (on NTFS of course) and explicitly report
• Even better, move+rename the file to %TEMP% before processing, and restore afterwards (if needed). Not failproof (not sure about open files) + has a time window where power loss is problematic, so making it an option might be a good idea.

Using Eraser v5.84, Windows XP SP2, NTFS.