Y2K: Please don't expect it to all be "taken care" of by someone else.
Maybe you've already upgraded your mission critical applications to be Y2K compliant, but continue additional Y2k testing throughout 1999. We know, most of our web site visitors are using a Windows system. Take a second to check seriously what consequences the following statements from Microsoft will have for your business, your PC, your network, your back-up, ...
Microsoft recommends executing the tests
on a "test-bed" machine rather than a production machine.
[source] [ms year2001] [ms year2k]
Make sure your company is aggressively fixing the problem in their organization, or you may find yourself unemployed in 2001. The bug has been proven to affect nearly every business at one or more levels. Hiring someone to fix it will become increasingly more expensive as we approach 2001 because of the growing labor shortage.
Y2K recources can be found at many sites on
We checked out some good tools to fix the Y2K problem.
You know, checking just one PC is a different task then checking a network with some servers and some 100 or some +1000 clients.
Please email some details of YOUR environment
so that we can provide YOU with the tool or information YOU realy need.
[ home ][noframe]
© 1997-2001 by pro-soft.de
Last modified: 2001-09-10