Path is too deep

[Guest]

When trying to copy files between two XP Pro systems I receive the following error message:
"Cannot copy <filename>; The path is too deep."

The directory names and structures on both machines are identical. The directory path is 33 characters (on both machines), and the source and destination directories are both six levels deep from the root.

I can copy from the source machine to a four level deep directory on the destination machine. The interesting fact is that this was not happening until I applied some of the most recent Windows updates. I have been backing these directories (and others) for for years using Win2K, and WinXP.

Is anyone aware of changes caused by any WinXP security or functionality updates or upgrades?

Thanks

 

[Richard Urban]

The entire path, including the file name and extension, can be no longer
than 256 characters!

--
Regards:

Richard Urban

aka Crusty (-: Old B@stard

When trying to copy files between two XP Pro systems I receive the following error message:
"Cannot copy <filename>; The path is too deep."

The directory names and structures on both machines are identical. The

directory path is 33 characters (on both machines), and the source and
destination directories are both six levels deep from the root.

I can copy from the source machine to a four level deep directory on the

destination machine. The interesting fact is that this was not happening
until I applied some of the most recent Windows updates. I have been
backing these directories (and others) for for years using Win2K, and WinXP.

 

[Billy]

It is actually 4096 characters by default. You may change this to 65535.
Yes, I know you would like to see a source for this info, Googling at
this time

 

[Billy]

Doesn't appear to be a good idea to exceed the Max_Path, most programs
are not ready to work with it.
95/98/ME, 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,
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/movefile.asp
Another example of exceeding the Max_Path can be found by opening a
command prompt and typing sort /?
then check the description for /Rec.
The more I read the more I realize that I have some misconceptions on
this issue.

 

[Billy]

Humbly stand corrected.
XP will not (by default), allow the path/filename to exceed the 255 or
256, character length.

 

[VManes]

As your MSDN reference notes, Max_Path is 260, and this is a value I've
found by empirical testing. Yuck!

What does the sort command parameter REC have to do with path length? Sort
works upon the contents of files, thus that parameter is a limit on line
(record) length within the file, which of course cannot have a path length
greater than Max_Path.

Val
--
Bringing you BeadWizard Design Software
www.beadwizard.com
***************************
Practice safe eating -- always use condiments.
***************************

Doesn't appear to be a good idea to exceed the Max_Path, most programs
are not ready to work with it.
95/98/ME, 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,
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/movefile.asp
Another example of exceeding the Max_Path can be found by opening a
command prompt and typing sort /?
then check the description for /Rec.
The more I read the more I realize that I have some misconceptions on
this issue.

"

 

[Guest]

Thank you for responding to my post. The important point that your comments seem to miss is
(1) The copy from machine to machine stopped sometime in late December or early January - it worked without problem from XP Beta
(2) The copy was done via explorer, file manager, Power Desk and any other file manager program,

ALSO - I can still do the copy (using explorer for example) from my XP machine to my Win2K server - just not XP machine to XP Machine.

Any other ideas?

 

[Billy]

Possibly try mapping the drive first, then copy to the mapped folder.

Thank you for responding to my post. The important point that your comments seem to miss is
(1) The copy from machine to machine stopped sometime in late

December or early January - it worked without problem from XP Beta

(2) The copy was done via explorer, file manager, Power Desk and any other file manager program,

ALSO - I can still do the copy (using explorer for example) from my XP

machine to my Win2K server - just not XP machine to XP Machine.

 

[jgolden]

I also would like to find an answer to this question. I just starte
having this issue on my Windows XP box yesterday. I can't seem to cop
anything out to any network drive/share or to a unc path. Although
can browse the whole network and copy files from the network to m
machine.

I have resolved to rebuild my machine since I have put over 12 hours o
trying to fix it. I can rebuild it in another 2.

I couldn't figure out what might have changed. I didn't install an
new software. My NIC settings didn't change either. I have found al
kinds of information on the internet about this type of error and th
solutions have ranged widely, none of which have worked for me.

Let me know if anyone else has something to contribute


-
jgolde

 

[legs]

Let me know if anyone else has something to contribute.

I have been trying to track this one down and have found a referenc
that adding a WINS server definition on you IP properties should fi
this. As I do not currently have a WINS server defined, I woul
appreciate hearing if anyone has tried this, and if it fixes th
problem


-
leg