XCOPY amd UNC path problem

[Susan]

I have a CMD file that copies my files to a location on
the server. Half way through the backup it says it has
insufficent memory and fails to complete the backup. This
only happens when I use UNC pathways to point to the
server. If I use a mapped drive the script
runs without error. I have 1.2 GB of RAM and none of my
files are that large. Why am I getting this message?

 

[Colon Terminus]

I have a CMD file that copies my files to a location on
the server. Half way through the backup it says it has
insufficent memory and fails to complete the backup. This
only happens when I use UNC pathways to point to the
server. If I use a mapped drive the script
runs without error. I have 1.2 GB of RAM and none of my
files are that large. Why am I getting this message?

Windows 2000 doesn't always handle UNC paths well. You're always better off
using mapped drives. Map the drive in your script when needed and delete it
when you're finished with it. Just for your info, I don't see any
improvement in XP's ability to handle UNC paths.

 

[Ricardo M. Urbano - W2K/NT4 MVP]

Windows 2000 doesn't always handle UNC paths well. You're always better off
using mapped drives. Map the drive in your script when needed and delete it
when you're finished with it. Just for your info, I don't see any
improvement in XP's ability to handle UNC paths.

Interesting, I tend to opt for UNC paths over mapped drives, particular
for paths that are not "standard" mapped drives in the organization.

I've never heard of that error. It may be that the path gets too deep
using the UNC path instead of the mapped drive letter. In that case,
yeah, I would agree that a mapped drive letter is a good "workaround"