SI
SI
discoversearch

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 : TAVA Technologies (TAVA-NASDAQ) -- Ignore unavailable to you. Want to Upgrade?


To: Bill Wexler who wrote (22590)8/23/1998 6:03:00 PM
From: AHM  Read Replies (2) | Respond to of 31646
 
Wexler, you are certifiable! I was involved with Y2K problems in the late 50's when I was marketing one of the first computers every programmed correctly for muni bond maturities in the Y2K+ range - and we needed to preserve precious storage by keeping everythin in 16-bit words which would compute correctly in double precision. What we did was look at dated dates (Issue dates) and we made an arbitrary decision that any 2-digit year beneath 45 was actually in the year 2000+. It worked for this narrow application - but it wouldn't for most - such as social security records where some people live more than 100 years. (Come to think of it, there are a few "century" bonds where the identical problem now exists.)

Read my earlier posting #



To: Bill Wexler who wrote (22590)8/23/1998 9:37:00 PM
From: Piotr Koziol  Read Replies (1) | Respond to of 31646
 
Dear Mr. Wexler,

<<1) An astonishingly large percentage of software and hardware gets
shipped and put into service with bugs - lots of bugs (that's why vendors
have technical support and upgrade policies). If the "cascading failure"
scenario is true for the so-called "y2k bug" then why hasn't this been the
case for other sorts of bugs. Companies and individuals have to contend
with shoddy software all the time, yet the power plants and military
facilities seem to work OK most of the time.>>

Yes, programs get shipped with bugs all the time...

But the Y2K "bug" is different because many, many
programs may fail AT THE SAME TIME. This is an event
that to my knowledge has not yet happened in history...

Does it put the issue in a perspective that is easier
to comprehend ?

:^)

/Piotr