The millennium bug seems to have been taken rather cavalierly in India, especially the government, perhaps due to low computer penetration. Nevertheless, consider the risks. Power plants, airlines, and even oil rigs and nuclear power stations will be hit. All operating systems and applications using date-related transactions, and embedded microprocessors in energy, transport, telecom, and manufacturing systems are at risk, apart from the entire financial system. While awareness of the problem has grown, remediation has not kept pace. For example, for normal, non-embedded systems, remediation can be done by programmers and new software simply saved on a hard disk. But, for most embedded systems the project often requires not only a team of programmers, but also engineers andtechnicians. Testing, too, has been superficial. Before remediated software is subjected to advanced clock-testing to prove its Year 2000 compatibility, it must undergo a thorough regression testing to prove that the original functionality of the software's non-compliant form is completely preserved in the compliant version. And the ultimate Y2K test of software involves running it with the system clock advanced beyond 1999. Not many are aware that to do advanced clock testing, a separate, redundant environment must be set up, with duplicate hardware, and upgraded operating system software. In view of the non-compliance risks, the Centre must set up task forces to monitor Y2K remediation and testing.