Recently I tried to run an encrypt from a BAT File (command line mode). I had two problems:
1. After issuing the command line AXCRYPT from within a bat file with other commands following, return from AXCRYPT is IMMEDIATE BEFORE the files are actually encrypted. I can get around this by issuing a SET /P to wait until I respond to it after checking manually to see if encrypt did its job. Should return from the AXCRYPT command not be done until AFTER the encrypt process is complete? If I issue the CALL command instead, specifying AXCRYPT on it, would I then wait until completions?
2. Also during one of my command line encrypts or decrypts from within a .BAT or .CMD file, AxCrypt failed and briefly just displayed a failure message. I figured the message wasn't a concern at the time since I could just forage on with my testing. Now the problems really started. I am encrypting and decryting all files in a directory and all subdirectories. The interactive interface always works. However, after the failure and about 6 hours of debugging, I found a leftover AXX###.tmp file which apparently had information re files. It caused even a XCOPY or COPY of already decrypted files (source) to a new TARGET directory to contain both unencrypted files as desired, but also ancrypted duplicates with .AXX suffix. Evey time I looked at the resulting target it had BOTH the encrypted and decrypted file in in. Obviously, erasing all AXX*.tmp files cleared everyhitng up (except for the mess it made). You might want to be sure all AXX*.tmp files are deleted after ANY error.
3. Is there parameter I can put on the AXCRYPT command to collect detailed bug data?
4. I there a better, more detailed description of command line use. Specifically including when return is made from command and possible return codes to check? Also, some of the switches (parameters) are not self-explanatory.
I have built a pretty complete backup cmd file that periodically backs up all my critical files, annully merges the first-level backup into a master file, and then creates an incremental backup of the master onto CD (at the moment). A correctly working command line AxCrypt is important (especially question 1 above).