How MS tried to keep the lid on its OEM customers

Mid-98 the wonderful new flexible MS didn't seem that flexible at all...


MS on Trial In his written testimony and in court this week, Microsoft OEM chief Joachim Kempin argues that Microsoft is willing to be flexible over the software its OEM customers can install. The permission to modify the Windows 98 startup sequence granted to seven large OEMs in the first half of last year will also be granted to other OEMs on application. We covered this a little this morning (MS demo breaches own licence) - but the story from the first half of 1998 (just) is a little different. A short email exchange from late May early June lists five OEMs who are allowed to implement "an alternate first boot process." These are Packard Bell, Acer, Hewlett-Packard, Gateway and IBM. The list is from one Pete Peter, who stresses: "Remember this process is only to be offered on an exceptional basis to those OEMs that cannot utilise the registration and/or referral server process as delivered [in Windows 98]." Clearly general permission is not available at this point. The first break with Microsoft's restrictions had been offered to Gateway, in consideration of the fact that it was running its own ISP service. This clearly wouldn't operate sensibly via MS' referral server system, although sense doesn't necessarily change minds at Redmond. The other OEMs had climbed onto the bandwagon, and around about this time Dell, which hadn't yet, was complaining about being penalised for being a 'good citizen.' Kurt Kolb forwards Peter's message to Kempin, adding: "Reports coming in that other OEMs are now asking for the additional Windows Experience provisions we offered the OEMs below." He suggests permissions be granted "on a case-by-case basis." Kempin, who you'll recall has this week been saying this flexibility is available to all and sundry, responds: "I agree - no flood gate please, this needs careful monitoring knowing that some might use this to abuse it." ® Complete Register trial coverage


Other stories you might like

  • Google Pixel 6, 6 Pro Android 12 smartphone launch marred by shopping cart crashes

    Chocolate Factory talks up Tensor mobile SoC, Titan M2 security ... for those who can get them

    Google held a virtual event on Tuesday to introduce its latest Android phones, the Pixel 6 and 6 Pro, which are based on a Google-designed Tensor system-on-a-chip (SoC).

    "We're getting the most out of leading edge hardware and software, and AI," said Rick Osterloh, SVP of devices and services at Google. "The brains of our new Pixel lineup is Google Tensor, a mobile system on a chip that we designed specifically around our ambient computing vision and Google's work in AI."

    This latest Tensor SoC has dual Arm Cortex-X1 CPU cores running at 2.8GHz to handle application threads that need a lot of oomph, two Cortex-A76 cores at 2.25GHz for more modest workloads, and four 1.8GHz workhorse Cortex-A55 cores for lighter, less-energy-intensive tasks.

    Continue reading
  • BlackMatter ransomware gang will target agriculture for its next harvest – Uncle Sam

    What was that about hackable tractors?

    The US CISA cybersecurity agency has warned that the Darkside ransomware gang, aka BlackMatter, has been targeting American food and agriculture businesses – and urges security pros to be on the lookout for indicators of compromise.

    Well known in Western infosec circles for causing the shutdown of the US Colonial Pipeline, Darkside's apparent rebranding as BlackMatter after promising to go away for good in the wake of the pipeline hack hasn't slowed their criminal extortion down at all.

    "Ransomware attacks against critical infrastructure entities could directly affect consumer access to critical infrastructure services; therefore, CISA, the FBI, and NSA urge all organizations, including critical infrastructure organizations, to implement the recommendations listed in the Mitigations section of this joint advisory," said the agencies in an alert published on the CISA website.

    Continue reading
  • It's heeere: Node.js 17 is out – but not for production use, says dev team

    EcmaScript 6 modules will not stop growing use of Node, claims chair of Technical Steering Committee

    Node.js 17 is out, loaded with OpenSSL 3 and other new features, but it is not intended for use in production – and the promotion for Node.js 16 to an LTS release, expected soon, may be more important to most developers.

    The release cycle is based on six-monthly major versions, with only the even numbers becoming LTS (long term support) editions. The rule is that a new even-numbered release becomes LTS six months later. All releases get six months of support. This means that Node.js 17 is primarily for testing and experimentation, but also that Node.js 16 (released in April) is about to become LTS. New features in 16 included version 9.0 of the V8 JavaScript engine and prebuilt Apple silicon binaries.

    "We put together the LTS release process almost five years ago, it works quite well in that we're balancing [the fact] that some people want the latest, others prefer to have things be stable… when we go LTS," Red Hat's Michael Dawson, chair of the Node.js Technical Steering Committee, told The Register.

    Continue reading

Biting the hand that feeds IT © 1998–2021