11–20 of 25 posts
A20 bugs were still with us until at least 2009, when I tripped over one: https://mjg59.livejournal.com/118098.html . I love the visualisations in this post, it makes it much clearer what's actually going on.
This is one hell of a rabbit hole...
What really caught my attention is how this marketing snippet highlights the tension between authenticity and polish in gaming culture. Xbox was trying to hit that sweet spot, it wanted to feel edgy and gamer-friendly but the copy ended up sounding like corporate speak.
[flagged]
What really caught my attention is how this marketing snippet highlights the tension between authenticity and polish in gaming culture. Xbox was trying to hit that sweet spot, it wanted to feel edgy and gamer-friendly but the copy ended up sounding like corporate speak.
This is a bot, right? Same with all the new accounts commenting completely unrelated things?
Still, Halo 2 legendary is unmatched.
For those wondering what software depended on A20 wraparound, there is this interesting series of articles: https://www.os2museum.com/wp/who-needs-the-address-wraparoun... https://www.os2museum.com/wp/the-a20-gate-it-wasnt-wordstar/ https://www.os2museum.com/wp/exepack-and-the-a20-gate/ https://www.os2museum.com/wp/the-a20-gate-fallout/
Something this article doesn't mention is how the A20 gate was toggled: by writing to registers on the keyboard controller . I was always thought this was a completely inexplicable design choice, until I started working in embedded, working with hardware engineers, and having to go through schematics myself. I now entirely understand the choice of wanting to minimize the redesign work and going with the one free pin…
[flagged]
[flagged]
As an FYI to others, it appears this account (and others in this thread) might be a bot.