CompuServe Messages

#C= Shareholder Movement

    25-Jul-93 14:51:23
Fm: Bruce Franklin 72047,2776
To: Bruce Franklin 72047,2776
[>> Continued from previous msg] of order" that the meeting be moved to the United States where shareholders could attend. This shareholder was bodily removed from the meeting despite his clear assertion that he did not want to leave. Such action is typical of this well fortified and unresponsive Commodoreboard of directors. Another shareholder, who worked for Commodore, warned the Board of the impending crisis of the MS-DOS price wars. The insufficient response on this point has, in great part, landed Commodore in its current jeopardy. Commodore's recent plummeting stock was not a result of unforseen economic conditions in Europe as they would have you believe, but rather a direct result of the Board's unwillingness to respond to the changing realities of the computer industry. Since the press coverage of the 1991 meeting, other people have joined the movement including other shareholders and Commodore employees. Similar attempts at affecting Commodore management have failed in the past. But now, new SEC regulations have given shareholders new abilities. The rules which previously favored management now allow shareholders to vote for board members that are not part of management's slate. With well chosen candidates and a well run proxy contest, alternative directors stand a good chance of usurping Irving Gould and Alexander Haig this time around. Once succeeding in this contest, the new directors can get to the business of commencing Commodore's long overdue recovery. FEASIBILITY There is a total of 3700 shareholders. The latest Standard NYSE Stock Report shows that Irving Gould owns only 19% of Commodore's common stock. A total of 70 institutional investors account for 20.6% of ownership, according to the Nelson's Directory of Investment Research. According to the new laws, these institutional investors may vote. Further, the remaining 60.4% of Commodore shareholders may be reached [>> Continued in next msg]