You're one of today's lucky 10,000. It was huge news at the time. The FTC considered not allowing it and the acquisition got delayed for months while back and forth public debate raged.
Easy to forget all the big moves that happened recently, especially since there haven't been (afaict) any major changes to service. I forgot the other day that Sony had bought Bungie, though it'd be pretty memorable if Sony announced Destiny 3 as a PS5 timed exclusive.
Massive media/telecom/tech companies get passed around between other massive media/telecom/tech companies so much that regardless of how much you saw the news at the time, a couple of years later it's tough to remember "Now who is it that owns Warner Bros. currently? AOL? AT&T? Netflix? The sovereign wealth fund of Saudi Arabia?"
And Sierra. It would be amazing if MS released the source code to some of Sierra classic Hi-Res/AGI/SCI games, or the engines themselves.
IIRC, Al Lowe had retained copies of source code from the early Sierra days, and was planning to release some of it publicly a few years ago, but Activision shut him down. Maybe MS would be willing to reconsider that now that they're pursuing historical preservation.
I specifically checked if DirectInput from DirectX 5 already supports/provides USB HID devices, and it does! Granted, even then it was unlikely to encounter 8 USB devices, let alone HID devices in particular.
Because I felt like it :) Also works for multiple versions/patchlevels.
But yeah, with the info provided it should be patchable. It's a `push esi` though, where esi has to stay 0 for a few further usages, so it's a bit more than a one-byte patch. It also wouldn't fully resolve the OOB write in the rare case where you _do_ have 9+ game controllers connected.
This is pretty amazing, and I'm surprised in a sense by how few workarounds you've had to implement. It makes me wonder what Windows would look like if we had Win2K or Win7 with today's system APIs (for high DPI, increased security etc.)
I know Windows has made great strides in security, but I deeply miss the old Windows and this really hits home about how _little_ has fundamentally changed, or rather, how much the continuance of these APIs means today's Windows could be like old Windows, if MS wanted.
I came across Windhawk a couple of days ago here on HN, a system to patch Windows to look and behave more old-style; wow.
AFAIK they are all backed up. For the blogpost I used the DX5 SDK docs, DX7 SDK docs, and the MSDN Library from VS2005 (last version to include 9x information).
The VS2008 version purged all API information regarding pre-Windows 2000.
reply