                      Ŀ
                       D O N ' T   P A N I C   ! 
                                ;-)              
                      

History


version 1.98
(12 August 1997)

- Tool MKSEM.EXE added. This little tool doesn't do much, it just
  make a file semaphore so you don't have to write a cmd-file for doing
  this (f.e. with an "echo . >semaphore" in it).
- email support:
  WarpCron sends a email...
  on start of program
  on end of program
  on unnormal exit (trap)
  
  And WarpCron can send you today's logfile via email every day.
  See warpcron.cfg for details.
- 4os2 support:
  if COMSPEC points to 4os2, WarpCron will use it.
  You can use .btm-files just like every .exe-file then.
- you can force WarpCron to run in 25-lines or 50-lines mode with
  LargeScreen true; or
  SmallScreen true;
- key 'w' shows last date/time of config file and its size

version 1.95beta
(5 May 1997)

- WarpCron can check its config for changes automatically.
  Keyword "CheckConfig;" in warpcron.cfg activates this.
- You can edit the config file directly out of WarpCron with
  your prefered editor via key "c" and keyword "Editor <your
  editor>;".
  Be warned. This is quite a fast hack, and it seems that it
  just runs with textmode editor, not with PM.
  If you really need a PM editor.. write me and I will rewrite
  this part.
- WarpCron can start events at startup and/or end.
  Keywords "RunAtStartup" and "RunAtEnd" in an event block.

version 1.94
(18 Apr 1997)

- if StartRelated is true, WarpCron writes the PID of a started
  program to logfile
- kill-events (type "k") and keyword "StartRelated"
  If "StartRelated" is true WarpCron will start every program as
  a child process and can kill that process with an event type "k".
  See example 7 in warpcron.cfg for or keywords "StartRelated" and
  "event type k" in warpcron.cfg.
- "min" true/false in event configuration.
   With "min true" warpcron will start the program of the event
   minimized.


version 1.93beta
(02 Apr 1997)

nothing, just bug fixing.

version 1.92beta
(01 Apr 1997)

nothing, just bug fixing.

Features added by version 1.9beta
(20 mar 1997)

- very much code is completely rewritten.
  I can implement new features much easier now :-). And WarpCron is much
  faster, too.
- ExcludeTimes for an event
- unmissable events
- DenyPath
- SemDelay
- pid-file
- show a event with all parameters (key "e")

Features added by version 1.5b3
(14 feb 1997)

- running an event JUST on semaphore, not on any time.
  Just leave the time-statement away in the event-block.
  See example 6 in warpcron.cfg.

Features added by version 1.5
(08 january 1997)

- cmd's are started with a '/c' after the 'start'-command.
  This means that you don't need an 'exit' in your cmd's anymore.
  CMDs are terminated automatically now.
- News cfg-statement:
  LogFile <path\logfile>
  specifies a special name and path for the logfile.
  Note: normally the normal statement 'LogPath' is sufficient.
- logging can be turned off/on during runtime now
- path to the warpcron.cfg can be given by the start parameter
  '-c<configfile'
  Try 'warpcron ?' for more info.
- WarpCron can be terminated by a semaphore.
  -> statement 'EndSem' in the config.
- an event can be manually started.
  Try key 's'.
  Note: you have 10 second to enter an event number, otherwise WarpCron goes
        back to its work automatically.
- WarpCron changes to the correct program directory of cmd's now, too.

Features added by version 1.47
(09 December 1996)

- WarpCron can start DOS-session now directly
  Write 'ProgramType D;' for fullscreen and 'ProgramType d;' for window
  I don't know if this works with Windoze-programs too... but:
  who care's anyway? ;-)
- exeption handling if logfile does not exists anymore
- help screen
- toggle between short event-infos (as usual) or long infos with
  program, type and parameters

Features added by version 1.45

- WarpCron can read its warpcron.cfg again on runtime when
  - a special semaphore exists (0 byte file)
  - every X hour
  - on key 'r'
- WarpCron searches its warpcron.cfg in the etc-directory which is
  defined by the "set etc=..." statement of OS/2 TCP/IP.
- signtime default is now 24 hours.
- you can write the event name right after the event keyword, for example:
  event MyEvent;
        bla bla;
  end;
- The screen repaints only after an event launch now. This saves a little
  CPU-Time and looks nicer ;-)

Features added by version 1.42
(08 October 1996)

- Textcolor and backcolor
- "next event to schedule"
- new sorting of events

Features added by version 1.41
(30 September 1996)


- Logfile in binkley-style
- signtime

Features added by version 1.4
(25 September 1996)


- calculating the RunEveryX... from TIME/DATE up to the actual time/date.
  For example: you write 'RUNEVERYXDAY 4' and 'DATE 2.03.1994'; then
  WarpCron will calculate the next valid day to run from the 2.03.1994.
  Or: 'RUNEVERYXMIN 120' (two hours) and 'TIME 02:15'.
  You start WarpCron at 12:40, then the event will start at 14:15, 16:15 and
  so on.
- semaphores for an event.
  For example: you write for event 'beam me up' a 'SEMPATH e:\ipc\mail_in.ipc'
  and 'TIME 14:42'.
  Then the event 'beam me up' will start on 14:42 OR when the file
  e:\ipc\mail_in.ipc exists.
- <no name> as name-default
- CTRL+BREAK will not corrupt the logfile
- 'q' quits every time now
- special path for the logfile
- WarpCron changes to 50-lines mode if >18 events
- you can lock an event for writing into the logfile

Features added by version 1.3x
(5 September 1996)


- RunEveryXDays
- RunEveryXMonths
- changes to the program's directory before starting it
- run on a specific date
- weekdays default to true

         

