MS OEM VP to IBM: dump Lotus and we'll cut a deal

Who's a naughty boy then, Joachim?


MS on Trial During a struggle over underpayment of royalties by IBM to Microsoft, MS OEM VP Joachin Kempin offered a deal if IBM would stop shipping Lotus SmartSuite for six months, according to trial testimony by Garry Norris of IBM. By bringing in SmartSuite Kempin was increasing the level of linkage, as the royalty issue was already entangled in IBM's attempts to secure a Windows 95 licence. In questioning Norris revealed that Kempin made the offer in August 1995, just three weeks before the launch of Windows 95: NORRIS: But during the audit period, Joachim Kempin did say, as a measure of something: We would agree to settle the audit if you don't ship SmartSuite for six months. PEPPERMAN[Microsoft attorney]: And IBM flatly rejected that proposal? NORRIS: Yes, we did. The settlement of the audit and the Windows 95 licence agreement were both signed on the same day: Windows 95 launch day - 15 minutes before the launch. Norris' deposition has brought to light some fascinating evidence about Windows royalty under-payment by IBM. In the Fall of 1994, Microsoft told IBM it wanted to conduct an audit of Windows sales. IBM had been saying publicly it had very good sales of OS/2 containing Windows licences, but Microsoft said it was not seeing this in the data that IBM reported. At the time there was also a certain amount of carpet bombing free copies of OS/2 going on. Microsoft claimed that IBM might have been under-reporting royalties for a couple of years. From Norris' perspective, there was no relationship between this allegation and his effort to negotiate a good price for a Windows 95 licence. Microsoft had decided to link settling the issue of the audit to IBM's Windows 95 licence negotiations, but Rick Thoman, an IBM VP, tried to get the audit issue de-linked. He wrote to Gates on 20 July and followed this with a conference call with Gates on 24 July 1995. Microsoft knew it was putting IBM under great pressure. Norris said: "A series of letters transpired back and forth, the net of which simply said: there's no reason to withhold the Windows 95 beta code, which you have begun to do because of the audit. The audit is unrelated to the Windows 95 license agreement. Please release the code." Pepperman asked Norris if he was aware that IBM ended up paying Microsoft $30 million to compensate Microsoft for under-reported royalties. Norris said he knew that IBM had offered $10 million in a settlement agreement, $5 million of which was to be held in escrow, as part of a move to speed up getting the beta code of Windows 95, and the licence. The escrow account was set up to give a measure of comfort against any under-reporting of Windows 95 sales, with interest and penalty payments being agreed in the contract should this happen. Pepperman said that Microsoft had ended up taking $30 million for what was claimed to be $50 million of under-reported royalties. Norris said he was unaware of this. Pepperman then asked Norris if he knew that an internal IBM audit had found that royalties were under-reported. Again, Norris said he was unaware of this. Pepperman indicated that the audit had taken ten months, and that a great deal of time had been taken up by IBM in negotiating a non-disclosure agreement with the auditors. Perhaps the most unexpected information was that, according to Pepperman, it was IBM procurement contracts manager Jim Miller who threatened in July 1995 to suspend negotiations of the Windows 95 licence until the audit was resolved. Norris confirmed that he had heard this too. Microsoft claimed to be upset at the discovery of the under-payment, but it could well be that it was pleased to have an excuse for making life difficult for its competitor. Pepperman asked "What was Jerome York's position at IBM at the time?" It was a question to which he clearly knew the answer, which was that he was CFO. Pepperman's follow up was to ask if Norris had heard in the Summer of 1995 that York admitted to Michael Brown, then CFO of Microsoft, that IBM's reporting system was outdated. York left IBM around this time, and Pepperman seemed to wish to float the suggestion that this was related. Pepperman did not know all the details, it seemed, since he asked Norris: "Did IBM fire the person who was determined to be responsible for the underpayments?" which suggested that it was an individual who had orchestrated the underpayments, rather than it being a deliberate policy by IBM. Norris said that he did not know. The details of this under-payment of royalties could have accounted in part for the presence of the large IBM legal team at the deposition. ® Complete Register trial coverage


Other stories you might like

  • Apple's latest security feature could literally save lives
    Cupertino is so sure of Lockdown Mode it's offering $2m to bug hunters to break it

    Apple's latest security feature won't be used by most of its customers, but those who need Lockdown Mode could find it to be a literal life saver.

    The functionality, coming with iOS/iPadOS 16 and macOS Ventura, dramatically shrinks an iDevice's attack surface by disabling many of its features. It's designed to protect the small number of Apple users who, "because of who they are or what they do, may be personally targeted by some of the most sophisticated digital threats, such as those from NSO Group and other private companies developing state-sponsored mercenary spyware," Apple said in a statement. 

    Lockdown, thus, effectively reduces the number of potential vulnerabilities spyware could exploit to compromise a device, cutting the possible routes into surveillance targets' kit.

    Continue reading
  • Has Intel gone too far with its Ohio fab 'delay' stunt?
    With construction unceremoniously underway, x86 giant may have overplayed its hand

    COMMENT The way Intel has been talking about the status of its $20 billion Ohio fab project, you would be forgiven if you assumed that construction on the Midwest mega-site has been delayed in light of Congress struggling to pass a large subsidies package that would support new American chip factories.

    When Intel delayed a groundbreaking ceremony for the Ohio manufacturing site two weeks ago out of frustration over the subsidies inaction, some headlines may have given you the impression the semiconductor giant was putting off construction entirely.

    However, an Intel spokesperson made it clear to The Register and others at the time that the start date for construction had not changed.

    Continue reading
  • Hive ransomware gang rapidly evolves with complex encryption, Rust code
    RaaS malware devs have been busy bees

    The Hive group, which has become one of the most prolific ransomware-as-a-service (RaaS) operators, has significantly overhauled its malware, including migrating the code to the Rust programming language and using a more complex file encryption process.

    Researchers at the Microsoft Threat Intelligence Center (MSTIC) uncovered the Hive variant while analyzing a change in the group's methods.

    "With its latest variant carrying several major upgrades, Hive also proves it's one of the fastest evolving ransomware families, exemplifying the continuously changing ransomware ecosystem," the researchers said in a write-up this week.

    Continue reading
  • What do you mean your exaflop is better than mine?
    Gaming the system was fine for a while, now it's time to get precise about precision

    Comment A multi-exaflop supercomputer the size of your mini-fridge? Sure, but read the fine print and you may discover those performance figures have been a bit … stretched.

    As more chipmakers bake support for 8-bit floating point (FP8) math into next-gen silicon, we can expect an era of increasingly wild AI performance claims that differ dramatically from the standard way of measuring large system performance, using double-precision 64-bit floating point or FP64.

    When vendors shout about exascale performance, be aware that some will use FP8 and some FP64, and it's important to know which is being used as a metric. A computer system that can achieve (say) 200 peta-FLOPS of FP64 is a much more powerful beast than a system capable of 200 peta-FLOPS at just FP8.

    Continue reading
  • Meta's AI translation breaks 200 language barrier
    Open source model improves translation of rarer spoken languages by 70%

    Meta's quest to translate underserved languages is marking its first victory with the open source release of a language model able to decipher 202 languages.

    Named after Meta's No Language Left Behind initiative and dubbed NLLB-200, the model is the first able to translate so many languages, according to its makers, all with the goal to improve translation for languages overlooked by similar projects. 

    "The vast majority of improvements made in machine translation in the last decades have been for high-resource languages," Meta researchers wrote in a paper [PDF]. "While machine translation continues to grow, the fruits it bears are unevenly distributed," they said. 

    Continue reading
  • Tracking cookies found in more than half of G20 government websites
    Sorry, conspiracy theorists, it's more likely sloppy webdev work rather than spying

    We expect a certain amount of cookie-based tracking on retail websites and social networks, but in some countries up to 90 percent of government sites have implemented trackers – and serve them seemingly without user consent. 

    A study evaluated more than 118,000 URLs of 5,500 government websites – think .gov, .gov.uk. .gov.au, .gc.ca, etc – hosted in the twenty largest global economies – the G20 – and discovered a surprising tracking cookie problem, even among countries party to Europe's GDPR and those who have their own data privacy regulations.

    On average, the study found, more than half of cookies created on G20 government websites were third-party cookies, meaning they were created by outside entities typically to collect information on the user. At least 10 percent, going up to 90 percent, come from known third party cookies or trackers, we're told.

    Continue reading

Biting the hand that feeds IT © 1998–2022