On Sat, Jun 22, 2013 at 6:34 PM, Nicolas Pomarède
<npomarede@xxxxxxxxxxxx <mailto:npomarede@xxxxxxxxxxxx>> wrote:
On 22/06/2013 18:21, Troed Sångberg wrote:
on real hardware ;) Thanks for the heads up - I hadn't looked
into why
yet but I did suspect our memtop handling.
Note that in stMemory.c we set ff8001 to what the user chose as RAM
size in Hatari configuration, unless another program modify this
byte, you should be safe to read it to know how many RAM is
"detected" on STF/STE.
So using ff8001 should give correct results under real HW or Hatari
; are you using another way to detect RAM size ? (writing at higher
RAM location and checking if you read what you just wrote ?)
No, but my code writes to $ff8001 ;) If that doesn't stick in Hatari it
could indeed cause the behaviour I've seen - I think. As I said, I
haven't debugged it.
(The code I have working on Hatari but not on real hardware has to do
with where TOS puts the video buffer - which I assume is done using
memtop. I'll look into it when I'm back with my STE in a few weeks)
/Troed