Issue with Secure command in Multi-Line Script from Command Line

I'm still working on testing, but I thought you might want to hear what I've gotten so far. I tried running the script from command line. First, I received no errors. Watching the prompts the script ran through the first job. After that though the script seemed to hang. I let it run for about 1 hour, 45 minutes with no further progress before I closed down the DOS box.

I've since run each job through via GUI and all run fine. I'm dealing with about 2GB of data total. The (3) longest jobs, (1) sync and the encrypt & decrypt jobs, took about 15 minutes each. It's possible the script was just taking a long time.

Right now I am testing each job of the script via command line. Once that is done I will run the whole script again to see if it goes through.

Unfortunately, found one more possible bug to report: The Preview function under the Sync tab doesn't seem to work if you use the @Drive@ variable (maybe others?) in the destination string. It will display the top level destination directory, but not the files or the sub-directories under it. (i.e. @drive@\Directory ... Sub-Directory, File, File, File...)

I'll have more info for you when I start testing again tomorrow.

Thanks Again,

Brook

Hey Again,

No problem, if you write it I'll test it. It only seems fair.

Think I'm done with testing now. I tested each job, both in the GUI & by command line. They all ran fine independantly. Then I ran the whole script and unfortunately things broke when I ran it by command line.

I put new files strategically within the directories to keep an eye on progress through the script without having to do a full copy each test. The Sync jobs ran fine, copying or deleting the new files. When it hit the Secure jobs though it stalled out after the first file.

I first tried the original script against an encrypted directory and it decrypted one file in the root directory and then stalled. I then ran a decrypt job alone so the script would 'skip' the decrypt step and move on to the sync. When I ran the script again it got past the decrypt step, synced the files, encrypted one file and then stalled again. It looks like there is a problem with the Secure command when run as part of a script from within the command line.