Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!milton!sumax!halcyon!ralphs
From: halcyon!ralphs@seattleu.edu (Ralph Sims)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: 4dos misfeature?
Message-ID: <H7Rey2w164w@halcyon.uucp>
Date: 6 Mar 91 22:26:16 GMT
References: <1991Mar6.192824.9889@en.ecn.purdue.edu>
Organization: The 23:00 News and Mail Service
Lines: 37

stevew@en.ecn.purdue.edu (Steven L Wootton) writes:

> This could be a bug in 4dos 3.02a, or I could be extraordinarily unlucky,
> or I could just be stupid :-)

[deletions]

> Being the unix user that I am, I executed:

(snicker--that'll teach you to mess around with Mother DOS!).

>   move mssibm.exe mstibm.exe

> which I thought would over-write the old mstibm with a new mstibm.  Didn't
> work out that way.  The directory listing was lost entirely to 4dos, such
> that every directory on my disk became c:\misc\*(&^%&%# with no files.

It probably moved the file to a directory called mstibm.exe which was a
sub-directory off the one you were logged in.

> programs would still run, I crossed my fingers and hit the panic button.
> On reboot, all was perfectly normal.

Scrambled cache?

> I haven't been eager enough to attempt this experiment again, at least not
> until I finish another full backup.  Be wary, I suppose.

Nope, use the move command for what is was intended, not as a replacement
for rename.

4DOS's HELP function works real nice.

--
                    halcyon!ralphs@seattleu.edu
  The 23:00 News and Mail Service - +1 206 292 9048 - Seattle, WA USA
                       +++ A Waffle Iron +++