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 : Y2K (Year 2000) Personal Contingency Planning -- Ignore unavailable to you. Want to Upgrade?

To: Caroline who wrote (73)	4/16/1998 6:58:00 PM
From: jwk	Read Replies (1) \| Respond to of 888

just a couple of more beats on my too many folks wound too tight drum --- Police in Fort Collins, Colorado (home of CSU) have arrested an 18 yr. old male who broke into four transformer sub-stations and knocked out power to 4 sq. miles over the weekend. About 18,000 homes and numerous business spent a good part of the weekend without power. A 43 yr. old father of 4 was killed at an intersection whose traffic lights were not working (not related to Ft. Collin's incident). Apparently drivers were refusing to yeild, take turns, and treat the situation as a 4 way stop. Another man was killed trying to beat a train so he wouldn't be late to work. The point: everyday we see plenty of examples, some major - most minor, of bad things happening to people which can be directly related to stress levels. Factor in the potential for added stress on a mass scale from y2k induced glitches, and consider the possibilities. Things don't have to fail in a major way to make our daily experiences more challenging. Still hoping for BW to explain away the concerns raised in the Fortune article.

To: Caroline who wrote (73)	4/16/1998 10:03:00 PM
From: Bill Wexler	Read Replies (1) \| Respond to of 888

Seems to me that the vast majority of Microsoft products are compliant. There are some issues with some older software, but I didn't see anything earth-shattering. BTW, I'm waiting on pins and needles for your report on the "6 or 7 bugs" in the VB date routines you encountered. I couldn't find any mention of such bugs in Microsoft's own assesment: microsoft.com In fact, it seems that 4-digit dates are always handled correctly and that the only "issue" is what a 2 digit date conversion defaults to (based on which version of VB you are using).