Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!tektronix!reed!kamath
From: kamath@reed.UUCP (Sean Kamath)
Newsgroups: comp.sys.cbm,comp.sys.apple
Subject: Re: The 65816 (was 6502 weirdnesses)
Message-ID: <6907@reed.UUCP>
Date: Thu, 20-Aug-87 12:32:14 EDT
Article-I.D.: reed.6907
Posted: Thu Aug 20 12:32:14 1987
Date-Received: Sat, 22-Aug-87 14:44:06 EDT
References: <907@edge.UUCP> <572@geowhiz.UUCP>
Reply-To: kamath@reed.UUCP (Sean Kamath)
Organization: Reed College, Portland OR
Lines: 48
Xref: mnetor comp.sys.cbm:653 comp.sys.apple:2391

In article <572@geowhiz.UUCP> scott@geowhiz.UUCP (Scott Kempf) writes:
>
>         The 65802  can directly  replace a 6502.  It has 99.9% compatibility
>    with existing hardware and software, and allows programs  to use  most of
>    the 65816 commands.  Although, because the 65802 has the same pin-outs as
>    the 6502, the 24 bit addressing ability of the 65816 is not  available in
>    the 65802.

Note that I hit that .1% When I tried to put SMT's No-Slot Clock in my
65802ed //e, it wouldn't work.  I put in the 65c02 and it worked.
Worked with a 6502 also. I switched to my othe //e.  It works (i'm using
it now) with the clock.  The only thing that didn't work was trying to
use the clock.  I don't know why.  Turns out Jim Sather, author of
Understanding the ][ and Understanding the //e, works for SMT now.  I
told him about my problem, so at least they know.  I doubt if anyone is
going to have a similar problem.  It may be a bad chip, but then why
does t work in one and not the other.  Probably bad tolerences.

>         While the  65816 does  not solve all of Doug Pardee's complaints, it
>    solve most of them and adds many needed features.   For those  of you who
>    own 6502s  and don't  want a //gs, think about replacing your 6502 with a
>    65802.    Only  programs  that   use   non-6502   instructions   will  be
>    incompatible, and you can write your own 16 bit code.

Yeah, like copy protection that used an undocumentd opcode for fetch
zeropage offset something or other.  I know that Apple Assembly line ran
an article about these undocumented opcodes.  Anyone know about it?
like, what issue?  Or better yet, anyone got a list of them?  I'd really
like to see them.

>         For more information on the 65816 get:
>
>    _Programming_the_65816_, by David Eyes and Ron Lichty.  New York:  Brandy
>    Communications (a  division of  Simon &  Schuster), 1986.   Prentice Hall
>    Press.

A really good book, since it covers all 65xx series.  I got it free from
APDA and it was well worth it! (;-)

>_____________________________________________________________________________
>Scott Kempf                            1302 Rutledge St

Sean Kamath
-- 
UUCP:  {decvax allegra ucbcad ucbvax hplabs ihnp4}!tektronix!reed!kamath
CSNET: reed!kamath@Tektronix.CSNET  ||  BITNET:  reed!kamath@Berkeley.BITNET
ARPA:  tektronix!reed!kamath@Berkeley <or> reed!kamath@hplabs
US Snail: 3934 SE Boise, Portland, OR  97202 (I hate 4 line .sigs!)