KeyNote NF

No Screenshot

Submit Screenshot

Released April 1st, 2024.

Application Details:

License: Free to use
Votes: 3
Latest Rating: Silver
Latest Wine Version Tested: 9.7

Maintainers: About Maintainership

Free Download .exe installer available on Github

Test Results

Selected Test Results

What works

90% of functionality works:

  • Even minimize to tray & check for updates works
  • It's easier to list what doesn't work.

10% of broken functionality boils down to:

  • Scrollbar issue in text content area (scrollbar can visually become out of date when switching between tree nodes, clicking the scrollbar will correct the visual.)
    Update: wine 9.5, keynote, and winetricks result in the scrollbar issue happening much less!
    (Needs further investigation, it seems new wine has come up though so I'll test against that.)
  • Insert Images (preexisting images will display correctly, but you can't add new ones.)
  • Spell Check

What does not

2 Noticeable Issues:

(If all Noticeable issues were fixed, the app compatibility could change from Silver to Gold.)

  • Scrollbar (Visual Issue): 
    When switching between tree nodes, the scrollbar in the In the text content area
    often becomes out of date. Clicking the scrollbar fixes it.
  • Can't insert Images:
    If you copy paste images, or use the File --> Insert --> Picture...
    (the dialog will show up, but the image won't show in the app.)

    Personally I think many users of KeyNote are probably used to avoiding images to
    avoid bumping up the file size, as when the file gets bigger than your disk write
    speed, you can see lag during saving, which happens frequently to avoid data loss.
    So I consider this a nice to have, but I don't think it's commonly used.

3 Not Fixable, but Ignorable Issues:

  • System Properties Invalid parameter:
    (This is a rarely used / useless feature that's easy to avoid)
    [Top Menu] --> [File] --> [Properties] --> (File Properties Windows Opens) -->
    [System] --> (Popup mentioning: Invalid parameter, OK) (you can just close it)
  • Insert Object does nothing:
    (This is a rarely used feature that won't be missed)
    [Top Menu] --> [Insert] --> [Object] --> (nothing happens) (the other items trigger a pop up dialog)
  • Spell check gives error:
    (This would be nice to have, but not having it isn't a big deal.)
    [Top Menu] --> [Note] --> [Check Spelling] --> (Popup mentioning:
    Unable to initialize MS Word (0): OLE error 800401F3, ProgID: "Word.Application", OK)
    (you can just close it)


Issues fixable with workarounds:

See the "HowTo / Notes section" for:
General Installation Tips on how-to avoid, fix, and work around known issues.

  • Missing Fonts (avoidable, a permanent fix exists)
  • Black boxes covering up parts of the interface (avoidable, a permanent fix exists)
  • User Interface can appear to be frozen when it's not (easy to avoid and easy to work around if encountered)
  • How to install in a way that you can see pre-existing images.
  • Scrollbar visual issue (annoying wine bug, a workaround exists)
  • Windows Hypervisor Tips to avoid performance issues (for anyone testing Linux)

What was not tested

Rarely used file import / export, and encryption capabilities.

I didn't tweak the default settings much. I tried to test how well the default functionality worked.

Hardware tested


  • GPU: Intel
  • Driver: open source

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowopenSUSE Tumbleweed (rolling release)May 02 20249.7Yes Yes YesSilverChristopher McGrath 
CurrentopenSUSE Tumbleweed (rolling release)Apr 03 20249.5Yes Yes YesSilverChristopher McGrath 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show open bugs

HowTo / Notes

Notes for Windows Users using a Hypervisor to test out KeyNote NF on Wine on Linux.

It's common to test out a Linux Distro in a VM before committing to a bare metal install.

If you are a Windows user who is interested in testing out KeyNote NF on Wine on Linux, then you should know that there is a recommended hypervisor to use for testing purposes: 

  • ALL Hypervisors that support Hypervisor Host to VM Guest based copy paste:
    • Recommendation: (It helps avoid potential copy paste errors related to text encoding.)
    • Load this webpage from within the VM Guest. Then copy paste the recommended commands from within the Guest VM. (This will result in a Linux to Linux copy paste.)
    • In other words, avoid the scenario of having this page open in a Windows Hypervisor Host, and copying from this webpage on Windows, into a terminal on Linux VM. (Note it'll actually work most of the time, just not 100% of the time, so the goal is to avoid unnecessary debugging.)
  • VMware Workstation Player - recommended Hypervisor:
    • It's free to download, install, and use for non-commercial use.
    • It's offers the best UX (User Experience):
      • Performance isn't as good as a bare metal install, but there's no significant lag.
      • You can bidirectionally copy and paste, both files and text between the Windows Hypervisor and the Linux Guest VM.
      • When you resize the Hypervisor application's "host window", the Linux guest VM will dynamically resize:
        • The guest VM's desktop resolution.
        • Any application windows running on the guest VM.
    • I've seen a rare stability issue specific to this hypervisor: 
      • By rare I mean about once every 2 days, KeyNote NF on wine and part of the Linux OS will freeze/lock up to a degree that the VM must be restarted to resolve it.
      • So data loss can occur in this scenario, it can be partially mitigated by changing Keynote NF's auto-save frequency from 10 min to 2 minute.
    • Important Tip: 
      • If you run a OpenSUSE VM in VMware Workstation Player, it'll prompt you to install VMware Tools (for guest VMs), you should ignore this. 
      • The intent of that is to get the ideal UX, you get that out of the box with no need to install anything extra because open-vm-tools & open-vm-tools-desktop are installed by default, so I believe the prompt is a false positive.
  • HyperV - not worth using: 
    • Its free/built into Windows and has near bare metal performance.
    • The problem with HyperV is the default user experience:
      • The guest VM will have a fixed resolution/fixed window size.
      • You won't be able to bidirectionally copy paste between the Hypervisor host and the linux guest VM.
    • These are probably fixable problems, but the amount of effort to fix them isn't worth it.
      • I was once able to change the default resolution of a linux VM, but that required lots of googling, running a hand crafted command in PowerShell, and rebooting the VM to make the change take effect. 
      • After too much effort spent trying to get it to work nicely, I still didn't end up with dynamic resolution/window resizing, and I couldn't figure out how to get bidirectional copy paste to work
  • Virtual Box - not worth using:
    • Pro: Virtual Box offers a UX similar to VMware Workstation Player, only it can only do bidirectional copy paste of text, instead of text and files.
    • The problem is it has extreme performance lag:
      • Launching KeyNote NF will be slow
      • Navigating Tree Notes will be painfully slow (on a bare metal install this would be instant.)
    • The following animated gif recording is how bad the lag looks when run on VirtualBox.
      Note: This is not normal and not a wine issue. It's a VirtualBox specific performance issue.
      I'm documenting it so others can avoid the issue / know the solution if they run into it.
Keynote NF Installation tips for maximum wine compatibility

Tips for installing Wine (In General):

The following page is likely to have instructions on how to install the latest version of wine for your preferred Linux Distro

Tips for installing Wine (on OpenSUSE TumbleWeed):

  1. Note: TumbleWeed is a rolling release that aims to always have the latest updates, this means things break from time to time, including wine installer, these instructions will help you navigate through temporary breakages.
  2. If you click through the general instructions for OpenSUSE you'll be taken to this page:
  3. Click OpenSUSE
  4. Click Grab Binary Packages Directly 
    (This is more reliable than the wine.ymp option, which is an auto installer. Problems with the auto installer is sometimes it's an older version like 9.1 instead of 9.3, and sometimes it breaks outright due to the nature of the TW distro. Grab Binary Packages Directly gives you more options in the event something is slightly broken.)
  5. Pick the .rpm that matches your cpu's architecture (most computers are x86_64). 
    Troubleshooting tips
    • I've seen wine 9.1 offered for OpenSUSE TW, while wine 9.3 was offered for OpenSUSE Leap 15.5. They're basically the same so I was able to use the Leap Installer to get the latest version of wine.
    • Usually you can double click the .rpm from your downloads folder which will trigger an installer program. This often works, but if it doesn't work and you get an odd error message, then use the terminal to install the rpm.
      cd ~/Downloads
      sudo zypper install ./wine-9.5.1700.1.x86_64.rpm
      ^--Tip:one you type 'sudo zypper install ./wine' you can usually press tab to auto-complete the rest of the filename.
      The advantage of using the terminal to launch the installer is if the GUI fails you'll get a useless error message. If you use the terminal and the install fails, you'll get a useful error message. Sometimes it's something like rpm was signed with gpg key, and no trusted gpg key has been imported would you like to ignore? and you can ignore and it'll install correctly.
  6. If none of those .rpm's work.
    (Example wine 9.5 mentioned couldn't install from .rpm, because it failed to resolve dependency of wine-32bit)
    • Then try the method titled "Add repository and install manually"
    • which would look like this:
      sudo zypper addrepo
      sudo zypper refresh
      sudo zypper install wine
  7. Note: that installing wine this way will also install winetricks, that doesn't need to be installed separately.

Recommended Way of Installing KeyNote NF into Wine:

  • Commands to copy paste into your terminal will be denoted in blue (like this).
  • The commands should all be copy-pasted into the same terminal during one single session.
  • It's best to copy paste each command one at a time.
  • Sometimes odd things happen to text when it's copy pasted between Windows and Linux, even in the case of uploading to a website from Windows, then copying from the website from Linux.
    • Like the text of 2 commands will look identical to human eyes
    • but the byte encoding of the characters or spaces used in the command will be slightly off, or it'll add an invisible space to the right of a command.
    • This produces the existence of a rare edge case that's worth being aware of where it's possible that a copy-pasted command will produce different results than a manually typed command. (even though they'll look identical)
    • so if as you're copy-pasting commands one at a time, you feel like you're getting odd/unexpected results, and it seems like it's not working when it should be working. Try to press enter to create a new line and then manually type out the command without copy-pasting it, and see if it helps you past the spot where you were stuck.

The following commands will prep the environment in an ideal way, and then launch the installer:
(If you're curious about what these commands are doing, that's explained at the bottom.)
(The following commands should be run in a non-root terminal / as a normal user, so don't use sudo in front of them, and it's recommended to run echo $USER to verify you're not root. If echo $USER returns root, then stop and open a new terminal as a normal user.)

echo $USER
wine --version
cd ~/Downloads 
export WINEPREFIX=~/.wine-keynote
export WINEARCH=win32
winecfg -v win11

winetricks gdiplus msftedit riched20 arial comicsans courier georgia times tahoma corefonts
wine ~/Downloads/kntSetup_1.9.2.1.exe

The last command launches the downloaded setup file:

  • Ignore the associate KeyNote NF with .knt file extension (Trying to configuring KeyNote NF to open .knt files during installation wizard won't work, tips on how to set up file association on linux will be clarified further down).
  • Check the box to create a shortcut on the desktop. (This will create a shortcut on your Linux desktop environment, which is useful as it generates the shortcut with with KeyNote's icon.)
  • Uncheck "View"
    • If you don't uncheck this, you'll see an error message pop up saying.
      Unable to execute file:
      C:\Program Files\KeyNote NF\doc\
      ShellExecuteEx failed: code 193. BAD EXEC format for %1.
    • If you see the error you can safely ignore it, since it was just trying to display a
      readme text file. Unchecking the box just avoids the ignorable error message.
      (The ignorable error seems to be caused by a difference in how programs with
      arguments are launched from a terminal in Windows vs Linux.)
  • KeyNote NF should show up in your normal application launcher at this
    point, if you have trouble it can also be launched using the following method:
    export WINEPREFIX=~/.wine-keynote
    wine 'C:\Program Files\KeyNote NF\keynote.exe'
  • When you first launch KeyNote NF. On the first boot you'll see a KeyNote Tip of the Day,
    It's recommended that you unselect "show tips at startup"
    (Useful Workarounds to Know, section below explains why.)

Useful Workaround to Know #1:

  • Interface Seems Frozen - Issue Explanation:
    • If a pop-up occurs, when running on a real Windows installation,
      the pop-up window would have 2 important properties:
      • It'd pop-up 
      • It'd stay on top
    • Examples of "pop-up windows":
      • KeyNote Tip of the Day 
      • Configuration and Settings
      • Top Menu --> Open
      • Top Menu --> Save as
      • Top Menu --> File --> Properties
      • Top Menu --> Tools --> Configuration Options...
    • If a "pop-up window" occurs, when running on WINE, those
      important properties are no longer guaranteed.
      • The "pop-up window", sometimes becomes a "pop-under under". 
      • It does not stay on top, if you click KeyNote NF's main window while the "pop-up"window" is on screen, then KeyNote NF's application will show over top of the "pop-up window".
    • If the "pop-up window", is under the KeyNote NF application window, Then it can appear that KeyNote NF is frozen. (In reality it's waiting for you to interface with the "pop-up window", which you might not see. In the event it's under KeyNote) 
    • Because "pop-up windows" aren't considered programs, you won't see a new app in the task area, so it's not usually possible to visually detect the presence of a "pop-up window" by looking at the taskbar area.
  • Interface Seems Frozen - Workaround Solution:
    • Minimize, resize to be smaller, or move the main KeyNote NF application window, until you see the "pop-up window" that "pop'ed-under", close it, and things will go back to normal. 
    • Something to consider: 
      I find configuring KDE's default of "Icons-only Task Manager" (which automatically groups similar instances of an app together), to "Task Manager" like below makes it easier to find Minimizable Windowed Apps. For example: If you have 2 copies of firefox open as 2 different windowed applications, each would get it's own name rather than be grouped together with an icon.
      To do that you'd right click the taskbar, and click Show Alternatives, like in the image.
    • If in doubt or you can't find the "pop-under window", close KeyNote NF (the default settings should autosave any work in progress documents documents upon close), then reopen KeyNote NF. This should get things back to normal.

Useful Workaround to Know #2:

  • Black Lines on Interface - Issue Explanation:
    Parts of the menu can be covered in black lines, It looks different each time it happens, but it tends to look something like this:
    And if you mouse over parts will become revealed, but there will still be some black visual artifacts will remain that can no longer be revealed by mouse over.
  • Black Lines on Interface - Workaround Solutions:
    • If you use CrossOver, (which isn't wine, but based on wine/supports the development of wine and funds the hosting costs for Switching from a 64-bit wine bottle (which are GUI representations of wine prefixes), to a 32-bit wine bottle, and going to Advanced options and turn on DXVK & ESync that should make the black lines issue stop appearing. 
    • If you randomly see the black lines every rarity, then closing and reopening the program may be enough to fix it. I've noticed it's a bit random and more likely to show up in some configurations than others.
    • The most stable configuration I've found for Wine 9.x that makes me never see the black lines issue is when I use:
      • A 32-bit wine prefix
      • That has either no winetricks OR only the corefonts winetrick applied
      • KDE Desktop Environment
      • Wayland Windowing System.
    • If you deviate from the above your not guaranteed to see it, I'm just trying to document a happy path configuration that's known to work.
    • I've been able to reproduce the black lines by switching to Gnome Desktop Environment, as well as a few others. I recall I didn't see it on Cinnamon DE.
    • I learned that trying to implement unnecessary winetricks can introduce the black bars.
    • Switching from X11 to Wayland or vice versa can also help. To do that you need to log out, then select a different session from the user login screen.
      Here's a picture for context:

      • Plasma (Wayland) refers to the Wayland Windowing System backed version of KDE Plasma Desktop Environment.
      • Plasma (X11) refers to the X11 Windowing System backed version of KDE Plasma Desktop Environment.

Useful Workaround to Know #3:

  • Scrollbar Visual Glitch - Issue Explanation:

    If you navigate through the tree nodes the scrollbar in the text area won't visually update.

  • Scrollbar Visual Glitch - Workaround Solution:
    Click the visually glitched scrollbar and it'll trigger a redraw / immediately correct itself. (It's annoying because you have to do it repeatedly, it's purely a cosmetic issue.)

Below are 2 .gif animations shared to help understand the scrollbar visual glitch:

  • Note: The following gifs were recorded prior to using winetricks,
    When you use winetricks:
    • Tree node text will have rich text
    • Note text will look richer/correct
    • Pre-existing image in "Welcome to KeyNote NF" will show up correctly
    • The scrollbar visual glitch will happen MUCH less often :), that said the recordings below are still handy to know how to workaround the scrollbar visual glitch when it does show up.
  • The 1st is a 43 second long loop, it demonstrates the scrollbar visual glitch and the workaround.

  • The 2nd is a 17 second long loop, it shows an interesting variation that happens when there's a mix of nodes that should and shouldn't have a scrollbar, which makes the visual glitch look a bit different.

Useful Workaround to Know #4:

  • Associate .knt with KeyNote NF - Issue Explanation:
    If you have mynotes.knt, you probably want to be able to just click that file and have it open with KeyNote based on the .knt file association. If you request to associate .knt during the windows installation wizard, it'll be ignored.
    TO DO: Figure out
  • Associate .knt with KeyNote NF - Workaround Solution:
    TO DO: Figure out
Detailed Explanation of what each command is doing and why (For those who are curious):

cd ~/Downloads 

  • cd: change directory, sets the context of the terminal's current working directory to Downloads folder in ~, which is $HOME directory (basically changes to /home/$USER/Downloads)
  • wget: downloads the setup installer into the current folder / current working directory (downloads folder)
    (wget is web get, it's a way of downloading a file from the terminal)
  • Note: you can type pwd, which means "print working directory", to see your current contextual location in the file system.)

export WINEPREFIX=~/.wine-keynote

  • The meaning of ~/.wine-keynote
    • ~ = $HOME = /home/$USER
      So the above location corresponds to /home/$USER/.wine-keynote
    • When . is in front of a file or folder name, it's called a "dot file" or "dot folder"
      "dot files" and "dot folders" are hidden by default.
    • cd $HOME
      ls -la
      ls -la | grep -i wine
      • ^-- If you type both of these and press enter between each. 
      • cd $HOME: will change your working directory to $USER's home directory
      • ls -la: will show all files and folders in that directory, including hidden ones prefaced by a dot, in an easy to read format.
      • ls: stands for "list segments" (it lists files and folders in the current directory)
      • ls -a: means "list all segments" (-a = --all)
      • ls -l: -l is long list format (it's easier to read)
      • many files and folders will be in your home directory,
        | grep
        ^-- (read aloud as "pipe grep" can be used to filter the output of the previous command)
        | grep -i wine
        ^-- "| grep -i wine" means do a case-insensitive search for matches containing the text wine, and only display a filtered subset of results of the previous command.
      • cd $HOME ; ls -la | grep -i wine
        ^-- assuming you followed the convention of using the word wine in your wine prefixes, this should return a list of wine prefixes you have installed.
      • If you ever want to do the equivalent of a factory reset to wipe a wine prefix, you'd close any apps using it and then run.
        rm -rf ~/.wine-keynote
        ^-- stands for remove r: recursive (used for folders) and f: force
        Then ~/.wine-keynote represents the location of a wine-prefix.
  • Wine Prefixes are also known as "wine bottles".
    • They are basically the same thing.
    • Here's the context of why 2 names for the same thing exist. Crossover is a paid/licensed fork of wine that supports wine's ongoing development.
    • Crossover is a more GUI-driven version of wine, and they prefer the wine bottle terminology.
    • Wine is more CLI-driven, and it prefers to wine prefix terminology.
  • What's the point/purpose of a wine prefix? 
    • This creates a wine configuration environment that's isolated from other wine configuration environments. 
    • The reason this is desirable is some applications need WINEARCH=win32, WINEARCH=win64, no winetricks, or specific winetricks to work. These are often mutually exclusive, so if you wanted to install 2 applications in wine, setting up the environment dependencies to make application B work, could make application A break.
    • You can think of wine prefixes as being remotely similar to docker containers, in that they can allow application A and B to each get their own semi-isolated environment, and have different architectures/dependencies in each isolated environment.
    • This also means that you can create a 3rd isolated environment and potentially break it, without breaking applications A & B. 
    • So using one wine prefix per windows application is a best practice in terms of stability.
  • Useful Information about wine prefixes and how they're used in practice:
    • echo $WINEPREFIX
      can be used to see your current terminal's currently configured environment variable for what wine prefix to use.
      If after typing that it returns a blank line, that means the implicit default value will be used.
    • env | grep -i wine
      ^-- is an alternative to the above, it prints all environment variables, then filters the output to those that are a case insensitive match for the text wine. It can show you how multiple wine specific environment variables are configured (if they're configured away from their implicit default values.)
    • export WINEPREFIX=~/.wine
      ^--  is equivalent to the implicit default value.
    • When you run any of the following commands:
      • wine ...
      • winecfg ...
      • winetricks ...
      • ^-- they will only operate on / take action within the currently configured wine prefix.
        So if you have 2-3 wine prefixes, any operations involving any of the above 3 commands, will only work against 1 wine prefix at a time.
  • Useful Information to know about Linux Terminal Environment Variables:
    • export VARIABLE=VALUE
      ^-- This syntax represents logic that's scoped to the currently active terminal / only valid within the current terminal.
    • So if you have 2 terminals open, or you close then reopen a terminal, the environment variable will get unset, and if you'll need to re export the VARIABLE VALUE pair to use it again.
  • What this all means in the context of how we're using it and why things were done this way:
    • export WINEPREFIX=~/.wine-keynote
      wine, winecfg, and winetricks commands will run only against the location:
    • You should run all these installation commands in the same terminal in 1 session, because environment variables are scoped to a terminal instance.
    • The choice to use a custom WINEPREFIX, and not use implicit default value, results in improved stability, because it makes it harder to accidentally break your KeyNoteNF installation in the future.
    • If you ever wanted to do further customization to it,
      like say install an updated version of KeyNoteNF.
      Then you'd want to re-run
      export WINEPREFIX=~/.wine-keynote
      before running
      wine ~/Downloads/keynote-setup-updated-version.exe

export WINEARCH=win32

  • Background Contextual information that explains why this is Important to use:
    • export WINEARCH=win64 is the implicit default value
      (as in the value that's understood to be used when this environment variable is not set.
      In other words, when echo $WINEARCH shows a blank line.)
    • KeyNote NF, can theoretically work perfectly fine with WINEARCH=win64
    • The short version of why we're not setting that is to make the installation easier (more automation friendly), more reliable, and standardized.
    • The value of the WINEARCH environment variable is only used on the first run of winecfg in a wineprefix.
  • export WINEARCH=win32 has 2 important effects:
    • 1st effect: somewhat cosmetic, but has consequences in terms of standardization, automation, and documentation.
      • Clarification of Potential Misconceptions:
        • It doesn't mean you have a 32-bit computer. It works on 64-bit computers.
        • It doesn't mean it's wine intended to be used on 32-bit computers.
        • It doesn't mean it's going to create a 32-bit install of windows guest on your 64-bit computer.
          Proof: We can use WINEARCH=win32 and winecfg -v win11, together.
          Also fun fact win11 doesn't have a 32bit variant.
          Win10 was the last version of Windows with a pure 32bit variant.
      • So... What does it mean then?
        It's only purpose is to chose which standardized folder structure you want to use for the wine environment.
        If you install KeyNote NF with:
        • Implicit default values:

          Then you'd end up with the following standardized folder structure
          ~/.wine/drive_c/Program Files (x86)/KeyNote NF/keynote.exe
        • How-to guided documentation suggested values:

          Then you'll end up with the following standardized folder structure
          ~/.wine-keynote/drive_c/Program Files/KeyNote NF/keynote.exe
      • That standardization is important for documentation
        The documentation in this how-to guide is standardized on the assumption that WINEARCH=win32 was used to generate certain folder structure and paths. Many of the commands documented herein, work because we're following the same standard.
    • 2nd effect: access to stable winetricks
      • Another good question to ask is:
        Why would it be useful for a 64-bit computer to use a 32-bit wine prefix?
        The answer boils down to standardization is essential for automation.
        • Automation isn't possible without standardization, it's literally a prerequisite for automation to be possible, because automation depends on assumptions which are only valid in standardized environments.
        • The more standardized a setup is the easier it is to maintain the automation.
      • winetricks = automation.
        winetricks is a form of automating the configuration of a wine prefix.
      • winetricks technically works for both win32 & win64 architectures.
      • That said winetricks automation is more stable, reliable, maintained, and tested against, and compatible with the win32 architecture standardized folder structure.
      • Supposedly a subset of winetricks automation's aren't compatible with win64, rather than find out, I'd rather stay on the tried and true happy path.

winecfg -v win11

  • Different variations of the command:
    • winecfg
      Opens a Wine configuration pop up window
      you'll see several options in the GUI, but the [Applications] and [Libraries] tabs tend to be the most useful to know about. 
      • [Applications]
        This let's you change your windows version (version 9 of wine defaults to windows 10)
        (adding -v flag can configure the windows version from the cli)
      • [Libraries]
        This let's you edit DLL overrides managed by winetricks.
        (Usually winetricks configures this for you from the cli)
    • winecfg -v win10
      Passing a version of windows allows you configure wine without triggering a pop up window.
      This is equivalent to explicitly specifying the implicit default value.
    • winecfg -v win11
      Configures wine without triggering a pop up window.
      The version of windows specified has a very small effect, and because it doesn't do much they allow you to change on the fly.
      It's just the version of windows wine tells the program it's running on.
      If you run winecfg -v win7, then KeyNote NF installer will complain that it refuses to run on an older version of windows. (Only the installer, the app itself will run if you change it to this after installing.)
      There's actually no need to specify windows 11, the latest version of keynote will work with win2008r2 and higher. (winecfg /?, will list all valid versions)
  • Additional Behavior specific to the 1st run of any variation of the command:
    • The first time you run a variation of winecfg, it'll detect the WINEARCH and take about
      1 minute to generate files in the WINEPREFIX based on the WINEARCH.
      A non-interactive pop up will mention "The wine configuration is being updated please wait"
      (After the WINEPREFIX has been populated with files, you won't need to specify WINEARCH again when dealing with this prefix, WINEARCH is only used for the initial generation of a wineprefix.)
    • The population of files in the wineprefix only happens the first run, so subsequent runs of the command would be faster, (and not needed).
  • What's the point of doing it this way:
    • we need to run winecfg at least once to populate the wine prefix
    • running winecfg with flags (winecfg -v win11) allows a configuration pop up to be skipped.

winetricks gdiplus msftedit riched20 msls31 corefonts arial comicsans courier georgia times tahoma

  • The above command is also equivalent to splitting it out into multiple commands:
    winetricks corefonts arial comicsans courier georgia times tahoma
    winetricks msftedit riched20 msls31
    winetricks gdiplus
  • The above is idempotent, as in running it more than once won't hurt anything, as it'll detect it's already been run.
  • Here's a before and after visual of the difference winetricks makes
  • winetricks corefonts arial comicsans courier georgia times tahoma
    This installs fonts that will be missing by default. If you don't add these the text in the tree pane on the left will look odd
  • winetricks msftedit riched20
    winetricks msftedit riched20 msls31
    This fixes the formatting of the rich text in the text area on the right and makes it look correct
    Note I haven't seen it documented but, it seems to be the case that these are intended to be installed together as a pair/trio
    winetricks msftedit by itself will cause errors
    winetricks riched20 by itself will cause all text to visually disappear
    but if you install msftedit and riched20 together at the same time it'll work
    riched20 will implicitly install msls31, I'm just adding it to make it explicit.
  • winetricks gdiplus
    This allows images to appear (Notice the Image to the right of Welcome to KeyNote NF's blue text, in the text area on the right.)

wineserver --kill

  • This command is specific to upgrading wine
    When upgrading the running wine server can be older than the installed one.
    So this restarts it so the running wine server matches the installed version.
    Basically lets you update in a way that avoids a system reboot.

cp -r ~/.wine-keynote ~/.wine-keynote-pre-update-backup
ls -lah ~ | grep wine
export WINEPREFIX=~/.wine-keynote
wineboot --update

  • These command are specific to upgrading
    It's a best practice to backup before updating, because updating wineprefix has a chance of breaking your setup
  • The 1st command does a recursive copy of the wine prefix to a new location (basically a backup)
  • The 2nd command verifies the backup exists
  • The 3rd command effects the context on which the 4th command runs
  • The 4th command updates a wine prefix to match wine installed on system.