|
|
| Re: dissasmbler [message #327210 is a reply to message #327209] |
Sat, 27 August 2016 22:46   |
|
|
Originally posted by: Don Bruder
In article <57c24905$0$31208$c3e8da3$a9097924@news.astraweb.com>,
Richard Thiebaud <thiebauddick2@aol.com> wrote:
> What disassemblers can run under DOS 3.3 or Prodos?
I always liked Sourceror (Part of the MerlinPro package) for disassembly
work. It was *MOST DEFINITELY NOT* a "just throw the code you want dealt
with at it and get back ready-to-go source" package, but once you got
the hang of it, it would produce outstanding source.
I can't remember if it ran under DOS 3.3 - By that time in my Apple II
"career", I was working almost exclusively under ProDOS. I know it did
an excellent job there.
--
Brought to you by the letter K and the number .357
Security provided by Horace S. & Dan W.
|
|
|
|
|
|
|
|
| Re: dissasmbler [message #327265 is a reply to message #327209] |
Sun, 28 August 2016 17:55 |
Michael AppleWin Debu
Messages: 1262
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
On Saturday, August 27, 2016 at 7:15:11 PM UTC-7, Richard Thiebaud wrote:
> What disassemblers can run under DOS 3.3 or Prodos?
Bit of an orthogonal question:
Is there a specific program / game you had in mind that you're allowed to discuss?
|
|
|
|
| Re: dissasmbler [message #327266 is a reply to message #327265] |
Sun, 28 August 2016 18:32 |
Richard Thiebaud
Messages: 222
Registered: May 2013
Karma: 0
|
Senior Member |
|
|
On 8/28/2016 5:55 PM, Michael 'AppleWin Debugger Dev' wrote:
> On Saturday, August 27, 2016 at 7:15:11 PM UTC-7, Richard Thiebaud wrote:
>> What disassemblers can run under DOS 3.3 or Prodos?
>
> Bit of an orthogonal question:
>
> Is there a specific program / game you had in mind that you're allowed to discuss?
>
Yes, the Russian Peasant Multiplication Applesoft Basic program recently
discussed in this group, compiled with TASC. Someone asked for a
disassembly of this. I was able to produce a source listing of the Bin
file, as done with some GS disassembler, but not to create a listing
with the addresses. I've been playing around with this not because it's
important, but just out of general interest.
It just occurred to me to try taking the assembly source file I have and
try running it through an assembler. (I suppose this should have been
obvious but sometimes I'm slow.)
|
|
|
|
| Re: dissasmbler [message #327267 is a reply to message #327266] |
Sun, 28 August 2016 18:52 |
Michael J. Mahon
Messages: 1772
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
Richard Thiebaud <thiebauddick2@aol.com> wrote:
> On 8/28/2016 5:55 PM, Michael 'AppleWin Debugger Dev' wrote:
>> On Saturday, August 27, 2016 at 7:15:11 PM UTC-7, Richard Thiebaud wrote:
>>> What disassemblers can run under DOS 3.3 or Prodos?
>>
>> Bit of an orthogonal question:
>>
>> Is there a specific program / game you had in mind that you're allowed to discuss?
>>
> Yes, the Russian Peasant Multiplication Applesoft Basic program recently
> discussed in this group, compiled with TASC. Someone asked for a
> disassembly of this. I was able to produce a source listing of the Bin
> file, as done with some GS disassembler, but not to create a listing
> with the addresses. I've been playing around with this not because it's
> important, but just out of general interest.
>
> It just occurred to me to try taking the assembly source file I have and
> try running it through an assembler. (I suppose this should have been
> obvious but sometimes I'm slow.)
>
Weird. I've never seen a disassembler that didn't list 1) the addresses, 2)
the code, and 3) the disassembled code. Typically every branch target gets
a generated label formed from the hex address.
--
-michael - NadaNet 3.1 and AppleCrate II: http://michaeljmahon.com
|
|
|
|
| Re: dissasmbler [message #327278 is a reply to message #327266] |
Sun, 28 August 2016 19:22 |
Michael AppleWin Debu
Messages: 1262
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
On Sunday, August 28, 2016 at 3:33:28 PM UTC-7, Richard Thiebaud wrote:
>> Is there a specific program / game you had in mind that you're allowed to discuss?
> Yes, the Russian Peasant Multiplication Applesoft Basic program recently
> discussed in this group, compiled with TASC. Someone asked for a
> disassembly of this.
That was me. :-)
Only because I was curious how to compared to hand assembly.
I was able to produce a source listing of the Bin
> file, as done with some GS disassembler, but not to create a listing
> with the addresses. I've been playing around with this not because it's
> important, but just out of general interest.
Strange that the disassembly didn't include the address.
I'm old "skool" -- I prefer address, opcodes, and assembly for completeness.
> It just occurred to me to try taking the assembly source file I have and
> try running it through an assembler. (I suppose this should have been
> obvious but sometimes I'm slow.)
Don't worry -- sometimes we all need a little sharping from time to time.
The wise man is the one who recognizes it !
|
|
|
|
| Re: dissasmbler [message #327279 is a reply to message #327267] |
Sun, 28 August 2016 19:22 |
Michael AppleWin Debu
Messages: 1262
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
On Sunday, August 28, 2016 at 3:52:34 PM UTC-7, Michael J. Mahon wrote:
> Weird. I've never seen a disassembler that didn't list 1) the addresses, 2)
> the code, and 3) the disassembled code. Typically every branch target gets
> a generated label formed from the hex address.
Yeah, I thought that was strange too.
|
|
|
|
| Re: dissasmbler [message #327280 is a reply to message #327209] |
Sun, 28 August 2016 19:33 |
Richard Thiebaud
Messages: 222
Registered: May 2013
Karma: 0
|
Senior Member |
|
|
On 8/27/2016 10:14 PM, Richard Thiebaud wrote:
> What disassemblers can run under DOS 3.3 or Prodos?
I successfully did what I was trying to do, using the GS/OS Breakdown
disassembler. It turns out, what I did not realize, that it
automatically saves the disassembly listing to a text file. Thanks
everyone for the help.
|
|
|
|
| Re: dissasmbler [message #327281 is a reply to message #327267] |
Sun, 28 August 2016 20:54 |
|
|
Originally posted by: Don Bruder
In article <9sOdnUv1fryw9l7KnZ2dnUU7-fPNnZ2d@giganews.com>,
Michael J. Mahon <mjmahon@aol.com> wrote:
> Richard Thiebaud <thiebauddick2@aol.com> wrote:
>> On 8/28/2016 5:55 PM, Michael 'AppleWin Debugger Dev' wrote:
>>> On Saturday, August 27, 2016 at 7:15:11 PM UTC-7, Richard Thiebaud wrote:
>>>> What disassemblers can run under DOS 3.3 or Prodos?
>>>
>>> Bit of an orthogonal question:
>>>
>>> Is there a specific program / game you had in mind that you're allowed to
>>> discuss?
>>>
>> Yes, the Russian Peasant Multiplication Applesoft Basic program recently
>> discussed in this group, compiled with TASC. Someone asked for a
>> disassembly of this. I was able to produce a source listing of the Bin
>> file, as done with some GS disassembler, but not to create a listing
>> with the addresses. I've been playing around with this not because it's
>> important, but just out of general interest.
>>
>> It just occurred to me to try taking the assembly source file I have and
>> try running it through an assembler. (I suppose this should have been
>> obvious but sometimes I'm slow.)
>>
>
> Weird. I've never seen a disassembler that didn't list 1) the addresses, 2)
> the code, and 3) the disassembled code. Typically every branch target gets
> a generated label formed from the hex address.
Whichever one it was he used for the disassembly he posted *DEFINITELY*
didn't do it. It output something that at least *RESEMBLED* assembly
code, but it was missing JMP, JSR, and branch target labels, and quite
obviously had no clue whatsoever how to deal with "not actually code"
(strings, mainly, I'd suspect, though I'd have to hand-translate to be
certain - not motivated enough to bother, sorry!) segments. It made a
valiant effort, and I suppose the output might actually be correct
enough that it could be re-assembled (assuming the availability of an
assembler that can cope with its rather strange - to me, at least -
notation) to get the original binary back, but what it produced
definitely isn't anything more than what I'd call "barely useful".
--
Brought to you by the letter K and the number .357
Security provided by Horace S. & Dan W.
|
|
|
|
| Re: dissasmbler [message #327282 is a reply to message #327278] |
Sun, 28 August 2016 20:54 |
Richard Thiebaud
Messages: 222
Registered: May 2013
Karma: 0
|
Senior Member |
|
|
On 8/28/2016 7:22 PM, Michael 'AppleWin Debugger Dev' wrote:
> On Sunday, August 28, 2016 at 3:33:28 PM UTC-7, Richard Thiebaud wrote:
>>> Is there a specific program / game you had in mind that you're allowed to discuss?
>> Yes, the Russian Peasant Multiplication Applesoft Basic program recently
>> discussed in this group, compiled with TASC. Someone asked for a
>> disassembly of this.
>
> That was me. :-)
>
> Only because I was curious how to compared to hand assembly.
>
> I was able to produce a source listing of the Bin
>> file, as done with some GS disassembler, but not to create a listing
>> with the addresses. I've been playing around with this not because it's
>> important, but just out of general interest.
>
> Strange that the disassembly didn't include the address.
>
> I'm old "skool" -- I prefer address, opcodes, and assembly for completeness.
>
>
>> It just occurred to me to try taking the assembly source file I have and
>> try running it through an assembler. (I suppose this should have been
>> obvious but sometimes I'm slow.)
>
> Don't worry -- sometimes we all need a little sharping from time to time.
> The wise man is the one who recognizes it !
>
As a matter of fact, the GS/OS Breakdown disassembler _does_ list the
addresses. It's just that I couldn't find an option to generate the
disassembly listing to a text file. It turns out that it always
generates this to a text file but I didn't realize it. My Apple II
experience is limited but I've learned a lot while doing this and had a
lot of fun.
I will post the dissembly list
|
|
|
|
| Re: dissasmbler [message #327285 is a reply to message #327281] |
Sun, 28 August 2016 21:06 |
Richard Thiebaud
Messages: 222
Registered: May 2013
Karma: 0
|
Senior Member |
|
|
>>
>> Weird. I've never seen a disassembler that didn't list 1) the addresses, 2)
>> the code, and 3) the disassembled code. Typically every branch target gets
>> a generated label formed from the hex address.
>
> Whichever one it was he used for the disassembly he posted *DEFINITELY*
> didn't do it. It output something that at least *RESEMBLED* assembly
> code, but it was missing JMP, JSR, and branch target labels, and quite
> obviously had no clue whatsoever how to deal with "not actually code"
> (strings, mainly, I'd suspect, though I'd have to hand-translate to be
> certain - not motivated enough to bother, sorry!) segments. It made a
> valiant effort, and I suppose the output might actually be correct
> enough that it could be re-assembled (assuming the availability of an
> assembler that can cope with its rather strange - to me, at least -
> notation) to get the original binary back, but what it produced
> definitely isn't anything more than what I'd call "barely useful".
>
What I found out is that it printed the disassembly to a text file,
which I was not realizing. The file pasted before was the result of a
command "Generate Source File", which was different.
|
|
|
|
| Re: dissasmbler [message #327298 is a reply to message #327266] |
Mon, 29 August 2016 02:55 |
spectrumdaddy
Messages: 191
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
Richard Thiebaud <thiebauddick2@aol.com> wrote:
> I was able to produce a source listing of the Bin
> file, as done with some GS disassembler, but not to create a listing
> with the addresses. I've been playing around with this not because it's
> important, but just out of general interest.
You could always try the GS/OS BrkDown dissasembler, that was released
at the end of last year. It is a desktop disassembler, unlike many of
the other ones that are text screen based.
It will generate 8 or 16 bit labelled source code for you, though like
all disassemblers, you do need to do some work on the output to
designate data areas etc.
Get BrkDown, and my other software from:
http://speccie.co.uk
Cheers - Ewen
|
|
|
|
| Re: dissasmbler [message #327299 is a reply to message #327298] |
Mon, 29 August 2016 03:41 |
Richard Thiebaud
Messages: 222
Registered: May 2013
Karma: 0
|
Senior Member |
|
|
On 8/29/2016 2:55 AM, Ewen wrote:
> Richard Thiebaud <thiebauddick2@aol.com> wrote:
>
>> I was able to produce a source listing of the Bin
>> file, as done with some GS disassembler, but not to create a listing
>> with the addresses. I've been playing around with this not because it's
>> important, but just out of general interest.
>
> You could always try the GS/OS BrkDown dissasembler, that was released
> at the end of last year. It is a desktop disassembler, unlike many of
> the other ones that are text screen based.
>
> It will generate 8 or 16 bit labelled source code for you, though like
> all disassemblers, you do need to do some work on the output to
> designate data areas etc.
>
> Get BrkDown, and my other software from:
>
> http://speccie.co.uk
>
> Cheers - Ewen
>
BrkDown is what I ended up using, thanks. Nice product!
|
|
|
|
| Re: dissasmbler [message #327324 is a reply to message #327281] |
Mon, 29 August 2016 09:56 |
Michael AppleWin Debu
Messages: 1262
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
On Sunday, August 28, 2016 at 6:54:05 PM UTC-6, Don Bruder wrote:
> Whichever one it was he used for the disassembly he posted *DEFINITELY*
> didn't do it. It output something that at least *RESEMBLED* assembly
> code, but it was missing JMP, JSR, and branch target labels, and quite
> obviously had no clue whatsoever how to deal with "not actually code"
> (strings, mainly, I'd suspect, though I'd have to hand-translate to be
> certain - not motivated enough to bother, sorry!) segments.
I was. :-) Wasn't too much work. Originally there were only 4 lights, er strings, but interestingly enough the compiler added the 5th string.
https://github.com/Michaelangel007/apple2_russian_peasant_mu ltiplication/blob/master/tasc_disasm_clean.s
|
|
|
|
| Re: dissasmbler [message #327493 is a reply to message #327299] |
Tue, 30 August 2016 23:55 |
Hugh Hood
Messages: 689
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
I would image that Ewen considers 'Spectrum' to be his finest (software)
work, but I've found 'BrkDown' to be one of the most useful Apple II
utilities that I've ever used.
Sure, I've played with Bredon's Sourceror and also Sander-Cederlof's S-C
disassembler, but they're just not in the same league as BrkDown,
particularly when you factor in ease of use (desktop interface vs. text
screen/command line) and completeness of features. 'BrkDown' actually
makes the hard part of disassembly fun, and provided it is run in
emulation, makes it fast.
I'll confess that I took a long, long look at The Flaming Bird, which
Antoine swears by, but I think you need to be the caliber of programmer
that Antoine is (a very small group indeed) in order to make it dance
for you.
I think Steve mentioned Hex Ray's IDA running under Windows/OS X/Linux
for 6502 use. I went to Hex Ray's web site and took another look at all
it does, and I'm still glazed over. If I ever get that good, I think the
NSA will track me down and offer me a job!
After you spend some time 'processing' Apple II code with BrkDown,
you'll really appreciate what Ewen has done, and the intelligent design
behind it all.
Obviously it allows one to re-construct source code for programs, and it
does do that for both ORCA and Merlin.
But my favorite feature in BrkDown is the text file listings it
generates of the disassembled code itself, particularly after I've had
the opportunity to pre-load it with my own labels, apply them, change
ORGs (often several times in the same code), and define strings and
data. Those listings allow me to actually understand the program's logic
and operation. After I've printed those and used a few colored
highlighters on the listings (ala Lancaster's 'Tearing Method'), I can
master the code, or at least the parts of it that interest me.
Hugh Hood
On 8/29/2016 2:41 AM, Richard Thiebaud wrote:
> On 8/29/2016 2:55 AM, Ewen wrote:
>> Richard Thiebaud <thiebauddick2@aol.com> wrote:
>>
>>> I was able to produce a source listing of the Bin
>>> file, as done with some GS disassembler, but not to create a listing
>>> with the addresses. I've been playing around with this not because it's
>>> important, but just out of general interest.
>>
>> You could always try the GS/OS BrkDown dissasembler, that was released
>> at the end of last year. It is a desktop disassembler, unlike many of
>> the other ones that are text screen based.
>>
>> It will generate 8 or 16 bit labelled source code for you, though like
>> all disassemblers, you do need to do some work on the output to
>> designate data areas etc.
>>
>> Get BrkDown, and my other software from:
>>
>> http://speccie.co.uk
>>
>> Cheers - Ewen
>>
>
> BrkDown is what I ended up using, thanks. Nice product!
>
|
|
|
|
| Re: dissasmbler [message #327508 is a reply to message #327493] |
Wed, 31 August 2016 09:23 |
Michael AppleWin Debu
Messages: 1262
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
On Tuesday, August 30, 2016 at 9:56:01 PM UTC-6, Hugh Hood wrote:
Thanks for the feedback on the various disassemblers!
I might take a look at some of these to see how they help automate the tediousness.
|
|
|
|
| Re: dissasmbler [message #327529 is a reply to message #327508] |
Thu, 01 September 2016 03:05 |
spectrumdaddy
Messages: 191
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
Michael 'AppleWin Debugger Dev' <michael.pohoreski@gmail.com> wrote:
> I might take a look at some of these to see how they help automate
> the tediousness.
Be prepared for a learning curve with any dissasembler, but in the case
of BrkDown, I tried to make that easier by putting the manual into an
illustrated PDF, in the style of the Apple's own IIGs manuals.
Cheers - Ewen
|
|
|
|
| Re: dissasmbler [message #363887 is a reply to message #327493] |
Mon, 19 February 2018 13:09 |
|
|
Originally posted by: James Davis
On Tuesday, August 30, 2016 at 8:56:01 PM UTC-7, Hugh Hood wrote:
> I would image that Ewen considers 'Spectrum' to be his finest (software)
> work, but I've found 'BrkDown' to be one of the most useful Apple II
> utilities that I've ever used.
>
> Sure, I've played with Bredon's Sourceror and also Sander-Cederlof's S-C
> disassembler, but they're just not in the same league as BrkDown,
> particularly when you factor in ease of use (desktop interface vs. text
> screen/command line) and completeness of features. 'BrkDown' actually
> makes the hard part of disassembly fun, and provided it is run in
> emulation, makes it fast.
>
> I'll confess that I took a long, long look at The Flaming Bird, which
> Antoine swears by, but I think you need to be the caliber of programmer
> that Antoine is (a very small group indeed) in order to make it dance
> for you.
>
> I think Steve mentioned Hex Ray's IDA running under Windows/OS X/Linux
> for 6502 use. I went to Hex Ray's web site and took another look at all
> it does, and I'm still glazed over. If I ever get that good, I think the
> NSA will track me down and offer me a job!
>
> After you spend some time 'processing' Apple II code with BrkDown,
> you'll really appreciate what Ewen has done, and the intelligent design
> behind it all.
>
> Obviously it allows one to re-construct source code for programs, and it
> does do that for both ORCA and Merlin.
>
> But my favorite feature in BrkDown is the text file listings it
> generates of the disassembled code itself, particularly after I've had
> the opportunity to pre-load it with my own labels, apply them, change
> ORGs (often several times in the same code), and define strings and
> data. Those listings allow me to actually understand the program's logic
> and operation. After I've printed those and used a few colored
> highlighters on the listings (ala Lancaster's 'Tearing Method'), I can
> master the code, or at least the parts of it that interest me.
>
>
>
>
>
> Hugh Hood
>
>
>
> On 8/29/2016 2:41 AM, Richard Thiebaud wrote:
>> On 8/29/2016 2:55 AM, Ewen wrote:
>>> Richard Thiebaud ... wrote:
>>>
>>>> I was able to produce a source listing of the Bin
>>>> file, as done with some GS disassembler, but not to create a listing
>>>> with the addresses. I've been playing around with this not because it's
>>>> important, but just out of general interest.
>>>
>>> You could always try the GS/OS BrkDown dissasembler, that was released
>>> at the end of last year. It is a desktop disassembler, unlike many of
>>> the other ones that are text screen based.
>>>
>>> It will generate 8 or 16 bit labelled source code for you, though like
>>> all disassemblers, you do need to do some work on the output to
>>> designate data areas etc.
>>>
>>> Get BrkDown, and my other software from:
>>>
>>> http://speccie.co.uk
>>>
>>> Cheers - Ewen
>>>
>>
>> BrkDown is what I ended up using, thanks. Nice product!
>>
Hi Hugh,
BrkDown is just for the Apple IIGS, right?
What 6502 Disassembler is best for running on an Enh. Apple IIe or in AppleWin?
Also, for running on an IBM/Windows PC? CiderPress?
James Davis
|
|
|
|
| Re: dissasmbler [message #363892 is a reply to message #363887] |
Mon, 19 February 2018 14:52 |
qkumba
Messages: 1598
Registered: March 2013
Karma: 0
|
Senior Member |
|
|
For the PC, I recommend IDA (the Interactive DisAssembler) from www.hex-rays.com.
There's a free version that supports the 6502 CPU.
|
|
|
|
| Re: dissasmbler [message #363893 is a reply to message #363892] |
Mon, 19 February 2018 16:14 |
Steve Nickolas
Messages: 2039
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On Mon, 19 Feb 2018, qkumba wrote:
> For the PC, I recommend IDA (the Interactive DisAssembler) from www.hex-rays.com.
> There's a free version that supports the 6502 CPU.
>
I've done a lot of work with the free version of IDA as well.
-uso.
|
|
|
|
| Re: dissasmbler [message #363906 is a reply to message #363887] |
Tue, 20 February 2018 00:16 |
Hugh Hood
Messages: 689
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
James,
You are correct. Ewen Wannop's BrkDown is a IIGS GS/OS desktop
application. These days I almost always run it on a Windows 10 machine
with the GSPort emulator. At the emulator's 'unlimited' speed setting,
supposedly it's the equivalent of a 200+ MHz Apple II. All I know is
that it flies under emulation, and is a real pleasure to use.
Now, if the constraint imposed is that the program has to run on either
a real or emulated 8-bit Apple IIe, I suppose I'd use either Bredon's
Sourceror (from Merlin) or Bob Sander-Cederlof's S-C disassembler, but
as I mentioned, they're just not in the same league as BrkDown, either
feature wise, or in ease of use.
OTOH, based on your earlier work I know that you're a skilled 6502
assembly language programmer, so I imagine you'd have no problem
mastering either one of the (2) 8-bit disassemblers I mentioned.
Hugh Hood
On 2/19/2018 12:09 PM, James Davis wrote:
>
> Hi Hugh,
>
> BrkDown is just for the Apple IIGS, right?
>
> What 6502 Disassembler is best for running on an Enh. Apple IIe or in AppleWin?
>
> Also, for running on an IBM/Windows PC? CiderPress?
>
> James Davis
>
|
|
|
|
| Re: dissasmbler [message #363923 is a reply to message #363887] |
Tue, 20 February 2018 10:26 |
|
|
Originally posted by: R.Kiefer.SPAEM
James Davis wrote:
> Also, for running on an IBM/Windows PC?
With Windows I like to use DASMx 1.40. Actually I write my own
Disassembler based on the User Interface of DASMx.
Regards, Ralf
|
|
|
|
| Re: dissasmbler [message #363932 is a reply to message #363892] |
Tue, 20 February 2018 14:18 |
|
|
Originally posted by: James Davis
On Monday, February 19, 2018 at 11:52:13 AM UTC-8, qkumba wrote:
> For the PC, I recommend IDA (the Interactive DisAssembler) from www.hex-rays.com.
> There's a free version that supports the 6502 CPU.
Thank Qkumba,
I see that Hex-Rays also has an IDC (Interactive DeCompiler).
Somebody was asking about decompiling last week in a post here on csa2. Lets hope they see this and take note of it.
James Davis
|
|
|
|
| Re: dissasmbler [message #363933 is a reply to message #363906] |
Tue, 20 February 2018 14:23 |
|
|
Originally posted by: James Davis
On Monday, February 19, 2018 at 9:16:19 PM UTC-8, Hugh Hood wrote:
> James,
>
> You are correct. Ewen Wannop's BrkDown is a IIGS GS/OS desktop
> application. These days I almost always run it on a Windows 10 machine
> with the GSPort emulator. At the emulator's 'unlimited' speed setting,
> supposedly it's the equivalent of a 200+ MHz Apple II. All I know is
> that it flies under emulation, and is a real pleasure to use.
>
> Now, if the constraint imposed is that the program has to run on either
> a real or emulated 8-bit Apple IIe, I suppose I'd use either Bredon's
> Sourceror (from Merlin) or Bob Sander-Cederlof's S-C disassembler, but
> as I mentioned, they're just not in the same league as BrkDown, either
> feature wise, or in ease of use.
>
> OTOH, based on your earlier work I know that you're a skilled 6502
> assembly language programmer, so I imagine you'd have no problem
> mastering either one of the (2) 8-bit disassemblers I mentioned.
>
>
>
>
>
> Hugh Hood
>
>
> On 2/19/2018 12:09 PM, James Davis wrote:
>>
>> Hi Hugh,
>>
>> BrkDown is just for the Apple IIGS, right?
>>
>> What 6502 Disassembler is best for running on an Enh. Apple IIe or in AppleWin?
>>
>> Also, for running on an IBM/Windows PC? CiderPress?
>>
>> James Davis
>>
Thanks Hugh,
I used to be, but not so anymore. Lately, I'm just analyzing Apple II's 6502 Old Monitor and Autostart (New Monitor II) ROMs. I'm not programming at all anymore.
James Davis
|
|
|
|
Members
Search
Help
Register
Login
Home
