Jump to content

Open Source File Long Character File Fixer?


FantasyAcquiesce

Recommended Posts

Hello MSFN,

Today, I am seeking to rename a file on Windows XP that I extracted on the machine. The character limit was too high (originally came from a Windows 10 machine) , so Windows won't allow me to move the file or even rename it.

I tried looking at utilities like File Name Fixer and Long Path Fixer, but neither has done the job...the first one costs 40 USD and the second one cannot rename (or even see) the folders with the file.

Is there any free, open source software with a GUI that allows me to rename?

Thank you for your time!

Link to comment
Share on other sites


I just wanted to update this in case anyone happens to find this topic.

It's odd I can't find good utilities to simply fix this long issue. An easy solution to this problem is to simply boot from a Linux distro from CD, USB, or any bootable media, then rename the file there. It's a bit frustrating Windows XP holds such a limitation but it's the most user-friendly one I know of.

Link to comment
Share on other sites

Is that the Max_Path issue?

You should be able to access the file via the \\?\ syntax, but it has to be tried, as any tool may (or may not) support this alternate notation:

https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation

But Long Path Fixer should be able to see those files, maybe there is some other issue involved? :dubbio:

The "traditional" way was to use subst to assign temporarily a drive letter to a "deep" folder:

https://support.code42.com/Incydr/Agent/Troubleshooting/Windows_file_paths_longer_than_255_characters

jaclaz

 

 

 

Edited by jaclaz
Link to comment
Share on other sites

Under Windows XP you can use alternative file explorer that have decent support for long file path.

I suggest you have a look at DoubleCommander (open source clone of Total Commander). for Windows XP+

https://doublecmd.sourceforge.io/

Note that when a file name becomes too long you may no longer have the context menu because shell32.dll si responsible for this one.

You can however still copy/move/rename files when they go beyond the limit.

 

Also if you prefer the command line you should use Yori http://www.malsmith.net/yori/

Yori is a replacement for cmd.exe and supports long path names even under NT3.5.

Yori works even on Windows NT3.1

 

Keep in mind that when you copy files under Linux, ntfs3g does not generate short names and you have to regenerate them manually.

I wrote a simple (ssname.exe) program to do it automatically https://github.com/RamonUnch/ssname

 

I was always shocked that the explorer did not handle long path names when it has been possible on Windows NT since 1993.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...