[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Enhanced //e ??

Subject: Re: Enhanced //e ??
From: dempson@actrix.gen.nz (David Empson)
Date: Sun, 3 Sep 2006 20:31:35 +1200
Newsgroups: comp.sys.apple2
References: <kCrKg.188$RW2.2@trndny04> <Pine.LNX.4.64.0609022317190.24334@dosius.ath.cx> <uNSdneVWaPmcwGfZnZ2dnUVZ_sSdnZ2d@comcast.com>
User-agent: MacSOUP/2.7 (Mac OS X version 10.4.7)
Xref: g2news2.google.com comp.sys.apple2:12282

Michael J. Mahon <mjmahon@aol.com> wrote:

> Lyrical Nanoha wrote:
> > On Sun, 3 Sep 2006, William Heckel wrote:
> > 
> >> I have been out of the //e loop for way too long..
> >>
> >> What was the purpose of upgrading the //e to an Enhanced //e  ???
> > 
> > 1. CPU upgrade (6502 -> 65C02)
> > 2. MouseText support
> > 3. Firmware bugfixes
> 
> and 4. Firmware enhancements: search, mini assembler, better self-test,
>         better interrupt responsiveness, etc.

Most of which can be summed up as consistency with the Apple //c,
establishing a higher standard for the basic feature set which should be
expected by application developers, rather than leaving the //c as a
side branch.

-- 
David Empson
dempson@actrix.gen.nz

References:
- Enhanced //e ??
  - From: "William Heckel" <wheckelny1@verizon.net>
- Re: Enhanced //e ??
  - From: Lyrical Nanoha <lyricalnanoha@dosius.ath.cx>
- Re: Enhanced //e ??
  - From: "Michael J. Mahon" <mjmahon@aol.com>

Prev by Date: Re: Enhanced //e ??
Next by Date: Re: ProDOS downloads
Previous by thread: Re: Enhanced //e ??
Next by thread: Re: Enhanced //e ??
Index(es):
- Date
- Thread