Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!delaney@xn.ll.mit.edu
From: delaney@xn.ll.mit.edu (John R. Delaney)
Newsgroups: comp.sys.mac
Subject: Possible RETROSPECT bug
Message-ID: <1478@xn.LL.MIT.EDU>
Date: 17 Jul 89 20:31:19 GMT
Sender: news@XN.LL.MIT.EDU
Lines: 38

Does anyone have an email address for Dantz, the makers of Retrospect. I
would like to report an apparent bug and prefer to do so in electronic
writing, not by telephone or USnail.

For curious Retrospect users:

The problem seems to be with the Browser command SAVE HILITES. It does
produce the appropriate select when used once. But try using it twice with
the same name for the selector and with the second set of hilited files
being a superset of the first. AS one would hope, you get a dialog that
asks if you REALLY want to overwrite the first selector. But it seems as if
the second selector, not the first is discarded.

For very curious Retrospect users:

I was trying to set up a simple custom selector to use for regular backups
of modified files. But to keep the amount of media I was using down, I
decided I would exclude those files I already have well backed-up
otherwise (e.g., the Word application and its associated dictionaries,
standard system folder files, et cetera). And I thought I might want to
increase these exclusions over time. So I created a selector (which I made
standard by adding the appropriate prefix) called "recoverable files" using
a new Browser in which I hilited all the files I did not want backed-up and
applied SAVE HILITES. Then I created another selector (which I also made
standard) called "full backup" which was simply a NOR of "recoverable
files". It worked fine when I then made my backup archive with "full
backup" as the sole selector. But I noticed I had missed a few files I had
not really wanted backed-up. So I made another new Browser, applied
"recoverable files" to get the same files hilited as before, hilited the
ones I had missed, again did SAVE HILITES, and again supplied the name
"recoverable files" (with the appropriate prefix). A dialog popped up
asking me if I was sure I wanted to do that; I did it. Then I tried a
second backup using "full backup" as the sole selector; it backed-up the
files I had tried to exclude. Further experimentation with new Browsers
seemed to prove my change to the "recoverable files" selector was not
taking.

John