AniDB O'Matic - Documentation: Linux
AoM on Linux
AoM is, strictly saying, a Windows client and, as such, expects an environment capable of understanding the Windows API. On Linux, for obvious reasons, that is not available natively. Wine gives linux users that environment. Due to the complexity of the Windows API, Wine is unable to run every Windows program flawlessly. Some work fine, some don't.
As of AoM 0.6.306 and Wine 20041201, AoM runs on wine with nearly no feature loss. It uses around 23 megabytes of resident memory on Linux with Wine, against 9 megabytes on Windows. It is expected that, after features are implemented and AoM 0.6 becomes a full working client, the resident memory difference of 14 megabytes will not grow much.
How to run AoM on wine
Like everything else on linux, you'll have two possibilities to install wine:
- Through your distro specific method; or
- By downloading the sources and compiling it yourself.
The installation of wine is outside the scope of this document, though. Refer to the WineHQ HowTo for details.
With a proper ~/.wine folder set up and working you'll need to make sure the following configuration options are marked: In the "[version]" section, make sure the line "Windows" is equal to either "win2k" or "winxp", just like the following:
[version] "Windows" = "win2k"
Also, you'll need to make sure wine can access the folder where AoM's running from and the folders you store your data.
* AoM 0.6 is not marked as stable yet. Don't assume your data as safe! *
Change permissions to read only, run with a user with less privileges or whatever. But know that you are the only one responsible for your own data safety.
It shouldn't do any harm running it, but risks are yours only.
That said, you'll need to look up how your version recognizes drives. On older wine versions you had to add a [Drive] section in ~/.wine/config. An example would be the following:
[Drive H] "Path" = "/path/to/the/data" "Type" = "hd" "Label" = "Nickname your disk here" "Filesystem" = "win95"
The Drive letter ("H" in this example), can be any unused letter. The rest should be pretty much self-explanatory.
Newer versions, though, require a symbolic link from ~/.wine/dosdevices to the folder. The following commands can do that for the current user:
$ cd ~/.wine/dosdevices $ ln -s /path/to/data h:
(In this case, again, we used the letter "H" for the drive. Use whichever you want.)
Follow those procedures for both AoM and your data's directory, go to the directory you've decompressed AoM and run:
$ wine AOM.exe
If everything was done correctly, you should have a splash screen appear shortly and then AoM's main screen. :D
So far, AoM has only been successfully tested on Wine. WineX and ReWind, similar projects which share some of the code, are still untested. If you would, test it and report to peeps in #firstname.lastname@example.org. ^^;
Known problems with AoM on wine
List of known wine limitations that affect AoM with latest wine (20050211 as of now):
- Adding a folder does not work on wine. fixme messages appear in wine's log, such as "fixme:shell:BrsFolderDlgProc flags 200 not implemented".
- The minimize button is rendered to a separate window.
Besides AoM, AniDB clients page mentions a Linux client under development. No info about it is available at the moment, though.
If you wish to develop an alternative *nix native client and have the time and capability to do so, drop by #email@example.com or the AniDB Development Forum and talk. We'll be expecting your presence.
Future of AoM for linux users
AoM 0.6 and on are made with wine compatibility in mind (whenever possible, that is). While there's no working native client, linux users will be able to use AoM under wine with hopefully no loss in usability.