December 4, 2025
Mute the boom, get more boom
Why WinQuake exists and how it works
WinQuake’s secret: smoother fights on Win95—if you kill the fancy sound
TLDR: WinQuake was built to make Quake run better on Windows, fix online play, and support Windows NT. Fans loved the nostalgia and debated modern tools, while the hottest takeaway was that turning off “fancy” audio made it faster—proof that simple can beat shiny when your CPU’s struggling.
Quake diehards lit up the comments like rockets after a breakdown of why WinQuake existed: the original DOS version ran faster than Windows 95, so id shipped a Windows-only build to claw back speed, fix online play, and work on Windows NT. The real jaw-dropper: the fastvid mode (which actually disables the newer DirectSound audio) delivered the best frame rate, proving the crowd’s favorite systems lesson—when your CPU’s gasping, “fancier” doesn’t mean “faster.” One nostalgic fan relived the grind of tuning Windows 95 for LAN-less deathmatches, while another dropped a modern hot take—this stuff is what SDL (a cross-platform toolkit) now abstracts, though devs chimed in that 90s Windows quirks were a whole different boss fight. The vibe? A split between map-tool modders cheering the glow-up and tech heads chuckling that the quickest fix was basically “mute the boom to get more boom.” There were jokes about WinQuake’s modes sounding like cheat codes—max, fast, verysafe—and a meme-y chorus of “WinQuake: it just works (without sound).” When the article mentioned Microsoft calls over “near pointers” breaking on NT, commenters turned it into a running gag: “NT stole our frames,” “DirectSound ate my CPU,” and “fastvid isn’t about video? Peak 90s chaos.”
Key Points
- •quake.exe runs about 25% slower under Windows 95 (38 fps) than directly in DOS (48 fps) due to DOS BOX virtualization overhead.
- •WinQuake provides direct access to Windows networking via winsock.dll, avoiding the Mpath bridge used by quake.exe.
- •WinQuake targets Windows NT compatibility; DJGPP’s DPMI client and near pointers fail under NTVDM, motivating a Win32 build.
- •Benchmarking on a Pentium MMX 233MHz with Matrox Mystique shows WinQuake modes reaching up to 45.0 fps, within ~6% of DOS performance.
- •WinQuake’s modes toggle backends (DirectInput, DirectSound vs WinMM, DirectDraw vs DIB); -wavonly (WinMM) correlated with higher frame rates than DirectSound.