Jump to content

SurprisedUser

Members
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SurprisedUser

  • Rank
    Newbie
  1. SurprisedUser

    path too long (error 1128)

    Doing a bit of research, it appears that the correct way to create long paths is to use the unicode versions of the system calls with a special character sequence prepended to the path. For more details (give this to the Dantz developers): http://msdn.microsoft.com/en-us/library/aa363859(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx Quoting from the first link: "In the ANSI version of this function, the name is limited to MAX_PATH characters. To extend this limit to 32,767 wide characters, call the Unicode version of the function and prepend "\\?\" to the path. For more information, see Naming a File." "Naming a File" is the second link. Mark
  2. SurprisedUser

    path too long (error 1128)

    Searching the forum, I found this bug reported as far back as 11-19-04. Dantz has had about 4 years to fix it. Instead, the repeated claim is that the users are doing something wrong or that Microsoft is broken. The problem is that the Dantz programmer who wrote the code to do restores made a mistake. These long paths are legal and nothing in the Microsoft system calls is broken. Retrospect needs to make the folder hierarchy in a recursive manner rather than attempt to make a long path in one shot. When is Dantz going to fix this bug? For the thousands of users of Retrospect HD software, they and the hard drive makers should know that Retrospect is not a suitable backup product, i.e. it will fail to restore backed up files (no error is thrown on the creation of the backup, only on the restore!). Yeah, I'm pretty disgusted. (Will you edit/censor this post as well?) Mark
  3. SurprisedUser

    path too long (error 1128)

    32 bit applications run on 64 bit Vista will run in WOW (Windows on Windows), which is designed to provide a 32 bit Windows environment to the application. As far as I can tell, Microsoft's WOW works. Has this bug been fixed in v 2.5 of HD (and other retrospect products)? If not, when will it be scheduled to be fixed? Mark
  4. SurprisedUser

    path too long (error 1128)

    I'm using Retrospect Express HD version 2.0.145. I have a backup from XP SP2 that I'm restoring to Vista x64 SP1. Both are NTFS file systems. Works great except for the *thousands* of files that I get a "can't write, error - 1128 (path too long)" error for. NTFS has a filename limit of 255 characters (for the ascii chars that I use) and a path length limit of 32767. http://en.wikipedia.org/wiki/NTFS Either way, I am trying to restore a backup from an identical file system and it should work. I am absolutely surprised and shocked that Retrospect has this bug. I cannot believe that I have trusted it for all this time with critical data. Is there a work around? Dantz/EMC may reply "it is an error from an OS system call to make the folder". Well, clearly Dantz/EMC don't know what they are doing then. One has to make each folder in the path separately for paths longer than the system call limit. Biggest lesson for me: I have to do complete restores on a regular basis to test backup reliability if you are using EMC/Dantz "backup" software. Mark
×