Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!pro-carolina.cts.com!delton
From: delton@pro-carolina.cts.com (System Administrator)
Newsgroups: comp.sys.apple
Subject: 65C02
Message-ID: <8902221021.AA05592@crash.cts.com>
Date: 22 Feb 89 03:11:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: pnet01!pro-sat!pro-charlotte!pro-carolina!delton@nosc.mil
Organization: The Internet
Lines: 16

I think this was discussed before probably a few years ago but I forget...
What's the shortest way (code size wise) to test for a 65C02 in software
(disregarding reading ROM ID bytes since the ROM's and CPU's don't 
necessarily go together).  Mainly I need to differentiate between the 6502 and
65C02.  

It could be done by setting up an address crossing a bank boundary or by
trapping the BRK vector and using an illegal opcode but both of these seem a
bit messy.  Anyone know a quicker/easier method?

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111