Cron the Clock Daemon

Distribution files:

CRON.EXE     Cron - Scheduling program for Windows.
CRON.HLP     Documentation for Cron.
FILE_ID.DIZ  Description In Zip file for BBS operators.
FILE_ID.TXT  Copy of FILE_ID.DIZ, with TXT extension.
KILLWIN.EXE  KillWin - Windows program to close an active window.
KILLWIN.TXT  Documentation for Killwin.
LOGMSG.EXE   LogMsg - DOS program for updating a log file.
LOGMSG.TXT   Documentation for LogMsg.
PRODUCTS.TXT Descriptions and prices of our other products.
README.TXT   This tidbit of information that ties it all together.

Copyright 1994-1996, Software Engineering, Inc.
All rights reserved.


Upgrading from Version 1.7
--------------------------
Cron versions prior to 1.8 kept a working schedule file in the Windows
directory. There are several methods by which you can retrieve your
old schedule file.

1. Run the old version of Cron and select File|Save As to save your
   schedule in a file with a .CRN file extension.

	or

2. Locate the file CRON.TAB in your Windows directory and rename the
   file using your favorite file renaming utility.

	and then...

3. Run the new version of Cron and select File|Open to load your old
   schedule file. Once opened, Cron will remember the file and
   automatically reload it each time it is run.


Revision History
----------------
Version 1.8

o Fixed renegade "Windows shutdown" messages when "Log All Events" was
  active.

o Fixed problems associated with running Windows from a read/only
  network share.

o Removed "Exit Windows To Run" option. The Windows API function
  ExitWindowsExec() has fallen by the wayside. Logic tells you that it
  makes sense. Consider the difficulty of maintaining an OS function
  that exits the OS to execute a task. It's interesting that the
  function ever existed in the first place.

o Elimination of active clock on Cron icon...alas. This was an
  unfortunate side effect of migrating to Microsoft Visual C++. It
  seems the undocumented window message WM_PAINTICON no longer works
  the way it used to. If anyone has any suggestions, send them this
  way. I kind of miss the little guy.

o The name of the Cron schedule file can now be passed on the command
  line.

o The name of the last used Cron schedule file is automatically saved
  in the profile. When Cron is run without command line parameters,
  the last used Cron schedule file is loaded.

o The name of the Cron log file can be configured on the Settings
  dialog.

o The cron schedule file is no longer updated automatically. The user
  must use Save or Save As to save the schedule. Cron will query the
  user to save a modified schedule before New, Open, Exit, etc.

o Switched from Borland Turbo C++ to Microsoft Visual C++ development
  systems. There was nothing wrong with the Borland system. We switched
  in the interest of standardization. Cron was the only product of ours
  in distribution that was developed using Borland so it lost out.
 
o Miscellaneous minor restructuring.

o Documentation updates.

Version 1.7

o History is only maintained in our revision control system up to this
  point. No concise history is available. This was the first good
  public release of the program so the development history prior to
  this version is irrelevant anyway.

Thanks to some of the good folks who have pointed out some of these
problems to us.