1. In Apple 2e mode (unenhanced) in 80 column mode, when moving the
cursor over characters from $40 to $5f, these appear as mouse text.
Likewise printing these characters with INVERSE displays mouse text.
This effect is turned off by referencing location $c00e and turned
back on by referenceing location $c00f.

This does not happen in enhanced 2e mode where mouse text appears
normally and properly.

I realize that most people don't run en-enhanced 2e mode, but the un-
enhanced 2e should not have mouse text at all! Nor should the
softswitch at $c00f be thrown. Generally I do run as an enhanced 2e.

I'm using 1.16.1.0, but I am sure that this bug goes back several
versions.

2. Not a bug, but a feature. Apple Win now lists the display mode that
it is in in the title bar, for example - TV. Not a problem unless your
are using WASP. WASP does not see any open AppleWin instances because
it checks the title for an exact match with what is in its config.
File. Fixing this is easy: add - whatever to the end of the string in
the WASP config file.

-- Elliot

On Sep 16, 11:50=A0am, e p chandler <e...@juno.com> wrote:
> I realize that most people don't run en-enhanced 2e mode, but the un-
> enhanced 2e should not have mouse text at all!

This is true.

> Nor should the softswitch at $c00f be thrown.

This is false. The $C00E/C00F soft-switch selects between NORM+UC_FLASH
+UC_INVERSE used by the default 40 column firmware and NORM+INVERSE
used by the 80 column firmware.

The new chargen ROM supplied with the enhanced firmware replaced the
redundant set of inverse uppercase characters with mouse text.

The unenhanced chargen contains:

00-1F INV UC
20-3F INV NUM+SPECIAL
40-5F INV UC
60-7F INV LC

80-9F NORM UC
A0-BF NORM NUM+SPECIAL
C0-DF NORM UC
E0-FF NORM LC

To generate flashing characters the screen bytes in the range 40-7F
get mapped to 00-3F and 80-BF (bit 6 is cleared and bit 7 alternates
to provide the flashing) before being fed to the chargen. This is
performed in hardware by the IOU whicjh explains why the INV UC chars
from 00-1F had to be left alone when mousetext was added.

To fix this AppleWin should load a different chargen image along with
the different firmware when un-enhanced IIe is selected.

On Sep 17, 2:56=A0am, David Wilson <mcs6...@gmail.com> wrote:
> On Sep 16, 11:50=A0am, e p chandler <e...@juno.com> wrote:
>
> > I realize that most people don't run en-enhanced 2e mode, but the un-
> > enhanced 2e should not have mouse text at all!
>
> This is true.
>
> > Nor should the softswitch at $c00f be thrown.
>
> This is false. The $C00E/C00F soft-switch selects between NORM+UC_FLASH
> +UC_INVERSE used by the default 40 column firmware and NORM+INVERSE
> used by the 80 column firmware.
>
> The new chargen ROM supplied with the enhanced firmware replaced the
> redundant set of inverse uppercase characters with mouse text.
>
> The unenhanced chargen contains:
>
> 00-1F INV UC
> 20-3F INV NUM+SPECIAL
> 40-5F INV UC
> 60-7F INV LC
>
> 80-9F NORM UC
> A0-BF NORM NUM+SPECIAL
> C0-DF NORM UC
> E0-FF NORM LC
>
> To generate flashing characters the screen bytes in the range 40-7F
> get mapped to 00-3F and 80-BF (bit 6 is cleared and bit 7 alternates
> to provide the flashing) before being fed to the chargen. This is
> performed in hardware by the IOU whicjh explains why the INV UC chars
> from 00-1F had to be left alone when mousetext was added.
>
> To fix this AppleWin should load a different chargen image along with
> the different firmware when un-enhanced IIe is selected.

Thank you for explaining the situation in detail. My mistake. The last
time I paid attention to the hardware at this level was when I had an
actual 2+ on my desk, and that was a long time ago. [smile]. You've
pointed out how to fix the problem.

---- e