mapping delete key

[Fairlight]

This public service announcement was brought to you by pmcnary:
> I would agree if I hadn't wasted a support call to sco. After 3 months,
> they couldn't get the delete mappings to be consistent even with their
> own software. They finally threw in the towel and said they couldn't do
> anything else. The delete key is hacked up between the numeric pad and
> the keyboard. The config files will work on a certain keyboard but not
> another. I finally just both PowerTerm even though I need it on the SCO
> box too.

Ouch!  Okay, I think I'd have looked at that too.  Actually, I'd have just
switched platforms.  Even though they've gotten better about supporting
open source stuff, it's just not a good platform yet for anything other
than canned apps.  The new OSR6 performs better, but when you can't
build/run what you need, what good is it?  What they provide, usually it's
a major version and a year behind current.  What they don't provide is
usually hard as heck to build--if it will build.  The lack of a non-buggy
gcc officially released by them is an issue, since their own compiler is
not ANSI, and not even quite 100% ISO-99 from what I've read (their 2.95.3
from skunkware segv's while building certain packages--including a later
gcc).  They claim they're going to release an open source tool kit on disk
and officially support it for OSR6, but it's not available yet.  So says a
page at the German SCO site, anyway.

Should have told them it was a legal issue and they might be able to sue
the keyboard manufacturer for "violating" their I.P. since it made their
code semi-to-non-functional.  Then they'd have -had- to actually try so
they had evidenc--er, wait a second, they don't actually back up their
claims as the courts request.  Oops. ;)

But they might have cared more and tried harder!

mark->
-- 
Try our new SPF-0 lotion, SunScream[tm].  Get it while it's hot!