#! rnews 38213
Path: van-bc!ubc-cs!ubc-vision!uw-beaver!cornell!rochester!udel!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!ain
From: ain@j.cc.purdue.edu (Patrick White)
Newsgroups: comp.binaries.amiga
Subject: MRBackup  (part 1 of 3)
Keywords: MRBackup, backup, part 1 of 3, untested
Message-ID: <6254@j.cc.purdue.edu>
Date: 26 Jan 88 01:19:56 GMT
Organization: PUCC Land, USA
Lines: 958
Approved: ain@j.cc.purdue.edu  (Pat White)

Program Name:	MRBackup  (part 1 of 3)	
Submitted By:	uiucdcs!amanpt1.ZONE1.COM!mrr@ee.ecn.purdue.edu (Mark Rinfret)
Summary:	A hard disk backup utility.
Poster Boy:  Pat White  (ain@j.cc.purdue.edu)
Untested.

NOTES:
   Won't run on an Amiga with 512K -- GURU's if it is severly short on
memory.


-- Pat White   (co-moderator comp.sources/binaries.amiga)
UUCP: j.cc.purdue.edu!ain  BITNET: PATWHITE@PURCCVM   PHONE: (317) 743-8421
U.S.  Mail:  320 Brown St. apt. 406,    West Lafayette, IN 47906

-------------------------------------------------------------------

#! rnews 15106
Path: van-bc!ubc-cs!ubc-vision!alberta!mnetor!uunet!husc6!linus!raybed2!rayssd!galaxia!amanpt1!mrr
From: mrr@amanpt1.UUCP (Mark Rinfret)
Newsgroups: comp.sys.amiga
Subject: Screen.c source for MRBackup
Keywords: blew,it,again
Message-ID: <407@amanpt1.UUCP>
Date: 6 Feb 88 16:52:04 GMT
Organization: Aquidneck Management Associates
Lines: 998


In my recent posting of MRBackup, I omitted the file Screen.c.  I sincerely
apologize for the omission.  I've posted it here to get it out as quickly
as possible.  By the way - I also found a bug (a typo) in Backup.c.  Look
for a statement beginning with:

	if ( ! CheckExclude( FIB->fib_FileName && ...

There should be a right paren after fib_FileName.  Natch, you'll have to
balance parens in the rest of the statement.  

For those who are interested, MRBackup 2.1 is ready for consumption.  I've
added the ability to test/set the file system archive bits (thanks to 
Steve Drew for the idea).  I've also changed the context saving routine to
use an external file and there's a new command, Resume Backup, which you
may find extremely useful.  Essentially, information about the state of the
backup list is saved to a file (S:MRBackup.context) as each new backup
floppy is started.  Should some non-recoverable error occur during a backup
(power failure, core meltdown, etc.) you can pick up where you left off
with the Resume Backup command.  Clever people will also discover that this
is a nifty way to backup a disjoint set of files (edit s:mrbackup.context,
then use Resume Backup).

I will probably not be posting any more source (since I can't seem to do
it right anyway :-) but it will remain available.  For anyone who wants it,
just mail me $2.00 and I'll send you whatever's "hot":

	Mark R. Rinfret
	348 Indian Avenue
	Portsmouth, RI 02871

Of course, that will include the most recent executable and docs.

Mark

P.S. I haven't gotten a response to my previous query regarding the endless
     retry situation with "Write to bad floppy".  Has anyone checked it out?