Thanks a lot, would have tons of work without U

Unfortunately, I have no control over what Google displays in its search results. I would apologise on their behalf, but there’s probably all sorts of legal imprecations and such. To be honest, I really don’t think the article is misleading. Installation on a 32 Bit system IS a snap – compile, then install. The rest of the article covers installation on a 64 bit system – admittedly a more complex process – followed by generic post installation and configuration steps for both architectures, which, apart from rewriting the source code myself, I have no control over. But as for the installation on a 32 bit system – which the particular sentence you point out clearly states (32 Bit, that is) – it’s really not that difficult. Also – and unfortunately, this is another “unfortunately” – considering the nature of the installation process, I have to guiltily admit that no, I didn’t consider users new to Linux when writing the article, because I didn’t envisage i) new Linux users searching on how to compile and install what is by its nature, a fairly complex application, and ii) Google displaying a rather obscure part of the article which could be taken out of context.

However, in my usual way of trying to placate everyone, I’ve edited the article for you

And then it goes on with a full page of cryptic terminal commands and some “oh and by the way you have to open a few text files and modify them with your favorite text editor” stuff. Unfortunately a google search of this app has your “Installing on a 32 bit system is a snap:” blurb in some main headers.

No a “snap” would be a .deb file for the new linux users among us. Identifying complex instructions like this and identifying them as a “snap” is what drives new users away. Don’t get me wrong…I appreciate your work and the time it took to post this but please don’t mislead the newer users. I get the impression that they were not even considered when you wrote this.

h