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 : Apple Inc. -- Ignore unavailable to you. Want to Upgrade?

To: inaflash who wrote (70011)	10/13/2007 2:13:39 PM
From: stock bull	Read Replies (2) \| Respond to of 213182

I really don't know if the firmware problem with affect the stock's price. But, I do believe that any negative news affecting the financial performance of the company, or any negative news on Jobs as related to the back dating of options will have a significant negative impact on the stock's price. JMO Stock Bull

To: inaflash who wrote (70011)	11/3/2007 2:40:06 AM
From: inaflash	Read Replies (1) \| Respond to of 213182

About a week ago, Apple release a very bad FIRMWARE update version 1.0.2 for the iPod Classic. I mentioned this problem a few weeks ago, and still no action. I'm still getting prompts to upgrade to the bad firmware in iTunes (which I've avoided). I guess it's not that significant and they'll deal with it in their own time. Meanwhile, it's getting more attention (and check the links at the bottom of the article, before the user comments): engadget.com The most typical symptom seems to be a dead battery with a unit off overnight. Other report hard drive activity or clicking constantly or randomly. Seems like a confusing problem with people reporting dead batteries overnight that are not running firmware version 1.0.2 and some reports that firmware 1.0.2 are not causing them any problems. Most reports seem to indicate the trouble is with Coverflow or with videos. If someone uses their iPod predominantly for music, that might explain why they're not encountering the problem. I hope Apple figures this thing out before it gets even more negative attention. Meanwhile, I suggest that everyone continue to avoid the firmware as I'm convinced it is the cause of the majority of these problems, and not worth taking a chance with it. For what it's worth, my e-mail/feedback communications with Apple have remained unanswered.