Yes, that's easy.  Put a Fix 7 towards the beginning of your program.  Remember to put a Fix 6 towards the end!
(Fix 0 - 9 are found next to Float in the Mode menu.)

Thanks ztrumpet! Got it working now! Almost no waiting for screen to load!

Sorry for the double post.  Are you really adding Mode 7?  If I wasn't stopping programming after S.A.D. (though I'll most likely still be on the site), I would serious use Axe for that.

why does Axe need so much space when running a program? I get many times an ERR:OUT OF MEM, while I just have left a little less than the size of my program. this is really very annoying, you know! is this a problem that can easily be fixed? or is it something that is needed for Axe? please help! I'm running out of mem this way! I can't develop any further right now! and how does the read from archive function work exactly? I don't understand the Commands documentation with GetCalc(PTR,FILE) or something like that...

ALternatively, you can make your game run through Ion or Doors CS. MirageOS can work too, but I think you can't use interrupts nor L2 in it.

Doing so lets you run Asm() programs with like 100 bytes of RAM left.

You can run it from the PRGM menu, though, right? (even without the Asm() command)

The user manual has been updated since I added the file commands, if you haven't looked at it recently, try the newest version.

Here is a little more technical insight.  Normally you use pointers to access something in ram, but only 65536 bytes of memory can actually be read because that's all the combinations you can make with only 2 bytes.  That's fine because there's only 2 ram pages anyway corresponding to 32768 bytes total.  But when it comes to reading from the archive, there is MUCH more data, 2 million bytes on the TI-84+SE.  So in order to compensate for this, you have to use files which you can think of as "extended" pointers.  Each file is 3 bytes corresponding to a page number and pointer within that page.  Because the files obviously have to be handled differently, they can only be used in a few commands: Copy(), {}, and GetCalc() are used most often.  If you need to use the data for other things like sprite drawing, you can use the Copy command to copy it to ram and then refer to it using a normal 2 byte pointer.

the axe "variables" are stored in the allocated portion just before L1, are they not quigibo(im just guessing here). if i wanted to set them all to the same value with one command instead of [num]->A->B etc could i just use for(A,0,number of vars:0->{L1-[whatever the offset is]+L:end? also, i too am unsure as to how reading from the arch works(probably because i havent read the command lists in a while, but because someone else already brought it up i dont feel guilty about asking )

the easiest way is (imo):
5->A
Fill(L1-56,56

and @quigibo: are can the current 2 Archive pages also be read? when running an App with data stored into GDB1, I can just do a Pt-On(X,Y,GDB1) on my calc, or is this strange?