1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Invalid long filenames

Discussion in 'Legacy Windows' started by dontwakeme, 2004/09/10.

Thread Status:
Not open for further replies.
  1. 2004/09/10
    dontwakeme

    dontwakeme Inactive Thread Starter

    Joined:
    2004/09/10
    Messages:
    1
    Likes Received:
    0
    Trying to upgrade my laptop HD and the copy program (EZGig) comes up with this error and stops. Have run Scandisk dozens of times both in Windows and DOS. Windows Scandisk says it's OK now, but DOS Scandisk says there's still one or more invalid long filenames, but can't tell me which file it is. Have browsed through the whole directory structure but too many possibilites. Anyone know another method to find these long filenames and delete or fix them?
     
  2. 2004/09/11
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    There is an option in the Win scandisk to look at/fix long file names....
     

  3. to hide this advert.

  4. 2004/09/11
    broni

    broni Moderator Malware Analyst

    Joined:
    2002/08/01
    Messages:
    21,701
    Likes Received:
    116
    As Steve said....
    By default, ScanDisk for Windows does not check for MS-DOS mode name length errors.
    To force ScanDisk for Windows to detect these errors, under "Advanced Options ", click the "Report MS-DOS mode name length errors" check box to select it.
    Onn the other hand DOS Scandisk is limited to paths of no more, then 66 characters, so, if you have some file burried very deep, so path to it exceedes 66 charcters, I believe DOS Scandisk will report it as "long filename ".
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.