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


To: Ken Muller who wrote (5555)7/25/1999 5:53:00 PM
From: Ram Seetharaman  Read Replies (1) | Respond to of 9582
 
Ken:

You and I share one common observation. ALSC is not going to beat Micron in the chip business (as I posted a while ago in message #
5462) by selling in volume. Micron's pretax profit margin is only 5 %. So your views on ALSC not making profits are quite realistic. They may do better in the embedded controller business. I also agree that at $ 8 ALSC is quite undervalued. But I have to differ in one respect - if ALSC doesn't put on a good show for the next quarter, the stock won't even make $ 10 this year!



To: Ken Muller who wrote (5555)7/25/1999 9:31:00 PM
From: Allen Furlan  Read Replies (2) | Respond to of 9582
 
Ken, have you read how ALSC plans to take advantage of their UMC shares. I am building a position in DIMD because I believe the momentum players will perceive the DIMD/S3 combination to be a "hot" concept stock. By itself DIMD is a financial nightmare, but with S3 I perceive the play to be part arbitrage, part value and part momentum, a pretty nice combo.
S3 has stated that it expects that UMC shares will be eligible for trading. So the outstanding issues are when and how. Who has to approve, what kind of time line? How do you place 30% of a company on the line(ALSC plus S3) without seriously affecting the stock price. Are secondary offerings ever made on the Taiwan exchange or can we expect a very prolonged period of disposal? Didn't find anything in S3 package that addressed these kinds of issues. Do you have any insight on this?