Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!apple!bbn!bbn.com!slackey
From: slackey@bbn.com (Stan Lackey)
Newsgroups: comp.sys.atari.8bit
Subject: Re: A65 problems
Message-ID: <46731@bbn.COM>
Date: 10 Oct 89 19:15:47 GMT
References: <19810004@hpfinote.HP.COM> <46526@bbn.COM> <1010@mgse.UUCP>
Sender: news@bbn.COM
Reply-To: slackey@BBN.COM (Stan Lackey)
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 30

In article <1010@mgse.UUCP> marks@.UUCP (Mark Seiffert) writes:
>In article <46526@bbn.COM> slackey@BBN.COM (Stan Lackey) writes:
>>AMAC wouldn't run under it; I think it was because as the AMAC disk
>>is copy protected, I couldn't copy it to a DOSXE format disk.  So I had
>
>Take the copy protection out, i did it years ago it was easy and it allowed
>my to use it on my dsdd percoms. I will try to figure out what i changed,

Never mind; I did this all by myself (almost) from a suggestion from someone
else.  It was triv; I used a disassembler I got from ANTIC a few months
ago, and a little BASIC program to actually twiddle the bytes.  It starts
up faster now, now that it doesn't do the extra disk access.

Note to any possible pirate dogs:  No!

AMAC USERS READ THIS:  It looks like some people don't know the fix
to AMAC's bug in putting a label on a macro.  Just terminate each label
with a colon.  That was what I tried when I first ran into the problem,
and have never had a problem since.

Now, for the request.  Has anyone written a debugger that can be
assembled in with an AMAC source?  I was thinking along the lines of
say pushing BREAK to interrupt out of the program to get to the
debugger, doing exam/dep, and returning to execution.  Sure a
disassembler for single stepping, breakpoints, etc would be great.
OK, MAC/65 has this stuff, not to mention the assembler cartridge, but
AMAC still has its advantages.  When I made my editor, I made up
a small one that I included that could examine only, but in that
environment it was easy.
-Stan