Author Topic: Bug Reports (Read 455754 times)

Quigibo · « **Reply #345 on:** June 12, 2010, 10:12:41 pm »

I THINK I MIGHT HAVE FOUND IT!

I need some asm expert to answer this question:

The user ram is 24-ish KB right? So it is possible to make a program over 16KB right? You can archive this program right? Wouldn't that imply that you can have a single program take up 2 pages of rom? Does that also mean that a program less than 16kb can also take up 2 pages since none of the rom is actually wasted? Because that would mean I have to switch pages at some point during compile time, something I'm currently not doing when reading from archive. Of course if any of these assumptions are wrong, then it must be something else...

calc84maniac · « **Reply #346 on:** June 12, 2010, 10:24:57 pm »

Quote from: Quigibo on June 12, 2010, 10:12:41 pm

I THINK I MIGHT HAVE FOUND IT!

I need some asm expert to answer this question:

The user ram is 24-ish KB right? So it is possible to make a program over 16KB right? You can archive this program right? Wouldn't that imply that you can have a single program take up 2 pages of rom? Does that also mean that a program less than 16kb can also take up 2 pages since none of the rom is actually wasted? Because that would mean I have to switch pages at some point during compile time, something I'm currently not doing when reading from archive. Of course if any of these assumptions are wrong, then it must be something else...

Oh, you seriously haven't been checking for page switching? That could explain it.

Deep Toaster · « **Reply #347 on:** June 12, 2010, 10:36:00 pm »

Funny, I could have sworn I read somewhere that flash apps are the only variables that can take up more than one page. But this explains why my calculator didn't crash on archiving a 20 KB program.

Do you think you're going to be able to add page switch checking in the next version of Axe?

And I've read your signature, but I'm still wondering: When do you think you will finish 0.3.0 (i.e., June, July, or August)?

calc84maniac · « **Reply #348 on:** June 12, 2010, 10:41:17 pm »

Even a two-byte variable can span more than one page, if you archive it at just the right time

Quigibo · « **Reply #349 on:** June 12, 2010, 10:48:51 pm »

Thanks, so that should finally stabilize it. I'm adding page swapping now, it's fairly simple. I just have to make sure that only my main routines are called when reading bytes and that I'm not using any exploits in the code anywhere. 0.3.0 will come in less than a week, but I won't have app compiling working yet unfortunately. But there is another cool new feature that will come in handy

Deep Toaster · « **Reply #350 on:** June 12, 2010, 11:14:43 pm »

Darn. This means that I won't be able to update my version until September.

0.2.6 is good enough for all I use Axe for, anyway. Really like it.

Quote from: Builderboy on June 11, 2010, 07:37:08 pm

Thats why im still ata round 0.2.4, im waiting for a stable release, either that or some sort of new feature that i cant live without.

Would you consider 0.2.5 more stable than 0.2.6?

This may have something to do with the archiving as well, since that's about when I started trying compiling from Archive. Just thought you'd like to know.

Just a tip:
Axe Parser 0.3.0 Finals coming, don't expect too much or an on-time release. Your heads will explode.
instead of
Axe Parser 0.3.0 Finals coming, don't expect too much or an on-time release. Your heads will explode.

Please disregard the "tip" above. Sorry, couldn't resist.

Just wondering: Since the 0.0s and 0.1s are called Alphas, and the 0.2s are called Betas, would 0.3.0 also count as a Beta?

DJ Omnimaga · « **Reply #351 on:** June 12, 2010, 11:59:05 pm »

Does it means program executables larger than 16 KB will not be possible at all? I was sure it could be done, considering Dying Eyes and Joltima RPGs are over 18

Quigibo · « **Reply #352 on:** June 13, 2010, 12:03:38 am »

0.3.0 will be a gamma version. Its basically the same thing as a beta version, but with a cooler name. Stability is relative. Since this problem only affects compiling from archive, you could argue that the version when you couldn't do that was more stable. But really, you can do the same thing now, its just that with the addition of new features, its usually the new stuff that can get unstable.

DJ Omnimaga · « **Reply #353 on:** June 13, 2010, 12:04:56 am »

Lol I doN,t remember hearing Gamma version before

I guess it's good though ^^

calcdude84se · « **Reply #354 on:** June 13, 2010, 08:11:12 am »

then the 0.4.x versions will be deltas, the 0.5.x versions will be epsilons... up to 0.24.x, which will be omegas...

Of course, we'll probably get 1.

before that. (maybe the 2.4.x versions will be omegas...)

ztrumpet · « **Reply #355 on:** June 13, 2010, 10:26:19 am »

Yea! I'm glad you found the problem. I'm really glad it's fixed now. Thanks Quigibo!

Yay, 1-5 days before a Gamma release!

calcdude84se · « **Reply #356 on:** June 16, 2010, 04:47:22 pm »

Apparently, this code

Code: [Select]

Repeat 1=2
If getKey=15
Goto E
End
-1→B
62→A
Repeat A>62
Shade(A)
A+B→A
If A<1
-B→B
End
End
End
Lbl E
Shade(47)

causes the BLOD's. I refuse to test this myself, so I cannot verify it. However, I am unsure why this would happen (I calculated the range at which Shade( should cause the BLOD's to be 92-95 (decimal)) Any clues?

Quigibo · « **Reply #357 on:** June 16, 2010, 04:58:00 pm »

I don't know. The command only allows values between $C0 and $FF so it is impossible to get into test mode. Are you sure these are the blue lines of death and not just the normal blue from high contrast values?

Ikkerens · « **Reply #358 on:** June 16, 2010, 05:02:45 pm »

You could see the person that posted everything at my topic with the wave effect.

calcdude84se · « **Reply #359 on:** June 16, 2010, 05:03:03 pm »

I asked him, but he never answered and now he's gone...

Author Topic: Bug Reports (Read 455754 times)

Quigibo

Re: Bug Reports

calc84maniac

Re: Bug Reports

Deep Toaster

Re: Bug Reports

calc84maniac

Re: Bug Reports

Quigibo

Re: Bug Reports

Deep Toaster

Re: Bug Reports

DJ Omnimaga

Re: Bug Reports

Quigibo

Re: Bug Reports

DJ Omnimaga

Re: Bug Reports

calcdude84se

Re: Bug Reports

ztrumpet

Re: Bug Reports

calcdude84se

Re: Bug Reports

Quigibo

Re: Bug Reports

Ikkerens

Re: Bug Reports

calcdude84se

Re: Bug Reports