Nope, mine is stable on 2.53

Mine is stable too on 2.53

I do of course get the defragmenting message but no ram clears fortunately. I have no problems with axe. I have revision L (incompatible with Ti-BoySe) so actually my faulty hardware (as defined in the Ti-BoySE Readme) is great :p

major weird!!!!!!!
Might like  to check this out.
,ight give out source tomarow if i have time.
story:  making gray style for my etch-1-sketch.

problem 1:  Ok this is the weird one.  i have the screen with a couple of lines on it.  i press storepic.  nothing happens, good.  recall it good too.
not i try a couple of gray style lines.... i press store...  they all dissapear.

restart prof from fresh.  i do a couple of gray lines and do recall, they all turn black, aka no longer gray...
no i do inverse screen. black to white and hite to black.

all goes black but for where the lines were.  they are gray again?!?!?!!?...



problem 2:  when i have the innterpruts on i can't seem to get this to work at all ,  getkey->g

help would be appriciated

I'm not too sure if I understand either. You should probably post more details about what you want to happen. The code would help too, if you post it tomorrow.

Happybob, I would appreciate it if you could spend a little more time forming your sentences with correct punctuation and grammar because it becomes difficult to read and especially for a bug report, clarity is really important.

For your first point, the back buffer used to draw grayscale is the same back buffer used in the Recalpic and Storepic commands. If you want to back up a grayscale screen, you have to create 2 additional buffers with Zeros(768) and then back up both the front and back buffers to each one using the Copy() command.

Your second point, the OS getkey command does not work with interrupts.  You will have to use direct keys instead like getkey(15) for instance.

Third, you mentioned to me in your PM that your AXEGUESS example program was not correctly returning random numbers and was the same number every time you played the game.  Has anyone else had a problem with this, especially if you use the modified OS by BrandonW.

the getkey->G   was very inportant in my program because u would have it double check with getkey(...)
for example if i press left, down, and enter; it acts as if i were holding down +.

This is actually the keyboard hardware's fault, and is unfixable. Basically, whenever you press three keys that make the corners of a box in the table on http://wikiti.brandonw.net/index.php?title=83Plus:Ports:01, the fourth corner will be read as pressed. This is, as said above, unfixable, and if it's a problem, you'll need to use other keys that won't interfere with each other.
(Also, less important, be aware that you can have multiple boxes, and that the falsely read corners can still act as corners for another box)

When I compile any program that ends with DispGraph or ClrDraw, Axe begins the first pass, freezes, and after a few seconds displays "ERR: OUT OF MEM."  If I add a space after ClrDraw or DispGraph, it compiles fine.

This was mentioned earlier, and it's a random bug that doesn't allow you to end programs with tokens that could have an "^r" after them. IIRC, Quigibo has already fixed this for 0.4.0
Edit: ninja'd