If you’ve ever tried to run Scrivener on a Chromebook, you already know the pain. For more than seven years, posts across the web have documented half-working setups, broken fonts, unstable Wine configs, patchy remote setups, and outdated Linux hacks.
Good news: it is possible to run Scrivener 3 on ChromeOS properly, with FULL and permanent activation
To make this easier, I built an open-source Chromebook installer that handles the heavy lifting and fixes many of the long-standing issues people run into.
What the Chromebook installer does:
Installs Scrivener 3 on Chromebook using Crostini
Runs Scrivener offline in a stable Wine environment
Fixes font issues
Avoids outdated beta Linux workarounds
Allows full, permanent Scrivener activation
Adds a launcher menu shortcut (penguin icon)
Automatically detects screen size and launches Scrivener fullscreen (without breaking)
Detects Scrivener-installer.exe in the home directory
Enables a working spellchecker
…and more
I won’t over-explain it here — the video walks through everything and includes the installer link:
Well as there are a fair number running Windows Scrivener under Wine on Linux, and I’ve used it under Crossover (Wine with a GUI) for many years, with a stable Wine installation on Chromebook is there any reason there could be a problem?
I wonder about the offline and permanently activated combination. It will work for a while. And revert back to trial eventually. But maybe the Windows version is different. Just curious.
That is a perfectly valid usage on both platforms, I can attest from experience. Back when I used the Mac, I used Little Snitch as a tool to protect privacy. I would pretty much “firewall” all software that did not have the sole purpose of doing something on the net, like an RSS reader. After activation, Scapple and Scrivener could have been considered permanently offline, in my case. In practice I would sometimes open a port to test software update, but no other traffic would have gone out.
For the Windows version, the copy on my Win10 VM probably hasn’t seen the live net since it was activated, years ago. As with the Mac, I do indeed need to test live functions now and then, but unlike the Mac, with a VM I always revert it back to snapshot on close, whenever doing so. It’s more about Win10 than anything else. Why waste money on an antivirus program, or expose an old and vulnerable OS to the net, when you don’t really need to?
Neither of these conditions are quirks or unintended. The software, by policy, is deliberately designed to respect that not everyone wants, or has the ability, to be constantly online.
I’m often wrong, but this is one of those cases where I’m glad I was wrong.
Somehow my brain keeps dumping the “… but that was a bug”-part of the story. Guess I can stop waiting for it to happen eventually now. (I’m also team “less Internet is more”.)
