Re: A89: Line 1111 Emulator and 32k limit?


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

Re: A89: Line 1111 Emulator and 32k limit?




Then what about Zelda, SMQ, SFT2, SMA, Big Dyna B2?  Are they "paged,"
isn't that just one of the z80's "feature?"  Can't the m68k handle progs
larger than 32k?

--h4X0r

----- Original Message -----
From: "Scott Dial" <wrath@calc.org>
To: <assembly-89@lists.ticalc.org>
Sent: Saturday, December 25, 1999 10:02 PM
Subject: Re: A89: Line 1111 Emulator and 32k limit?


>
> It is hard to understand what you did, but I thought there had always
> been a 32k limit on ASM programs because anything larger would have to
> be paged
>
> TurboSoft@aol.com wrote:
> >
> > l found the problem; why l would get "Line 1111 Emulator" errors.  l
don't
> > know the mechanics of how it has to happen or how to fix it, but l think
l'm
> > on to something.  Maybe this is common knowledge, l dunno.  But
anyway...
> > What l was trying to do was make a file (snoboard.89z) that compiled to
be
> > 30521 bytes.  l noticed that running this file would cause crashes on
the
> > emulator, after running the first part of the program (displaying the
title
> > screen).  l noticed that taking out a part of the program l had just
written
> > (which was totally isolated from the crashing part of the code) would
end the
> > error and the game would run normally.  After taking this code out, l
tried
> > just putting in one line of the code (a ROM call) and the program would
again
> > crash.  l removed this line of code, and put it in a function at the
bottom.
> > This also caused it to crash.  l wondered if "there was a limit as to
how
> > many ROM calls a program could have?"  l then began to think that the
program
> > was too large.  So l just repeated the command
> > c = 0;
> > until having that command one more time would cause the error.  The max
size
> > of the program at this point was 34525 bytes.  l then cut out all of the
code
> > between where the 1111 error was taking place and the end of the
program.  l
> > compiled the program again, and it was 1725 bytes.  Here l was thinking
that
> > l was getting an error as a result of 32768 bytes being between a
library
> > call and the end of a program (is this right?).  So l took the 34525
byte max
> > that l had on the running program, and subtracted 32768 from that and l
got
> > 1757 bytes -- pretty close to 1725.
> > So, l'm thinking...if this is the problem -- the latter 32k of code just
> > being there -- how do l fix this?
> >
> > --TurboSoft
> >
> > Visit the TURBOSOFT HOMEPAGE:  The most current Basic and C programs
created
> > by TurboSoft for the 89, and the most 89 web links.
> > <A HREF="http://turbosoft.ticalc.org/">http://turbosoft.ticalc.org/</A>
>
> --
> Scott "_Wrath_" Dial
> wrath@calc.org
> ICQ#3608935
> TimeCity AI Guy II - www.timecity.org
> Member of TCPA - tcpa.calc.org
> __________________________________________
> NetZero - Defenders of the Free World
> Get your FREE Internet Access and Email at
> http://www.netzero.net/download/index.html
>
>

__________________________________________
NetZero - Defenders of the Free World
Get your FREE Internet Access and Email at
http://www.netzero.net/download/index.html


Follow-Ups: References: