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

To: Jack Zahran who wrote (8533)	1/7/1998 2:26:00 PM
From: Karl Drobnic	Respond to of 31646

Jack and I are on the same track with the last two posts. A further thought is that if 2Q revenues are flat compared to 1Q revenues, we can assume that Y2K revenues were minor. Since we know that TPRO was working its base business full bore in 2Q, we can assume that most revenues came from the base business, not the CD. Since WNDR actually shipped the CD in Dec., we're still in the 60-day "free" period. That throws the WNDR-client revenues squarely into 3Q. I and a few others have been squarely focused on the 3Q report (due after March 31) for a long time as the place where we would see the big impact of Y2K. We are following that baseline. My surprise is that the shares are not running up in anticipation of those 3Q numbers, now only 4-5 months away.

To: Jack Zahran who wrote (8533)	1/7/1998 5:18:00 PM
From: Jack Zahran	Read Replies (1) \| Respond to of 31646

Millennial mayhem for manufacturing ...will factories function today? memagazine.org from mechanical engineering magazine (for all you so called engineers) Power utilities must also fix the millennium bug: One reported test for y2k compliance by Hawaiian Electric caused the entire system to shut down. . . Determining the true costs of y2k is difficult because of the compared with banks, say, or the Social Security Administration. Most estimates reflect corporate IT's needs-fixing applications that are supported by IT and easily identifiable as computer-based-and not manufacturing's needs, like adjusting embedded dates in various production functions. "Nobody really knows how severe the problem is," Miklovic said. Only now are companies becoming aware of y2k as it concerns manufacturing operations. "Most manufacturing firms have a y2k corporate project in place already," Owen said, "but very few have kicked it in at the operations side of the issue. The problem's been a combination of people in plants thinking it's strictly a downstream corporate/IT problem and the corporate/IT people not being aware of how the systems are running in plants." . . Embedded Bugs "Embedded systems are everywhere," Owen said, "in chips, circuit boards, proprietary units, and so on." Unlike corporate programs that use languages like COBOL and can be rewritten, "these systems have hard-coded logic that we can't get the source code for, so they require a whole different approach for testing and resolution. Unless fixed, they can be the source of bad data, especially with date/time stamping. . . . High-level systems, such as those for analysis and scheduling, may have more problems because they'll be working from 'injected' bad data." Inventories, which often rely on such date/time stamping, may not be restocked properly because of misread years. Any manufacturing-related process that is measured over time can be affected. For example, a number of smart sensors have the ability to track when they were last calibrated, and they issue a signal if they operate past their scheduled recalibration date. Many of these instruments currently use the two-digit year, so after Dec. 31, 1999, they will quite likely go out of calibration. . .