Subj : Re: MS XCOPY v 4DOS internal COPY To : CBFalconer From : meirman Date : Sat Feb 02 2002 08:40 pm From: meirman@f3.n342.z1.cereal.mv.com (meirman) Subject: Re: MS XCOPY v 4DOS internal COPY From: meirman In comp.os.msdos.4dos on Sat, 02 Feb 2002 13:37:52 GMT CBFalconer posted: >Outsider wrote: >> >> E. S. (Steve) Fabian wrote: >> > >> ...snipped >> >> > The sole reason I use XCOPY is that it is supposed to be faster due to >> > its own buffering. How does TC32, 4NT, and 4DOS internal COPY speed >> > compare with MS's XCOPY? >> >> As I understand it, xcopy should be faster with larger files (>64K). >> But is xcopy allowed in 4DOS? It probably sounds like a stupid >> question, but when I previously gave an outline for a batch using >> xcopy, someone sent me an email saying it was not a 4DOS solution. >> So now I am a little in doubt. Is there a problem with using xcopy >> in 4DOS? > >Of course there isn't. It is just another external utility. What >it won't do is automatically copy over associated file >descriptions, which is harmless. Smarter utilities may copy >descriptions, IIRC xxcopy does. Another minor nuisance will be >that newly created directories won't be in the jpindex file. But What's that! I never heard of it. >many things don't do that, so you need to rebuild the index >periodically anyhow. Until then a bland "cd newdir" will only How, please? >work from the parent dir, as with COMMAND.COM as the shell. So And it otherwise does more than that?! >you lose nothing. meirman@QQQerols.com If you email me, please let me know whether remove the QQQ or not you are posting the same letter. -- |Fidonet: meirman 1:342/3 | | Origin: The Cereal Port BBS (603)899-3335 199.125.78.133 (1:132/152) --- # Origin: (1:132/152.4) * Origin: Baddog BBS (1:218/903) .