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 : WDC/Sandisk Corporation
WDC 173.81+6.6%10:24 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Rex Dwyer who wrote (1370)11/7/1997 7:42:00 AM
From: Done, gone.  Read Replies (2) of 60323
 
>> what brings you to a thread like this?? <<

First of all, I'm a photographer. Nudge, nudge, wink, wink, say no more...

Secondly, I am up to my eyeballs in TPRO, the leader in dealing with the embedded systems y2k problem:
exchange2000.com

Put one and two together, and here I am.

This is my line of reasoning, and I hope someone can tell me where I'm dead wrong:

The embedded systems y2k problem has not yet even shown up on most radar screens. TPRO is just now beginning to be visible, their y2k products and services just being rolled out.

TPRO, (and a ton of mom and pop shops with TPRO's y2k CD in hand) will soon scurry all over the world, yanking non-compliant chips, and replacing them. With what???

I want to own a chunk of whoever it is that stands to gain the most from the manufacture of these y2k compliant chips.

Since, as I said, the embedded y2k problem is only now starting to show up on the radar screens, it is probably unwise to use 20-20 rear view vision, and instead, it is crucial that we put on our thinking caps, and figure out who it is that will, within a year, be cranking out y2k compliant chips like there's no tommorrow.

I can't see any reason why Siemens and SanDisk would want to miss this opportunity.

A wise man will make more opportunities than he finds. --Bacon.

Bounced Czech
(FBN - Visions.)
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext