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.

Disk Error and File Name Changes

Discussion in 'Legacy Windows' started by Goaglen, 2003/06/28.

Thread Status:
Not open for further replies.
  1. 2003/06/28
    Goaglen Contributing Member

    Goaglen Well-Known Member Thread Starter

    Joined:
    2003/06/28
    Messages:
    121
    Likes Received:
    2
    A month or more ago, I received an error message from the Norton One Button Checker. There is a disk error on drive G. The program runs to a file where photos are stored. When checking this file, I noted that the file names, suffixes, had been changed. Access was only granted through the program for which they are named or used. I could not change the names in Windows Explorer.
    It took me a month to figure out the protocol for changing the names to the proper suffixes, *.tif, *.jpg, etc.
    The error still shows on a scan. Norton Disk Doctor shows the error, runs a fix, then shows that it is fixed. However, on next scan, the error is still there.
    Has a bug invaded this photo file? How can I fix this?
    Note: No emailed photos are stored in this location.:confused:
     
  2. 2003/06/28
    WhitPhil

    WhitPhil Inactive

    Joined:
    2002/01/07
    Messages:
    599
    Likes Received:
    4
    Can you post back the exact wording of the error message?
     

  3. to hide this advert.

  4. 2003/06/28
    Goaglen Contributing Member

    Goaglen Well-Known Member Thread Starter

    Joined:
    2003/06/28
    Messages:
    121
    Likes Received:
    2
    Yes, sorry, forgot to include:
    "GG contains illegal long files names on drive G "
    This is from Norton Speed Disk (optimizer). It follows with recommendation to run Norton Disk Doctor, which ID's the problem, creates Undo Directory," then clears. Problem is not solved. On rerun, same sypmtoms exist. Has been going on for a month or so just like this.
     
  5. 2003/06/28
    WhitPhil

    WhitPhil Inactive

    Joined:
    2002/01/07
    Messages:
    599
    Likes Received:
    4
    Just out of curiousity, run Scandisk with the Auto fix option OFF, to see what errors it detects. Also, ensure that logging is set.

    If/when it finds one, do not fix any, just ignore them.

    If errors are found, open the file C:\Scandisk.log using Notepad, and copy/paste one the error messages back here.
     
  6. 2003/06/29
    Goaglen Contributing Member

    Goaglen Well-Known Member Thread Starter

    Joined:
    2003/06/28
    Messages:
    121
    Likes Received:
    2
    Thank you, WhitPhil.
    The error message is below. Apparently, from an Adobe download, a set of calendar file names have tripped the file name length fault. There is one of my photos which has done the same.

    Scandisk log:
    "The G:\ADOBE\PHOTOD~1.1\PDGALLRY\TEMPLATE\TEMPLATE\INVITES\TOP1F2S\SSFTF
    folder could not be opened in MS-DOS mode because its complete short name
    was longer than 66 characters.
    Resolution: Ignore this error and continue
    Results: Error was corrected as specified above.

    The G:\My Files\Pictures\GG
    folder contained incorrect information about Butler Cherry310_1.jpg (MS-DOS name BUTLERCH):
    The file or folder's long name was stored incorrectly on your disk.
    Resolution: Ignore this error and continue

    ScanDisk found errors on this drive but did not fix all of them. "

    There were approx fifty Adobe name violations. Though "autofix" was unchecked, the Adobe files were corrected.
     
  7. 2003/06/29
    WhitPhil

    WhitPhil Inactive

    Joined:
    2002/01/07
    Messages:
    599
    Likes Received:
    4
    The long file name errors are essentially warnings, indicating the file name is too long to be opened in DOS. In 99.99999999% of the cases, this is a "who cares ", since you don't plan to anyway.

    I have some of these on my PC and also run NDD and Speedisk, but neither have ever complained. I also don't see any option to specifically ignore them (which you can in Scandisk, and may as well)

    I would run NDD with automatically fix OFF, which you should be doing all the time anyway. Never allow a piece of software to "fix" something, until you have checked out what the error means, and how it plans on "trying" to fix it.

    Then, when it hits one of these files, just select ignore.
     
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.