Re: Major frustrations with "Path is too deep" copy problems...help??
- From: "Rick \"Nutcase\" Rogers" <rick@xxxxxxxx>
- Date: Sat, 15 Oct 2005 22:06:00 -0400
Hi,
Specifically, I was referring to the length of the PATH statement on the
machine making the copy.
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org
<intrepid_dw@xxxxxxxxxxx> wrote in message
news:1129427379.380505.309570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi, Rick, thanks for the assist.
>
> The files being copied reside in a first-level directory on the source
> machine (eg C:\BobsFolder), and are going to a share corresponding to a
> first-level folder (eg to \\Ralph\RalphsShare which is
> C:\RalphsFolder), so I can't fathom name or path lengths are the actual
> problem.
>
> Also, per your reference to the KB article notes, I'm not sure how a
> long PATH variable would affect a network file copy...sorry if I'm
> missing something obvious??
>
> -David
>
.
- Follow-Ups:
- Re: Major frustrations with "Path is too deep" copy problems...help??
- From: intrepid_dw
- Re: Major frustrations with "Path is too deep" copy problems...help??
- References:
- Major frustrations with "Path is too deep" copy problems...help??
- From: intrepid_dw
- Re: Major frustrations with "Path is too deep" copy problems...help??
- From: Rick \"Nutcase\" Rogers
- Re: Major frustrations with "Path is too deep" copy problems...help??
- From: intrepid_dw
- Major frustrations with "Path is too deep" copy problems...help??
- Prev by Date: Re: Way to 'bulk change' one word in name of several folders in parent
- Next by Date: Re: Major frustrations with "Path is too deep" copy problems...help??
- Previous by thread: Re: Major frustrations with "Path is too deep" copy problems...help??
- Next by thread: Re: Major frustrations with "Path is too deep" copy problems...help??
- Index(es):