Windows 1.0 and the WinAPI, 40 years later – OSnews
Home > Windows > Windows 1.0 and the WinAPI, 40 years later<br>How far can you get, application development-wise, by using only the original APIs from Windows 1.0, and only whatever came included by default with Windows 1.0?<br>I finally decided to write an application for the very first version of Windows and see how different the modern WinAPI really is from its earliest versions. Windows 1.0 came out back in the mid-1980s – the era of 16-bit processors, MS-DOS, and cooperative multitasking. At first glance, you might think it has almost nothing in common with modern Windows, but when you look specifically at the application API, that’s where things get interesting.<br>I wanted to see how far it would be possible to go using only the capabilities of the first version of Windows. I didn’t want to just make a minimal example with a window and a menu, but a small, complete application with graphics, keyboard input, timers, and constant redrawing. For this experiment, I chose Xonix – a simple yet surprisingly addictive game.
↫ Stanislav Safronov<br>It turns out that surprisingly, despite the 40 years and massive changes since Windows 1.0, there’s still a lot that feels recognisable. It’s also remarkable that the code Safronov ended up with ran on every version of Windows from 1.0 to 10, but sine it’s a 16 bit application it no longer works on Windows 11. It also had a hiccup on Windows 95, but he suspects that’s an issue in the 16 bit subsystem in Windows 95, and not in his code.<br>The code’s available on GitHub.
About The Author
Thom Holwerda
Follow me on Mastodon @[email protected]
3 Comments
2026-06-15 12:07 pm
kurkosdr Yeah, win16 won’t work on x64 Windows. Not just Windows 11 but also all x64 versions of Windows.<br>Win16 is one of the things "XP Mode" did for you on x64 Windows (n addition to DOS apps and 32-bit device drivers), before Microsoft decided that we don’t need compatibility anymore and dropped "XP Mode" from Windows 8 onwards.<br>As an aside, Microsoft could have made win16 work natively on x64 WIndows (like they did for win32), they just couldn’t be bothered.
Log in to Reply
2026-06-15 12:18 pm
Alfman verbose=1 kurkosdr,<br>Yeah, win16 won’t work on x64 Windows. Not just Windows 11 but also all x64 versions of Windows.
I agree the article should be more explicit about this. Binary compatibility doesn’t really work unless you go out of your way to install a 32bit OS. AMD designed this limitation into "AMD64" at the very beginning. Unless your ok with running a 32bit OS, the hardware stopped supporting 16bit native modes decades ago.<br>As an aside, Microsoft could have made win16 work natively on x64 WIndows (like they did for win32), they just couldn’t be bothered.
Microsoft could emulate 16bit software, but it was AMD that dropped native support 16bit in hardware from 64bit operating systems, which is what all major operating systems are these days.
Log in to Reply
2026-06-15 12:35 pm
sukru Alfman,
Microsoft could emulate 16bit software, but it was AMD that dropped native support 16bit in hardware from 64bit operating systems, which is what all major operating systems are these days.
Yes, people skip this part, but AMD basically said: "you can have 64/32 bits or 32/16 bits but not both"<br>Just for this reason Microsoft had to go to great lengths to emulate 16 bit installers on 64 bit system. They basically had a specialized parser for Install Shield and others and swap them out for something that works without the user realizing.
Log in to Reply
Leave a Reply Cancel reply<br>You must be logged in to post a comment.
Donate to OSNews
You can also:<br>Become a Patreon<br>Buy OSNews merch
Search OSNEWS
OSnews Accounts<br>Create Account<br>Login
Topics<br>TopicsSelect Category.NET3DAcademic OSesAMDAmiga & AROSAndroidAppleBenchmarksBSD & DarwinBugs & VirusesClown carComicsDatabasesDebianDesktop environmentsEditorialFedora CoreFinanceFreeBSDFuchsiaGamesGeek stuffGeneral DevelopmentGenodeGentooGifts, ContestsGnomeGoogleGraphicsGTK+HaikuHardwareHealthHumorIBMIn the NewsIntelInternetInternet ExplorerJavaKDELegacy OSesLegalLinspireLinuxmacOSMandriva, Mandrake, LycorisMicrosoftMobileMonoMorphosMozilla, GeckoMultimedia, AVNetBSDNovell and XimianOfficeOpen SourceOpenBSDOpenStep, GNUstepOperaOracle and SUNOriginal OSNews InterviewsOS NewsOS/2PC-BSDPodcastsPrivacy, SecurityQNXQtReactOSRed HatRedox OSRetro computingRISC OSRumorsSCOServoSGI and IRIXSkyOSSlackware, SlaxSolarisSponsorSuSE, openSUSESyllable, AtheOSTechnofascismUbuntuUnixWaylandWeb 2.0WindowsWirelessXfceZeta
Related Posts
What the heck is happening to Windows?
February 10, 2014 •<br>114 Comments
Microsoft to add virtual touchpad to Windows 10
November 9, 2016 •<br>13 Comments
Risk Mitigation for Legacy Windows NT 4.0 Systems
January 3, 2007 •<br>23 Comments
Microsoft launches new WinUI website, listing the advantages of the platform
March 16, 2020 •<br>7 Comments
64% of MS Vulnerabilities...