Jon and Keith,
I like the work you have done on this app; I use it more than any of your other tools.
I like the fact that it will act as a tool to find files that exceed the path length and this doesn't cause a terminating error - it just keeps searching. It would be really useful if you could either delete the file from the search window or when you right click and go open file location it opens the last correct folder in the path before the character limit.
Obviously - this would be a good plus\selling point for the Pro version.

I did previously file this as a bug with you in Feb 2012, however I actually find it as a useful tools to find long paths - butr adding the above would be really useful.

Pete

Keith,
Both, but in order of preference the delete capability would be my first choice and excellent.
I can envisage the open last readable folder been useful - particularly if there are many files that have paths are too long - just to check. The ability to delete that folder (and contents) from FileSeek would also be useful. For example there could be a Delete dialog that was access from a right click which could say interpret the mouse position on the file path and open at that point.
Just thinking of possibilities with this last point.
Pete

Keith,
This is what I get too.
So this is why I suggest the ability to right click the path in the UI at last valid folder to open a delete dialog.
Going back to the original post in Feb 11 I did mention other methods for correctly enumerating file\folder paths that are too long i.e. using the Windows API rather than .Net as described here: http://msdn.microsoft.com/en-us/library/aa365247(v=vs.85).aspx. Obviously you would need to catch the exception caused by max path length then enumerate with the UNC method. I know there are other utilities out there that do this - incorporating the functionality into FileSeek would add a big selling point.

Also see these: http://gallery.technet.microsoft.com/DelimonWin32IO-Library-V40-7ff6b16c
http://gallery.technet.microsoft.com/Delimon-Win32-Explorer-V40-bc957ab4
Pete

Keith and John,
I see you have added the functionality to remove files that exist at the end of a very long path. Can you add some feature to remove the folders as well? I know your tool is FileSeek and we are talking folders now - but it would be great if it could handle theses in some way. I know that one would need to be able to navigate the folder space and decide where along the whole path things broke and remove from there. A typical problem is with Macromedia\Flash files that can create huge path lengths.
Basically removing the file is only half the problem.
Pete

Tried this but is doesn't work. However I believe vb9 is broken now for long file paths.
Please see the images for returned folders\files showing in both Delimon and FileSeek.
Pete

Weird - its working now. Also the method for deleting worked. I will keep testing.
Pete

So I spoke too soon. Done some more testing. Use Delimon to create long path. Then pick one of the folder names. Use FileSeek to find it and then try and delete it. FileSeek doesn't delete but no error.
This is now with bv10.
Pete

Keith and John,
Long path delete for any folder (or intermediate folder) now seems to be working in bv11.
Pete

Jon and Keith,
Since the changes you have implemented I now have a use question.
In the previous version I would put a query like *.xyz2 that I knew would not exist and FileSeek would error on the long file paths but show them.

Now when I put that query nothing gets returned so I need to verify how I can now get FileSeek to return just file paths that are too long - given not knowing their names before I start? Obviously I don't want to use *.* on a 2 TB fileserver.

Would it be simplest to have a check box somewhere that says "only look for files with paths too long"?

Pete

Keith,
I see you released v3 and it handles paths that are too long. However - what was decided about my last question? I don't see anything obvious that is included.
Pete

Keith I think I found it - "Show an error and skip path when longer than 260 characters"

Keith and Jon,
I have just spent half and hour testing the long path feature. The querying works fine and FileSeek will error on long paths if it finds one if the appropriate check box is selected. It will also enumerate correctly if you use a query for a file\folder at the end of long path without the check box.

However, FileSeek is really inconsistent about deleting folders on long paths that may contain subfolders and files. I cannot find any rational. It will not delete either via a right click > delete or highlight and press delete and then some time later it will delete. This is what was happening earlier in the week when I was testing.

OK - I believe I have found what happens. If I now close and reopen FileSeek I can then delete a higher folder on the long path if I just specify that folder as a query.
I suspect if I do a query and FileSeek returns long path and then you try to delete somewhere I believe there is a handle open within FileSeek and it will not delete. Maybe you need to test some more - and provide some deletion error logic?

For reference I was using Delimon to create the paths. Then I made sure nothing else had handle anywhere on the path.

Pete

Search was completed

C:\Temp\test
A - folder name in query
1) Use Delimon to create long path
2) Pick a folder name on Delimon path within standard 260 character limit
3) Search for folder name with only folder names checked returns folder name AND files in that folder (they have foldername as prefix)
4) Click on returned folder name and choose delete. FileSeek deletes all files in this folder and all sub folders but does not remove any folders
B - folder name in include file
Same process same result

Now in all tests I can't delete the returned folder in FileSeek even when I restart the application and it only returns that single item

Thanks for the info. Also try long path tool, it helped me with error 1320 in Win7.,

Long path tool is the best solution for your problem.try it and solve your problem

Use Long Path Tool, Long Path Tool can simplify and probably end your problems in unlocking, managing and renaming files that appear to have a long filename.