The MS campaign to rein-in Intel multimedia development

Engstrom admits MS need to "own all the driver software down to the metal"


MS on Trial In the Microsoft trial, Eric Engstrom is being used to challenge the account of Microsoft's Intel relationship, as told by Steve McGeady and Intel's documents. Strangely, McGeady's name was never mentioned: he has evidently become a non-person. An Intel internal email from Gerald Holzhammer on 13 April 1995 summarised a face-to-face meeting with Engstrom, Carl Stork and Marshall Brumer of Microsoft. He concluded that Microsoft wanted to own the drivers in Windows 98; that nobody but Microsoft was qualified to do good driver software; that Microsoft would not collaborate on NSP; and that Microsoft had "completely missed the boat" on developing a compelling state of the art media subsystem for Windows 95", according to a confession by Carl Stork. Engstrom sent a status report email on 26 May 1997 about the "collaborative" multimedia efforts of Microsoft and Intel. It was very revealing: "The goal for our interactions with the Intel Architecture Labs is that all their efforts are neutral or positive for our strategic mm [multimedia] initiatives. I think it is unlikely that we will achieve 100 per cent of this goal". It turned out that Microsoft was obsessed at this particular time with collaboration between Sun and Intel over Java-based competing multimedia standards - the MPEG4 specification. Engstrom's goal: "Intel to stop helping Sun create Java Multimedia APIs, especially ones that run well (ie native applications) on Windows". Engstrom was unhappy that every IAL partner slide referred to Sun. His proposed actions included Microsoft stopping giving any help to Javasoft wherever Microsoft agrees to ship Intel technology in DirectX media. Microsoft was concerned at Intel's efforts "to do multimedia on Intel-based Windows platforms" such as RSX (3D sound), RD (sprite engine), video playback extensions, and procedural textures generally. So far as large model management was concerned, this was competitive with "our" HP Jupiter technology. Engstrom ruefully noted that Intel had "a rather large evangelist force that is willing to use monetary incentives." Whatever next? It could not have helped Microsoft that Chrome (the multimedia browser) was projected to Intel as "the big carrot", in view of what subsequently happened to Chrome. Engstrom said in his testimony that Intel wanted some software that would produce special effects to make its processors look good, but Microsoft just pressed on with pressuring Intel to stop software development. Rather than admit that Sun and others were important Intel partners, Engstrom puts Intel's behaviour down to Microsoft "not paying enough attention to Intel" rather than recognising that Microsoft's lack of expertise and arrogance might be part of the problem. Microsoft needed "to own all the driver software down to the metal" Engstrom agreed, because in 1995 "we were trying to move the games market forward. They had been basically stuck using very similar technologies for ten years because all of the advances in Windows hadn't helped games at all. So, the purpose of the DirectX technology was to make the Windows environment and Windows hardware acceleration accessible to games. At that time, given the speed of the processors and the hardware state, you wanted the game to know exactly what was happening. If there was a bunch of code running in there that the application didn't know about and couldn't test against, you would get bizarre behaviour in the game. It would stop being realtime." Surely there is no relationship between Intel's friendliness towards Gates' arch-enemy Sun and Microsoft's violent reaction against Intel producing software that Sun could use? ® 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