TP> I've done re-installs, using defaults etcetera but
 TP> to no avail ... it keeps flashing up an error message
 TP> when invoked to the effect that 'a non-recognised
 TP> command in 'Termcap.Dat'.

Ah, termcap!  Another UNIX mechanism derived from the silly and antiquated
"you users are really all 1960s teletypes" paradigm that UNIX uses, that leaks 
onto OS/2 because UNIX programmers either don't use curses properly or the
people who port the tools use curses libraries that are just straight code
ports, rather than ones where the effort has been put in to make them use
OS/2's console subsystems (VIO and KBD) as they properly should do.

The first thing to do, if this were a UNIX system, would be to check the value 
of the TERM environment variable that the `lspell' process is inheriting from
its parent.  It should probably be some variant on "ansi".  Then check the
value of the TERMCAP environment variable to ensure that it points to the
TERMCAP.DAT file.  Then GREP the TERMCAP.DAT file for the entry corresponding
to the value of the TERM environment variable.  The entry will probably be
wrapped onto multiple lines by using slash characters at the end of the line,
so use something like "/O,10" as an option to GREP to list the 10 lines
subsequent to the matching one as well (or some other number of your choice).

In other words:

        SET TERM
        DIR %TERMCAP%
        GREP /O,10 %TERM% %TERMCAP%

Then read the termcap(3) man pages to try and work out what the gibberish
actually means and why lspell doesn't like it.  (-:

 ¯ JdeBP ®

--- FleetStreet 1.22 NR
143/1