Re: A82: Galaxian bug......not found???

To: assembly-82 <assembly-82@lists.ticalc.org>
Subject: Re: A82: Galaxian bug......not found???
From: Dines Christy Justesen <c958362@student.dtu.dk>
Date: Mon, 20 Apr 1998 22:47:10 +0200 (METDST)
Delivered-To: assembly-82-outgoing@towerguard.unix.edu.sollentuna.se
Reply-To: assembly-82@lists.ticalc.org


If the problem is that the system memory gets messed up you would get
problems with both Ash and CrASH. If the problem is that the programs
overwrites some data stored in the shell you would see a problem like the
one seen with Galaxian, since the data in Ash and Crash is stored in
different places. One thing which could cause the problem is that it
overwrites the data used by Crash to derelocate the program. 

Dines
-----Original Message-----
From: Barubary <darkstar_usa@pipeline.com>
To: assembly-82@lists.ticalc.org <assembly-82@lists.ticalc.org>
Date: 20. april 1998 03:09
Subject: Re: A82: Galaxian bug......not found???


>
>>Barubary-  Are you sure the Galaxian bug is caused by the use of that 
>>display routine? I thought it was but now I'm not so sure. I replaced 
>>the routine with ROM_CALL(DISP_GRAPH) which required changes throughout 
>>the source, but still the bug occured. I originally thought the display 
>>screen routine was the cause of the bug, but that was mainly based on 
>>the fact that the routine was the last common link between Orzunoid and 
>>Galaxian. But it could be something else. Tonight I'll check the sources 
>>for anything similar. Could it be the highscore routine?
>>  Sam
>
>ANYTHING that writes past GRAPH_MEM+767 WILL cause problems...  you need
>to scan the source code checking to see how far it can possibly write
into
>RAM.
>
>-- Barubary
>
>

_______________________________________

Dines Justesen
Email: dines@post1.com or
       c958362@student.dtu.dk
WWW  : http://www.gbar.dtu.dk/~c958362/
_______________________________________

Prev: Re: A82: Orzunoid (now Ash 3.1)
Next: Re: A82: Orzunoid
Index(es):
- Main
- Thread