Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!stevew From: stevew@en.ecn.purdue.edu (Steven L Wootton) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: 4dos misfeature? Message-ID: <1991Mar7.065400.24641@en.ecn.purdue.edu> Date: 7 Mar 91 06:54:00 GMT References: <1828@manta.NOSC.MIL> Organization: Purdue University Engineering Computer Network Lines: 43 In article you write: >north@manta.NOSC.MIL (Mark H. North) writes: > >> If the move command is not supposed to be used for this purpose the *polite* >> (read non-RUDE) thing for it to do us warn you of impending disaster not >> trash your disk. Jeesh. > >It would have... from the manual... It says nothing about using it in >place of RENAME. YES IT DOES! >MOVE > >Syntax: MOVE [/PQR] [d:][path]filename... [d:][path]filename > > MOVE first attempts to rename the file(s). If that > fails (the target is on a different drive, or the target > already exists), MOVE will copy the file(s) and then > delete the originals. If MOVE cannot delete the original > (for example, a read-only file), it will display an error > message, but the target file is still created. RIGHT! EXACTLY! It should have worked. I have two files, A and B. I run move A B. Here is what should happen: MOVE attempts to rename A to B. It fails, because B already exists. MOVE then tries to COPY A B MOVE then deletes A B is now all there is, and used to be A This is EXACTLY what I wanted to have happen. This did not happen. 4dos FAILED to do what it was supposed to do. This is my ENTIRE point. I followed the instructions, and the system went berzerk. Steve Wootton stevew@ecn.purdue.edu stevew@pur-ee.uucp stevew%ecn.purdue.edu@purccvm.bitnet