home *** CD-ROM | disk | FTP | other *** search
- ┌───────────────────────────┐
- │ D O N ' T P A N I C ! │
- │ ;-) │
- └───────────────────────────┘
-
- Bugs fixed
- ──────────┘
-
- warpcron: version 2.00ga
- wcrsetup: verison 1.00beta4
- (17 June 1998)
- ──────────────────────────────
-
- warpcron.exe:
- - Fix: display problem: "was on..." displayed wrong sometimes
- - Fix: warpcron crashed when starting an event sometimes or behaved very strange.
- - Fix: warpcron didn't find an event's program sometimes
- - Fix: warpcron displays wrong weekday for a right date sometimes
- - Fix: setting a weekday to false/true didn't show the expected result sometimes
- - Fix: warpcron didn't always recognized a config change
- - Fix: warpcron didn't write alive messages (SignTime) to logfile
- - Fix: timeChanged routine was too sensitive; Warpcron detects a time change if the new time is 5 minutes different from the old time
- - Fix: if Warpcron wants to send the daily logfile, CPU load goes to 100% and sending mail failed
- - Fix: if Warpcron rereads its config a NoOfEvents of 0 results sometimes.
- - Change: Caution! Changed behavior! Warpcron does not change in the program's directory before starting it anymore!
-
- wcrsetup.exe:
- - Fix: some strange behaviour... I think still not perfect,
- but does what it should do here.
- - Fix: compiled with new compiler version; fixed some bugs.
-
-
- warpcron: version 2.00beta3
- wcrsetup: verison 1.00beta3
- (26 January 1998)
- ──────────────────────────────
-
- popup.exe:
- - trap when file given with -f option doesn't exist
-
- wcrsetup:
- - checkbox if event's name dialog was not cleared
- - SpecScreen not initialisied at program start
- - Day-Checkboxes not set correct
- - some other minor bugs and cosmetics
-
- warpcron:
- - nothing worth to say ;-)
-
- warpcron: version 2.00beta2
- wcrsetup: verison 1.00beta1
- (17 January 1998)
- ──────────────────────────────
-
- wcrsetup:
- - misc bugs, but some reported bugs are still in beta2
- don't panic, I will kill 'em as fast as possible.
-
- warpcron:
- - at some machines warpcron scheduled an event many times in one minute.
- Again this was a problem with a different time format.
- I use a much better system to seperate secondes and miliseconds from the time.
- - complete redesign of time calculating functions
- much better code now
- surely removed some old, ugly bugs.
- perhaps some new bugs, but them are are lot easier to locate and kill :-)
- - Logfile etc. in current dir when not configured
- - events didn't start at 00:00
- - events with one time only started several times in a minute
- - when many events should start at the same time, some started events had
- strange errors
- -> pause 100ms between starting events -> max 10 per second
- -> max 600 events per minute
- - RunSemOnly and not a single RunOnDay checked caused a hang at startup
-
- warpcron: version 2.00alpha3
- wcrsetup: verison 1.00alpha4
- (03 January 1998)
- ──────────────────────────────
-
- WarpcronSetup:
- - pushing "next" button on "events advanced" page caused a trap
- - "delete" function now works
- - Convert errors in date/time fields are catched now and a "0"
- is filled in the field
- - many minor bugs fixed
-
- Warpcron:
- - automatic config change detect didn't update the screen
-
-
- XMas Release
- warpcron: version 2.00alpha1
- wcrsetup: verison 1.00alpha2
- (24 December 1997)
- ──────────────────────────────
-
- First test release with new PM setup program!
-
- Warpcron:
- - help screen scrolled up in 25 lines mode
- - problem with 4os2 and starting programs
- - am/pm time formats still had problems with unmissable feature
- - displaying of times/dates in program was not consitent
- - some display bugs
- - StartEventNow: BACKSPACE didn't do anything
- - program hung if no event with a time is present
- - wron starting of cmd's
-
- WcrSetup:
- first test release. Try out with care.
-
-
- V1.96
- - no hiding of cursor anymore
- some editors had problems with it
- - a problem with RunEveryXMon if >1
- - default for editor (tedit.exe)
- - after editing config via key 'c' events were not sorted
- - ConfigChanged didn't always detect a changed config file
- - error with calculation of DoNotRun...
- - some cosmetic bugs
-
- V1.95
- - a config file without any event caused an exception.
-
- V1.94
- - red screen at start
- this bug was involved by version 1.9beta :-(, now hopefully fixed.
-
- V1.93beta
- - when starting with one single event WarpCron hung -> fixed.
- - a small error in the config-read routine fixed.
-
- V1.92beta
- - WarpCron sometimes starts up with a red screen and terminates after that.
- That was a problem with an internal converting routine during reading of
- warpcron.mis . Fixed.
-
- V1.9beta
- - all time routines completely rewritten. They're much smarter now and I don't
- think that there are still bugs in them.
-
- V1.5b3
- - the calculating in RunEveryXMin, RunEveryXDay and RunEveryXMon was buggy.
- Now hopefully fixed.
- - very strange bug in an internal routine: MaxDayOfMonth returns everytime
- 31 and not 28, 29, 30 or 31. Perhaps I was drunken as I write this
- function ;-)
- - WarpCron didn't search the config in the etc anymore... fixed.
- - verification of logfile didn't always work
- - some little internal bugs fixed.
-
- V1.5ß
- - the mode of the screen at start was not always restored
- after end of WarpCron (25 <> 80 lines mode).
- - screen-bug: the word 'today' sometimes occured instead of 'tommorow'
- - bug in calculation of RunEveryXMin
- - StartByKey did not count RunEveryXMin
- - at a reread of the config WarpCron sometimes did not find its warpcron.cfg
- and caused strange errors.
-
-
- V1.47
- - a bug with the config read routine; keywords were recognized after the
- terminator ';' too :-( This caused some strange errors.
- - screen became blank if logfile does not exists anymore.
- Now WarpCron proofs the logfile every time it will write something in the
- logfile.
-
- V1.45ß
- - some screen-painting bugs
-
- V1.42
- - signtime does not work correct
- - sometimes the screen becomes black
- - the boring "waiting for next minute..." is not needed anymore
-
- V1.41ß:
- - calculating of minutes was not perfect
-
- V1.4:
- - events don't start at 00:00
-
- V1.3x:
- - sometimes an event time went >23
- - DATE showed day/month/day, not day/month/year ;-)
- - some programs terminated immediately after starting.
- This was the thing with the wrong directory.
- - RunEveryXMin did not run >24 hours
- now hopefully fixed.
-
-