• How To Install Wine Mono
• Install Mono On Mac
• Wine Mono Is Not Installed

Information about running AWB on Mono/Wine.

Mono[edit]

Status: Not yet usable for general use.

• See http://tools.wmflabs.org/awb/mono/output.html
• AWB can be built under mono, but raises exceptions at runtime during load, and does not open cleanly.

May 23, 2019  I got the same issue, yesterday it was working perfectly, not sure what happened today it throws following exception 'Mono version installed on mac may not be compatible with this version of visual studio. Would you like us to install mono 5.18.1.15 for you?' My configuration is 'Microsoft Visual Studio 2019 professional edition on windows' and 'Microsoft Visual Studio 2019 Professional. While it’s most often used on Linux, Wine can run Windows software directly on a Mac, too–without requiring a Windows license or needing Windows running in the background. This isn’t necessarily the best option if you want to run Windows software on a Mac. Wine isn’t perfect, and not. How to enable font anti-aliasing in Wine. The term aliasing pertains to the process of sampling something smooth and continuous using a series of discrete measurements. If the measurements do not accurately represent the function, unwanted artifacts which are not present in the original will appear. I am using fedora 23 and I want to install.NET framework 4 in wine. Based on here, I have to remove mono first. But when I run the following command I receive unsuccessful result. $ wine uninsta. Oct 10, 2017  Wine-mono should have been downloaded when you created the wineprefix, unless you said no to the prompt. If your distro packages wine-mono, that's the easiest way to install it.

Mono setup[edit]

While it’s most often used on Linux, Wine can run Windows software directly on a Mac, too–without requiring a Windows license or needing Windows running in the background. This isn’t necessarily the best option if you want to run Windows software on a Mac. Wine isn’t perfect, and not every application will run ideally.

Mono install (Linux)[edit]

• Get the packages/see the official guide at the Mono downloads page
• Be sure to install mono, monodevelop, mono-devel, mono-nunit and any other packages for dependencies
• perl is required for the build event to set the SVN revision number.

Mono install (macOS)[edit]

• Read the guide, and install MonoDevelop. Be sure to have MDK.
• Stop right here -- There's no libgluezilla. You can try compiling the lib for macOS. MonoMac or Monobjc may be a solution, still.

Building AWB[edit]

• To run AWB under wine you must build under Mono version 3 (3.8 works). Mono version 4 enforces use of .NET 4 libraries that wine isn't happy with.
• Open the AutoWikiBrowser no plugins project solution
• Manually create the SvnInfo.cs file in WikiFunctions directory (copy the SvnInfo.template.cs file, write the version code if you want to).
  • An incomplete shell version of SubWCRev: http://stackoverflow.com/questions/1954062/emulate-subwcrev-when-using-git-svn
• If build fails due to WikiFunctions pre-build event, edit WikiFunctions.csproj to delete the text within the PreBuildEvent tags (at the end of the file)
• rev 8712 and earlier: Make a change to the end of Resources.resx to fix the build error, then AWB will build (AWB rev 7686, opensuse 11.4 64-bit, MonoDevelop 2.4.2)
• rev 8966 and later: download Microsoft.mshtml.dll and add a reference to the file in the AutoWikiBrowser project. Ensure the dll is placed alongside AutoWikiBrowser.exe when you run it.

• Hint: Always try the Unit tests. Under Mono 3.8 around 5 sets of unit tests fail due to mono issues. Under Mono 4.2 all unit tests pass correctly.
• If at runtime under Wine you get errors relating to System.Drawing version 4.0.0.0, disable the “use msbuild” option for WikiFunctions and AutoWikiBrowser projects in MonoDevelop and rebuild. If the build then fails due to missing .resources files, remove the obj directory in AWB/AWB/ (per MonoDevelop bug note) and rebuild.

Running under mono[edit]

• Disabling a couple of references to webbrowser in Main.cs will allow AWB to open cleanly (Mono 3.8 or Mono 4.2). Things such as list comparer, list filter, database scanner (Mono 3.8 gives error on large files, Mono 4.2 works cleanly) can be used.
• The web browser component is not working. Installing libgluezilla does not work as libgluezilla gives a stack trace.
  • Therefore cannot view diff or preview when editing pages.

Running unit tests (for developers)[edit]

• Mono: Running unit tests under Mono using MonoDevelop all pass correctly with Mono 4.2.2 and rev 11894. With Mono 3.x some unit tests incorrectly fail.
• NUnit via Wine Running unit tests using NUnit through wine works, all tests run and pass successfully, as of AWB rev 10524.
  • Download pre-compiled Windows binaries (zip) from NUnit website
  • Run using wine nunit-x86.exe, open the UnitTests.nunit file.

Wine[edit]

Status Known to be generally working.

• See Wine AppDb entry for AWB

Setup and installation[edit]

Getting Wine and Winetricks[edit]

Ubuntu/Mint[edit]

1. Install Wine. Use the package installation tool of your choice, such as apt-get. If you prefer, direct downloads of Wine are here.
2. Install Winetricks using the same installation tool. You'll need this to install additional components and DLLs used by AWB. Some distributions of Wine include Winetricks; others do not. For more information, see the Winetricks on the Wine wiki.

Fedora[edit]

1. Install Wine by running command sudo yum install wine
2. Install Winetricks by running command wget http://winetricks.org/winetricks && chmod +x winetricks

openSUSE[edit]

Just install wine and winetricks and any required dependencies via YaST/zypper.

Arch Linux[edit]

Ensure the multilib repository is enabled by uncommenting or adding the following lines in /etc/pacman.conf:

Then, install wine and winetricks: pacman -S wine winetricks

macOS[edit]

1. If you don't have X11 installed (check by trying startx), install a working X11 environment from XQuartz.
2. Use your package manager to install wine. If you don't have a package manager, consider using Homebrew:
   1. Head to brew.sh, and follow its instructions for installing Homebrew.
   2. Run brew install wine to download and install wine. Append --devel for new bugfixes and potentially new bugs on the development branch. Read brew info wine for informations and suggestions.
3. Install Winetricks by running command curl http://winetricks.org/winetricks > winetricks && chmod +x winetricks.

Setting up the Wine environment[edit]

1. If your Wine environment is 64-bit (it is by default on 64-bit machines), you'll need to reconfigure it to 32-bit as .NET 2.0 requires a 32-bit environment. Use Terminal (i.e. the command-line) to adjust the WINEARCH variable by running the command WINEARCH=win32 winecfg. See this wiki section for more information. If you get the wine: WINEARCH set to win32 but '[PATH]' is a 64-bit installation. message, choose a different prefix in that previous command, or if this is your first time using WINE, delete the .wine folder specified by the path, then run the command again. This will recreate the Wine prefix with a 32-bit environment (i.e. WINEARCH=win32 WINEPREFIX=~/.local/share/wineprefixes/dotnet35 winetricks dotnet35).
2. Use Winetricks to install dotnet35. You can use the Winetricks GUI to do this, although it can also be done in the command-line (winetricks dotnet35). This may require manual downloads, and make sure that all the required components are actually installed: you may need to rerun Winetricks to finish the installers.
   • .NET 4.5: with wine 1.7.39 and winetricks from March 2015, .NET 4.5 will install correctly. AWB appears to run fine under this .NET version as well.
   • November 2019 / TLS 1.2: from November 2019 it appears that Wikipedia requires HTTPS TLS 1.2 for connectivity, a known working setup for this is wine 4.19 and winetricks dotnet462 (wine 3.7 and dotnet462 did not work). If you're using an older Ubuntu/Debian package, you may need to get a newer version of winetricks otherwise it may fail to download the necessary files.

Starting AWB[edit]

1. To start AWB, run command wine 'path/to/AutoWikiBrowser.exe', putting the location of AutoWikiBrowser in the quotes.

How To Install Wine Mono

• AWB should be working, though there is a glitch in the diff view that is fixed by installing Internet Explorer. IE6 or IE8 have both been confirmed to be sufficient. As of September 2015, IE7 is the only version working well. Use winetricks ie7 to install it, and avoid installing IE8, as it would render AWB unusable.

Wine AppDb entry for AWB[edit]

Please update this page or the Wine AppDb entry for AWB with further information on your experience.

What works[edit]

• Open AWB
• Open Settings, save settings
• General fixes, typo fixing, TypoScan plugin
• Edit box, diff (with winetricks ie6), preview
• Save pages
• List comparer, list splitter
• List providers (searches)
• Custom modules
• External processing
• Logging

Known problem areas[edit]

• Database scanner, often fails after a few minutes or seconds before the scan has completed (with error 'No access to memory location', Wine bug 40156). No current known workaround or solution for Wine. Database scanner works with wine 3.5 and winetricks dotnet40, was not working with wine 2.0.1 or earlier. Database scanner also works under Mono 4.2.
• Find match/error/syntax highlightingwinetricks riched20 fixes this.
• Tooltips
  • Focus change: AWB 5.6.0.0 and earlier, up to SVN 11269: Tooltips can cause application focus to switch to the tooltip (could be Wine bug 9512). Workaround: in wine config, Graphics section (winecfg) uncheck 'Allow the window manager to control the windows' and restart AWB, tooltips will then display without stealing focus, but this will mean AWB window isn't integrated with your system's window manager. Workaround implemented in AWB in rev 11270 and later, display of tooltip does not affect application focus.
  • Caching: there can sometimes be a caching/lag issue whereby tooltips fail to display the first time, or are shown once when they should not be. Focusing on another item that does have a tooltip generally causes the tooltip display to move on or catch up. No current known workaround or solution.
• External Processing: in rev 11780 and earlier scripts may not work under Wine. Alternative solutions to running unix scripts with AWB. From rev 11780 scripts work using full Linux paths.

Tips & tricks[edit]

• You may get more frequent connection errors, especially on login/the first save, but just try again.
• If you sometimes encounter the exception 'attempted to read or write protected memory' and the wiki page you are processing has some Latin extended Unicode characters in it, change AWB's edit box font away from the Tahoma default to another TrueType font e.g. one of the Liberation sets. This should prevent the exception.

Wine on a Mac using homebrew[edit]

AWB can be installed to run under Wine on a Mac using the Homebrew package management software. It may be possible using other package management systems like Fink, Gentoo/Alt, MacPorts, Pkgsrc or Rudix. See the main WineHQ - macOS page.

• Install Homebrew.

• Or update homebrew and its formulas, if you already have Homebrew.

brew update

• You may need to install XCode for brew to work fine and install the XCode command line tools. The brew installer will ask you to do so automatically.

xcode-select --install

• Check for problems.

brew doctor and just in case, you may want to do it again: brew doctor

• Make sure you have X11.

Run startx. If there’s a “command not found” error—or similar—then you probably need an X11 client. Try XQuartz if you’re not sure which one to use: http://xquartz.org

• Install wine and winetricks: brew install wine winetricks
  • Sometime the dependancies of wine may need to be reinstalled, systems older than OS X 10.9 may need them installed with the --universal option. e.g.

• Sometimes you may want to change how the fonts are rendered so they look better. See manpage: fonts-conf for rendering stuffs and wine winecfg for changing the DPI setting of wine. — Preceding unsigned comment added by 222.65.178.5 (talk) 09:04, 11 September 2014 (UTC)

• Install .NET Framework 3.5 in wine, following the steps in #Setting up the Wine environment.
  • It may fail on wine msiexec /i XPSEP XP and Server 2003 32 bit.msi. Don't worry.
  • If the installation looks like it got stuck the window might just be hidden. Click on the icon in the menu bar to bring it back to foreground and confirm the dialog to continue.

• Run AWB

wine AutoWikiBrowser.exe

• AWB runs fine but does not clear the diff window so you will need to scroll to the bottom of the page.

CrossOver[edit]

Wine's commercial version, CrossOver, has good and easy support for AWB. It works under Linux and Mac. (A free trial is available for 14 days.)

• Download and install the trial version from https://www.codeweavers.com/products.
• Install the .NET Framework 3.5 SP1 choosing Windows Vista or later
• Run Command, browse to the AutoWikiBrowser.exe. Click Run.

Translations of this page:Françaisภาษาไทย(Translators, please see Discussion page.)

What is winetricks?

Winetricks is a helper script to download and install various redistributable runtime libraries needed to run some programs in Wine. These may include replacements for components of Wine using closed source libraries.

Note: Although using winetricks may be very useful for getting some programs working in Wine, doing so may limit your ability to get support though WineHQ. In particular, reporting bugs may not be possible if you've replaced parts of Wine with it. See Reporting bugs after you have used Winetricks below.

Note: Some of the packages listed below may not work well with older versions of Wine. As always we recommend you use the latest version of Wine.

Getting winetricks

The script is maintained by Austin English at https://github.com/Winetricks/winetricks. The latest release is available at https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks. Right-click on that link and use 'Save As' to save a fresh copy.
Alternatively you can get winetricks, using the commandline, with the command:

Also, some winetricks 'packages' require a few external tools to be installed, namely: cabextract, unzip, p7zip, wget (or curl). For GUI support, either zenity or kdialog.
Linux users can usually get these via their distribution's package management system.

Using winetricks

Once you've obtained winetricks you can run it simply by typing sh winetricks at the console. You can also use ./winetricks if you chmod +x winetricks first. If run without parameters, winetricks displays a GUI with a list of available packages. If you know the names of the package(s) you wish to install, you can append them to the winetricks command and it will immediately start the installation process. For example,

will install both the corefonts and vcrun6 packages.

Options

Version 20190912 help text:

Tip: As with all Wine commands, winetricks knows about the `WINEPREFIX` environment variable. This is useful for using winetricks with different Wine prefix locations. For example,

installs the mfc40 package in the `~/.winetest` prefix.

Tip: Users with more than one version of Wine on their system (for example, an installed package and an uninstalled Wine built from git) can specify which version winetricks should use. For example,

installs the mfc40 package using the Wine in the ~/wine-git directory.

Reporting bugs after you have used Winetricks

Please do not report bugs if you have used winetricks to install native (ie non Wine) files, as we cannot support Microsoft dlls.

Using winetricks to install gecko, mono, and fakeie6 options is acceptable for bug reports - just be sure to mention that's what you've done.

Additionally if you found it necessary to use winetricks for an application please mention it when submitting to the AppDB, mailing lists, and other Wine resources.

Garageband update for mac os x. Add percussion to your GarageBand song using Drummer If you can't record audio after a macOS Mojave update After installing macOS Mojave on your Mac, you might not be able to record audio in Logic Pro X, MainStage, GarageBand, Final Cut Pro X, or third-party audio and video apps. GarageBand (GB) is a consortium of MacOS and iOS compatible digital audio workstations for creating music or podcasts. It’s made and marketed by Apple Inc. And is an iLife software suite component. The tool helps tap into different music instruments and also share the music created. Oct 21, 2013  Screenshots. GarageBand is the easiest way to create a great-sounding song on your Mac. Add realistic, impeccably produced and performed drum grooves to your song with Drummer. Easily shape the sound of any instrument in the Sound Library with Smart Controls. Crank up the bottom end with Bass Amp Designer, or mix and match electric guitar amps. Jun 26, 2019  If you've upgraded to macOS Catalina 10.15 and downloaded the latest version of GarageBand, you can remove the older version: Click Finder, then choose Go Applications. Select the GarageBand folder, then choose File Move to Trash. Enter your password if asked, then click OK. Dec 12, 2019  The new GarageBand is a whole music creation studio right inside your Mac - complete with keyboard, synths, orchestral and percussion instruments, presets for guitar and voice, an entirely redesigned sound library, and virtual session drummers. A beautiful and intuitive interface makes it easy to learn, play, record, and create great-sounding songs.

Reporting bugs *in* Winetricks

Winetricks has a bug tracking system at https://github.com/Winetricks/winetricks/issues, please use it. If you don't want to get an account there to file a bug, posting on the wine user forum may also eventually get noticed.

How to remove things installed by Winetricks

It's easy to install an entire wineprefix, so by default, winetricks installs each app into its own Wine prefix, and offers an easy way to remove wineprefixes and the menu items they created.

Winetricks does not provide a way to uninstall individual apps or DLLs inside a Wine prefix. This is for several reasons, but mainly because the preferred way to uninstall anything in Wine is to simply install into a fresh Wine prefix. (Yes, it would be nice to have uninstallers for everything, but I don't need it myself. Patches welcome.)

If for some reason, you still don't want to fiddle at all with your Wine prefixes, Wine does offer a built-in Uninstaller program. Like the Windows 'Add/Remove Programs' applet though, it only recognizes programs installed by well-behaved Windows installers that respect the registry, like InstallShield or WISE. There are no guarantees it will work with a program installed by Winetricks or other installers like .msi packages.

Installing winetricks

It's not necessary to install winetricks to use it. You may choose to install winetricks in a global location so you can just type winetricks on the command line. Some Linux distributions include winetricks in their Wine packages, so you don't have to download it separately. You probably do want to follow these steps, if the distributions packaged winetricks version lags behind the current winetricks release (e.g. Debian/Ubuntu users).

Install Mono On Mac

To download and install your own copy of winetricks, you can install it manually like this:

To download and install the (separate) BASH completion script for winetricks:

See Also

• http://www.cabextract.org.uk/ -- cabextract is a tool for extracting MS cabinet files under Unix environments.
• http://mike.kronenberg.org/index.php?s=trix (Darwine now comes bundled with trix, a gui that invokes winetricks)

Wine Mono Is Not Installed