X-Authentication-Warning: delorie.com: mail set sender to opendos-bounces using -f From: shadow AT shadowgard DOT com To: opendos AT delorie DOT com Date: Mon, 29 Sep 2003 16:44:51 -0700 Subject: Re: confirm before over-write Message-ID: <3F786183.26223.4E97861@localhost> References: <3F74E134 DOT 3996 DOT B901C43 AT localhost> In-reply-to: X-mailer: Pegasus Mail for Windows (v4.02) Reply-To: opendos AT delorie DOT com On 30 Sep 2003 at 1:58, DONALD PEDDER wrote: > > True enough. But that's why my backup routines went > > like this: > > > > Backup to tape > > Verify backups > > And sometimes backups become un-usable even after a successful > verification. People shouldn't have to rely on backups. They are just that > - a back-up, a back-up plan. Plan B. What you resort to when Plan A > doesn't work. That's why they're called "backups". Well, given that a "proper" backup scheme involves daily, weekly, monthly and yearly backups (though the latter two are mostly for archival purposes, not for restoration of the system), you really have to have problems for the backups to be useless. Then again, that sortof thing was overkill for most home systems. > > Alas, since copy is built into command.com, you can't use the batch file > > dodge to "force" the /c. > > I don't understand. Are you saying that "copy ... .... /c" in a batch > file won't work? Why not? Confused. No, I'm saying that since "copy" is in internal function of command.com, you can't use the dodge that we used with the *external* format program. The dodge worked because we could rename FORMAT.COm to something else and create a FORMAT.BAT. Doing that with COPY requires (if you are lucky) using a hex editor to patch COMMAND.COM Somebody posting something about a COPYCMD environment variable. No oidea how (or *if*) it works in DR-dOs. -- Leonard Erickson (aka shadow) shadow at krypton dot rain dot com