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 : IBM
IBM 291.16+0.9%1:50 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: J R KARY who wrote (4151)10/26/1998 7:09:00 PM
From: Arrow Hd.  Read Replies (2) of 8218
 
JR, we are not on the same page. The robot example was for exactly
the opposite reason. That there are significant Y2K problems and
they have not been fixed. Gerstner did not indicate that IBM was
going to fix this customer's problem. IBM got out of the robot
business a long time ago. This is an embedded chip problem that only
the robot vendor can fix. Yet the supply line gets disrupted when
one company within it screws up. What if this company made mainframe
power supplies which are basically an IBM design but vendored out and
most often on sole sourcing. IBM mainframe manufacturing is dead in
the water until it is fixed. IBM keeps minimum inventory on hand
somewhat similar to Dell's assembly operation. There is this
continuing thinking that IBM can fix anything anytime. They cant.
The FAA, which represents the worst scenario Y2K situation in the
U.S. is still using 3083 mainframes which simply can't be fixed. The
source microcode is useless and the skills dont exist. IBM has
refused to make the machine's Y2K ready and yet the FAA continues
to attempt fixes themselves. They are supposed to cut over to CMOS
machines next year but continue to put dollars and resources in to
useless projects. The thinking is when Humpty Dumpty falls IBM will
bring in all the King's horses and men and fix it. Wrong answer. When
H.D. falls he's a dead son of a bitch.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext