fail on excessively long file names / paths
Posted: 22 May 2015 06:55
Hello,
I have run into an annoying problem in Windows XP. Inadvertently, when saving various online internet articles for later reading, I have saved files with ridiculously long names (and of course their associated equally long named accessory folders). Unfortunately Firefox let me save them, but now I can't manage them. xyPlorer will display them but is then unable to delete or rename them. I can't blame xyP, because Windows Explorer can't handle them either. This has been causing some good sized problems in my routine file cleanup and automated ftp backup activities.
I did find some manual workarounds: for example I can pull out all the good files, leaving just the bad ones in a folder and then delete the whole folder one level up. The main problem that is most aggravating is that all file copy operations just halt with the expected "unable to copy" message, with no indication of which actual file is the offender. When one is attempting to do mass file backup operations that makes it extremely tedious to try and search through the whole file tree looking for the offenders -- especially when some filenames and paths are marginally close to the limit but not quite defective. Expanding whole trees helps, but is also a pretty slow way to go.
I realize that the very uninformative error message probably originates from Windows' API and not from xyP itself, but I was wondering if xyP has any diagnostic utility that can be called up to identify exactly where file copy operations are halting. That would sure speed things up when I'm trying to locate and toast the offenders. I did of course go through xyP's help screens and have a look through the online FAQs. Sorry if I missed something obvious. If there is in fact some utility in xyP to identify file copy fail points I would be most grateful for that information. Also, I was wondering if there is any kind of environment variable I might alter in Windows to enable excessive length paths and filenames to be handled, even just temporarily. I will of course be a lot more careful about what I save off the net in future, but at the moment I am stuck with a considerable cleanup job from several years of unsuspecting downloads. Thanks to anyone who can advise.
I have run into an annoying problem in Windows XP. Inadvertently, when saving various online internet articles for later reading, I have saved files with ridiculously long names (and of course their associated equally long named accessory folders). Unfortunately Firefox let me save them, but now I can't manage them. xyPlorer will display them but is then unable to delete or rename them. I can't blame xyP, because Windows Explorer can't handle them either. This has been causing some good sized problems in my routine file cleanup and automated ftp backup activities.
I did find some manual workarounds: for example I can pull out all the good files, leaving just the bad ones in a folder and then delete the whole folder one level up. The main problem that is most aggravating is that all file copy operations just halt with the expected "unable to copy" message, with no indication of which actual file is the offender. When one is attempting to do mass file backup operations that makes it extremely tedious to try and search through the whole file tree looking for the offenders -- especially when some filenames and paths are marginally close to the limit but not quite defective. Expanding whole trees helps, but is also a pretty slow way to go.
I realize that the very uninformative error message probably originates from Windows' API and not from xyP itself, but I was wondering if xyP has any diagnostic utility that can be called up to identify exactly where file copy operations are halting. That would sure speed things up when I'm trying to locate and toast the offenders. I did of course go through xyP's help screens and have a look through the online FAQs. Sorry if I missed something obvious. If there is in fact some utility in xyP to identify file copy fail points I would be most grateful for that information. Also, I was wondering if there is any kind of environment variable I might alter in Windows to enable excessive length paths and filenames to be handled, even just temporarily. I will of course be a lot more careful about what I save off the net in future, but at the moment I am stuck with a considerable cleanup job from several years of unsuspecting downloads. Thanks to anyone who can advise.