15
edits
Avdump2 on Linux: Difference between revisions
Jump to navigation
Jump to search
Note about InternalError when using --auth
m (Updated soon to be obsolete workaround.) |
(Note about InternalError when using --auth) |
||
| Line 1: | Line 1: | ||
Avdump2 was developed on Windows, for Windows. Thanks to Mono it’s possible to run Avdump2 on Linux and all efforts are made to support all basic features on Linux as well, but handling every peculiarity of every Mono version on every Linux installation is beyond the scope of Avdump2 at this time. Therefore, some things just don’t work on Linux, or at least not right away, without some workarounds. | [[Avdump2]] was developed on Windows, for Windows. Thanks to Mono it’s possible to run Avdump2 on Linux and all efforts are made to support all basic features on Linux as well, but handling every peculiarity of every Mono version on every Linux installation is beyond the scope of Avdump2 at this time. Therefore, some things just don’t work on Linux, or at least not right away, without some workarounds. | ||
This page is a collection of various workarounds and suggestions that should help you get started with Avdump2 on Linux. If you need more assistance, try to catch [[User:catweax|CatWEax]] on IRC. | This page is a collection of various workarounds and suggestions that should help you get started with Avdump2 on Linux. If you need more assistance, try to catch [[User:catweax|CatWEax]] on IRC. | ||
| Line 33: | Line 33: | ||
If you modified ''any'' of the required files Avdump2 came with, you will usually get the misleading error ''Either the client is outdated or your username/password combination is wrong.'' So no, you can’t edit the config file either. | If you modified ''any'' of the required files Avdump2 came with, you will usually get the misleading error ''Either the client is outdated or your username/password combination is wrong.'' So no, you can’t edit the config file either. | ||
If you're using build 5028, you will get ''Couldn't establish session with anidb (InternalError)'' if your current working path is different to the path the .exe is running from. This is a known problem and will be fixed in the next released version; for now the workaround is to <tt>cd</tt> into the directory Avdump2 is running from. | |||
== Workarounds == | == Workarounds == | ||