Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.apple2.programmer > #3177
| From | D Finnigan <dog_cow@macgui.com> |
|---|---|
| Newsgroups | comp.sys.apple2.programmer |
| Subject | Re: identifying enhanced IIe |
| Date | 2016-11-07 20:27 +0000 |
| Organization | Mac GUI |
| Message-ID | <dog_cow-1478550453@macgui.com> (permalink) |
| References | <ff0256c8-5fe7-4706-b3a3-325ed518d807@googlegroups.com> <c3fbcdeb-b4b0-40c5-9326-699e5d42de71@googlegroups.com> |
6502workshop wrote: > On Sunday, November 6, 2016 at 12:02:10 PM UTC-6, roger....@gmail.com > wrote: >> On Sunday, November 6, 2016 at 11:44:25 AM UTC-6, roger....@gmail.com >> wrote: >> > "By the book", identifying an enhanced //e is done by checking the >> > ROMs: >> > $FBB3 = $06 (//e or later) >> > $FBC0 = $E0 (//e type; //c is zero; IIGS is also $E0) >> >> Having just remembered the //e Extended Debug Monitor ($FBC0 = $E1), the >> lazier way would be to check: >> $FBB3 = $06 (//e or later) >> $FBC0 <> $EA (not an original //e) See the Apple II technote referred to below for identification routines and check bytes. > > > Thanks Roger. > > Is the term original //e synonymous with unenhanced //e ? Yes. As well as the term "Standard Apple IIe" > > > I tried this out in AppleWIN using the "Apple IIe" and "Enhanced Apple > IIe" > settings and got the following results: > [...] > > > If I understand correctly, this looks like it is what is expected. > Correct? No need to mess around and waste time with emulators. You can trust and reply upon the official Apple Computer documentation, specifically the tech notes that explain all that you're asking about. Miscellaneous #7 Apple II Family Identification http://www.1000bit.it/support/manuali/apple/technotes/misc/tn.misc.07.html Also: Miscellaneous #2 Apple II Family Identification Routines 2.2 http://www.1000bit.it/support/manuali/apple/technotes/misc/tn.misc.02.html > > >> There should be nothing wrong with using a 65C02 in an unenhanced //e. Correct. Because everyone who has ever used a Transwarp in the IIe has used a 65C02 in that machine. > > Just to make sure I understand the difference between unenhanced and > enhanced, does this refer to a scenario only the 65C02 chip was installed > and the 3 ROM chips in the enhanced IIe upgrade kit were not installed? > http://apple2history.org/history/ah07/#07 > This version of the Apple IIe was introduced in March of 1985. It involved > changes to make the IIe more closely compatible with The Apple IIc and II > Plus. Again, don't refer to emulators or 2nd party sources for this information. Don't guess around. The official Apple Computer documentation defines what is an Enhanced Apple IIe. See the "Apple IIe Technical Reference Manual," page xxix for a definition. The enhanced Apple IIe includes the following changes from the original Apple IIe: - The 65C02 microprocessor, which is a new version of the 6502 microprocessor found in the original Apple IIe. The 65C02 uses less power, has 27 new opcodes, and runs at the same speed as the 6502. (See Chapter 7 and Appendix A.) - A new video ROM containing the same MouseText characters found in the Apple IIe. (See Chapter 2.) - New Monitor ROMs (the CD and EF ROMs) containing the enhanced Apple IIe firmware. (See Chapter 5.) - The identification byte at $FBC0 has been changed. In the original Apple IIe it was $EA (decimal 234), in the enhanced Apple IIe it is $E0 (decimal 224). For further reading, look for the manual called "About your Enhanced Apple IIe: Programmer's Guide" It looks like this: http://macgui.com/gallery/showphoto.php?pic_id=1335 That's my copy, but I don't have a PDF. There may be some other Apple IIe manuals from 1985 and later that also include the definition of what is an Enhanced Apple IIe. There's also this manual, "Apple IIe Guide To The New Features" http://macgui.com/gallery/showphoto.php?pic_id=1341#img (Again, my copy, no PDF) -- ]DF$ The Marina IP stack for Apple II-- http://marina.a2hq.com/
Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
identifying enhanced IIe Mark Lemmert <mark.lemmert@gmail.com> - 2016-08-07 16:27 -0700
identifying enhanced IIe Antoine Vignau <antoine.vignau@laposte.net> - 2016-08-07 20:35 -0700
Re: identifying enhanced IIe qkumba <peter.ferrie@gmail.com> - 2016-08-08 07:55 -0700
Re: identifying enhanced IIe Mark Lemmert <mark.lemmert@gmail.com> - 2016-08-08 18:34 -0700
Re: identifying enhanced IIe John Brooks <jbrooks@blueshiftinc.com> - 2016-08-09 21:16 -0700
Re: identifying enhanced IIe Mark Lemmert <mark.lemmert@gmail.com> - 2016-11-03 18:47 -0700
Re: identifying enhanced IIe Steve Nickolas <usotsuki@buric.co> - 2016-11-03 23:00 -0400
Re: identifying enhanced IIe 6502workshop@gmail.com - 2016-11-05 08:27 -0700
Re: identifying enhanced IIe Mark Lemmert <mark.lemmert@gmail.com> - 2016-08-08 18:32 -0700
Re: identifying enhanced IIe D Finnigan <dog_cow@macgui.com> - 2016-08-08 17:20 +0000
Re: identifying enhanced IIe Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-08-08 16:05 -0700
Re: identifying enhanced IIe roger.shimada@gmail.com - 2016-11-06 09:44 -0800
Re: identifying enhanced IIe roger.shimada@gmail.com - 2016-11-06 10:02 -0800
Re: identifying enhanced IIe 6502workshop@gmail.com - 2016-11-07 10:44 -0800
Re: identifying enhanced IIe D Finnigan <dog_cow@macgui.com> - 2016-11-07 20:27 +0000
Re: identifying enhanced IIe roger.shimada@gmail.com - 2016-11-08 19:39 -0800
Re: identifying enhanced IIe "Bill Buckels" <bbuckels@mts.net> - 2016-11-10 03:24 -0600
Re: identifying enhanced IIe Steve Nickolas <usotsuki@buric.co> - 2016-11-10 09:39 -0500
Re: identifying enhanced IIe "Bill Buckels" <bbuckels@mts.net> - 2016-11-10 11:55 -0600
Re: identifying enhanced IIe Steve Nickolas <usotsuki@buric.co> - 2016-11-10 13:04 -0500
csiph-web