Could a technological virus in the world's computer systems shake Western civilization to it's core?
Has the federal government already anticipated the problems with a new "emergency government" to be imposed when the trouble hits?
Is there a global cover-up in an attempt to avoid a panic?
These questions and many more are answered in this eye-opening video by Ken Klein. "Millennium Bug and the Year Two Thousand" will awaken you to, and help prepare you for, the bombshell about to burst upon the world.
Or, Contact Don Ewald at
Millennium Madness LLC and arrange for delivery.
What is the Millennium Bug? The Millennium Bug (or Y2K issue) is a general description of the problem caused by software, hardware, and firmware not being able to deal correctly with the change from the year 1999 to 2000. It is not confined to personal computers; it also affects central heating systems, cars with computerized engine management systems, home and business alarms, banking and transportation systems. In fact, the entire Y2K issue is beginning to resemble a matryoshka doll; more levels become apparent as each new level is revealed. All software, either directly or indirectly, obtains its date from the hardware. If the hardware incorrectly reports the date, it is very difficult for the software to have the correct date. If the hardware problem is not rectified then any process involving dates will be unreliable. The Y2K problem does NOT start at midnight on 31 Dec 1999 as many people might think. It starts much earlier. Your financial software will generally want to ‘rollover’ the financial year on or around July 1, 1999, and you will have to have all the bug problems (if any) sorted out by then. In real terms, you will have to have all of your systems verified and the changes implemented, before even that date; it has been suggested that 31 Dec 1998 is the real deadline! How does Y2K affect PC Computers? The Y2K issue will be a problem for any computer operating system, application, or other electronic device that uses a two-digit field for the year, as in 08/22/98. That two-digit date field, a seemingly innocuous programmer's shortcut, is a time bomb, one that will definitely go off unless it is defused. The WRONG way to defuse the Y2K time bomb would be to take the tack that Dilbert the "do-it-yourselfer" might take ... just crank the PC clock ahead to see what happens. Dilbert's "test" might not be able to be "untested", and some of his software licenses may become invalidated, or his system might lock up. The Millennium Bug in PC computer hardware, is caused by an error of logic in the PC's Real Time Clock (RTC). This is a small chip inside your PC that ticks 18.3 times every second, and enables it to maintain the time and date. The chip takes its power from a battery when the PC is switched off, which enables it to keep the date and time even when your PC is not in use. The bug occurs when the RTC rolls over from 1999-2000; it may not roll over the century byte correctly, so 1999 becomes 1900 instead of 2000. Millennium Compliant BIOS If your PC is more than three of years old it is ALMOST CERTAINLY NON-compliant. When PC manufacturers first became aware of the Y2K problem, they started to deal with it by fixing the BIOS of the PC, so that it could detect the bug AFTER it happened, and then fix it. When a manufacturer put this patch into their BIOS, they called it a "Millennium Compliant BIOS", which encouraged users to buy their computer as opposed to someone else's. There is nothing wrong with calling something a "Millennium Compliant BIOS", as long as YOU know, as the user, what that means. It means that the PC is "OK", AS LONG AS YOU TURN IT OFF in 1999 and TURN IT BACK ON in the year 2000! In other words, if you don't use it DURING the millennium rollover, unless you have powered it OFF in 1999 and ON in 2000, first. An extended form of this patch has found its way into some BIOS programs, and this is the method ALMOST ALL Millennium Bug fix software packages use, that you could pay from $150 up to $5,000 a copy for! Using this "fix", as well as "fixing" the RTC at boot-up, the "fixed" BIOS will detect a call to BIOS by an application using the BIOS to retrieve the date, and it will see if the year 1900 is about to be passed back instead of the year 2000. This solution makes LARGE assumption that someone will issue a suitable BIOS call VERY soon after midnight 1999. If they don't, you will be running with a clock that says 1900 until they do. Even if the system does roll-over in real time (ie when the system is turned off then on), there is no guarantee that when the power is turned off again, the century information will be retained. Conversely, some systems will not report the correct date in real time, but if the system is rebooted, the correct century is reported. Most BIOS versions DO support the century byte in RTC memory, but some DO NOT automatically adjust the century byte when the date is read. It is assumed that some external program will issue the 'Set Date' function of the RTC BIOS service to update the century information. Millennium Compliant RTC The Millennium Bug is actually a fault in the RTC (Real Time Clock) chip, not the BIOS. Therefore, a Millennium Compliant RTC is simply a Real Time Clock that does not have the bug, that is, it correctly rolls over from 1999-2000 just as it would from 1998-1999. They DO EXIST but they are RARE. Y2K TEST will tell you if you happen to have one! You could be wondering at this point, "Why don't all the PC manufacturers simply use compliant RTCs???". One reason "could be" that they cost more, and that there are only two suppliers of the RTC world wide. This was in spring of 1998, when the Millennium Bug was well known, and board manufacturers were using non-compliant RTC's BY CHOICE, prefering to fix the bug with a "BIOS fix" for cost reasons. Y2K General Discussion Operating Systems Windows 95/98 Windows 95/98 will correct the year 2000 problem on systems that fail. But Windows 95/98 is based on DOS and DOS itself can have a problem. Therefore, the problem is most likely to affect DOS based applications that must run in dedicated DOS sessions. Windows NT Windows NT 4.0 will correct the year 2000 problem on systems that fail, but only within the NT operating system. If other operating systems are run on the same system (ie multiboot), the problem MAY STILL EXIST. Unix Unix uses drivers that bypass the BIOS, and deal with the RTC chip directly. For this reason, any RTC problem should be looked at VERY SERIOUSLY! The BEST Y2K TEST Software can be had FREE! NOW! The best Y2K TEST software is available, now, FREE, at the NetsaversCenter!
Sutton Design Test Download.This Y2K TEST software runs 12 tests that will POSITIVELY determine whether your PC will fail when it is ON, and whether it will fail if it is OFF. When you KNOW that a PC will NOT FAIL IF it is switched off (and you leave it switched OFF during the 1999-2000 roll-over) then you won't have a problem with THAT PC! The following is a TEST LOG. ****BEGIN SUTTON DESIGNS Y2K TEST**** TEST ONE: Date rollover while system active.. RTC :- 01/01/1900 00:00:02 FAIL BIOS :- 01/01/2000 00:00:02 Pass System:- 01/01/2000 00:00:02 Pass Real Time Clock (RTC) will fail rollover if PC ON Also see test FOUR for same tests with PC off! TEST TWO: Year 2000 Leap Year Test... RTC :- 29/02/2000 00:00:02 Pass BIOS :- 29/02/2000 00:00:02 Pass System:- 29/02/2000 00:00:02 Pass TEST THREE: Year 2001 NON-Leap Year Test... RTC :- 01/03/2001 00:00:02 Pass BIOS :- 01/03/2001 00:00:02 Pass System:- 01/03/2001 00:00:02 Pass TEST FOUR: Date Rollover during reboot... RTC :- 01/01/2000 00:00:45 Pass BIOS :- 01/01/2000 00:00:45 Pass System:- 01/01/2000 00:00:43 Pass ****END SUTTON DESIGNS Y2K TEST**** Y2K Outlook - What to do now? See if all of your application programs will work. This is not going to be simple, and you may want to have a look at our software pages for some considerations.
Sutton Design Y2K Apps.And Do it NOW!!! I have some links here, that you might find useful. Many internet sites are wrong about Y2K, confused about it, or talk about it as if it were the end of the world as we know it! Still others are using the opportunity to GOUGE USERS out of their hard earned money, while others talk about the BIOS clock, when they mean the RTC, and others focus only on mainframes. Here at "Mellinnium Bug: Fact or Fiction", you will get the straight facts. Period.
mil-len-ni-um: 1. a period of one thousand years. 2. a thousandth anniversary. 3. the millennium, the period of a thousand years during which Christ will reign on earth. 4. a period of general righteousness and happiness, esp. in the indefinite future.
Ar-ma-ged-don: 1. In the Bible, the place where the final battle will be fought between the forces of good and evil, to occur at the end of the world. 2. a great and decisive battle.
It is early in the year of our Lord, 1998. Where, geographically on plant earth matters not. I'm simply establishing a time and a place as a reference point for this mini-thesis. Keeping in mind I've never been a Theologian or a Millenarianist, but I am becoming increasingly aware of how often the number one thousand appears in the Bible, especially in prophecy. That observation cited, I don't now, nor have I ever believed God was or is constrained to do his work in even millennia, or any other numbering methods, just to please numerologists. On the other hand, I know myriad logical and devout people are placing emphatic importance on the forthcoming end of the Second Millennium, with Judgement Day and Armageddon (and whatever follows) expected at that time. They find, as well they should, their reasoning in the Bible, and claim confirmation in the variety of Apocrypha available to them. With the knowledge that it is nearly impossible to get even three people to agree on anything, I know these thousands of savants differ greatly, even among themselves, as to the actual end of the millennium. Is it 2000 A.D.? Or is it 2001 A.D.? Or, it the correct dating 3 p.m. Jerusalem local time April 7, 2030 A.D.? All this hinges on the one question; do scholars (or anybody) have the real time and date of the Crucifixion, and the earthquake at the moment of Christ's death, correctly figured against mundane (at best) time recording? How about this. Should it be Good Friday 2030 A.D. as calculated by the lunar calendar? I submit this is no trivial matter in view of what we are attempting to date here. Another twist is if we take the birth of Christ rather than the date of the Crucifixion as the starting point from which to count the millennia, it's obvious at once that neither the naive date of 2000 A.D. or the slightly less naive date of 2001 A.D. can be the bimillenarina date because Jesus was born in Bethlehem on Christmas day 5 B.C.! Nearly every educated person knows this, and almost no one ever thinks about it. I ask you, how could the absolute greatest event in all history, the birth of Jesus Christ, have been misdated by five whole years? Incredible! Or is it? After more than a little fact-finding, I now see it was done quite easily. It's as simple as a sixth century monk making a mistake in his arithmetic. Rumor has it his calculator was broken at the time. Anyway, our present dating (Anno Domini) was not invented and put into use until centuries after Christ was born. And anyone who has ever tried to decipher on a cornerstone a date written in Roman numerals, can surely sympathize with and understand the error of Brother Dionysisus Exiguus. Fact was, in the sixth century there were so few who could read at all that the Brother's mistake went undetected for many years, and by then it was too late to alter, thus correct all the records. So we are stuck with the ludicrous situation that Christ was born five years before Christ was born. For two thousand years the good monk's haphazard miscalculation was seemingly of little importance, but herein it becomes of ultimate focus. If a large number of the so-called Millenarianists had been correct (and in spite of these facts, still think they are), the end of the world would have been on Christmas Day 1995. I wonder how they explain that one? Anyway, please note I didn't say "December 25th". The exact day and and month of Christ's birth are unknown. Matthew notes that Herod was King; Luke states that Augustus was Ceasar, and that Mary and Joseph traveled from Nazareth to Bethelhem to be counted and taxed. This did not happen in Winter - more likely Spring or Fall. Other that this, there is no other data, either Holy Writ or Roman civil records. None. So, there you have it. By the remaining Millenarianist's theories, the Final Judgment (or whatever) can be expected about thirty years from now ....... or later this afternoon. What does this little thesis mean to me? I'm no Bible scholar and would never even attempt to decipher or interpret Revelations. However, I do believe that most of
Grants Pass, OR