
| Task | complete | problems |
| Clean Compile | 2008/07/08 | pointers, inline, 16 bit asm, data sizes | initialize | 2008/07/13 | GPF after initialize but before program start, must preserve esi and edi |
| Spinning Globe | 2008/07/21 | absolute, shortint <> smallint |
| access violation on activation |
2008/07/24 | incorrect stack handling in CRC routine |
| character display | small font OK, large font numbers OK, letters not |
1) GeoClock MUST be run as administrator
2) GeoClock MUST be run in XP compatability mode
3) GeoClock will not run in Vista64 or XP64
We will issue further reports as more is known.
We assume users will
send comments
about their experience with Vista and GeoClock.
The registration number is printed on the program (#1) diskette, and on the cardboard sleve for the CD. If you have a registered windows version running, click Help, then About, then Info, and the registration number will appear in the list of data in the window.
For newer versions, you should have a GEOCLOCK.KEY file (between 8 and 512 bytes). If you email this to us, we can determine the registration number. Similarly, older versions will have a REGISTER.EXE file (about 3000 bytes) from which we can determine the registration number.
Finally, we can usually determine the registration number from the name and address you used when you first ordered GeoClock.
The clock sync problem is also an NTDVM bug - the windows clock is not synced with the hardware
clock when it returns from a DOS box, a suspend, or a hibernate.
We now have a possible solution to these problems. Download
GEO84D.ZIP
and see if it solves the problem for you. Please report your findings.
Both versions require downloading and running an install program, and entering a registration code sent via e-mail
You can download the your purchased HAM package by following the instructions in the e-mail. It requires downloading and executing one file, retrieving another ZIP file attached to an e-mail, the then unZIPping the file over your installed GeoClock.

If you do not think about it at all, January 1, 2000 seems the obvious date for the first day of the third Millennium. If you think about it just a little, January 1, 2001 seems the right date (since the first AD day of the current BC/AD calendar was January 1, 1 AD). However, a little thinking is often dangerous, and this is one case where it leads to the wrong conclusion.
Until about 1200 years ago, the years were marked by reference to some historical event (5 years after the flood, 2 years after the new king, etc). A monk about 1500 years ago first advocated numbering the years from the birth of Jesus, and this was adopted several hundred years later. Since new years were marked at the beginning of spring, the first date in this new calendar was at the spring equinox (about March 21, 1 AD. In 1582 AD, 10 days were dropped from the calendar (due to errors between the calendar and the sun's apparent position), and New Years Day was changed to January 1. All the years before 1582, including BC, were renumbered so that January 1 was the first day of the year. (The "April Fools" were the people who still celebrated New Years Day on April 1, since the spring equinox had precessed to about April 1 by then.)
It is now well documented that Jesus was not born in 1 AD. There are good cases made for many different years for Jesus's birth, all of which are between 8 BC and 2 BC.
So why should January 1, 1 AD be celebrated? It was: defined about 525 years after the fact; changed about 1582 years after the fact; 3 months earlier than the original first day of 1 AD; evidently a day like any other day; not the birth year of Jesus. Is this really something whose 2000th anniversary ought to have a world wide celebration? NOT!
Since there is no reasonable start date for marking the millennia (or centuries, for that matter), the only rational choice is just to celebrate the zeros. This has been called the odometer method. Regardless of how many miles were on the odometer when you got the car, you celebrate the zeros as they roll by.
The beginning of the second millennium was feared (in the Christian world) because it seemed to be a likely time for the second coming of Christ (1000 years after what? - birth, death, resurrection, ascendance). The beginning of the third millennium is feared for a much more concrete reason (Y2K computer problems) and also on a very specific date (Jan 1, 2000).
I am going to celebrate the new millennium on the evening of December 31, 1999. I am going to celebrate at home, because I am not sure about any software except GeoClock!
"63.251.171.164 blocked by blacklist.mail.ops.worldnet.att.net. 550 - Blocked for Abuse"
Attempts to get this fixed
has resulted in lots of finger pointing between ATT and MyDomain,
and in the meantime I (and many others) am caught in the middle.
Eventually, I will change to a new ISP. In the meantime, I have
rerouted
joe@geoclock.com to a non-AT&T address, and
geoclock@att.net
continues to work (provided your ISP is not on ATT's blacklist).
