Re: A89: ReCompiling Phoenix89


[Prev][Next][Index][Thread]

Re: A89: ReCompiling Phoenix89




It says: "
_main:
         lea      $600000,a6                 ; Allow relative port addressing
         bclr     #2,1(a6)                   ; Allow writes to low memory
         move.w   #$d1,$16(a6)               ; Set Int5 frequency to 30Hz

 ; If you want to make a "turbo-charged" version of this game, you can
 ; try replacing the $d1 on the line above with $e1.  This will make the
 ; game run about 1.5 times its normal speed.
" in the code, and it compiles fine.  When I change it to: "
_main:
         lea      $600000,a6                 ; Allow relative port addressing
         bclr     #2,1(a6)                   ; Allow writes to low memory
         move.w   #$e1,$16(a6)               ; Set Int5 frequency to 30Hz

 ; If you want to make a "turbo-charged" version of this game, you can
 ; try replacing the $d1 on the line above with $e1.  This will make the
 ; game run about 1.5 times its normal speed.
", the compiler crashes withour giving an error.  I assume something's messed up with the compiler,
so I reinstalled it, and no dice.

-Miles Raymond

-----Original Message-----
From: Daniel7073@aol.com <Daniel7073@aol.com>
To: assembly-89@lists.ticalc.org <assembly-89@lists.ticalc.org>
Date: Saturday, December 12, 1998 3:18 PM
Subject: Re: A89: ReCompiling Phoenix89


>In a message dated 98-12-11 23:42:13 EST, you write:
>
> > I've taken a look at the code for Phoenix, and it says to change the
>  > d1 in the beginning to an e1 (why e?) for a faster game.  So I did,
>  > but now I can't compile it.  I downloaded Phoenix again and it
>  > compiled fine, then I changed d1 to e1 and it wouldn't compile, it
>  > just crashed.  Anyone have any ideas?
>
>When you changed it to e1, does it say #$e1, #e1, $e1, or just e1?  It should
>say #$e1.  The # signifies that you are passing a number, not a memory
>location, and the $ says that the number is hexadecimal.  Also, are there any
>spaces between the comma and the operands?  I don't think that's allowed.
>If this doesn't work, what error does the compiler give you?
>
>Daniel Imfeld


Follow-Ups: