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.
Non-Tech : Any info about Iomega (IOM)? -- Ignore unavailable to you. Want to Upgrade?


To: rll who wrote (48356)2/20/1998 3:57:00 PM
From: Zakrosian  Respond to of 58324
 
IMO, it's the analysts fault for completely overlooking this statement.

Robert - I don't think the analysts did overlook the warning. I recall reading that (I think) Emerald's analyst responded that the delay was irrelevant because Jaz2 and Buz were not even factored into their estimates for the 4th quarter. And the earnings were only off by about 7% on record revenues - up almost 30% from the 3rd qtr and 40% from the 4th qtr of last year - unit sales were up even more. IOM had a heckuva better fourth quarter than most of my other holdings - which is why I find this lawsuit surrealistically ludicrous.



To: rll who wrote (48356)2/20/1998 6:06:00 PM
From: Brendan2012  Read Replies (1) | Respond to of 58324
 
>>"We had planned on revenue (from the two-gigabite drive) in the fourth quarter and we're disappointed that we didn't ship it."

The whole release can be read at:

Message 2999209

IMO, it's the analysts fault for completely overlooking this statement. Last time I ever regard an analysts "belief" over my own.<<

I think you're confusing Iomega's plans with the analysts plans here--Iomega may have planned revenue, but the analysts did not. The analysts' estimates were the similar to what Iomega would have gotten if they had shipped Jaz2 and Buz not because they were expecting revenue from Jaz2, but because they were expecting higher tie ratios. However, Iomega talked about its own internal targets in the conference call.

Brendan