BayStar provided $20 million of the financing involved in the A series (later A-1 series) preferred stock deal, though the 20,000 shares figure is correct.
Royal Bank of Canada provided the other $30 million, and apparently hasn't made a decicion on how to react yet.
SCO, as usual, is trying to play the bad news down, claiming they didn't breach the agreement. In a truely odd twist of this mess, they're claiming Baystar didn't "specifically" identify the breach(es) involved.
Sounds like a case of hoist on your own petard to me....
Open Source and Free Software are neither subparts of the other.
They have many similarities, and many of the same proponents, but are seperate classes.
It happens that the similarities are great enough that there is a large amount of software that fits both classes - which leads to a lot of confusion between the two classes.
In my experience, having BEEN short on SCO intermittantly since it first topped $15, and currently short with every penny I could dig up (less a small amount for short-term variations) the margin required on it is exactly the same as on any other stock that your broker will allow you to short at all.
Margin rwquirements are limited/mandated by Federal Law, and most brokarages follow those requirements exactly, and do NOT give you any "extra" leeway on anything - or anything less.
Margin INTEREST will vary a lot - but in the current low-interest market, it's usually under 6% a year currently.
Oddly enough, very little to NONE of the legal stuff to date has shown up in the newswires at all, except when a new major case gets filed. The only exception I can think of was the German court finding in favor of SuSE against SCO....
Given that SCO seems to have at least one analyst in their pocket (I can't think of any other reason one specific Deuche Bank analyst keeps saying "buy", but I suppose he could have just not bothered to research *all* the facts), it may be a while for the price to drop a lot.
I also have to wonder at the real "why" behind the Earnings Announcement postponement - my guess is that it's a "last-second propup" attempt on the stock price, before the legal news gets a LOT worse for SCO....
Well, if SCO gets stupid enough, my short-sale position in their stock should pay off big-time in a month or so.
But I'm not holding my breath for that fast of a resolution - they'll do everything they can to keep delaying....
For most of the work most of MY machines do, the bottleneck seems to be a COMBINATION of CPU and Memory limits - mprime/Prime95 is highly memory intensive, but I've seen significant improvements from kicking the CPU multiplier up on my Thoroughbreds WITHOUT kicking the FSB up.
I get even MORE improvement from kicking the FSB up *too*, though....
The rest of the work done by most of my machines is RC5 - and that is VERY CPU limited, as the core code fits easily into cache on anything from a Celeron up, and mostly so on the K5 and P5 generation CPUs.
Slashdot Mirror
One word. Neat! 8-)
BayStar provided $20 million of the financing involved in the A series (later A-1 series) preferred stock deal, though the 20,000 shares figure is correct. Royal Bank of Canada provided the other $30 million, and apparently hasn't made a decicion on how to react yet. SCO, as usual, is trying to play the bad news down, claiming they didn't breach the agreement. In a truely odd twist of this mess, they're claiming Baystar didn't "specifically" identify the breach(es) involved. Sounds like a case of hoist on your own petard to me....
Nylon string doesn't dessicate - it lasts nearly forever. Same for Dacron, but nylon is more flexable and resists abrasion better.
Open Source and Free Software are neither subparts of the other. They have many similarities, and many of the same proponents, but are seperate classes. It happens that the similarities are great enough that there is a large amount of software that fits both classes - which leads to a lot of confusion between the two classes.
The news of the decision didn't hit the major newswires 'till yesterday afternoon. Stock price has taken a pretty big hit today. 8-)
In my experience, having BEEN short on SCO intermittantly since it first topped $15, and currently short with every penny I could dig up (less a small amount for short-term variations) the margin required on it is exactly the same as on any other stock that your broker will allow you to short at all. Margin rwquirements are limited/mandated by Federal Law, and most brokarages follow those requirements exactly, and do NOT give you any "extra" leeway on anything - or anything less. Margin INTEREST will vary a lot - but in the current low-interest market, it's usually under 6% a year currently. Oddly enough, very little to NONE of the legal stuff to date has shown up in the newswires at all, except when a new major case gets filed. The only exception I can think of was the German court finding in favor of SuSE against SCO.... Given that SCO seems to have at least one analyst in their pocket (I can't think of any other reason one specific Deuche Bank analyst keeps saying "buy", but I suppose he could have just not bothered to research *all* the facts), it may be a while for the price to drop a lot. I also have to wonder at the real "why" behind the Earnings Announcement postponement - my guess is that it's a "last-second propup" attempt on the stock price, before the legal news gets a LOT worse for SCO....
Well, if SCO gets stupid enough, my short-sale position in their stock should pay off big-time in a month or so. But I'm not holding my breath for that fast of a resolution - they'll do everything they can to keep delaying....
For most of the work most of MY machines do, the bottleneck seems to be a COMBINATION of CPU and Memory limits - mprime/Prime95 is highly memory intensive, but I've seen significant improvements from kicking the CPU multiplier up on my Thoroughbreds WITHOUT kicking the FSB up.
I get even MORE improvement from kicking the FSB up *too*, though....
The rest of the work done by most of my machines is RC5 - and that is VERY CPU limited, as the core code fits easily into cache on anything from a Celeron up, and mostly so on the K5 and P5 generation CPUs.