XCOPY

In computing, XCOPY is a command used on IBM PC DOS, MS-DOS, IBM OS/2,[1] Microsoft Windows,[2] FreeDOS,[3] ReactOS,[4] and related operating systems for copying multiple files or entire directory trees from one directory to another and for copying files across a network.

Not to be confused with XCOPY (artist).
Developer(s)Microsoft, IBM, DR, Datalight, Novell, Rene Ableidinger, ReactOS Contributors
Initial release1986, 36–37 years ago
Operating systemMS-DOS, PC DOS, MSX-DOS, SISNE plus, OS/2, eComStation, ArcaOS, Windows, DR DOS, ROM-DOS, FreeDOS, ReactOS
TypeCommand
LicenseFreeDOS: GPL
ReactOS: LGPL
Others: Proprietary
Websitedocs.microsoft.com/en-us/windows-server/administration/windows-commands/xcopy Edit this on Wikidata

Overview

XCOPY stands for extended copy,[5] and was created as a more functional file copying utility than the copy command found in earlier operating systems. XCOPY first appeared in DOS 3.2.[6]

While still included in Windows 10, XCOPY has been deprecated in favor of robocopy, a more powerful copy tool, which is now supplied with the Microsoft Windows Server and Desktop operating systems.[7]

DR DOS 6.0[8] and Datalight ROM-DOS[9] include an implementation of the XCOPY command.

The FreeDOS version was developed by Rene Ableidinger and is licensed under the GPL.[10]

J. Edmeades developed the Wine-compatible version that is included in ReactOS. It is licensed under the LGPL.[11]

Compression

Since Windows Server 2019 and Windows 10, a compression option is available in xcopy when copying across a network. With this switch, if the destination computer supports SMB compression and the files being copied are very compressible, there may be significant improvements to performance. The SMB compression adds inline whitespace compression to file transfers. Compression is also available with the robocopy command and Hyper-V Live Migration with SMB.[12][13]

Example

Create a new directory by copying all contents of the existing directory, including any files or subdirectories having the hidden or system attributes and empty directories.

>xcopy e:\existing e:\newcopy /e /i /h

If the pathnames include spaces, they must be enclosed in quotation marks.

>xcopy "D:\Documents and Settings\MY.USERNAME\My Documents\*" "E:\MYBACKUP\My Documents\" /D/E/C/Y

Copy entire drive in to a mapped network drive while ignoring any errors in network restartable mode.

>xcopy *.* z:\Netmirror /E /V /C /F /H /Y /Z  1>out.txt 2>err.txt

Copy a single file without prompt if it is a file or a directory

>cmd /c echo F | xcopy "c:\directory 1\myfile" "c:\directory 2\myfile"

Limitations

XCOPY fails with an "insufficient memory" error when the path plus filename is longer than 254 characters.[14] An option "/J" copies files without buffering;[15] moving very large files without the option (available only after Server 2008R2) can consume all available RAM on a system.

No open files

XCOPY will not copy open files. Any process may open files for exclusive read access by withholding the FILE_SHARE_READ [16]

XCOPY does not support the Windows Volume Shadow Copy service which effectively allows processes to have access to open files, so it is not useful for backing up live operating system volumes.

XCOPY deployment

XCOPY deployment or xcopy installation is a software application's installation into a Microsoft Windows system simply by copying files. The name is derived from the XCOPY command line facility provided by Microsoft operating systems.

In contrast, the installation of a typical Windows application will require a significant number of additional steps before the application is ready to be used. Most of this additional work involves, directly or indirectly, adding or modifying entries in the Windows Registry. Even when an application uses ordinary files for its own data, many common facilities provided by Windows require some type of registration step before they are available to programs. Usually, one or more specialized tools (such as Windows Installer, InnoSetup, or NSIS) are used to help coordinate these relatively complex operations.

See also

References
  1. "JaTomes Help - OS/2 Commands". www.jatomes.com. Archived from the original on 2019-04-14.
  2. Xcopy
  3. "The FreeDOS Project blog: FreeDOS commands quick-reference". freedos-project.blogspot.com. Archived from the original on 2018-07-22.
  4. "Reactos/Base/Applications/Cmdutils/Xcopy at master · reactos/Reactos". GitHub.
  5. "Windows NT File System Files". Microsoft Help and Support. Microsoft. 2006-11-01.
  6. Wolverton, Van (2003). Running MS-DOS Version 6.22 (20th Anniversary Edition), 6th Revised edition. Microsoft Press. ISBN 0-7356-1812-7.
  7. Pietrek, Matt (2007-01-16). "Robocopy built into Vista". Under The Hood (an MSDN blog).
  8. DR DOS 6.0 User Guide Optimisation and Configuration Tips
  9. "Datalight ROM-DOS User's Guide" (PDF). www.datalight.com.
  10. "FreeDOS 1.2 Updates Package - XCopy (FreeDOS Base)". Ibiblio.org. 2007-09-22. Retrieved 2022-09-08.
  11. "Reactos/Reactos". GitHub. 26 November 2021.
  12. Smith, Russell (27 November 2020). "SMB Compression Lowers Bandwidth and Improves Copy Times in Windows Server and Azure". Petri.
  13. Output from xcopy /? in Windows 10 includes "/COMPRESS - Request network compression during file transfer where applicable".
  14. Maciak, Luke (2007-02-05). "Xcopy: Insufficient Memory".
  15. "Technet: Xcopy". 2019-05-01.
  16. CreateFileA function (fileapi.h)

Further reading
  • Cooper, Jim (2001). Special Edition Using MS-DOS 6.22, Third Edition. Que Publishing. ISBN 978-0789725738.
  • Kathy Ivens; Brian Proffit (1993). OS/2 Inside & Out. Osborne McGraw-Hill. ISBN 978-0078818714.
  • John Paul Mueller (2007). Windows Administration at the Command Line for Windows Vista, Windows 2003, Windows XP, and Windows 2000. John Wiley & Sons. ISBN 978-0470165799.
Wikibooks has a book on the topic of: Guide to Windows Commands
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.