>I want it to do a "FULL" by default. I'm not an AppleScript guru, but I was
>wondering if anyone else has walked this path ahead of me, and has a simple
>"brute force" script I could scam/adapt for my purposes.
I have written a script for a small company that owns an iMac, a
Powerbook, and a PC, networked. The iMac has a zip disk connected.
The script can copy any source target to any destination target,
mount remote disks (automatically detects remote paths), and also
handles the special case of backing up selected items from within a
Virtual PC C-drive. I have it tuned to backup all targets (including
those on the PC, running an atalk file server) to a folder on the
iMac, then copy this folder en masse to the zip. It searches for a
specifically-named zip drive (mon, tue, wed, etc) for daily backup,
and can be made to refuse to run if it can't find it (right now it
reports a possible error with option to try again or continue). It
has a verbose debug mode to search for problems in development.
It is slow, but it works. I'm working out the last couple of quirks,
and adding a report capability to it, hopefully one that can send an
e-mail report. Also to be added is .sit compression. It does no
auto-restore (you have to go search and drag) yet, and also does no
incremental backup yet. But I hope to add these.
It relies on no scripting additions, and is big and long due to
debugging code and comments. It fails to remote mount if it is
running OS9 (OS9 "feature"), but I plan to refine this (no
>Before you respond, consider also that almost any and every "exception" to
>flawless operation will result in a phone call to me, day or night! Any
>"*unexpected*" dialogue boxes, etc; are a "show stopper".
Just an aside, I quit using this phrase. Apparently, a show stopper
is something so -good- that it brings the house down. Anyway, right
now, all errors (every task in the script is error-checked) are
reported to dialog boxes, and they're worded to help me (the
programmer) troubleshoot it, not make things clear to the user, so
this is -not- what your correspondent wants. In a couple of weeks I
should have it finished up (I work on it on-site on weekends).
>This is what makes me think, MAYBE AppleScripting may be the way to go here.
>But I'm not a programmer - just a Mac bigot! ;-) If so, does anyone have a
>basic script I can "borrow" - hints on how to adapt it, if necessary, are
If I supply it free, your support will be limited to what you would
expect, but Applescript is not all that hard. That said, being a Mac
bigot by itself will not help you. The paths set in my backup script
are "hard coded" (for now); you will have to open it up in script
editor, understand what you are doing, change it, and recompile it.
>Please cc any replies to: [EMAIL PROTECTED]
I'm posting back to the list in case anyone else wants it. For me, it
mostly has been how I learned Applescript. It's been fun, but I've
suggested to the company that they buy Retrospect :-), since their
backup needs will be growing. If anybody wants this, send me e-mail,
I will put your name in the basket, and shortly I will spiff it up
and make it available.
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]