yeah that's what I thought. One thing I worrry about, still, though, is that I am not sure what Safe RAM areas the new DCS uses. It's not even guaranteed DCS6 Axe programs will work well under DCS7. That's unless he changed none, though.

I actually have been putting off conditional compiling, I think only a few of the commands do that, and only in mirage.

The problem is that most of the built-in functions are either slower than my routines, don't take the right input or output, or don't work quite the same way.  For instance, there is a shell call for sprite drawing, but it doesn't clip the sprites.  And there is one for random numbers, but only 8-bit random numbers.  There really aren't as many routines as I first though either.  I think Doors has a lot, but other than that, the line drawing and get-pixel routines seem to be the only ones I can use.  I think I'm going to just drop conditional compiling all together until I add a new compiling mode to compile for size rather than for speed.

All commands work in all shells, the problem is just that I can't use the built in commands that come with Ion/MOS instead to save space.

EDIT: 500th post 

You can also reach the statVars safe ram through iy.

I saw now it is one of free ram used by Axe Parser. You could instead use statVars+2 for the pointer.

Maybe someone wants to do or use Axe Parser program as an assembly lib. We need to add to the documentation what safe rams are used by xLib and CelticIII if they are used too...

Yeah, i cant wait for the day when variable reading and writing are added, then we can start writing our own helper programs akin to celtic and xcopy ^^