Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : CSGI ...READY FOR TAKE-OFF! -- Ignore unavailable to you. Want to Upgrade?

To: tech who wrote (1267)	11/19/1997 8:15:00 AM
From: tech	Read Replies (1) \| Respond to of 3391

Major Y2K Problem-Solving Seminar Is Cancelled: 3 Attendees Link: ieee.org A New York City seminar on solving the y2k problem was cancelled by the Institute of Electrical and Electronics Engineers in late October. There was no interest. The IEEE asks why not. At this late date, there should be widespread awareness of the problem. Apparently, there isn't. Yet awareness is phase one: 1% of the overall y2k repair project, says the California White Paper. Draw your own conclusions. * * * * * * * The New York Section of IEEE scheduled a seminar with the title "Are You Ready for the Year 2000?" to be held on Wednesday, October 29. As of the evening of Thursday, October 23, we had three (3) people signed up. What went wrong? The subject is discussed all over the world, on TV, radio, in newspapers, magazines, etc. Promotion of the seminar was published in IEEE magazines with worldwide distribution, in the IEEE Monitor, the sections newsletter, etc. Direct mailing, as well as e-mail and fax was used. Still just a few people showed interest. A minority thinks that the year 2000 computer dating (!) is a problem, while the majority thinks that it can be fixed before the end of the year 1999. This means that these persons are ignorant of the problem with having "99" assigned to mean "not known," or something like that, and not specifically date related. Thus, in those cases, the problem occurs at the end of 1998--14 months from now. Surveys reveal that over half of the community is not working on fixing the year 2000 problem. The response to our seminar invitation indicates that it is more than that. The entities that have not yet started working on fixing the year 2000 problem will not be able to fix it in 14, or even 26 months. Concerned entities will not be able to find enough programmers to work for them. Studies indicate that this is a $600 billion problem engaging millions of programmers worldwide. Considering that this is an engineering problem, we know that engineering projects are overrun at about 50 percent of the time. In the case of the year 2000 problem, there is no leeway--it has to be fixed before midnight on December 31, 1999, or in some cases before midnight of December 31, 1998. Thus, at least half of the world will not be prepared for the new millennium. Chief Executive Officers, CEOs, should not count on being able to find programmers in the last minute. Not even from the pool of programmers in India. The major problem is in fixing COBOL programs and the Indians do not know much COBOL after their government threw out IBM. Also, the Indians will be busy working for the Europeans and others, who are behind most nations in fixing the year 2000 problem. What company do you know of that can increase their capacity without having to add additional "bodies" ? What company do you know of that can do conversion remotely from their home base ? What company do you know of that can automatically convert up to 3 million lines of code overnight ? What company do you know of has such an accurate process that testing time is significantly reduced? ConSyGen

To: tech who wrote (1267)	11/19/1997 8:20:00 AM
From: tech	Read Replies (2) \| Respond to of 3391

Greenspan Says Banks Need 100% Y2K Compliance: 99% Will Not Do Link: house.gov James Leach, Chairman of the House Banking Committee, quotes Alan Greenspan's warning. Is Greenspan serious? If so, we are heading for a guaranteed banking disaster. There is no way that 100% of the banks in the international banking system will achieve 100% compliance. At present, there is no major money center bank anywhere on earth that is compliant. Here is what Cong. Leach said: * * * * * * * Experts also emphasize that the problem must be fixed properly and on time if Year 2000 related problems are to be avoided. I was intrigued by a statement Federal Reserve Chairman Alan Greenspan made a couple of weeks ago. He pointed out that 99 percent readiness for the Year 2000 will not be enough. It must be 100 percent. Thus, the message seems clear: all financial institutions must be ready; federal and state regulatory agencies must be ready; data processing service providers and other bank vendors must be ready; bank customers and borrowers must be ready; and international counterparties must be ready. The problem: The YEAR 2000 The Solution: ConSyGen

To: tech who wrote (1267)	11/19/1997 8:33:00 AM
From: tech	Read Replies (2) \| Respond to of 3391

Things You Had Better Do Today (and not Do in Jan. 2000) THINGS TO DO DURING THE NEXT FEW MONTHS: 1. Write letters to financial institutions with whom you have dealing (banks, mortgage company, etc) and ask if they are Year 2000 compliant. Send the letter registered and ask for a signed return receipt. A sample letter is included at the end of this report. Ask for up-to-date copies of your records. There are going to be plenty of lawsuits relating to the Y2K problem. These letters may come in handy. 2. Get copies of your credit report. 3. Make certain your financial records are complete and up-to-date. If you are not already doing so, keep records of EVERY one of your financial transactions. 4. Ensure you have copies of the last five years of your state and Federal tax returns. 5. If you own stocks or other instruments, and the company holding them does not convince you that they are Y2K compliant, consider selling your holdings and do not reinvest until after Jan 1, 2000. Check with your tax advisor for the best way to do this so that you do not incur unnecessary tax liabilities. 6. Check your own personal computer for Y2K compliance. This involves checking both the hardware and software packages you use. Checking the hardware involves the use a small software package that will test to determine if your hardware will function properly after 12/31/99. 7. Contact each manufacturer of your software packages and ask if they are Y2K compliant. Again, the Internet is an efficient way to do this since nearly all software manufacturers have websites. For example, Microsoft, at: microsoft.com. 8. Carefully check every invoice and bill you receive. Errors are likely to occur. 9. If you are doing any traveling, check and recheck your reservation status with hotels, motels, airlines, trains, rental cars, etc. THINGS YOU SHOULD CONSIDER NOT DOING BETWEEN DECEMBER 30, 1999 AND JANUARY 5, 2000: 1. Fly on an airplane (air traffic control may be disrupted or fail; on-board computer systems may fail) 2. Use an elevator (Elevators may stop suddenly between floors; doors may fail to open) 3. Schedule any medical tests or surgery in a hospital (hospital records may become corrupted; emergency systems may fail) 4. Make a long distance call at midnight, Dec 31, 1999. (you might get charged for a 99 year long phone call) 5. Ride a train or any underground people movers (subways, etc) (traffic systems may fail, automatic systems may malfunction) 6. Don't use an ATM machine (your bank account records may reflect an incorrect withdrawal amount) 7. Don't make a bank deposit (your account may not reflect the deposit) 8. Don't pay any bills (pay any bills due the first few days of January, 2000 the middle of December, 1999. Send payments via registered mail (this one time) and keep good records of the payment! (You may find that your account is not properly credited) ****** Who was it again that had an FULLY-AUTOMATED solution to this mess ? BTW- A solution that has been TESTED and PROVEN to work. ConSyGen**