[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

1655.0. "MRbackup V2.4" by MTWAIN::MACDONALD (WA1OMM 7.093/145.05/223.58 AX.25) Fri Sep 02 1988 17:32

    I downloaded MRbackup24 and tried it on my machine last night with
    mixed success. First, it has a nice interface and is easy to use,
    until ... until, it comes time to use the RESUME BACKUP option on
    the menu. 
    
    Apparently, resuming a backup means starting over again
    with the disk that was in the drive at the time the backup was
    interrupted. MRbackup reads the MRbackup.context file in S: and
    starts over again with the first file on the disk. However, it does
    not consider that the archive bit is probably already set on that
    first file since it was already backed up just prior to the
    interruption. 
    
    Apparently, when resuming a backup, MRbackup generates an Error 205 
    "File not found" error if the archive bit is set on any of the files 
    (especially the one on line 2 of the .CONTEXT file). The way around 
    that is to check the previously completed disk and see which files 
    were successfully backed up. Then do a PROTECT filename RWED on all 
    those files that were backed up onto the interrupted disk. Sort of a pain,
    particularly if the disk that was interrupted contained all your
    font directories.

    To start from scratch, its probably a good idea to do the following
    sequence of commands:
    
    PROTECT */*/*/*/* RWED
    PROTECT */*/*/* RWED
    PROTECT */*/* RWED
    PROTECT */* RWED
    PROTECT * RWED
    
    This clears the archive bit on all your files (assuming 5 levels
    of directories and subdirectories). I've found that the archive
    bit isn't cleared all the time, and that a direct PROTECT command
    to a specific file is occasionally necessary.

    Future enhancements I would like to see include a CLEAR ARCHIVE
    option for all hard disk files. And, under the Utilities menu, a
    display of the protection for files listed in the file window.
    Also, a write/append feature for the MRbackup.files file that lists
    all the files that are being backed up. An interruption like
    a Guru destroys the file. A simply write/append after filling each
    disk, would insure against such a loss.
    
    Paul
    
    
T.RTitleUserPersonal
Name
DateLines
1655.11.3 PROTECT WJG::GUINEAUTue Sep 06 1988 14:0022
under Workbench 1.3, PROTECT lets you set/clear any flags:

	h - hidden
	s - script
	p - pure
	a - archive
	r - read
	w - write
 	e - execute/extend?
	d - delete

ex: PROTECT file +A  sets the archive bit

Problem though, 1.3 STILL has #? as wildcard "*" and PROTECT doesn't support
wildcards anyway.

ARP does support wildcards, but doesn't know about the other 4 bits.

Comprimise:	make both PROT13 and PROTECT!

John