 |
 |
 |
 |
 |
 |
 |
 |
|
|||||||||||
|
|
|
|
|
|
|
|
|
#5
05-22-2018, 08:01 AM
|
|||
|
|||
|
This morning, both systems did not display their respective external hard drives on the desktop. The corresponding SD! log files reveal that SD! performed all of the backup scripts, properly, last night.
Does re-saving an SD! copy script alter SD!'s behavior in this manner? Should we re-save our copy scripts with each new SD! update?
__________________
Kurt R. Todoroff 
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| destination HD does not eject after copy | ctucker10 | General | 1 | 05-07-2018 05:46 PM |
| Eject destination on completion is "dim" | Jeff48 | General | 1 | 10-29-2009 10:04 AM |
| Feature Suggestion: Eject on Completion ejects ALL volumes on the Drive | cmarcus | General | 2 | 08-31-2009 08:52 PM |
| SD update - congrats but::: Eject???? | tuni | General | 6 | 08-28-2009 03:13 PM |
| 3 source drives -> 1 dest drive -> 3 destination folders | Leon | General | 1 | 06-04-2007 06:14 PM |
Threaded Mode