Xcopy – “insufficient memory”

Popular copy commad do (for the first look) the same with one difference. It can’t handle copying recursive directories. For resolving this issue, microsoft has released newer version of this tool called Xcopy (eXtended Copy). The new one is present in Windows up to today and helps me in situation, which looks as hopeless (for example when the GUI copy methods fail). It has one serious issue. It raises error cited in post title. It is reported when copied file has absolute path (including the drive letter) longer than 254 characters. Because novadays file systems handles longer path, this factitiously small issue comes to really hard problem.
Solution is, of course, find an alternative tool what will have similar syntax. First shot was xxcopy what behaves similars, not exactly the same way. This one has failings too. Most important of them is fact that it requires license for some important features. Closer info can be obtained from program home site.

Tool what I suggest to all (happy ;-) ) Windows 7 Users and (not) happy users of Windows Vista is Robocopy. It is available for users of those systems as buildin one. Others can obtain it as part of resource kit. This tool, what name is derivied from “Robust File Copy”, is really powerfull during manipulation with huge number of files. Good description of it can be found in Wikipedia.

Comments (1)

Quick Question. Does it keep track/share which files are opened arocss servers? Situation: Two offices, with a Server in Office1 and File Server in Office2. If Employee1 opens FileA at location Office1 at say Time 0. Then Employee2 opens FileA at location Office2 at time +2, will there be a notification that the file is already open? What happens then if Employee1 modifies the file and saves it at time +4, and Employee2 saves the file at time +6?I like the possibilities here because it puts the syncing of files on the backend of the user request, instead of the front and backend. However, accessing/overwriting the same files is not worth the risk. Currently on one system, if someone opens an in-use file we get the So and so already has this file open, open this read only? etc Thanks and I look forward to your comments.Scott

Write a comment