Completely random guess here (I have not thought this through), but, try mapping a drive say half way into this hierarchy and see if that will let you delete some of the deeper folders.
Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: SMREKAR, JACK [mailto:[email protected]] Sent: Thursday, April 23, 2009 10:52 PM To: NT System Admin Issues Subject: RE: path longer than 1023- actually only about 200 or less some one did something stupid in a programming class. there are others that have done this, even the teacher did it. I tried running check disk before but that did not fix it , also it would take about 2 days to run as the drive size is around 1 terabyte. but is there also a way to tell what files or directories are above the limit or can not be deleted Jack ________________________________________ From: Ben Scott [[email protected]] Sent: Thursday, April 23, 2009 5:21 PM To: NT System Admin Issues Subject: Re: path longer than 1023- actually only about 200 or less On Thu, Apr 23, 2009 at 5:44 PM, SMREKAR, JACK <[email protected]> wrote: > K:\Staff And Students\Programming Classes\NHS\Eng086037\web applet > project\Coords\Coords\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java\Coords.java That looks somewhat broken. It's just "Coords.java" repeated over and over again. Is the folder supposed to contain nested copies of itself? Did someone do something stupid? If there's no explanation, you may want to run CHKDSK to make sure the filesystem hasn't got corrupted somehow. On Thu, Apr 23, 2009 at 5:32 PM, SMREKAR, JACK <[email protected]> wrote: > I have some files that my backup is saying are longer than 1024 characters, > but when you put the path into MS Word and do a character count it is only > about 200. Windows is full of maddening path length limitations. Microsoft says NTFS can support path lengths up to 64 KB in length, but it seems like every other component has some arbitrary and inconsistent limit. That includes the Win32 API libraries, shell libraries, Windows Explorer, etc. It's a crock. The symptoms you describe (files show up, but can't be accessed) match this situation. Some possible fixes include: (A1) Map a drive letter into a folder part way into that deep path. Then go into the drive letter and delete/move stuff out, to a shallower path location. For local folder, use SUBST. For network folders, use "NET USE". For example: SUBST Q: "K:\Staff And Students\Programming Classes\NHS\Eng086037\web applet project" Q: CD Q:\Coords\Coords\Coords.java (B2) Rename higher level folder names to shorter names. That makes the overall path length shorter, so you can go deeper. For example: K: REN "Staff and Students" a CD a REN "Programming Classes" b REN NHS c CD c REN Eng086037 d CD d REN "web applet project" e CD e REM ... etc ... you get the idea > 1. Um... what? :) > 2. How can I find those files "DIR /A/S/B" will generate a list of path and file names all the way down. Redirect output to a file. Sort by length. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
