Microsoft Word for Windows 1.1a, Native X64 Port | Hacker News Reader

Microsoft Word for Windows 1.1a, Native X64 Port

github.com

174 pointsBruceEel76 comments

Back in '85-6 I developed training for USDA (using Dan Bricklin's Demo) for a curses version of Word 5 that ran on 3B2s with SysV v2. I'd be very happy to see that ported to Linux or one of the BSDs.

In fact, I'd love to see both Word and Excel '98 on one of my workstations. IMHO things went South after that.

I had to use Windows and Office off and on with clients up to 2010 and I'm sure that Excel provided some important edge-case functionality after '98, but for me the UI went steadily to sh*t.

FWIW, Office 97 works perfectly under Wine, so there's nothing stopping you from continuing to use it, well, except maybe the lack of support for modern OOXML formats. An alternative could be Abiword and Gnumeric, both are super lightweight and retain the classic Office 97-style UI and support OOXML formats (though somewhat limited compared to LibreOffice).

Microslop’s free “Office format converters” pack from Microsoft adds support for new office formats to old office versions. Read and write.

> adds support for new office formats

Barely... I'm using them with Office 2003 and most of the time it's a garbage conversion.

LibreOffice will do it better.

office 2003 (for word + excel at least) were peak - after the ribbon it all went downhill

I just installed my copy in a new Win10 VM. With the added OOXML support pack, there's nothing left wanting.

Does the activation still work for these are do you have to use a hack to get them running? I still have a TON of older Office 2003 licenses, I'd love to go back. I've hated modern Office with the ribbon for half my life now.

Please don't. There are so many unpatched exploits for old Office... opening any document could trash your whole system or silently steal information from you.

Just like a current Office does?

maybe so but that would imply the end user is opening sketchy files - most of the time these products are for low risk files

The product keys still work. You can skip online activation. Only annoyance is needing to run once as admin to make the EULA acceptance write to the registry.

I have a stockpile of patches that I preserved a while back that are not readily available today.

https://lock.cmpxchg8b.com/wordperfect.html describes getting the UNIX release of Word Perfect running on modern Linux. There was a SCO release of Word in 1990, so plausibly that could be fudged into a similar setup?

> Dan Bricklin's Demo

There's a name I haven't heard in a while. During our undergrad (90s), we used it to mock up UI designs for one of our early courses.

If you need something much easier then you can run Word 2.0 (well any Windows 3.0+ 16bit app) easily on x64 Windows 10/11 https://files.catbox.moe/dy4bqy.png

All you need is this https://github.com/otya128/winevdm

Tried to build it but it references a `cmake/GenerateMenuHelpHeader.cmake` that seems to be absent from the repository?

A screenshot or two would have been nice

Might the lack there of be copyright related? I guess not something you want to burn your hands on.

The original source for WfW 1.1a was open sourced (I realize that doesn't mean there isn't copyright, but it's unlikely to be the reason that there are no pics):

https://github.com/danielcosta/MSWORD

The point of open source is to address and concerns around copyright. And this source is not open source by the definition most people use when they refer to “open source”. It’s still proprietary but source available.

However I will say, this source is unlikely to be useful to anyone beyond academic curiosity. So for the purposes of this project, the source license is “good enough”.

We should care about Microsoft's licenses exactly as much as Microsoft cares about ours.

Only if you have a lawyer department as large as theirs.

But to be fair/realistic, as an individual, I've never worried about their licenses (for myself, my friends, and family). The only time I did was when installing their software in professional/commercial contexts, that's where they do most of their enforcement as far as I know... and only when the scale is egregious.

I don't have a lawyer department. What I do have is a server paid in XMR.

More concretely, Microsoft's license [0] gives you at most one of the four essential freedoms:

0. Freedom to run for any purpose? No.

1. Freedom to modify the program? Maybe; Microsoft can revoke it without cause at any time.

2. Freedom to distribute unmodified? No.

3. Freedom to distribute modified? No.

I'm using the free software definition [1] because it's simpler and clearer than the open source definition [2], which is usually considered mostly equivalent in practice, but as far as I can tell Microsoft's license satisfies zero of the latter's ten criteria, apart from perhaps non-discrimination and technology-neutrality. Most of the criteria of the open source definition have to do with distribution, which is not allowed by Microsoft's license.

[0] https://computerhistory.org/blogs/microsoft-research-license...

[1] https://www.gnu.org/philosophy/free-sw.en.html

[2] https://opensource.org/osd

The license isn't really open source. It's more like source available. Non-commercial use only.

https://github.com/danielcosta/MSWORD/blob/master/LICENSE

says

You may use, copy, compile, and create Derivative Works of the software, and run the software and Derivative Works on simulators or hardware solely for non-commercial research, experimentation, and educational purposes. Examples of non-commercial uses are teaching, academic research, public demonstrations, and personal experimentation. “Derivative Works” means modifications to the software, in source code or object code form, made by you pursuant to this agreement. You may copy and refer to any documentation provided as part of the software. You may not distribute or publish the software or Derivative Works. You may not use or test the software to provide a commercial service unless Microsoft permits you to do so under another agreement. You may publish and present papers or articles on the results of your research, and while distribution of all or substantial portions of the software is not permitted, you may include in any such publication or presentation an excerpt of up to fifty (50) lines of code for illustration purposes.

It’s interesting that the license says “You may not distribute or publish the software or Derivative Works.”

There is now a published GitHub of a derivative work.

There is a screenshot in the original source code release: https://computerhistory.org/blog/microsoft-word-for-windows-...

Direct link: https://computerhistory.org/wp-content/uploads/2019/08/ms-wo...

Versus the port: https://cdn.neowin.com/news/images/uploaded/2026/08/17861716...

There are pics from the developer in this article (not sure why he neglected them in the README):

https://www.neowin.net/news/developer-ported-word-for-window...

Wow, it really looks like Win 10/11. Microsoft is back to the roots now. But Word 1.0 even has 3d GUI elements. They must have had impressive computers back then.

It’s mere decades ago!

CTL3D.DLL .. I remember installing Office for Windows 3.1. It would update this system DLL and make the UI of the entire system look more 3D.

https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2F...

I'm pretty sure it was an opt-in thing for individual programs, if an app didn't intentionally use it they kept the old look.

I've always thought that it's a bit of an undocumented and slightly forgotten bit of Windows 3.1, most things on the internet only show the flat style. I guess people doing retro things often only mess around a bit with the base OS, and don't really install things like Office 4.x on top of it.

so true - modern windows has no contrast between windows - so terrible

Top-left window icon looks garbled. A porting bug, maybe?

I think it's just that 16x16 icons didn't become a thing in Windows until Windows 95, and so older apps don't supply one. Windows will then scale down the 32x32 icon instead, and it's never really done it that attractively, and I suspect the black and white nature of this icon really suffers.

WinWord 2 or maybe 6 had everything I ever needed.

Should also add disk space to the requirement list.

People will be shocked when they realize word didn’t require gigabytes…

how complicated would a port to linux be ?

Just use WINE?

Afraid 16bit Word versions have a "Garbage" rating on Wine.

I guess I misunderstood. It was ported to 64bit I thought

was my impression as well

A native Linux application would be preferable, even if it does work with WINE (which I don't know... yet).

Win32 is Linux's only stable ABI.

A fair statement, but a stable ABI is only needed when you don't have the source. Seeing as most of the value proposition of Linux is that having the source is good, I find no fault in an unstable ABI.

Source available is of little use for many of the current breed of languages and libraries. Even standard C support is starting to break down as incompatible "standard" newC is being pushed because some C++ guy didn't like K&R function definitions.

Linux's remarkably stable kernel ABI is the only reason we can still use a lot of unbuildable dependency hell stuff on Docker containers.

> a stable ABI is only needed when you don't have the source

> A stable ABI is only needed when you don't have the source or you don't know enough C to fix incompatibilities with every new version.

There, I fixed it for you.

That is mixing up a stable ABI vs a stable API.

OpenBSD is sort of the poster child here, They notoriously do not have a stable ABI, I would not want to try and ship closed source software on obsd, it would be an absolute nightmare. But their API is very stable (insert counterexample of the recent pledge change here)

An interesting side effect of obsd changing their ABI fairly often is they are good at it(add comment about this is because it is a small self contained system with few users here), in Linux land an ABI change is a nasty, messy, multi year process with much wailing and gnashing of teeth, for obsd, it just happens. To misquote Raul Julia in Streetfighter "For you, the day the ABI changed was the most important day of your life. But for me, it was Tuesday.

It's the compiler too. I recently found out that kernel 6.6 can't be compiled by gcc 15. So, even if you have the source, unless it's extremely simple, at some point the current toolchain will refuse to build it.

Winemaker + winegcc.

This was the first thing that crossed my mind when I read about this port. It's heartening to find out I'm not the only one!

I prompted Claude Opus 5 (I don't really have the Fable tokens to spare) to do just that (via winelib). It's gotten to the point where it opens, runs for three seconds, and abruptly exits.

edit: got it running but a ton of things are do-nothing, and the fonts are completely rubbish. Not really worth posting ATM, but I'll see if it can fix things further by running the UI tests and telling it some of the things that don't work...

(That it was able to build and run at all with just a few prompts is a HFS moment, though!)

An interesting thing that came up is that MSVC uses 32-bit longs instead of 64, so a pure gcc/winelib build is another level of 64-bit porting.

Claude then suggested using mingw instead, which makes sense...

Cool!

No compiled binary is available?

If you’re the target audience you don’t need one.

>This project is a fully working native Windows x64 port of Microsoft Word for Windows 1.1a, whose historical codename was Opus.

Not to be confused with the Anthropic LLM model Opus - what was once an old codename is as good as new once again!

It’s a common word amongst people with even a bit of erudition. In truth, using it for any kind of software is overusing it.

For erudites Word is a much better name. We seldom use that verbum.

Would be ironic if Claude Opus was used in making this port. IMHO the README does have a bit of LLM smell to it.

I came here to say that. Though not in a bad way; the economics of what is possible but practical/impractical changes greatly with LLMs, and I suspect and hope we will be figuring out the ramifications for a while.

Agreed... I suspect we're not too far off from being able to say "port this Win16 application to Win64" if we're not there already... and most of it will be harness improvements!

Check in the github src directory.

What should one check for?

And not to be confused with its plural form "opera".

the Romans, btw, knew two kinds of labour: labor, -is the laborious one (see ?), and opus, the achievement

The Oracle corporation would like to speak to you about the name of their property management system.

(Also some Norwegians and a Web browser?)

Indeed the name of the art form is just Italian for "work".

Also, a direct cognate with "operate", "operation", etc.

Wow, TIL.

“Opus” is/was a lot of things: https://en.wikipedia.org/wiki/Opus#Computing

My first guess (and probably the first guess of many of the old school nerds) was that the MS Word codename is from Opus the penguin from Berkeley Breathed's Bloom County comic strip and that seems to be correct.

High five for anyone who still remembers the brief Bill the Gates arc in the comic or the Banana Computer parody ad of Apple starring Gene Simmons (https://computerhistory.org/blog/the-banana-junior-6000-comp... , about halfway down the page).

Reply on news.ycombinator.com