Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!math.fu-berlin.de!tmpmbx!netmbx!cosheff From: cosheff@netmbx.UUCP (Charles Shefflette) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: 4dos misfeature? Message-ID: <2057@netmbx.UUCP> Date: 7 Mar 91 22:30:29 GMT References: <1991Mar6.192824.9889@en.ecn.purdue.edu> <1828@manta.NOSC.MIL> <9241@star.cs.vu.nl> Organization: netmbx, Berlin, West Germany Lines: 35 Stephen Wooton started a discussion about a possible misfeature with 4dos regarding the operation of the move command. His complaint: Given two files xxxayyy.zzz and xxxbyyy.zzz execute the following command move xxxayyy.zzz xxxbyyy.zzz result: a temporarily trashed disk (until reboot) I'm not exactly sure what happened, however, I do know that I have never experienced that sort of behavior from the 4dos move command. In fact, when I read his post, I created two slightly different files with exactly the names he mentioned and executed exactly the command he gave, with exactly the result he expected, the first file was "moved" to the second, the original contents of the second having gone to never never land. I am at a loss to explain the behavior he mentioned, but I have no doubt that it is not a bug in 4dos. I am somewhat surprised at the mention of PCOPY, though. One of the many reasons I use 4dos was to reduce the number of miscellaneous utility packages I had to keep track of (PCOPY was one of them). I find that 4dos will do virtually everything that PCOPY will do, and what it won't, I probably don't do often enough to bother to remember the PCOPY syntax anyhow :-) No flames intended! Chuck Charles Shefflette, System Engineer cosheff@netmbx.UUCP cosheff@bitcave.UUCP (US Mail) ==================================== Box 9086 USAFSB | Off Switch? WHAT Off Switch??? | APO New York, NY 09742-4824 |===================================