More random questions...
What would be the best way to get text() functionality without actually using the command (speed reasons)?  My first thought is to just tilemap the screen and have sprites be letters.  However, depending on how many different characters I use, this could end up being a lot of sprites to define.  Are there any better methods out there?

Anyone have any methods for better grayscale?  I'm currently using Hayleia's method, but even after extensive calibration I still get light diagonal lines running down (these are called scanlines right?). The best I've gotten is a loop with Pause(22), but this makes it impossible to do anything else.  Just using four level grayscale.

Something isn't clicking for me.  Could you provide a quick example of a program that would store some text into a string?  My current attempts don't seem to actually be doing anything, despite compiling and running fine.

(Also, sometimes it is good to look on the forums before making a new topic, or try Googling a bit (second link when typing "run basic progs in axe"))

In my defense (not that I'm justifying it or anything), neither forum searches nor googling turned up the results I wanted.  In fact, most of what I got was requests on translating Basic code into Axe.  Shmibs, I'm basically trying to create a string, based on user input, that can later be recalled by the user.  Since Axe support for this is...lacking...I figured Basic would be much simpler to implement.

So...should I ask again somewhere else?  Or will somebody see this?

I feel like this should be incredibly easy, but experimentation has not given me any help.  Obviously its easy to execute an Axe program from within Basic, but how can the process be reversed?  Essentially I'd like to use the simpler data handling of basic for a portion of my program.

I don't quite understand how pt-change twice will erase the cursor?  Will it not just undo itself?  As for using the backbuffer, that's quite a good solution.  My only worry would be the cursor being even harder to see while moving.
Runner, I couldn't look it up and redraw (as far as I knew) because what is underneath is not another sprite, but text from the text() command.  Now that you mention the pt-get command though, I have solution.
Thanks for the quick replies, I'll try these and see what works best.

Edit:  Is there a reason text wouldn't display?  I've tested in other programs and it works fine, it even displays when I put it in the program loop.  But if it's just at the start it won't display...

Edit 2:  It's due to dispgraph.  Is there a solution to this?

Edit 3:  Ah.  Fix 5.  May I ask why this is necessary instead of just having it occur by default? 

Yes with a For loop.

While I do appreciate any help...I have no idea how a for loop could possibly improve handling of getkey routines.  Could you perhaps elaborate on how to use it?  (Not the for loop, I can use those fine, using it for a better input routine).