[user02934123123]

Just a note to say that the key to the problem I was having with install (as per my above post in this thread) was indeed on account of remnants of the older version still around. Re-uploading the installer for the 3.5.4 version and using it to firmly uninstall the old system seemed to sort the issue. The main installer for the new vbSpell still would work; but I did manage to get the 'alternative' installer to work, via importing the dictionary SQL files directly into the database. All now does seem to be working properly.

Comments on vbSpell for 3.6.x at present:

I'm delighted that vbSpell has finally been ported over to a version for 3.6, and indeed with some very pleasant improvements (the new check spelling icon, automatic integration into most templates, etc.). Once up and running, it seems to work rather well, and is a great asset to any forum.

I would summarize the issues with the 3.6 version at present as follows:

• Problematic installation process: The main problem with the hack is the complexity and unreliability of its installer. The default installer, with the dictionary as a flatfile for import, takes to much extended server time for most hosting server configurations, which kill the process and abandon the install. The 'alternate' installer provided in the discussion thread (1st page) provides a workaround for this, but the workaround presumes the user installing the hack has a working knowledge of SQL imports into a database (and indeed, has access to MySQLAdmin on their server, which many do not). All in all, it's a problematic process. I would think first priority would be to re-work the installer slightly, so that it uses a series of flat files (e.g. dict1.dic, dict2.dic, etc.) rather than simply one great enormous file, importing them in series so that the server is not in one sustained process. The installer really does need to work first go, first time.
• Traces of old installations: Many admins may not be clear that uninstalling the old 3.5. version of the hack from AdminCP > Manage Plugins > Uninstall doesn't actually remove all traces of the hack, and that the bits and pieces left behind from that manner of install in fact prevent sucessful installation of the 3.6 version. Either this should be explained explicitly in the current version's instructions, with guidance given on re-uploading the old installer and using it for a complete uninstall prior to running the new installer; or - far better - the installer for the current version should have a 'remove all traces of vbSpell for 3.5.x' feature as an option in the new installation process.
• Customizable dictionaries: One of the nicest 'new features' that could be added to really flesh out the hack would be some concrete guidance on how to use customized dictionaries with the hack, or advice on how to customize the standard/default dictionary that is provided. Ideally, an ability for the admin to upload a file of 'additional words' to augment the standard dictionary, without replacing it, would be perfect -- i.e. if there are a host of specialist or local words in common use on a forum, these could be compiled to a list and uploaded (or otherwise added in) by the administrator, so that they become a part of the standard dictionary.