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 : BAY Ntwks (under House) -- Ignore unavailable to you. Want to Upgrade?

To: jkb who wrote (5727)	5/11/1998 4:41:00 PM
From: Bosco	Respond to of 6980

Dear ricky & Jay - interestingly, drawing from the same commentary [BAY option,] I disagree that it is the hope of M&A that provides the floor for BAY. While it is possible for someone to make some bet on M&A via the option mkt, it is doubtful the bear would want to bet against that - and that alone. Mimicking the option mkt, BAY share price has also been bouncing around the trading range, and I don't see a particular point of merging speculation. I mean, for those who bet BIG in M&A are the arbitrageurs and they don't have the reputation [this is a manner of speaking <G>] - well, maybe 'patience' is a better word - to tie up their dough for more than a few days. Given the fact that BAY buyout has been rehashed for months, it is my conclusion that no excessive amount of share price is tied to the buyout mindset. JMHO rgds Bosco

To: jkb who wrote (5727)	5/11/1998 4:41:00 PM
From: Jay Lowe	Read Replies (1) \| Respond to of 6980

Anyone ... what are the options for LU to initiate an acquisition before Sep that would allow for pooling of interest? IE, is it possible for LU-BAY to lock up an arrangement based on a letter of intent, or something on that order, but not consummate the deal until post-Sep? What are the legalities in this area? What are the reporting requirements? What must be announced? I assume LU would be doing something if it wasn't for the pooling issue ... so what's the work-around?