![]() |
1998,1999 by Reptilian Associates. Reproduction of this or any document on this site (http://www.ecis.com/~alizard) for non-commercial use is permitted as long as this notice is included and a pointer to this site is included. To reproduce this document for commercial or governmental distribution, whether for print or a for-profit Web site, request permission from alizard@ecis.com |
| image use by permission of Namebase |
note: page tracking moved to new y2k page
|
This page is primarily for historical / archival purposes, though it will come in handy if you've still got Y2K computer trouble or your equipment (including embedded systems, mainframes, medical equipment suddenly develops it. This assumes the compliance databases I linked to are still up. It will almost certainly never be updated.
For my current opinions on the subject of survival and disaster preparation, go to my current y2k page.
This is probably the last 1999 update to my Y2K page. To all of you who've been using it, good luck for the rollover, and may your Y2K experience be a safe one.
Overview To find out how to
prepare, keep reading, your
life may depend on you're getting the points I'm making here. If you have
your own computer, getting it fixed is your responsibility. If you
own a business that depends on computers, you will fix whatever
problems you have or come 1/1/2000, you are out of business. On the other
hand, don't put all your resources into preparing for Y2K unless
it's become obvious that you have no other choice. You may have the good
fortune to live in an almost unaffected area, and you might want to be
able to pursue your normal life should it be possible to do so. Hedge your
bet, but don't use this as an excuse not to prepare. Also remember
that the sooner you prepare, the cheaper it will be to buy what you need
to get ready.
If you don't believe that dates have
the magical power to create computer disaster that endangers your health
and safety, click here and click the
links.
I've gotten reports of difficulties in printing this page given the
text and background color combination. While the text and background colors were
recently changed to make reading easier, I think you'll still find the "how to
print" information that follows helpful.
I'm not satisfied with the current page appearance, but I'll fix it properly when
time allows.
To print this page without having to worry about page color, go to the File
Menu, use
Save As, specify text file in the pull down menu, then make sure you've
saved it with a text extension, e.g. y2k.txt . Then open the text file
from any word processor or text editor, read it / print it as usual.
This works for any Web page with strange color combinations. However, if
your friend you were printing out for has a personal computer, you're
best off simply saving it as usual to floppy as a Web page... (.htm
extension) Warning, my page is 51 text pages at last count. That's why
downloading this page took so long. The intent here was to make a primer
on Y2K one could read on the Web or save to disk as a single file.
NEW!!! (9/12/1999) Recent "Horn" report on 43 designated "high impact programs" -- House y2k
Committee 37 of 43 not ready. Most have December 1999 as "expected" completion date. NOT ready list includes Air Traffic Control system, Medicare and Medicaid, welfare programs, and so on. OH, and disaster relief (FEMA) as well.
MOST are administered by the states and that is where the problems *seem* to
be.
Some reassuring news about our nuclear deterrent from Federal Computer Weekly. Sample quotes: "did not review the software code for the microprocessor in the W88 to determine Y2K compliance, but rather he relied on his memory of what the code contained". . . "two weeks testing and verifying the warhead for Year 2000 problems but did not produce any documentation outlining his discussions or the documents, diagrams and software he examined" The W88 is a nuclear warhead.
(8/24/1999)The US Navy has prepared an Excel spreadsheet which gives its evaluations of electric power, utility, water, sewer Y2K readiness. You can find the explanation page here. You can download the spreadsheet directly from here. This is the latest revision. Whether the good news in it is real or publicity spin you'll have to decide for yourself. One argument for its reflecting actual research is that there are several 2 - 3 (probable to likely Y2K failure) ratings for US cities left in it. If your city comes up OK, I recommend preparing anyway, there might be only one major error in it, and that might be in the description of your home town. Also note that the "explanation" is more cheerful than the spreadsheet content. It may be that the explanation is intended to be as far as the average reader or newsperson will go, with the bad news left for people willing to dig for it. Excel or Excel-compatible spreadsheet or viewer is required to read the spreadsheet file. The viewer is available somewhere on the Microsoft site.
NEW!(written 8/5/1999) The bad news keeps right on coming. Here's an article that scares the hell out of me. Here's a quote: "Of the 15 large corporations she is personally consulting on Y2K risk management issues, only one is currently Y2K-ready. (Due to confidentiality agreements, she could not divulge company names.)" The woman has a high-level position with PriceWaterhouseCoopers. This Big 5 accounting firm / consultancy not only tabulates the votes for the Emmys, I know of my own personal knowledge that they do foriegn government Y2K-related work, and they are working with quite a few major corporations all over the world on this. See this VAR Business article here.
GAO: Medical bills, records may encounter Y2K problems
"Manufacturers are urging GPS receiver owners to check whether their devices can handle the upcoming WNRO. In many cases, potential problems can be repaired with a simple upgrade. A comprehensive list of GPS manufacturers, along with their WNRO updates, is available on the Internet at this US Navy GPS Info site. Information about a GPS receiver's WNRO fitness also may be obtained by calling the federal government's Y2K hot line, 888-872-4925"
The infamous Wired Magazine article is finally out. A bit
sensationalist in tone, but not bad at all. Find it here.
The latest comment (as of 11/12/1998) on Y2K from ABC News - Too
Late to Squash Y2K?. The news isn't good.
Here
is a chart from the California Office of Emergency Services of potential
Y2K impacts for the purpose of emergency service Y2K planning.
Here's what the National Guard says about Y2K impact
Here's a US
Army discussion of Y2K impact.
As of June 17, 1999, it appears not all problems are solved. A
sewage plant in Van Nuys tried some Y2K testing. Here's
what happened.
This is an ongoing Y2K discussion hosted by the
Naval War College. I found it unsettling. Take a careful look at
Table 1 on this page. To see finished drafts, go
to Decision Support and look for the Y2k project link in the
right frame. Some of the people Dr. Barnett will be presenting this
information to include the DoDIIS Worldwide Conference (25 May),
Directorate of Intelligence Operations (26 May), N3/5, OPNAV (26 May),
and U.S. Central Command (23 June). The most unsettling thing about
this site is that the author has told me in private e-mail that he
believes that the "new economy" will pull the US through Y2K trouble and
his concerns as expressed on the site are for foriegn countries.
The reason I'm pretty much certain that the minimum impact of
Y2K will be a major recession is that not only are there unsettling
rumors that at least a few Fortune 500 companies will disappear due to
mainframe software problems, but what's needed to insure that the
smallest businesses remediate isn't going on. As is said elsewhere on
this page, if your Wintel computer isn't remediated for Y2K and running
any flavor of Windows, unless the fixes are installed, your hardware and
software are broken.
Not to say that they'll stop operating completely,
we might all be better off if they did. If it breaks completely, people will figure
out that it needs to be fixed. Just imagine the effects of
little Y2K date handling errors in the hardware, operating system, software, and
spreadsheet / database worksheets affecting date entries and date-based computation
(e.g. 10 net 30 discounts) on your accounting software, your
spreadsheets, your databases, and your EDI hookups with your customers
and vendors. Multiply by a few million. Remember that no matter how many
mainframes the big companies are using, the data generally comes
ultimately from PCs... noncompliant PCs. Opinion surveys have uniformly
found that non-IT businesses that have heard of Y2K are planning to fix
on failure, believe that Y2K is a scam perpetrated by unscrupulous
software vendor to sell unneeded and unwanted products. Saying "leave
them to Darwin" isn't an option, this kind of IQ test will wipe out
businesses by the hundreds of thousands, including remediated businesses
depending on their customer / vendor unfixed machines. In other words,
we can't afford to lose large numbers of businesses even if they are run
by idiots. Even if the
average small businessperson knew there was a problem, most don't know
what fixes are needed, where to get them, how to install them, and how
to deal with installation problems. Latest survey by Wells Fargo Bank says that 60% of small
businesses have done something about preparation, 20% definitely don't
plan on it.
For small business help, click here.
The root of this problem is largely Microsoft. The problem with an
effective monopoly is that if the monopolist carries the same mistakes
across its entire product line, those mistakes are everybody's
business. Fixing their part of the problem isn't beyond either their
technical or financial capabilities. If they'd create a
free CDROM with auto-installing fixes for all versions of their major
products (and the IBM BIOS/RTC software patch) and distribute to every single one of their registered
customers, put in a date scanner for the most common business
package data files (I'm sure they can buy a company
somewhere who's got one), throw in a product scanning filenames across a
product compliance database (yes, buy another company or license the
product) with a toll-free number and e-mail for anybody who got missed
in conjunction with a massive publicity campaign to make sure people
would install this fix as soon as they got it, and toll-free technical
support for people who needed help with the fixes.
This would probably take
care of 2/3 or more of this Wintel problem, and effectively, nearly all as
their competitors followed suit. If this sounds familiar, think of the
last auto manufacturer factory recall. Same problem, same fix. This is
merely a whole lot cheaper, under $1 per customer and the physical
installation done by the end user. The MS
problem doesn't put that many human lives at risk, but our economy is on
the line. I think a 1 CDROM PC Y2K fix is within the capabilities of the
average PC user if it doesn't require much more than "stick it in" or
"stick it in, follow the instructions on dropping to DOS and typing
INSTALL D:" I doubt that much more effort or knowledge of PCs can be
expected from the majority of people who use their boxes at the
household appliance level.
If this sounds like a "silver bullet" for Y2K, note that it would
only work for Microsoft products running on Wintel box PCs and
non-Wintel boxes running NT, it won't solve mainframe problems, and it
most certainly will not do anything about embedded processors. It also
won't fix any computer with an Award BIOS v4.51. (only replacing the
BIOS, motherboard, or computer will do that) However, it would fix the
bulk of PC problems and make fixing the rest of PC problems much easier for
people who are not themselves IT professionals. Not a silver bullet,
just a collection of smart missiles designed to aim themselves at the
collection of easy Y2K targets created by MS. It would be the greatest
contribution to the US that any single company could possibly make in
terms of Y2K readiness.
The CDROM is finally out. (in advance of detailed examination) There's no BIOS or RTC fix, no date
scanner, and there's no
associated publicity I know of, but even this is very good news.
If one of these Windows PCs is yours, click here.
The news that is most
frightening is that it is now certain that portions of the US will suffer
prolonged power outages (weeks or months). This can be
deduced from this information:
Here's some other information which may help you decide if Y2K trouble
is really likely:
I'll improve the above links to make it unnecessary to poke around within to discover the
information I'm citing sometime soon. I'd also like to point out that
the Y2K situation at the places that are cited as trouble spots are even
worse than described. Major power plants require a significant amount of
power from the electric grid to restart. There is no assurance that
this power will be available. Worst is that fixing major power plants
for Y2K takes months even when ample power is available. This is
work that can not be done in the dark by flashlight. If you
manage to find out that your local power company isn't fixing its
problems, you might want to consider moving while it's still time. Most
places who get their power from IOUs (Investor Owned Utilities, i.e.
most major power companies) will probably be OK most of the
time. Don't bet your life on this if you can avoid it.
Here is
an analysis from the UK government on the impact different infrastructure
failiures on society. Explanation of terms (for US users) NHS - National
Health Service (medicine is a government program there, as it is in most
civilized countries), A "county" in the UK is closer in population
to a state in the US, interpret "region" as meaning several "counties".
"New Deal" is the UK "welfare reform" program. Magistrates and Crown
means the UK criminal justice system.
One basic presentation of the Y2K problem that's good for people
totally new to it is at this page.
This is as much space as I intend to devote to convincing you that there
is a problem. People all over the world will die
of this, and not getting the message in time will be a leading cause of
death. It's called Darwinian selection, perhaps this will comfort you if
you decided not to prepare and your number comes up.
Don't figure on being
able to get the computers you need to run your business fixed after 1/1/2000,
anyone you would want to hire to get the problem fixed will probably be
working for someone else with a lot more money than you've got. If your
business depends on computers, get to work on getting the problem fixed
now, while you can still get expensive outside help. Wait a few
months from now and expensive becomes astronomical, or worse, unavailable.
Special Disclaimer:
While I take no responsibility for the results of following any piece of
advice given on this site (your conditions may not be the ones I gave the
advice to cover), I really disclaim the results of taking any piece
of advice in this page. Too many unknowns, what works perfectly for one
user may blow up in your face. Also, what's here is primarily my opinion.
though there are many facts either here or via links. However, I am certain
that whether you use a computer in business or not, if you don't deal with
the probable consequences of the computer-related events of 1/1/2000, they
will deal with you. This page is intended to give you an overview
of what 1/1/2000 will mean to you, your business, your job and practical
advice on what to do about it. This site has plenty of links to places
where you can get more detail and I suggest that you use them.
If you see any obvious glitches on my site, ranging from factual
errors to html problems (e.g. links extending across several lines of
text) please let me know.
A number of people preparing for Y2K
trouble do not want to share their discussions with the public. There
are a number of governments who don't agree that you should have this
right. Learn about a threat to your privacy and your ability to do
business on the Internet and what you can do about it here
Definitions: Y2K
means year-2K (K as in 1000, not 1024) = the year 2000 computer problem.
You'll see the acronym SME in a lot of stories / articles / literature
dealing with Y2K. It means Small / Medium sized Enterprises. Y2K
itself means Year 2000. COTS means Common Off-The-Shelf software.
This means items most people buy over the counter at local computer
stores, usually from major manufacturers. IOU means Investor
Owned Utilities, the large corporate organizations that supply most of
the country's power. Embedded computer means the computers one
finds inside electronic devices that people don't think of as computers,
these computers range anywhere from single chip microprocessors (like
the one inside your VCR) to repackaged personal computers often found in
automotive electronic test equipment. IT means Information
Technology. RTC means Real-Time Clock, the part of a
computer that does internal timekeeping. The CMOS is where the Wintel
RTC stores its time when the computer is turned off. BIOS means
Basic Input / Output System (I think), it's relevant to Wintel platforms
only, it basically tells your computer what it's supposed to be doing at
the most basic level; where the disk drive is, what to do with memory,
etc. If it doesn't work, neither does your computer. (including ones running
PC type Unix flavors) Wintel encompasses what we used to call DOS
clones; ones running 80x86 compatible (including Pentium / Pentium II)
microprocessors originally developed by Intel
Corporation which mostly run DOS / Windows 3.x / Windows 9x (Windows 95,98)
operating systems developed by Microsoft
Corporation and Wintel-platform flavors of Unix(tm). Nearly all Y2K related
hardware-specific personal computer problems relate specifically to the
Wintel platform. csy2k is shorthand for the comp.software.year-2000
newsgroup, where many critical discussions of Y2K problems take place,
as well as much nonsense.
I also recommend you
read through the entire site, painful as the process may be, there are
limits as to what I can do with a table of contents, a search engine just
doesn't make sense here, and the information you need may not be where
either of us would expect it, or more likely, what you need to know isn't
what you expected when you first showed up on this page. Note that even
if you're certain you and your business are year-2000 ready, it doesn't look like society
as a whole is going to be, read the personal
preparation section carefully. Most of what's recommended for
purchase are things every household should have anyway for more common
disasters like earthquakes, tornados, hurricanes, floods, and longer
than usual non-Y2K power outages.
You might want to save this page to disk and read it at your leisure, especially
if you're at work right now.
Also note that if you
consider this page a reliable source of information, visit it once in a
while, the information I present here will be changed continuously as I
get more up-to-date and accurate information. This means what I think is
true today may not be what I believe tomorrow, if I find something that's
here isn't so, I'll change it as quickly as I can. If you know things I
don't, please catch me in e-mail. If you have conspicuously good or bad
experiences with resources I point you at, please let me know.
I am planning a
book on the Year-2000 problem which will be based largely on what you
see here. I've got much more information than I'm presenting on this
page, it
isn't here because this page is intended to simply provide an overview of the
problem and what to do about it. I have a lot more to say and would like
to say it to people who don't happen to find this Web page. I am looking for a literary agent to
represent me in marketing this book. If you know of a good agent, (I mean
one that you have personally worked with or know someone who is
happy with her/his agent.) please catch me in e-mail quickly.Table of Contents
NEW
Those of you who want to load Y2K compliant office software should look into the Corel products, e.g. Word Perfect, their office suites, etc. A quick summary: Anything version 8 or later appears to be complaint. Period. Since Version 8 software is still available, often at fairly massive discounts (it's vintage 1997 or so) you might want to look into it. In general, their export/import to / from MS Office is pretty good. Their office suite has the usual word processor / spreadsheet / database / presentation manager stuff in it.
Here's a quote: "A new government report raises questions about
whether health care providers, from doctors to hospitals, are prepared
to head off problems with medical bills and records that could be
caused by the Y2K computer bug." The article suggests even more bad medical news.
Blackout
Inside
Texaco, mostly a discussion of embedded in one of the oil industry
companies.
Y2K
If you'd like to be informed when the book will comes out and where to get it, click here.
The latest on the book is that... the book isn't happening, so my completed
chapters and outline is here,
hopefully some of you will find it of interest. One of the complete chapters is on
providing yourself with power / heat / light in the absence of a power
grid.
In discussing the problem,
I'm consciously taking a moderate approach. Some people are saying that
1/1/2000 will be just another day. Those people haven't bothered to research
the problem. Others say that it will be the end of technological civilization.
I believe neither, though if you're in an area that's totally unprepared,
it will certainly look like the end of the world. For the USA and
the rest of the developed world, I think that for most people, the truth
is somewhere in between and that's what this page is intended to help you
sort out. Anything you regard as unduly paranoid is largely based on my
analysis of discussion from the programmers who are trying to undo the
effects of the year 2000 computer problem, who know it can't all
be fixed in time and are hoping the most critical parts can be. . . but
who are also telling us to prepare for serious disruptions.
If this page makes
sense to you, let your friends, family, and business associates know about
it. The more people who know about this, the safer we all are.
Also, if you believe
me, contact your elected officials and tell them that they either stop
playing political games with Year 2000 preparation or you will vote for
replacements that will. In the US, the Clinton
Administration has provided a lack of leadership for solving Y2K problems
either in or out of government. In an example of bi-partisan Y2K idiocy,
read about how GOP leadership is trying to blame Gore for national y2k
problems while they
cut $2.5 billion dollars from government y2k funding!
A quick summary of the
year 2000 problem is simply that a lot of programmers and engineers for
various reasons set the calendar functions of their computer programs or
computer systems (anything from a microwave on up to the mainframes that
run major businesses) to handle 2 digits instead of 4. As a result, instead
of a computer program knowing that the date is 1/1/2000, on 1/1/2000 one
might find that the program thinks it's 1/1/1900, 1/1/1980, or the computer
has decided that the problem is too much to deal with and locks up. This
was done to save storage space back when storage space was very
expensive. It's only been in the last few years that this ceased to be
true. Unfortunately, management failed to heed programmer warnings that
these programs would break when they hit 2000, figuring that the code
would have been replaced by then. So the code didn't get fixed as part
of routine maintenance when it should have been, and as a result of in
some cases, over 20 years of putting the problem off, it all suddenly
has to be fixed at once. Not all of it can or will be fixed.
Given
that just about every single function in civilization is dependent on computers,
this program affects everyone. Even those who don't have a personal
computer are in trouble if some or all of what they use in everyday life,
their power, telephone, car, local grocery stores, pharmacies, hospitals,
banks, mail, Social Security, elevators, traffic lights, etc. go down at
once. Y2K preparation is for everybody. By the way, 1/1/2000 isn't
the only projected failure date, especially for mainframes, and there are
problems with date-related data corruption that have already happened.
You'll be seeing more and more of these in the news during 1999. (And
2000.) Most of these early failures can be fixed easily enough so that
nobody outside the company knows it was broken. In some cases, nobody
knows there's a problem until, for instance, welfare checks or food
stamps are issued incorrectly. (that happened in 2 states within the last
couple of weeks, apparently due to program code being entered
incorrectly during Y2K remediation - 4/20/1999)
Here's the first
article that addressed the Y2K problem written back in 1984 for
Computerworld. If his advice had been taken, we wouldn't be in this mess
at the mainframe level and the practices he recommends probably would
have carried down to the PC level and ... there would be no Y2K problem.
The mass media has been
of little use so far in helping the public understand this problem, largely
because the journalists don't understand it themselves and the people in
power who do know what's going on are trying to prevent public panic or
worse, the public blaming them for the trouble we are about to be
in. The only professions which can be expected to benefit from this are
computer specialists who can fix Y2K problems and mainly, the legal profession.
If you have a business,
your choices are to be able to demonstrate due diligence at Y2K compliance
or face massive lawsuits from your customers or vendors which you'll have
no chance of winning. You may get sued anyway even if you are ready but
the courts will be so overloaded during 2000 that cases that are obviously
without merit because the people being sued made an honest effort to remediate
will probably be summarily dismissed. If you get a questionaire from a
customer about your year 2000 readiness, do answer it honestly.
If that questionnaire highlights problem areas you don't like to talk about,
tell the truth anyway and tell them you're working on the problem. Companies
that don't respond to these questionnaires from larger companies or worse,
get caught lying are likely to be rudely surprised to find they disappear
from "approved vendor lists". Better to admit your problem and get it fixed
than lose your major customers. Also, you really need to know what your
suppliers are doing about Y2K.
The first Y2K related lawsuit has already been judged. A company's
2 year old POS terminals ALL crashed every time someone put in a credit
card with a 2000 date. Here
is the story. The company that made that Y2K mistake will pay.
The only way that
the first working day of the year 2000 will be anything but a disaster
will be if everyone who's responsible for computer equipment in
whatever form, pretty much including anything with a date you can set in
it... possibly including your car, your elevator, medical equipment, security
installations, your cash register / POS terminal, make damned well
certain that the equipment is Y2K ready as far in advance as possible.
This is too important for "let George do it". If we don't hang together
on this, we've had it.
If you're a PC tech or
consultant, most of what I think you'll need to know to prepare PCs for
Y2K is linked to here somewhere. If you see anything I've left out, please
let me know. The Wintel Y2K compliance section is a work in progress based
on the incomplete / unsatisfactory information I've spent hours every day
trying to gather.
Assuming that most of
us do our parts, what I foresee for the first days of 2000 are major problems
and the occasional disaster. In the areas where power stays up, figure
on some bank (the ones FDIC thought were compliant and weren't)
and store closures ranging from a few days to
permanent, companies from the Fortune 500 down to one-person businesses
will go down for a few months, the companies who combine being worst prepared
and in the worst financial positions won't be coming back. Even if your
company survives 1/1/2000, your job may not. When I say unplanned
bank closures, I mean take out some cash well in advance of 12/31/1999;
runs on the banks are rather likely.
Here is an analysis of the Fortune 500 10-Q (annual
report) statements from a Y2K perspective. For the full reports, go to
"Fortune 500 Y2K
progress from 10K reports". This includes links to the actual 10Q statements
of the companies listed. In some ways, this is the most
frightening information to come to light with respect to probable Y2K
trouble.
Many companies with substantial
Y2K problems will handle them via triage; they'll only try to fix their
newest facilities and/or the ones which make the most profitable products.
Many companies who are suppliers to places like Fortune 500 companies and
the health industry are going to find out that they've been crossed off
vendor lists because their Y2K compliance isn't satisfactory. As one hospital
information technology manager put it,"We are going to be around for 2000.
Some of our vendors won't be." A fair number of banks will be absorbed
by larger banks during mid-late 1999 under orders from the FDIC for the
same reason. Try to find out what level of Y2K compliance your company
has and if it's obvious they aren't going to be ready, or are saying "We'll
fix it if it breaks" or "[government/microsoft/etc.] will fix it for us"
start looking for a job somewhere else that does plan to be ready for 2000
as soon as you're sure.
I expect major
disruptions, but disasters in the US, Canada, Australia and some of the European
countries farthest ahead on Y2K will be relatively rare. While power, phones,
water, and the food chain may go down simultaneouly in some areas,
what I'm figuring is that one or two of these categories will go down in
any specific area for not more than a few days. If power stays up, important
services can be restored. I'm expecting a major recession as a result of
our problems and those of the rest of the world.
This is what the CIA
is telling it's people about 1/1/2000: Sounds like the CIA concurs
with my personal assessment of Jan 1, 2000, but didn't think through their
advice to employees completely. If you're one of the people who got the
CIA recommendations in inter-office mail, read this site carefully. Then
tell your co-workers to read this page. Should you happen to be employed
by the CIA, if the CIA has revised their recommendations, I'd be very
much interested in being informed of this. If the CIA or any
governmental organization or business would like to
print this as hard copy for their organizational staff, let me know and we can discuss terms.
White House Fears Y2K Panic
White
House officials fear federal agencies that advise employees to begin personal Y2K
preparations could
unduly alarm the public.
Read the full story here
To get early indications of how bad things are likely to get, watch
your newspapers and TV around the dates in this post by D. Scott
Secor, one of the comp.software.year-2000 experts.
My basic advice is to
do everything you can to get ready and stop worrying. Not that there's
nothing to worry about, but all worry can do for you is to get you to take
action. Once you've done all you can, there's no point in further concern.
Get ready, and then enjoy New Years Eve, 1999. Seriously. This is the best
chance for a millenium party we'll have for the next thousand years. While
the millenium will officially start on 1/1/2001, those parties will be
relatively subdued.
For a look at grocery
stores and Y2k by a store manager of a major chain, go to grocery
stores and y2k. Here's a quote from the article: Here are another couple of infrastructure posts, food distributor and Gas
distribution at major-chain owned gas station. The good news about
gas distribution is that independent gas stations are generally older
technology, i.e., they should be able to sell gasoline, on a cash basis
at least if power stays on.
This section is written
on the assumption that 1/1/2000 will be a difficult experience that can
be prepared for affordably, not the end of the world or at least of technological
civilization. It assumes that major services which are interrupted around
you will be either be restored within a few days or a week or two or that
your area will be receiving disaster relief from areas less affected within
a few weeks at worst.
Power may be down, your
phone may be down, the food chain might go down, emergency services might
go down temporarily. Get some of your money out of the bank well in advance,
or at the very least get hard copy records (account statements) close to
the end of Dec. 1999. Pay bills and get written receipts.
By the way, according
to FEMA, anyone requiring any type of life support that uses electricity
should register with your local Emergency Management office -- regardless
of possible circumstances, presumably to make your power the first priority
for restoration in case of a power outage. If it were my life, I'd arrange
for a solar panel and/or generator and/or large battery pack and/or a hospital stay for New
Year's Eve 2000. Let's hope you won't need any of what I recommend here,
but while we know when 1/1/2000 is coming, there is a disaster in your
future no matter where you live, so if you get these items and the power
stays on, don't be too disappointed. You'll find a use for this stuff sooner
or later. At worst, you can eat it, or donate it to your local food bank.
(and take a tax writeoff)
I think the most likely
serious problem for most people is a few days of power outage, possibly
taking down the water supply, and phones followed by months of occasional
brownouts and blackouts.The hardest hit areas are likely to be totally
off the grid for weeks or even a couple of months or so. Think in terms
of preparing for a 1-2 month camping trip in an area where power probably
won't be available. If you've got an RV, you've probably got everything
or just about everything I'm suggesting except food and extra water.
However, if the power
goes down New Year's Eve 1999, don't panic. There's a good chance that
it was turned off on purpose and will be back up within a few minutes or
hours. There are going to be a lot of very nervous people in utility
power management facilities who will be pulling plugs at the first sign
of cascade or other major failures. Looks at this point that some major
utility failures are certain. Believe it or not, some utility company information
tech people are still trying to convince management that Y2K compliance
work needs to start. In most places in the US, that work is already
well under way. One reason I assume power failure is most likely is that
one Y2K project manager at a major Southeastern US provider said that every
electric power plant tested crashed when fed a 1/1/2000 "detonation test"
date. He went on to say that the problems found either have been fixed
or will be shortly. I believe him, but note that he only speaks for one
company. I also believe him when he says that preparation for temporary
Y2K related power outages is a good idea no matter where you are. Minor
good news is that I saw a report from an association of natural gas distributors
that said that their Y2K remediation process is far less complex than the
electric process and that they expect to be Y2K ready. The bad news, of
course is that there's no way to know if they are telling the truth until
some time on 1/1/2000 and the ones that fail may be yours.
Some of the following
is based on experience, the stuff I either had access to or wished I had
access to when I got to experience a major earthquake a few years ago.
By the way, I'd get these items months in advance if possible, there's
a good chance that the public panic and panic buying will hit during December
1999. If you decide to get really serious and buy the nitrogen packed foods
for long-term storage, I'd order... now would be a good time. Some of the
outfits selling this kind of food are already overbooked and are quoting
several weeks (e.g. Walden Foods) to fufill orders. The reason is simple.
The people who already do business with these organizations immediately
decided to stock up on food as soon as they heard Y2K was likely to be
a problem. (7/3/1999)
Also, whatever you get,
get spare parts whenever you can. Even if society is pretty much fully
operational a month or so after the crash, whatever organization supplies
the spare part you need may not be. A word to the wise should be
sufficient. (spark plugs, fan belts, fuses, radiator hoses, a tire or two,
bulbs, batteries... whatever is most likely to fail on whatever you depend
on)
Anyone who says that there is not enough food available to make Y2K
preparation possible for every household in the US hasn't checked the
facts. We have 51 million metric tons of
wheat and 204 million metric tons of maize stored in the USA. We also
have quite a few megatons stored of just about everything else we grow
in the US. Click here
for details. That's about 1 ton for every man, woman, and child in
America. Can you eat a ton of food in a couple of months? The problem
with food isn't a lack of it, it's that transportation and computer
problems mag make it possible for the food to get from storage
facilities to your home. If it's at your place already, that ceases to
be a problem.
Unless you're reading this in late 1999, you don't have to do all
your preparation immediately. A painless way to start doing this is to
buy a few extra cans or packages of non-perishable food every time you
go shopping, put them in a box labeled "emergency supplies", and keep
doing this. Sooner or later, you'll want to take stock of what you've
got against what you'll need for a full (x) months of food. Other
information here or linked to this page will help you figure out what
you need.
It is my understanding that British supermarket chains will be putting
out ad campaigns discouraging this kind of preparation, due to the
fact that people buying more than usual will cause problems in their supply
chain. I would suspect that the same will happen in the USA. I can say
that as soon as you see this kind of ad campaign, don't wait another
minute, it means you've already waited too long. Of course, this might
put you in the middle of a panicked supermarket crowd, on a basis that
"Don't worry, there is no cause for alarm" translates to "PANIC TIME!!!".
Sorry, best I can do at this point, when I have more solid ideas, I'll
post them. Try to make sure the shelf life of whatever you buy will take
you at least through 2/2000. The other reason why having a food supply
may be helpful even if you're in an area where the lights don't even
flicker on 12/31/1999 is that high unemployment is quite likely for a
while in 2000, and having a few months of food in place will reduce
financial stress on you quite a bit. For more information on food, go here. The other reasons to check into food are
probable Y2K-caused inflation and the high probability of very high
unemployment, even if your company is Y2K ready, it's suppliers,
vendors, transportation, or communications may not be. You'll want to
be able to spend money on things other than food if you're without a job
for a while.
The bottom two lines should be the first 2 lines of your text
message, they are commands for the list server program. Subject left blank on purpose, not that it matters.
Power surges are very
probable on New Years Eve 1999, as various sections of the power grid are
switched on and offline. If you're seriously paranoid, either unplug that
evening or consider adding a cheap surge protector between your good one
and the wall so if a power surge hits as a sacrifice to protect the more
expensive one. By the way, the ones with MOV varistors wear out from normal
use every couple or three years. After that, they retain their use as power
strips, but don't protect anymore. Most low - medium cost surge-protected
power strips use them. If you're buying, make sure yours has UL1449 compliance,
and has three protected lines. (ground-hot, ground-neutral, hot-neutral)
You might as well get surge protection for your incoming phone line(s)
as well. Some power surge boxes have it built-in (the ones with 2 phone
jacks), or you can get separate boxes.
For business use, a UPS
(uninterruptable power supply) is a good thing to have for post Y2K conditions,
as I am expecting frequent blackouts and brownouts. This can not only damage
your computer, but eat your last several hours of work. A small one can
give you time to save all your work and shut down cleanly, a big one can
keep you working. Here's information on one company's (allegedly) Y2K-ready
UPS systems. This isn't the only place you can get them, just the first
to come up in a quick Web search. Other manufactures make them, too. For
larger power problems (like an office with quite a few machines) a backup
generator system is the way to go to keep critical functions up. Note that
with a generator, you need surge protection (or better, UPS systems) to
provide safe power for computer systems.
Something to send to friends, relatives, etc. or even to attach
anonymously to neighbors' mailboxes / front doors.
If you plan to buy firearms for self-defense for Y2K, BUY GUNS
RIGHT NOW!!!. New gun control legislation was passed in a
couple of states within a few days of the Littleton, CO massacre by
people who are perfectly aware that those laws would not have saved any
lives in Colorado and won't save any children's lives in the future.
There has been a movement in the US to ban private possession of
firearms for years. The anti-gun hysteria which is being deliberately
fomented by politicians and mass media will result in more anti-gun
legislation which will make it harder for you, the law-abiding
citizen to purchase the most powerful tool for self-defense available in
current technology. If 911 is totally down in your area and you become
the target of a home invasion robbery, not having a gun in the house
probably means no recourse against the intruder, particularly if you are
a single woman with kids. Since my opinions with respect to Littleton
have other than that they will make guns harder to buy (already
happened) are not relevant to a Y2K page, you can find them on my Gun Control, Censorship, and Littleton page.
You can also get a phone
security program will make your phone calls or Internet voice conferences
(Net phone) at the freeware sites as well.
Get the commercial version (about $100, worth it) at the PGP Inc. site. If you're planning to use
it for business applications, this is the one you should get. It will
work with the freeware versions.
You can get my current PGP key here. If and only if you have my old PGP key,
get the key revocation certificate for that key here.
This is pretty much what
FEMA and other groups say you should keep around your place in case whatever
natural disasters are common to where you live (earthquakes, tornados,
hurricanes) strike. Even 1/1/2000 is just another day for the world, if
you prepare as I suggest, your efforts and money will not be wasted. You'll
be ready for the natural or manmade disaster which will be coming for you
sooner or later, or you'll be ready to go camping. Here is more by FEMA
on emergency
preparation. Also here is brief advice on long-term food
stockpiling.
The reason why organizations
who advise people on how to prepare for disaster say 3 days is that this
is how long it generally takes disaster relief from unaffected areas to
come in. Since this situation cover a larger area than anything anyone
has ever seen (like the whole world), more extensive preparation is in
order. The emergency organizations themselves or the methods used for transporting
aid may themselves be too caught up in Y2K problems to be able to respond
normally to your disaster. Aid might come in weeks or months or
possibly, never depending on where you are and how hard your area,
region, or country got hit.
Being outside a major
city would probably be a good thing. Imagine being next to, or worse,
in
an inner city where the welfare checks for 1/1/2001 didn't show up. (even
if the reasons had nothing to do with Y2K) I'm pretty sure this will actually
happen somewhere. Combine this with the distinct possibility that we're
going to find out the hard way that some public safety agencies aren't
Y2K ready, I foresee a hot time in several old towns that night. Even if there
aren't any riots, if 911 service goes down, which is likely in a number
of places, fire departments may not find
out about fires until entire city blocks are ablaze. I'd be more surprised
than not if we don't lose a major city or two on the New Year's Day - 2000
weekend even if almost everything goes right everywhere in the US. Which
it won't. Don't be in one. I plan to spend that weekend on vacation in
a rural area somewhere.
There is a well informed
body of opinion (and a few nuts) who thinks that 1/1/2000 will be the end
of civilization. These people recommend survivalist level preparations,
up to and including a retreat way back in the hills stocked with years
of food and supplies needed to make long-term subsistence farming
possible. They might be right,
though I don't agree with them. While a tetreat is probably the best way
to get through y2k-panic in the first few weeks of 2000, I think it'll
probably be possible to start participating in the recovery process
starting shortly thereafter. There are too many people who enjoy the
comforts of civilization to lightly walk away from it and there are too
many tools which will allow its repair, at least at minimum functional
levels to make it reasonable to take for granted that everything is going
down forever. I'll be adding survivalist oriented links somewhere on this
site in the next few weeks.
Here's a survivalist
oriented link, but a moderately realistic one, they advocate that you also
plan for the case where year 2000 happens and society survives pretty much
intact. Warning, the site owner is Religious Right, so take the
practical how-to information and ignore the political and religious
propaganda. y2kchaos This is good
advice for many of the better Y2K information and preparation sites.
As for the Internet, I'm
guessing a number of ISPs will be down for reasons ranging from local power
/ phone outages to backbone problems. If you've got power and your ISP
is working, you'll be able to connect to quite a few places... though traffic
may take much longer to get from place to place than normal. The good news
is that the Internet was designed to tolerate the kind of outage level
that goes with a nuclear attack. The bad news is that if your ISP doesn't
have power, your messages go nowhere. However, if you don't have power,
you've got more immediate problems. You also won't be able to connect to
quite a few places and people. Your data traffic may have to go via direct
modem connect for a few days if you've got anyone who's up to send it to
you can get through to via phone. If you work for an Internet Service
Provider or if you are wondering about issues relating to operating ISPs
under y2K conditions, click here.
One problem with the
totally worst case scenario of everything breaking at once is that not
all mainframes are "old iron", I doubt you can buy a new or relatively
recent mainframe that isn't Y2K compliant, and I doubt anyone has
written code in the last couple of years or so that doesn't recognize 4
digit dates. However, be wary of "good" deals on older mainframe / supermini
hardware, the owners may be unloading for a very good reason. The worst
case fears are about the amazing amount of 10-20 year old legacy code that's
been patched, updated, modified that has been ported over to newer systems
and not checked for Y2K, and embedded systems (anything which isn't defined
as a computer but has a computer chip in it).
Another is that not all
embedded systems care what year it is. The best example is the computer
embedded in your microwave or toaster. (Your VCR might have a problem.
. . however, not being able to record videos via timer is annoying, not
dangerous.) The good news is that most date-sensitive household applicances
are Y2K compliant. For more information (e.g. which ones aren't)
click here.
Finally, the word will
have gotten out to the general public months before the deadline that there
is a problem and that anyone who wants to be in business in 2000
will fix it. With the exceptions of the very few large companies
who need years, not months or weeks to fix their most critical operations
and didn't start in 1998, those companies who couldn't find the expertise
in time, and those too stupid to understand the word when they get it,
just about everything will be mostly fixed. This document is written around
that moderately optimistic scenario. Say, 80% of everyone with Y2K problems
getting them 80% fixed is sufficient to require that anyone who wants to
survive early 2000 comfortably will prepare as I recommend here.
What should your local
governments should be doing about possible Y2K problems? Obviously, all
government agencies should do whatever Y2K fixes are necessary so that
they will be able to continue doing business in 2000. As for their response
to Y2K based emergencies due to infrastructure breakdown, the most important
thing they should be doing is arrangements to continue emergency services
in the event of loss of electric power and telephone communications. This
means emergency generators (emergency service dispatch, police / fire stations,
critical city hall functions, and some spares in case hospitals, etc. run
short) and weeks worth of stored fuel that does not require electric power
to dispense from tanks. Warehousing non-perishable food and putting together
emergency soup kitchens not dependent on utility power would be
intelligent. Emergency shelters, especially in cold weather areas with
heat make sense. If you decide to check with local elected officials to see
what the state of your community Y2K preparations and
they're totally clueless, refer them to this article from Money
Magazine. Also, try them on this Business
Week article. This is also a good starting point for dealing with business people who
are new to this. A community organizing site I haven't checked with is
Napa Y2K, this might give you an
idea about how one community is organizing.
In this Computerworld
article, William Ulrich suggests that the US government Y2K policy may
foster panic instead of reducing it.
Here is a discussion of work financed by the Naval
War College on recommended government responses to Y2K trouble.
The real problem with these measures is that local communities are
simply not up to the task of housing all of their inhabitants in
emergency shelter in the event of a regional power outage. The best they
can be expected to do is to provide shelter for the elderly, homeless,
and others who can't prepare for Y2K trouble themselves. Sheltering
everybody in emergency shelters isn't all that great an idea to begin
with. A cold-weather emergency shelter is the ideal way to spread
epidemics.
You can find a budget / bill of materials for an emergency command
center designed to function under emergency conditions here. The main difference between
this and ordinary emergency facilities design is that I made a serious
effort to optimise for minimum power consumption. It's an Excel
spreadsheet.
At the Federal level, other than the obvious tasks of remediating all
government computer systems and providing assistance to local
communities / counties / states for preparation, I've recommended to the
President's Commission on Y2K's Chairman, John Koskinen that the
goverment take drastic action to encourage individual household
preparation, mainly:
Koskinen said in private e-mail (I may link a copy here) that this plan is too expensive and unwarranted. If
absolutely nothing bad happens for Y2K, it is. Even if the impact is
limited to a major recession, a month or two or more of food might make
waiting for the first unemployment checks a lot easier. If the
unemployment programs are hit so hard that checks are months in coming,
this would really help. If there are major long term power outages
anywhere in the US, this would save lives and make fixing them a
lot easier.
Actually, Koskinen deserves credit for taking the time to provide a
courteous, if illogical response. If there is no reason for Y2k
household preparation, just what is being discussed at these
secret sessions on Y2K that elected government officials and others are
having? Find more on them on the Y2KCulture personal site run by Declan
McCullagh of Wired News. Copies
of my proposal were sent to staff members of the Congressional Commitee
handling Y2K and ignored. As for why I didn't mass e-mail Congress, it's
widely known that e-mail sent to Congress is counted pro / con on
issues, not actually read. If you know any Congresspeople who might be
interested in the full version of my proposal, have them catch me in
e-mail.
If things get bad and your elected officials tell you that "There was
absolutely nothing we could do", you now know in advance that they will
be lying to you. While there may be alternative methods to insure that a
supermajority of households will be solidly prepared for Y2K, they need
to be started now to be usable. Nothing is happening.
This is a tale of a major city which may actually have somebody
competent running their Y2K planning. Would you believe Los Angeles? I
wish this person success in his efforts, and hope that upper-level city
management doesn't undercut his efforts or fire him. Check this out.
Here's what The Federal Emergency Management Agency's United States Fire
Administration (USFA) and the FCC have to say about possible emergency
services communications problems in The Year 2000 Bug and Public
Safety Communications. This is something your fire and police chiefs
should take a deep and personal interest in. Here is Police Y2K Preparation Guide
issued by the UK Police Information Technology Organization. It
appears mainly oriented larger / metropolitian police departments, but
the appendices at the end of the document listing equipment likely to
celebrate the New Year in 2000 by failing totally, or worse, producing
false information should be of interest regardless of the size of the
department. If you are from a major metropolitan UK police organization, you might
find this novel and interesting reading, as the government millenium
people are suggesting that the recommended remediation has NOT
been done yet. (5/21/1999) Given that you are looking at this in late
May or afterwards, I suggest for your own health and safety that you
find out what the hell is going on with your department. More information of interest to residents of the UK is on Home Office Y2K page.
This is the Texas
Guidebook 2000 from the State of Texas Y2K office. Looks excellent,
especially if you're doing Y2K planning for a government or large
business. I like the contingency planning section.
Here is the Managing
the Y2K Problem in Local Government from the Iowa State government.
It looks useful. Their contingency planning section looks optimistic to
me, but that's easy enough to compensate for.
Here's a story on the Canadian military planning for Y2K disaster
relief. Here's More Canadian Military Preparedness.
This is the first story about any US military organization planning
to do anything about Y2K trouble, THE SAS and other special services are to deal with outbreaks of civil disorder and the collapse of utilities under secret plans being drawn up by the armed forces to cope with the millennium bug.
The optimistic estimate
above is US / Canada only. Here's
a Wired News article about how well the rest of the world's prepared for
Y2K. Major problems I don't think the article covered are: the idiots running
the European Community decided to impose the Euro currency in the 1999-2000
timeframe. Changing how every computer in Europe handles local currency
is a problem comparable to fixing year 2000; very few organizations have
the resources to do both, and reports coming out of Europe say that businesses
are concentrating on the Euro conversion. The good news is that if the
CIA estimate is correct, Europe averages between 6-9 months behind US compliance
and there are claims coming from Europe that their Y2K public awareness
is considerably ahead of US public awareness. This suggests that Europe
will probably be in comparable condition to the US. If you're in Europe
right now, please let me know what you've seen, I don't entirely trust
what I've heard. My advice for preparation in Europe is the same as for
the US. Here's a cheery piece from ZDnet that's a lot more recent.
If you operate a Canadian
small/medium sized business, your Y2K upgrade may be tax
deductible: "Accelerated capital cost allowance (CCA) deductions of
up to $50,000 will be provided to small- and medium-sized firms for computer
hardware and software acquired to replace systems that are not year 2000
compliant. This will allow smaller firms to deduct 100 per cent of eligible
expenditures in the year in which they occur."
From a recent Usenet post: "In this week's edition of 'Technology
Corner,' columnist David Eddy
discusses the recent report from Statistics
Canada that states that 'in order to make the necessary Y2K deadlines, Canadian companies are
planning on increasing their project productivity by factors of 200,
300, and 400 percent.' Mr. Eddy continues, 'Individual organizations
may, under extraordinary circumstances, be able to achieve that sort
of productivity ramp-up in a potato chip factory, but it simply does
not happen with complex intellectual work like Y2K projects.' What
does this all mean? Read on to find out.
For further information on Y2K-related programs and general Y2K advice in Canada, "Call 1 8� O-Canada (1 800 622-6232; TTY 1 800 465-7735),a toll-free line set-up on behalf of the Government of Canada, for information on the
government's Year 2000 preparedness activities, including publications and
tools to assist businesses, organizations and consumers in their Year 2000
planning. The service also provides phone numbers and Web sites for the
provinces, territories, and some private sector associations that you can
contact for more Y2K information.".
As for Asia. . . I'm
not sure what to tell you other than that we are hearing practically
nothing coming out of Asia about fixing year-2000 problems. The financial
institutions are concentrating on the fallout from the current economic
downturn, other business organizations seem to be ignoring it. If I lived
in Asia, particularly Japan, I'd consider departing. The bad news is that
I can't recommend anywhere as a safe place to depart to. (consensus on
Usenet year-2000 newsgroups and elsewhere: "Asia is toast!") Asia is estimated
at 2 years behind the US.
Africa and South America.
. . would anyone like to tell me what's going on down there? We aren't
getting a lot of year-2000 news out of either place. (except for South
Africa) It may be that the infrastructure is sufficiently primitive that
year-2000 won't make a whole lot of difference outside the big cities,
except for the services rural areas depend on big cities for that won't
be happening. Of course, the real bad news would be, I'd think, the numbers
of armed bands floating around after the government computers crash and
there's no way to pay the army, etc. This suggests political instability,
probably violent in quite a few places.
The head of Russia's atomic energy program says he's going to fix
whatever breaks after the year 2000 happens. I'm glad I don't
live downwind from one of their nuclear reactors. I'm merely wondering
why some ex-KGB operatives haven't tried reasoning with that moron using
the persuasion techniques agency operatives were famous for. The other
news out of Russia is very, very bad.
I will say that I heard that a financial consultant actually advised
American companies to forget about year 2000, that we need to
concentrate on getting ready for the Euro conversion. That advice is
stupid even for companies which reside in Europe. If your company does
business and has the resources to do the Euro conversion after
getting Y2K done and tested, go for it. If your company can't do both,
make the Euro a secondary priority. For most companies, immediate
conversion to the Euro is desirable but not essential. No matter where
you are, if your computers go down and stay down on 1/1/2000, you won't
be doing business anywhere.
As for travel plans, it's already known that some airlines won't be
flying towards the end of 1999 / beginning of 2000. There are lots of
embedded systems in airplanes and their support facilities, FAA computer
facilities are notoriously obsolete, and it's quite possible that all
civilian commercial air operations will be shut down during the
transition period. If you're planning any plane trips for winter 1999,
you'll do well to avoid 12/16/1999 - 1/15/2000. While some rail systems
will probably continue to run, some haven't started Y2K work, either.
Don't figure on rail transportation being available. If you go during
the time window I mentioned above, make sure before you leave that you
are welcome for an extended stay wherever you're going if things work
out that way.
The Fortune 500 are mostly already in panic mode, and that's why most
of them will still be in business in 2000. The ones that aren't will be
in panic mode in the next few months. After that, this will hit
the mass media and every business that hasn't gotten a fix
already underway will be hiring people or sending their computers out to
be checked / fixed. When that happens, you want to be wondering
if your suppliers are going to be ready, not about whether your
computers will be ready or not. Start your year 2000 checkout process
right now. See below for how.
Admittedly, perspectives vary. I know of one computer journalist who
says she actually believes that 1/1/2000 will just be another day, here's the link
to the dumbest story she's ever written. If you read it, note the lack
of discussion with any technical people, just the most optimistic group
of industry analysts (about 10 layers removed from the real action)
who've gone public on Y2K. Can't account for how she blew this one,
she's generally very good. Of course, her Mac will probably get
through 1/1/2000 fine. She lives in San Francisco, though, so if she
doesn't change her mind between now and 1/1/2000, she may not get
through the New Year. I hope she reads this page (Hi, Rebecca!) and
changes her mind quickly. I also hope nobody dies of taking her advice.
It took me entirely too long to get the Y2K point myself, this
page should have been up a year ago.
Hamasaki's Y2K Weather
Reports. Cory Hamasaki is the most respected poster on the
comp.software.year-2000 newsgroup and is probably the world's top
authority on Y2K as it impacts mainframes, large organizations, and
government. He's a top bracket mainframe programmer, if your
organization has to ask
what he costs, it can't afford him. These reports are snapshots of the current situation as he
sees it. The most recent reports from him are more frightening than HP
Lovecraft on a good day.
While I hope everybody
will be ready, I don't believe it'll happen this way. There's always somebody
who didn't get the word, and that person is likely to be one of your vendors
or customers. Keep an eye on stuff going into your computers from outside
your organization after 1/1/2000.
If your business is small
enough to be solidly personal computer, you've got time to fix it if you
don't waste time wondering whether or not you need to fix it. If you're
running larger non-PC systems, check with whoever is running your IT (Information
Technology) stuff to find out how big your problem is. If the person doesn't
know that there is a problem, consider replacing that person. But send
him or her here first, and if you can't get a report on how big your problem
is after this after the person checks the links out of here, find someone
else before it's too late.
Business should also
start checking your suppliers and customers, mission-critical ones first. Let your suppliers
know that if you can't get straight answers from them, you'll find other
ones who will tell you what's going on. You can find links to the Small
Business Administration files on year2000 business compliance below.
Also, especially if you're running JIT (Just In-Time) with suppliers,
borrow or rent warehouse space, your deliveries may get interrupted even
if your suppliers are 100% ready.
If you've got a machine more than 2 years old, you probably should
back up the control configuration settings in CMOS and
replace the battery. If you've got a newer machine, find out what kind
of battery it needs and buy one or two spares. Finding replacement
batteries post-2000 may be extremely difficult for an unknown period of
time.
Microsoft Products Y2K Trouble.
For Microsoft, Y2K compliance for their products seems to be
a moving target. I recommend that you bookmark this URL link,
it'll take you straight here. Once you've got your patches installed,
check back occasionally, their patches keep getting replaced with new
patches intended to fix new bugs. I suspect that some of the "y2k"
patches also contain non-Y2K bug fixes as well. You could wait until the last minute, of
course, but if you do, be warned that a site running on multiple NT
servers has a very, very limited capability to handle peak loads. You
may not be able to download your Y2K patches at the last minute. That's
why their hotmail site runs Linux.
Check to see if the free rental Microsoft Y2K computer preparation video is available from your local Blockbuster Video store yet. It's supplied with a copy of the MS Y2K-fix CDROM described in the next paragraph which provides fairly complete fixes for MS operating systems and applications. You can download the video here. To see an article about it, click here. The bad news is that much of what's on it is obsolete. For more information, click here
A CDROM is available from Microsoft which is free to
registered product users. From Microsoft: "In addition to a wealth of information, white papers and Microsoft Excel
Plug-Ins, the enhanced Microsoft Year 2000 Resource CD now contains
easy-to-use and simple-to-install product updates for the Microsoft Windows(R)
95, Windows 98 and Windows NT(R) 4.0 Service Pack 4 operating systems, as well
as Office 95, Office 97 and Microsoft Works 4.5a. The Microsoft Year 2000
Product Analyzer is also included on the CD, allowing a customer to scan a
computer's hard drive, or mapped network drive(s), looking for core Microsoft
products and immediately generating a report with Y2K-compliance information.
The CD also provides links to additional product information and updates if
needed. Customers can subscribe to this quarterly CD-ROM free of charge via the
Microsoft year Y2k CDROM page
or by calling 1-888-MSFT-Y2K (1-888-673-8925). This suggests that they
are expecting to come out with new Y2K bug fixes for the rest of the
year. I don't know if the CDROM as shipped has the most current bug
fixes... but you can always be sure if it's Microsoft... that you CAN'T
be sure. I've also heard there are problems with the MS Y2K Product
Analyzer. Anybody who has a copy who has tried it, catch me in e-mail. the bad news... it is obsolete, see above..
If you're still running Win3.x , Window 3.x is NOT compliant
unless you download a fix from Microsoft,
Windows NT is NOT compliant unless you download the latest fix
from Microsoft. See below for where.
Windows 95 is NOT compliant unless you install the latest
program patches made available in November. Even if you have downloaded
and installed the earlier fix from MS, you need to get the new one. The original fix
replaced two files, the new one replaces several more. See below for
where. Aren't you glad you bought Microsoft?
Windows 98 at this time is NOT compliant,except for the 2nd Edition. There is a
patch in the downloadable Service Kit available. They claim that this is all that is needed.
Go to PC Profile to get the right
link at the Microsoft site for whichever MS operating system or
applications you are running. Believe me, it's a lot easier than trying
to use the Microsoft search engine.
Machines running MS software may work through 2000, and break on
12/31/2001! For the announcement from MS, click here.
Remember, even if your
machine is 100% compliant and your operating system has been made
compliant, your major applications may not be. Check with
your vendors, most are on the Web. It is known that not all Microsoft applications
are Y2K compliant, especially the older ones. If you've got custom applications
or industry specific applications, check very carefully. If there
isn't a fix ready, you may have to replace these applications or have them
rewritten. Better you do this now. More fun to do it now than to
go to a computer store on New Year's Day, 2000 and find that the next load
of Y2K compliant applications will be delivered ??/??/2000.
This
article gives useful information on how to find out if your applications
have problems, how to fix problems with database, spreadsheet, etc.
files,
A Y2K problem scanner for applications running in Win 3.x / 9.x can
be downloaded free, check Netsavers
NET2000 Total Year 2000 Scanner and let me know if you try it and
how well it worked for you.
Here is an
online personal computer software compliance database listing applications by vendor name and list of
applications with "no issue exists", "issue exists", etc.
By the way, you should
virus check these downloads just like you should virus-check anything
else that goes onto your computer. In a network environment, virus-check,
RTC, and BIOS Y2K compatibility is the network administrator's problem,
there are companies where a user loading software onto her own PC could
get fired. In these cases, you might talk to the network admin, and if
that person doesn't believe that Y2K is a problem and you can't even get
the person to look into it, start looking for another job, that employer
is likely not to exist after 1/1/2000. You can get downloadable virus-check
software at the McAfee subsidiary of
Network Associates. (As for virus checking that download, you may
have gotten a virus check application with your PC. Otherwise, I guess
there are exceptions for every rule.)
By the way, if you don't
have a backup tape drive or whatever, spend $150 or so and buy one, or
if you want a really cheap backup system and have a slot free, spend about
$70 for something that uses your VCR as backup media. For more information,
click here.
DOSCHK is the utility I recommend for testing for Wintel Y2K hardware
problems on individual personal computers, it's more informative than the
other ones and in the new revision, does support the reboot in
2000 test. You can get it at the DOSCHK
page. The documentation supplied with it will explain the hardware
problem clearly if you know computer hardware. It also has a (very short)
list of computers found Y2K compliant. this
one from AMI will tell you which components (RTC, BIOS) passed / failed.
This one is suitable if you feel the need for a backup test for
confirmation.
There are other diagnostic
packages, but I believe the above provide satisfactory performance. While
remediation suites generally do analysis of network hardware and can provide
software patches, there are reasons for being suspicious of the
software fix for network and certain other applications.
Here is a diagnostic tool which may indeed be useful for system
adminstrators who wish to run Wintel box testing over a network. Through a script
file customized by the administrator, it can be made to do pretty much
anything required for a diagnostic tool, including reporting and
including the reboot test.. Check it
out at Y2Kare. I don't
recommend it for an individual unless that person wants to test a number
of PCs using a standardized format for a test lab or customer service
environment, this is a program one has to learn how to use. While other
tools are designed for network fixes, this one looks best for the
PC hardware testing of a network, use the other tools for other issues
(e.g. which workstations have non-compliant applications, )
The first generation software fix usually works by resetting the BIOS clock, which will work
for systems which will hold a 2000 date. Note that the clock will have
to be reset to 2000 if the PC battery goes down or is replaced. It will not work on all machines or all software. The
fix will not work on programs that make direct BIOS or RTC calls, but this
is fairly rare for applications running on computers used in the home.
One software fix actually emulates the RTC/CMOS and BIOS and actually
does intercept the calls. The bad news is that I can't remember which
one it is. The second generation fix is one that intercepts RTC calls,
that's the one Compaq and Dell will be providing. If you need a software
patch, check your computer or motherboard vendor first, then check the
IBM driver information below.
IBM has written a year-2000 driver that appears to provide a BIOS
/ RTC fix for all but the very most critical real-time situations, with
the exception of the BIOS chips that can not accept 2000 dates. It
appears to run on almost any computer whether manufactured by IBM or
not. If your computer is noncompliant as shown by tests and your vendor
doesn't provide a fix, see below.
You can find the IBM PC evaluation tool IBM Prototype
Evaluation Tool, and the
program to find out if your computer is compatible with the drivers
(chek the Not Ready section of the page) and the drivers on the IBM
Prototype Device Driver page. Run the tools in this order, evaluation tool,
compatibility tool, driver installation. Evaluation will tell you if you
have a problem, compatibility will tell you if the driver will fix it,
drivers is the software fix. DOS, Win3.x, Win95, NT, OS/2 Warp are
supported. Will the W95 driver work with a W98 machine? I don't know.
This fix took my machine from non-compliant BIOS (rollover failure) and
RTC to fully compliant BIOS and RTC as measured by AMI2000 and DOSCHK
evaluation programs, Your mileage may vary. Note the words "prototype" on these pages, if this
fix gives your machine trouble, it's your problem, not mine or IBM's,.
Good luck.
In some machines the clock or BIOS can NOT be set for 2000
and the hardware must be replaced, it's unlikely the Dell/Compaq fix
will help you. I'm deleting my previous software fix recommendations
pending release of the Dell / Compaq fixes, I'll give new
recommendations (probably in the form of "here's where to get it,
download it, install it, and get to work on your software") when the
patches are released.
If you're running accounting
software or other software where an occasional glitch putting the date
of your record update as 1/1/1980 means big, expensive problems, don't
even think about a software fix. LAN servers are in the hardware-only BIOS
and RTC fix category, too unless your software vendors (all of them
running on the server) say otherwise. If you're doing real-time test and
measurement, you're in the hardware-only category, the software fixes add
a few milliseconds to response time. If your network server supplies date
/ time to the whole network, you're really in the hardware-only
fix category. If your LAN provides date and time to the network, I do not
know what category of fix (software, hardware, none) is required for the
other computers on your network. You are probably best off making everything
on the network Y2K compliant at the hardware level, at minimum, BIOS, RTC
as well preferable. While this is expensive, exotic forms of network crashes
are even more so, see below. The Dell/Compaq software fix is probably
the answer.
Another reason for considering
a complete BIOS/RTC hardware fix even if it isn't strictly necessary is
an exotic effect that has been observed to happen on certain personal computer
hardware / software combinations, it results in time / date instabilities
resulting in dates spontaneously changing and in extreme cases, scrambling
of the CMOS information; hard drive settings, problems in recognition of
COM ports, etc. This information is new to me but appears to come from
reputable sources, I'll be checking on it myself rather soon. A Y2K compliant
RTC will fix this problem. (see below) I think what's going on is whatever
software is reading the time is alternating between reading the RTC/CMOS
directly and reading either the BIOS or DOS clocks. (I can guess, but guesses
without experimental evidence are only of use in telling where to look
on the test bench.) This is discussed in the "Time Dilation" or
"Crouch-Echlin" effects pages below. Note that this is mainly a problem
on 286 / 386 machines, but if these are the "embedded" parts of your
"embedded systems", this could be serious trouble for you.
The state of information on time dilation is completely unsettled at
this point, there are arguments at this point as to the cause or even
whether the effect is simply experimental error. More information will
be available here when I've got some.
The best fixes for a
computer that isn't compliant is a replacement BIOS and/or RTC (real-time
clock) if needed. Almost no one needs that fix, with the possible
exception of people running the most critical real-time process control
and laboratory test and measurement software and network servers.
The following chart will be revised when I know exactly what the IBM
driver fix does and it is in a condition where I can safely advise
people to use it. I don't know what they will be doing about
non-compliant BIOSes so my final comment on this topic will have to
wait for that. I now do know, they say that even if the BIOS is
compliant or replaced later with a compliant BIOS, there is no problem.
by Declan McCullagh
PERSONAL PREPARATION
Prepare for impending
disaster. Not necessarily because one is scheduled for 1/1/2000, but
because disaster is always impending. Your cities are generally
no more than 3 days away from hunger, that's how long most places can go
without a constant outside input of food from the food distribution chain
without store shelves suddenly going bare. There are an amazing number
of things that can disrupt the food chain. Very few people recognize just
how fragile our social order is. Read this section even if you honestly
believe that 1/1/2000 will be just another day, the preparations described
here are mostly intended to help you protect yourself against any
natural disaster.
While most police and fire
departments will probably be fully mobilized on New Years Eve, 1999, 911
may not work, emergency service dispatching communications equipment may
not work, it's possible that even automotive computer systems on police
/ fire vehicles might not work. I'm figuring 911 failure as most likely.
Emergency rooms at hospitals may not be fully functional due to electronics
or power failure.
To: y2kprep-request@list-server.net
Subject:
subscribe
set digest
alt.energy
alt.energy.homepower
alt.energy.renewable
sci.energy
"For $20 (that's 20 cents apiece, folks) plus about $11 shipping, you can
get 100 of the Y2kNews CPR issue (in other words, 30 cents for each person you want to make aware, and NO WORK on your part except ordering). CPR stands for Critical Preparation Resource. This issue is being used around the country for edification by the
Year 2000 National Education Taskforce. They have huge numbers of these. There is not a single person that I have given one to that hasn't come back for more information. There are articles by Yourdon, O'Riley (Cassandra), Yardeni, Keyes, Meagher, Stevens
(author, "Making the Best of the Basics"), Lord, Bell, Bennett, North, etc., and my very favorite is one on specific steps to preparedness [finding potable water, the difference between stockpiling food (legal) and hoarding food (illegal), etc]. Call 1-8
88-925-9925 for details on bundles (minimum 100); they are quick shipping.
I guess I felt that, for about $30, it would be worth it if only one
person's life was changed toward preparation---might be the best $30 I spend in ALL this y2k stuff."
PGP freeware for US Citizens ONLY
PGP freeware for anyone OUTSIDE the
US
Effects on Society / the World
So what about my computer?
Hint:
An estimate I saw recently said that 97% of all personal computers (I
assume PCs are meant) are non-compliant. I now believe the estimate.
This ranges from computers which will merely need to have the date /
time reset the first time someone uses it on 1/1/2000 or after to
computers whose time/date can NOT be reset to 2000 even by software
patch. While newer machines and software mostly are compliant, check
it yourself, your machine might have gotten a BIOS and RTC out of
the back of the storeroom and be the only one built that day that aren't
compliant. The preceding only deals with hardware compliance. That's the
easy part. The hard part is making sure your software is compliant, and
the hardest part is making sure your data files; spreadsheets,
databases, etc. are compliant.
Wintel / (DOS, Windows 3.x, 9.x) compliance
for Wintel users:
You've probably heard of the test that says "set your computer's internal
clock to December 31, 1999, 11:58 PM and wait 5 minutes." It is NOT good
enough. There are THREE clocks on your motherboard. You can only get to
ONE from date/time settings. I found this out the hard way. Well, not quite
as hard as finding out on 1/1/2000. The good news is that the only fix
required for many computers under certain circumstances is simply rebooting
in the year 2000 and entering the correct date/time. The other thing you
must remember is that MS says that once you've downloaded whatever
MS says you need to make your OS and applications Y2K compliant, whether
it works correctly or not depends on the hardware. If you are running
on a network operating system, find out from your vendor what level of
Y2K hardware compliance is necessary for the server and workstations on
the network.
Wintel Y2K diagnostic packages:
These check your PC (Wintel
platform) hardware for year-2000 compliance. WARNING! Copy diagnostics
you download onto a bootable floppy. (use File Manaqer to make a bootable
floppy unless you know how to do it from DOS) Boot from that floppy and
run the diagnostic from the floppy at the DOS prompt. Do NOT run
your Y2K diagnostic from your hard drive. If you're using a diagnostic
intended to test software, back up your whole system first!!! The
problem is that in order to operate, diagnostics have to set the system
clock to the year 2000 one or more times. Some software is sensitive to
this, i.e., virus check software will tell you that it's out of date because
it thinks that it's 2000, time-limited beta test software will suddenly
expire, and other date-sensitive software will suddenly start doing the
unexpected. I was lucky that the only problem I found was "out of date"
virus checking software. I just tested the RightTime software diagnostic
below which does a reboot as part of the test process from floppy, it works
fine, as did my system when I booted normally from the hard drive afterwards.
I was reminded of this while reading the year-2000 discussion mailing list
available at year2000.com. (I'd noticed
the effect, since it didn't give me serious problems, I attributed it correctly
to my Y2K tests and forgot it might give others serious trouble,)
Wintel Hardware Fixes
including unix running on x86 platforms
This section is in the revision process. (10/25/1998)
| minimum compliance needed | home/office no network COTS | office
LAN workstation COTS | network server real-time use non-COTS anything on Novell LAN |
| software patch | |||
| compliant BIOS | |||
| compliant BIOS + compliant RTC | |||
| BIOS can't be set to a 2000 date and can't be replaced | replace | replace |
I no longer see a reason to merely have a compliant BIOS, if the BIOS is
compliant and the RTC isn't, there's generally no reason to simply use
the IBM driver, unless your vendor has other specific recommendations.
Replace means either replace the motherboard or the entire computer.
Note that Microsoft says that NT workstations/servers must have Y2K
compliant RTC/CMOS according to their definition of compliance
, and Novell says that anything on a Novell LAN must
be RTC/CMOS compliant to stay in warranty. I'd say better safe than
sorry, get a Y2K-compliant RTC/CMOS on the server, install a patch making
BIOS / RTC compliant if necessary and find something better to worry
about. If this means fixing a few thousand workstations, this is still
probably cheaper than finding out the hard way which products "don't
conform to 'good' programming" practices.
It is claimed that the new service pack for Windows NT4 is both
Year-2000 and Euro ready. Good luck, you'll need it, here's the link.
Novell network compliance
information.
Most people don't need true hardware compliance given the existence
of downloadable RTC
fixes available from many vendors or if yours doesn't have one, from
IBM. If you're running real-time
process control or real-time lab / test and measurement applications, or
a network server, you might need true hardware compliance. A
small network server might get by with a BIOS and RTC software patch,
particularly if the IBM patch is compatible with the server in question.
If I remember correctly, the IBM software fix is specified to work with
Y2K-ready BIOSes.
For those who need true hardware compliance, whether you get this in the form of a new motherboard, or chips is your choice. If these
chips are socketed on your computer, fixing them shouldn't be a problem.
If you've checked your BIOS and RTC and you know they're both
non-compliant and socketed, get the chips and pop them in. This
alternative makes most sense for a technically knowledgable person with
her/his own personal computer, or pay a technician. The software
utilities above should tell you which (BIOS, RTC, or both) need to be
fixed. For where to get the chips, see below. I now believe based on a
recent comp.software.year-2000 posting from a person from a company
selling BIOS boards that while they are probably workable for Windows
through version 9.x, they are not suitable for network operating
systems such as -ix / Linux / NT.
Resource 800 sells the
Dallas Semiconductor Y2K
compliant RTC chips to end users. This will fix the clock problem in
almost all cases. It costs $24.95 plus shipping/tax. Note that not all
computers have real-time clocks compatible with the Dallas Semiconductor
Y2K compliant chips, and some have the chips soldered in. For those computers,
try the software patch and relegate them to home / non-network use. Read
what they have to say about Y2K hardware issues, including the BIOS. Note
that the reason why I recommend downloading the hardware diagnostic program
to bootable floppy and running the procedure from the DOS prompt after
booting from floppy is to avoid the problems of unpleasant things happening
to your computer as a result of programs seeing a "bad" system date or
the possibility of serious problems if you run the diagnostic with Windows
NT (source - Resource 800). The other option is the RTC board in the
board fix section below.
Year-2000 compatible
BIOS chips you get from the manufacturer or your computer vendor. Note
that if they can't help you, look into Mr.
BIOS. This company claims their line of BIOS chips will support a wide
range of motherboards If the parts are required and socketed on your machine,
parts cost is probably in the $25-60 range ($60 for both- I'm guessing
on BIOS cost) plus installation labor. (I'd estimate 1/2 hour for socketed
chips.)
If you have relatively
new (Pentium/PII/486DX100 or faster) PC, you probaly have a flash BIOS.
Fixing this should simply be a download from the vendor's Web site plus
following the installation instructions. Check! The price of this
upgrade might be 1/2 hour of labor for the first machine (including finding
the right BIOS upgrade and downloading it to floppy) and 10 minutes per
machine after that. The bad news is that if anything goes wrong, your machine
is dead, you won't even be able to boot from floppy, so think
about whether or not you want to chance this. You might be better off
with the IBM software Y2K patch. Ask wherever
you bought it from or the manufacturer how they can help if something goes
wrong before downloading the new flash BIOS software. Unless the instructions say otherwise, I'd suggest putting the Flash
BIOS upgrade program on a bootable floppy, booting it straight from floppy,
and running the program at the DOS prompt. If you boot to Windows and your
regular TSRs, etc., there's a possibility that something running in your
regular operating environment may interfere with the data stream to your
flash BIOS, and if so, you're going to need immediate help to get your
computer running.
If your computer has
a soldered-in BIOS chip that is NOT a flash (software upgradable) ROM,
your options are getting a BIOS board (see below), motherboard replacement,
or new computer, or spending far more money on technician labor (I'd guess
a tech will bill 1-2 hours. If nothing goes wrong. If the chips have accessible
leads, many surface mount packages don't.) than the board is worth.
Another alternative is
a motherboard replacement or even a new computer. If you've got an older
motherboard, this may be for you. However, make sure the new motherboard
is year2000 compliant. If you know of some not mentioned here that
you've checked personally using test software mentioned here that passed
both utilities 100%, catch me in e-mail. If you think it's certified
because a sticker or advertising says so, check it before telling me about
it. Given that this is probably a new motherboard is comparable in price
to either replacing soldered in BIOS / RTC chips or to buying a drop-in
Y2K BIOS board, if you can find one you know to be compatible, this
might be the best answer. Also note that the best way to insure compatibility
is find out if your vendor can stick in the Dallas Semiconductor RTC if
it isn't already there BEFORE the motherboard is installed. If the motherboard
isn't in the case, sticking in a socketed chip takes less than a minute.
I no longer recommend
the NSTL compliance suite for testing year-2000 compliance. As I understand
it, a lawsuit alleging false advertising was recently filed against Compaq
in the UK over its claims of Y2K compliance based on the NSTL test suite, Compaq
withdrew the advertising campaign (without legal admission of guilt) rather
than attempt to defend the suit.
My guess is that the BIOS is compliant and the RTC/CMOS isn't. If you're
considering Compaq, they either have or will have a software fix
available. Local computer stores
are generally very cooperative about customer-requested fixes when
the request is part of the order. You might have to explain the problem
to the technician in order to have him order the right part, this information
isn't going to be common knowledge among PC techicians for several months.
New ones are probably
compliant at the BIOS level, but make sure you can return it or get it
fixed if it fails your compliance test. Getting a "compliant" machine
does not get you off the hook on testing it yourself, and a
vendor "certification" of compliance might crash quite nicely in
your application.
If you're getting a number
of motherboards, build one machine and test compliance before putting the
others together. Assuming it passes and you build the others, check every
machine for compliance after they're assembled. I'll try to find out more
later. Estimated price here is $150+ for the motherboard (AMD K6-233MHz,
Triton TX chip set), $100 or so for labor. However, this gives you 2-3
years of reasonably current computer. The kind of motherboard I would look
for is one with an AMD K6-200 or faster, an AGP video slot, and a USB port.
Before deciding to go this route, remember that new computers (minus monitor/printer,etc.)
start at about $600. You can find motherboard reviews for this motherboard
type at Tom's
Hardware. At this point, simply make sure the BIOS is compliant, you
can handle the RTC in almost all cases via patch.
Tyan will be marketing a new line
of Y2K compliant motherboards with the Dallas Semicondutor Y2K RTC/CMOS
chips, due in 9/1998. The bad news is that the ones announced are all
Pentium II, you might ask them about Super7 (the 100 MHz FSB bus
supporting K6-2 AMD processors.)
PC
Guide is a guide describing the internal workings of a PC (Wintel platform)
in sufficient detail to allow knowledgeable users to make changes. This
should provide you with background on what goes on in your PC which might
help you to better understand what's discussed here.
There's also some good
info here
on upgrading motherboards. The format at this site is unusual, it's actual
chapters from various books from that publisher relating to various aspects
of repair / maintenance of PCs. Judging from what I saw on that link, some
of these books might be worth buying. Personally, I'd rather have a book
next to me than a printout from a Web site if I'm working on PC hardware
for the first time.
Another hardware fix is to buy a board to drop into your PC with a
2000-ready BIOS or RTC or both in it. They cost $60-100 at this point. This fix
may make sense for many businesses, because by the time you've
purchased a RTC chip and a new BIOS chip and paid for someone to install
them, you've already spent more than it costs to buy and drop in one of
these boards. The review I saw says it'll even work on 286 and 386
machines. The bad news is that I've seen no adequate reviews of this
class of products yet (one that mentions that how the board was tested
for Y2K compliance, and how the BIOS and RTC were exercised.). I've seen
one person so far (older Compaq machine) report that it wouldn't work on
his system. Since the point behind a fix of this sort is to allow
popping off the top, dropping the board, and slapping on a "2000
hardware compliant" sticker, having machines on which these won't work
kind of removes the point from buying them. However, it is possible that
the PC clock battery was dead, which is something the BIOS board maker
can hardly be blamed for. BIOS fixes will not work on software that
reads the RTC/CMOS directly. While this is considered bad programming
practice, it's fairly frequent in homegrown programs and is used in
network applications.
Of course, at this price,
you should be thinking of motherboard replacement, since the price of a
low-end motherboard with a fairly fast Pentium / Pentium clone is comparable.
Depends on how much longer you're expecting to keep your machine. I'd advise
replacing 286-386-486s in most cases. However, I'm expecting the price
to drop on these boards. I'd estimate the cost of this to be $60 plus 1/2
hour labor. . . say $100. Do you think your current computer is worth putting
$100 into? Of course, if you're dropping the board in yourself, labor isn't
as much of a problem. Your call. At this point, I prefer either the BIOS/RTC
replacement or another motherboard.
The other bad news is that in a recent (1999-5-18) post, an expert on
these boards said that most will work on Windows 9.x and earlier
systems, but that this is generally not a solution for network
servers. (to look this up, check Dejanews for : comp.software.year-2000,
title North Wind Blows From Scotland).
You can get them at:
In Windows, you're
going to want to make sure the default Windows format has a 4 digit date.
(I'm running Win3.x... some variation of this should work on Win9x.) Go
to the International application in the control panel, set it for Century
("1990 vs 90") ON (checked), Day Leading-Zero ON, Month Leading-ON. The
standard format is YYYY-MM-DD. (may or may not be acceptable in your office.)
This will provide a 4 digit default year to your Windows applications.
Once your hardware
is fixed, then check your applications and data. Click here
for more information.
By the way, if you're
running a network, getting the server compliant does not let you off the
hook on getting the workstations on it compliant. If anyone is working
on programs running on individual workstations when the network is down
or the LAN card is fubared or simply unplugged on purpose, the dates on
uncorrected machines (e.g. defaulting to 1980) might do some amazing things
to databases or accounting or whatever the uncorrected machines connect
to when they are back online with the network. While the "leave the machines
off during rollover and reset the dates" might work for you if the test
results support this, you have to be 100% sure this will be done on every
workstation on the network. Easy in a small office, in a larger enterprise,
I'd feel safer if the RTCs worked right.
While this isn't an
emergency for you unless you're with a larger company (say, over 12 workstation),
get it done before July 1, 1999. I suspect that computer repair shops will
suddenly be filled with panicking people by then or not before. Don't be
one of them. The people trying to do this at the last minute are likely
to find the stores out of stock on whatever they need to get their machines
fixed.
Here's a FAQ on
PC-related Y2K probems.
For more information on fixing PC Y2K-related problems, go to UC Berkeley PC Y2K.
If you've got a machine more than 2 years old, you probably should
back up the control configuration settings in battery backup memory and
replace the battery. By control configuration, I mean CMOS for PCs, the
Mac version has a variety of names depending on machine generation. If you've got a newer machine, find out what kind
of battery it needs and buy one or two spares. Finding replacement
batteries post-2000 may be extremely difficult for an unknown period of
time.
PowerMacs are compliant, I think that the 68xx0X0 CPU machines are
compliant, but making sure is a good idea. Apple Computer.Then check your
applications. Then check your data files, i.e. check spreadsheets,
databases, etc. for 2 digit dates. Click here for programs that might help here.
Warning, before working on that kind of fix, whether checking by hand or
using software automated remediation applications, make sure you've
backed up the system first!
UNIX is compliant, though it's day of reckoning is sometime in 2038.
Your applications and data files may not be. You probably should check
your server anyway, at least if it's an older machine. If you're running
linux or BSD or other x-nix apps on a Wintel box, download the DOS
program from the link above and test it from a bootable floppy. The new
RTC patch from Compaq or Dell or IBM should run out of the boot files that run
before x-ix take over, if so, your machine is y2k ready after they are
installed. However, you may be better off with full hardware compliance
if you're running a server. I don't know for sure, which is why my
advice is extremely conservative.
Some versions apparently provide
automatic remediation, older versions of QNX doesn't unless you download the patch
at the vendor site. Basically, check the OS and/or hardware vendor's
site and see what they say you need, if anything to be Y2K compliant.
Once your hardware is OK, check your applications. Then check your data
files, i.e. check spreadsheets, databases, etc. for 2 digit dates. Check
your routers and other network software as well. I've heard there are
problems and don't know where they are.
To check for Sun workstation / server compliance issues, check the
Infoworld article here.
If you can't find it anywhere else, try here and click the link.
Mainframes - While newer ones are probably Y2K ready, I don't know your environment
well enough to give advice, though many of the larger Y2K sites will have
information that can help, and there are other links here which will help.
Here's a mainframe resources site
Note that if you're running IBM S/390, version 2.5 is not compliant, apparently v2.8 is the upgrade you want. (someone reposted from bit.listserv.ibm-main) Find references to this on Dejanews, or at the IBM site. That last URL may be wrong, I'm offline and did it from memory.
This site provides y2k bug fixes and
examples at the detailed coding level. I haven't had a chance to
find out what languages are supported here.
Here is a shareware tool (no line number limits) that claims to
reformat COBOL in a more readable form. Can't comment, I don't do COBOL.
Some of you may find this helpful.
If you can't find it anywhere else, try here and click the link.
Embedded Systems: Here's a good FAQ for those new to the embedded systems problem. Embedded System FAQ.
Here is an excellent paper on possible embedded system Y2K
trouble
from a major embedded systems (PLC, etc.) manufacturer, ABB.
If your building has any embedded systems, get going on a fix
NOW. Click
to see why.
Here is their Embedded
Systems Fault CasebookHere is a sample quote:
The
odds that anyone will be available on 1/1/2000 to fix your problem basically
suck. There are only so many people with the technical skills to fix these
problems and I expect them all to get called at once in any areas in which
the phones and power are up.
To use these MS information pages, including the ones linked from PC
Profile, you'll have
to register, after which you'll go right to the page. Personally, I don't
see where you as a MS product user have a whole lot of choice. You'll even
have to accept their cookies. This is what MS has to say about it's products,
though given the lack of 4 letter words, you probably should consider
their remarks neither accurate nor complete. For what MS is NOT telling you,
check links below.
Microsoft
gives confusing answers about Y2K.
If you've got time
to upgrade from NT to unix, check intoLinux,FreeBSD,
and if you insist on paying for a PC style unix, BSDI.
You will get better hand-holding for what you will pay them. If you need
another reason than Y2K to switch to (whatever)ix, see what Microsoft
employees on NT and here
and unix vs. NT white paper
They all seem to be ISA
(short slot) boards... set a single jumper if required, drop in, add the
provided "2000 Hardware Compliant" sticker. Your computer should be ready.
(still researching... is a BIOS board OR a RTC board adequate? Probably,
but I'd like to hear from anyone who knows for sure and is NOT employed
by any manufacturers or distributors) Now check the applications. (see
below - the article on PCs in Computer Currents is a good start.) Presumably,
the BIOSes are specially written to handle whatever the RTC puts out and
turns it into a 2000 compliant date, at least that's what the product ads
I've seen imply. A BIOS-only fix might be adequate for anything short of
a network server, but I don't know that for sure.
Compliance - Everything Else
Basically, if there's a way of getting a date into whatever piece of equipment
you've got, from your car to the elevator, to medical test equipment you
are responsible for set the clock for 11:56 PM 12/31/1999 and see what
happens. Make sure whoever fixes your equipment is within call if you do
that test, people who've tried this with their security systems have found
that nobody in the building has passkeys that'll let them into the building
anymore. (actually, for security systems, read the docs first, it may well
be what this test will show is that nobody has logged in between whenever
you test and 1/1/2000...) I take no responsibility for the results of this
one... but if your equipment tanks due to this, at least you'll be able
to get it fixed NOW. Many people have already tried real life tests and
had their equipment or worse, their factories tank. The Incidents
section has examples.
May 1999
EXAMPLE NO EG-07
Equipment Type: DCS
Industry Sector: Oil & Gas
PC or Computer based: No
System Age: 6 years
Application
DCS control system control for petrochemical plant
Description of the Problem :
Online rollover to Year 2000
How was it Identified:
During testing. Offsite testing on a testbed was performed with
satisfactory results. Upon testing of stations on site, control
was no longer possible after the system had rolled over to Year
2000. It was not until this problem was evident on three of the
four operating stations was testing aborted.
What was the Solution:
No known workaround. Plant had to be operated from one station
until problem could be rectified
Consequences for the SYSTEM: System Stops
Consequences of failure to the BUSINESS :
Near catastrophic. Limited reliability and operability of plant.
Reduced production
Real Life Y2K-Related Incidents
More Y2K Links
Note that if you don't
find the information you need anywhere on this page, the answer to your
question may only be a link of two away:
y2k approach, and here's y2k for kids
article,
complete with link to the coloring book on y2k put out by the CIA.
PC users should go
here.
Ignore what he says about simply checking it by setting DATE and TIME from
DOS, but this article does have some good info in it.
Mac users should
go here.
Here
is more information, including compliance information for major vendors.
Note that if the product is really important to you, go to the vendor site
and check it there.
I'll put in more links as I find them, I'll also put links to commercial long-term food storage food providers around here.
If you plan to buy guns, get them NOW. If possible, buy from private parties guns which you are reasonably certain have not been stolen. If you can avoid getting your name run through government databases of armed people, i.e. potential subversives, it's a good idea. It's only within the last couple of hours (4/23/1999) that I've come to this conclusion. The one exception is if you live in a state that has a "must issue" concealed carry permit, the convenience of being able to carry a handgun probably outweighs the fact that you'll wind up in a state database.
Here's a SF Examiner story about the second batch of gun control laws in the wake of Littleton. One of the proposed bills was for banning sales of all guns without the specific approval of the Secretary of the Treasury. Also note that some of the bills have GOP support as well. I've heard about recent lawsuits against firearms manufacturers by major cities (San Francisco, Oakland, Berkeley) attempting to make them financially responsible for misuse of firearms. These lawsuits are intended either to drive gun manufacturers out of business or force them to drastically increase their prices out of reach of the average citizens.
If you are to the political left of Hitler and you are still wondering if you need a gun, or concerned about "political correctness", check out Shadowgov.com as a prime example of why. Their main purpose is to set up a parallel government to that of the United States, and to take over should the US colapse. After that, they want to start by making it a capitol crime to perform or advocate the right to: abortion, gay and lesbian relationships ... Whether you like the above or not, acting on the idea of hijacking the mechanism of governmnet to impose religious tyranny should be opposed by just about everyone, by armed force if need be. In the event that the Feds shut down, either temporarily or permanently, we may not be able to depend on them or police to keep people like that in their cages.
You have a choice here. The politicians who are telling you we need to lock up all the guns are the same people who are telling you that there will be no significant problems for Y2K. Unless they have Y2K compliant crystal balls and know the future, anyone who tells you this is either a liar or a fool. If you don't believe them on Y2K, you should not believe them on gun control issues, either. The common thread here is "do you believe that the government can protect you if you do what they want you to do?" If you believe that they can, why are you here? The bottom line here is new laws will make your purchase of firearms much more difficult.
Besides, I've heard a lot of reports that say that there are supply problems with respect to popular makes, models, types, and calibers of various firearms. You may be lucky enough to have access to gun dealers who are in stock on what you're looking for. If you wait, that dealer might not be in stock for a few days, weeks, or months. This page isn't intended to discuss Littleton or gun control. Now for some practical advice.
For a first-time buyer, for around the house, a 12 gauge shotgun, pump or automatic, using #6 or #8 shot... is a good choice; i.e. enough to blow a big hole in the target, not enough to blow holes through multiple walls, and easy to aim. If you expect to be using it outdoors more, get #4 buckshot. Get a 20" deer slug barrel if you have the option. The shorter barrel makes for easier handling and a test report I've seen says you don't give up that much range. The good thing about a pump is that it has a certain psychological intimdation value, the ker-clack of a round being loaded into a pump action shotgun chamber will get the attention of potential targets. Also, if you're rural, it will knock over medium size game and birds, which might be helpful if the food chain really gets fubared.
Handguns can be a good thing... 9 mm is very popular these days. Warning, they take lots of practice. If you live in a state where concealed carry permits are available, seriously consider getting one. (Of course, if law and order really break down, concealed carry permits won't matter much, you might want to be visibly armed anyway..)
You may find a laser sight helpful, the prices are dropping. If you do, get extra batteries, preferably rechargable via solar recharger if this can be managed. If you already shoot, you know what you like and why. . . have fun . . . and may you never have to use it on a live target. Laser pointers probably can be mounted in scope rings. I saw one at a local 99 cent store for $7.
Rifles are best suited for distance shooting. They make the most sense in a situation where civilization is going to be down for a while and you need a tool capable of "reaching out and touching" someone or something at quite a distance. The something might be a cute little bunny rabbit who plans to eat your food crop before you do, a marauder, or a deer you thought might look good on your dinner plate. For "vermin" and cheap practice, get a .22 semiautomatic. More p owerful assault rifles (Ruger Mini-14, AR-15, AK-47, SKS are examples, the last one is fairly cheap) really are good at killing people. . . and deer. Think about a scope-sighted bolt-action hunting rifle for serious hunting. More later. . . after all, this is supposed to be a computer-oriented page.
If you get a gun, make sure you are willing to use it if necessary (a threat to your life / safety and/or those of others, or to shoot dinner) and get enough gun range time in to make sure the lead will go where you intended it to go. Be polite and friendly at a gun range, no matter how insane the political discussion. the person who can tell you how not to keep hooking your shots to the right will probably be a friendly, nice member of the Religious Right. The good news. A gun doesn't care about your religion or politics. For gun related information, check out the National Rifle Association site. Whatever you think of their politics, these people do know guns. What they can tell you may keep you alive someday. Useful information can also be found at www.recguns.com. I've seen it recommended for information on gun choice and defensive shooting.
Remember that you should be able to get some books listed here through public libraries, etc., you don't have to buy what you see here to become informed. Of course, if you do buy via Amazon Books what you see listed here via link from this page, I get a commission. At this point, I've been too busy researching online to do any print reading on Y2K, so if there's something you've seen you think others need to know about, please catch me in e-mail. What's here is based on what appears to be competent recommendation. For reviews and ordering information, see below.
This form will, of course, find anything that's at Amazon Books, not just my recommended reading list. Note that they are adding music and video to their products. For authors, the format is last name,first name. For books, simply type in the title.
Here is a link you need to see!
If you're finding yourself overwhelmed with the amount of info you are collecting on Y2K from mailing lists, etc., here's a text-in-file search utility for DOS. It supports Boolean searches and will search the files in an entire directory tree (including root) if you ask it to. LOOKFOR.COM Note: It won't work if you used doublespace on your HD... It can be made to work straight out of Win3.1 with the creation of a modified DOS prompt .PIF file, I don't know if the PIF will work in Win95.
A final word. The news in the US isn't all bad. Southern Electric Company announced they're Y2K-ready. A Y2K project manager from that company said the same thing weeks before. The Southeastern US will probably have power in 2000. However, this doesn't that anyone there should neglect preparation, the project manager also has said in other posts that he's ready for Y2K disaster as well.(I'll find the URLs if I ever have time.)
Return
to Home Page. Note that if you came directly to this page from a search
engine or whatever, if you go to my home page, you'll find information
on topics ranging from computers to mainstream / alternative news to .
. . if you liked the way I selected information here, check it out.
E-mail me at alizard@ecis.com.