On Aug 15, 4:49=A0pm, "Michael J. Mahon"  wrote:
> WK2 wrote:
> > Thanks. =A0CTRL-A worked!
>
> > And thanks everyone for your suggestions and input. =A0What I wanted to
> > do was:
> > 10 PRINT "Hello"
> > -- lower cases as a string, not as commands or basic statements.
>
> > The Apple computer I've got already have the keyboard mod, but I read
> > that that mod is only supported by certain software.
>
> It depends on how the Videx card keyboard "driver" operates.
>
> If it intercepts the KSWL keyboard input routine, then most
> programs that use that vector for keyboard input will find
> mixed case chaaracters.
>
> If it polls the actual keyboard itself, then its support for
> lower case depends on its own code.

As I understand it, it's no different from the mechanism used by the
bult-in firmware in later machines, so yes KSWL is patched to the
firmware on the videx. I wonder if it'll work for input only if you
IN#3....

> There was a window of time between the ][+ and the //e where
> a number of apps supported the shift key mod for lower case.
> As the //e became the dominant platform, with native lower
> case, supporting the shift key mod became passe.

Somewhat interestingly, the //e had the shift key mod built in but
disabled which I suspect was a deterrent. A shame too, since having
one more 'modifier' key available is quite useful. Unfortunately since
it's essentially impossible to shift key mod the //c (PB2 is used by
the mouse) no post-1984 program could rely on it.

Bizarrely, the shift-key mod is installed by default on the platinum //
e!

What I always wanted was a control key mod. Why? So that an
application could distinguish between navigation keys and their
respective control characters. Very handy for terminal emulators.

Matt
--- SBBSecho 2.12-Win32