#3
|
|||
|
|||
I reversed the times. Then, I subtracted three hours from the two start times (starting at 2040 and 2050, instead of 2340 and 2350), so that I could collect immediate data for you.
Both copy scripts properly ejected the hard drives. I reversed the times, again, such that they were consistent with their original starting time configurations (still adjusted by three hours earlier, plus an additional 20 minutes to account for the time elapsed during the two copy operations.). Again, both copy scripts properly ejected the hard drives. I have reverted the script start times to their original configurations (2340 and 2350). Tomorrow morning, I will examine the results of the two backups. By the way, each time that I attempted to save the second edited script (with a new start time), SD! would quit unexpectedly. This occurred multiple times, and, was/is reproducible. Saving the first edited script did not cause an unexpected quit. Whether I edited script A or script B, first, did not alter the outcome. Saving the second edited script caused SD! to quit unexpectedly. (e.g. Edit script A. Save edited script A. SD! continues to operate. Then, edit script B. Save script B. SD! quit unexpectedly.)
__________________
Kurt R. Todoroff Last edited by Kurt Todoroff; 05-21-2018 at 10:03 PM. |
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 |