Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)
I am currently managing a small network and have run into a very interesting
problem. My users are very well organized and love long file names. I was
trying to xcopy some folders to the network when xcopy gave me the
insufficient memory error. I tracked this down to the fact when they created
a folder it was not over the 255 limit when mapped starting as the root, but
once you add the //servername to a UNC for copy the folder is outside of that
255 limit. A friend of mine told me I could restrict the max path or ma file
name length in the registry, but I have been unable to track that down.
Please help me out.
Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)
Create the folder on the server, log onto the server, and copy from that folder with xcopy. You need no destination for xcopy if you
copy from it.
cd longna~1
xcopy /s //thatserver/longna~1/*.*
--
Mark L. Ferguson
FAQ for Windows Antispy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm "Christopher C" <Christopher C@discussions.microsoft.com> wrote in message
news:02FA0FEC-EC2D-4FD7-8046-8C2A0CFDFEC0@microsoft.com...
>I am currently managing a small network and have run into a very interesting
> problem. My users are very well organized and love long file names. I was
> trying to xcopy some folders to the network when xcopy gave me the
> insufficient memory error. I tracked this down to the fact when they created
> a folder it was not over the 255 limit when mapped starting as the root, but
> once you add the //servername to a UNC for copy the folder is outside of that
> 255 limit. A friend of mine told me I could restrict the max path or ma file
> name length in the registry, but I have been unable to track that down.
> Please help me out.
Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)
I know several ways to get around this problem. What I am looking for is a
reg change to shorten the allowed File name length.
"Mark L. Ferguson" wrote:
> Create the folder on the server, log onto the server, and copy from that folder with xcopy. You need no destination for xcopy if you
> copy from it.
>
> cd longna~1
> xcopy /s //thatserver/longna~1/*.*
>
> --
> Mark L. Ferguson
> FAQ for Windows Antispy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm > "Christopher C" <Christopher C@discussions.microsoft.com> wrote in message
> news:02FA0FEC-EC2D-4FD7-8046-8C2A0CFDFEC0@microsoft.com...
> >I am currently managing a small network and have run into a very interesting
> > problem. My users are very well organized and love long file names. I was
> > trying to xcopy some folders to the network when xcopy gave me the
> > insufficient memory error. I tracked this down to the fact when they created
> > a folder it was not over the 255 limit when mapped starting as the root, but
> > once you add the //servername to a UNC for copy the folder is outside of that
> > 255 limit. A friend of mine told me I could restrict the max path or ma file
> > name length in the registry, but I have been unable to track that down.
> > Please help me out.
>
>
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.