>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!
And not to be confused with its plural form "opera".
Microsoft Word for Windows 1.1a, Native X64 Port
71–80 of 81 posts
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#72Re: Microsoft Word for Windows 1.1a, Native X64 Port
#73Earlier quoted context omitted.
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.
Linux's remarkably stable kernel ABI is the only reason we can still use a lot of unbuildable dependency hell stuff on Docker containers.
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#74People will be shocked when they realize word didn’t require gigabytes…
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#75Earlier quoted context omitted.
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.
Barely... I'm using them with Office 2003 and most of the time it's a garbage conversion.
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#76Earlier quoted context omitted.
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.
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#77Earlier quoted context omitted.
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.
> 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.
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#78Earlier quoted context omitted.
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.
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#79Earlier quoted context omitted.
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.
Re: Microsoft Word for Windows 1.1a, Native X64 Port
#80Earlier quoted context omitted.
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.
> 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.
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.