- Published on
Microsoft Word for Windows 1.1a, Native X64 Port
- Authors

- Name
- DeepHorus
A software developer has released a native x64 port of Microsoft Word for Windows 1.1a, bringing the early 1990s word processor to modern 64-bit Windows systems. The project, hosted on GitHub by user jmarshall23, compiles the original Word source code and resources alongside modern replacements for 16-bit assembly, segmented-memory, and Win16 platform boundaries. The result is the original application and user experience running as a 64-bit Windows executable, not an emulator or a reimplementation using a modern editor control.
Microsoft Word 1.1a, historically codenamed Opus, was a foundational version of the word processor. The port uses Visual Studio 2022 with Desktop development for C++, a Windows 10 or 11 SDK, CMake 3.25 or newer, and PowerShell. Build instructions are straightforward: clone the repository, configure the x64-debug or x64-release CMake preset, and build from the command line. The generated solution file can also be opened directly in Visual Studio.
The project includes a comprehensive test suite covering the ported x64 runtime, original Word data structures, command tables, process startup, and automated UI workflows such as typing, selection, formatting, dialogs, and saving. The port translates 16-bit x86 assembly entry points to fixed-width C or C++, maps segmented and double-indirect memory handles to an x64-safe native runtime, and adapts Win16-specific startup, messaging, graphics, file, and resource behavior to current Win32 APIs. Original command, dialog, cursor, bitmap, and other generated assets are rebuilt by native host tools as part of the CMake graph.
This project matters because it preserves a piece of computing history, allowing modern users to experience an early Microsoft Word without relying on emulators or virtual machines. It also demonstrates a practical approach to porting legacy 16-bit software to 64-bit architectures, which could inform similar efforts for other historical applications. The developer emphasizes that the original C and resource files remain the authoritative implementation, with the port adding only the platform work needed to run safely on 64-bit Windows.
While no external reactions are included, the project is likely to appeal to retrocomputing enthusiasts, software historians, and developers interested in low-level porting techniques. The historical source files retain their original Microsoft and third-party copyright notices, and the repository does not currently include a top-level license file, so users must review applicable rights before redistributing source or binaries.
Looking ahead, this port could serve as a model for bringing other legacy Windows applications to modern platforms. The test suite and clear build process make it a valuable educational resource. As the project evolves, it may attract contributions that add compatibility improvements or additional documentation, further extending the life of a landmark piece of software.