Category : Utilities for DOS and Windows Machines
Archive   : CRON26.ZIP
Filename : ERROR.LOG

08/25/91 - Versions 2.24 and 2.25 were writing garbage parameters into the
CRONWK.BAT file. It worked great as long as you only had one
entry in the CRONJR.SCH file. Changed token scanning code and
tested and tested and tested.

08/01/91 - Installation process ( CRON START ) was not working correctly
for DOS versions 4.0 and above. CronJr treated DOS 4.0 and
higher as if it was a version below 3.3. Oops. We plead
stupidity. If you have DOS version 4.0 or above, and have
installed CRONJR, you should recreate the CRONJR.BAT file
by running CRON START with the new version of CRON .

05/20/91 - The 386Max memory manager software together with the Palindrome
tape backup software have problems with nested CALLing of batch
files. The problem occurs when a batch file CALLs a batch
file to EXECUTE a batch file to run the TNA2TAPE.exe program.
This is not a problem inherent to CRONJR, but a problem with
386MAX, Palindrome and DOS. The error can be reproduced without
using CRONJR.

The versions of 386Max and the Palindrome tape backup software
are not known. They may have fixed this problem with later
releases, but in the mean time......

Software Shorts released version 2.24 which allowed parameter
passing from within the CRONJR.SCH file. By not using a
batch file to execute TNA2TAPE.exe in CRONJR.SCH, the total
number batch files in use was reduced by one. This solved the
386MAX / Palindrome problem.