Announcement

Collapse
No announcement yet.

Folder path too long

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Solved Folder path too long

    I get "Can't read file header" when I try to open images in deep folder paths, I am very sure that the problem is my folder paths are too long because the images work fine with other viewers. I know the obvious solution is to make shorter folder paths but I would rather not do that. I've looked through these forums and on google and didn't find anything resembling my problem with irfanview. Would greatly appreciate any assistance and I apologize if there is already a thread on this issue somewhere.

    #2
    Originally posted by Draugluin View Post
    I get "Can't read file header" when I try to open images in deep folder paths, I am very sure that the problem is my folder paths
    Maybe it's a Unicode problem. Try to activate the basic Unicode support (plugin) which is new in 4.20.

    Comment


      #3
      Path too long

      I think it's still caused by the (too) long directory names you use. Even the Windows Explorer can't read loads of deep subdirectories with long filenames, see the attachment.
      Attached Files

      Comment


        #4
        Maybe it's a Unicode problem. Try to activate the basic Unicode support (plugin) which is new in 4.20.
        This is the first thing I did when I upgraded to 4.20 :P

        I think it's still caused by the (too) long directory names you use. Even the Windows Explorer can't read loads of deep subdirectories with long filenames, see the attachment.
        This is true but it is only too long for Irfanview to open the image, even Windows Picture and Fax Viewer opens it with no problems at all. So how is it Windows Picture and Fax Viewer can open it with long folder path and Irfanview cannot?

        Comment


          #5
          Originally posted by Draugluin View Post
          So how is it Windows Picture and Fax Viewer can open it with long folder path and Irfanview cannot?
          Most programs are using a fixed length for filenames it's called MAX_PATH. MAX_PATH is 256. Because Irfanview does not support Unicode internally it may be the case that this Unicode plugin is not able to convert the filename correctly if the Unicode path is quite long already.

          Comment


            #6
            Originally posted by impdf View Post
            Most programs are using a fixed length for filenames it's called MAX_PATH. MAX_PATH is 256. Because Irfanview does not support Unicode internally it may be the case that this Unicode plugin is not able to convert the filename correctly if the Unicode path is quite long already.
            That makes sense because the folder names have a lot of Unicode in them, so you think there is probably nothing that can be done to allow Irfanview to open these images?

            Comment


              #7
              Originally posted by Draugluin View Post
              That makes sense because the folder names have a lot of Unicode in them, so you think there is probably nothing that can be done to allow Irfanview to open these images?
              If you are able to open these images in general (means on an other location) then I guess you can not do anything in the moment. Maybe you should try to contact the Unicode plugin author to get information about the limitations of this plugin.

              Comment


                #8
                Originally posted by Sjef View Post
                I think it's still caused by the (too) long directory names you use. Even the Windows Explorer can't read loads of deep subdirectories with long filenames, see the attachment.
                yes. you are right. I was stuck with the same issue. Used longpathtool to solve the problem. it saved my project!
                try it yourself. works like magic.

                Comment


                  #9
                  Hey,
                  That's great! I used Longpathtool program,
                  Thanks!

                  Comment

                  Working...
                  X