Maybe it would be better if Retrospect "recognized" the file it
itself had messed with and would silently ignore that particular
error on that particular file.
Just seems fairly logical to me to NOT report that as an error.
D
At 2:18 PM -0500 10/5/00, Fuzzy Gerdes wrote:
Retrospect is
OK, I'm running Retrospect 4.3 on my Mac, and I cannot, for the LIFE
of me, get automated scripts to run.
I guess I might just be confused on how this is "supposed" to work,
so I'll describe what I'm doing, and hopefully someone can tell me
which part of it is wrong. ;-)
[ First, I've
At 9:11 PM -0500 8/20/00, Pam Lefkowitz wrote:
1) what does the log say?
Aboslutely nothing (well, it shows the times that I started the
software, quit the software, etc., but nothing related to the
automated backup)
2) do you have any error messages in modal/non-modal boxes (like backup
OK, the Hardware Compatibility List says "All HP DAT Drives" for both
Mac and Windows, but THEN goes on to enumerate a bunch of HP DAT
Drives.
Is it safe to still say "any HP DAT Drive", or is it just the
enumerated HP DAT Drives that are acceptable?
Secondly, is anyone using Retrospect to
Couldn't you, in theory, just share out "/" as an appletalk/smb share
(platform-dependent), and tell Retrospect to back up that network
share?
Then, in theory, if you had to restore it, you reinstall, share it
out and let it dump it back out on the share. The only potential
problem I could
