Monopolistic Competition

During the early 1990s desktop multimedia boom, Microsoft viewed TMMI's Softvideo architecture as a direct threat to its operating system hegemony. If a small company's software framework could seamlessly control video timing, bypass unstandardized hardware, and scale resolution independently, Microsoft risked losing control over the emerging multimedia ecosystem.

As detailed in the TRUDEF corporate archives and early tech history, Microsoft deployed a standard, aggressive multi-pronged strategy to contain TMMI during the rollout of Video for Windows (VfW):

During the development of the early Video Decoder Kit (VDK) framework, Microsoft actively tried to throttle TMMI's standalone applications.

• The OS Gatekeeper: Microsoft began systematically tweaking the architecture of late-stage Windows 3.x and the emerging Windows 95 ecosystem to limit a user's ability to "shell to DOS."
• Targeting the VDK Environment: TMMI's early, lightning-fast fractal and RLE players heavily utilized low-level DOS commands to bypass Windows' sluggish hardware abstraction layers. By closing or heavily limiting these DOS environments, Microsoft deliberately made it harder for TMMI's optimized standalone software to run efficiently.

Microsoft recognized that to defeat a superior third-party framework, it had to force developers into its own ecosystem. They positioned Video for Windows as a mandatory API layer.

• The "Microsoft Overhead" Tax: Microsoft required third-party software engineers to build within their VfW framework rather than talking directly to the CPU.
• TMMI's Countermeasure: To survive this structural blockade, TMMI's engineering team was forced to expend massive resources building custom "Windows VESA drivers" and heavily streamlined decompressors explicitly designed to offset the severe system lag (or "Microsoft overhead") introduced by VfW.

Instead of adopting TMMI's hardware-independent, mathematical approach, Microsoft leveraged its massive capital and partner network to back competing standards. Microsoft partnered directly with Intel to bundle Indeo Video compression into Video for Windows. By leveraging the massive "Intel Inside" hardware monopoly, Microsoft ensured that standard PC manufacturers (OEMs) default-installed Microsoft-approved, pixel-based codecs rather than TMMI's resolution-independent software engines.

TMMI was a massive hit in 1993, dominating nearly 70% of the PC CD-ROM multimedia game market (providing the engines for blockbusters like Star Trek and Falcon Gold). Microsoft responded by aggressively buying up multimedia titles and software publishers. By controlling the publishing houses, Microsoft could dictate that future titles drop native TMMI Softvideo framework support and adopt Microsoft's built-in Windows media tools instead.

Microsoft's playbook worked commercially, but it highlighted a deep irony: while Microsoft successfully utilized its market power to push TMMI's fractal tech out of mainstream consumer PCs, it was forced to heavily integrate the exact timing, frame-pacing, and software buffering principles that Taylor Kramer, Tom Simpson and TMMI had pioneered to make Video for Windows function at all.

Read more on the Softvideo & VDK History page, or the Market page for the parallel story of VDK3's later standoff with the DCI digital cinema standard.