Doors CS is coming along smoothly; program deletion now works, libbed SOS programs are now bug-free, and Doors CS ALE (addended library extensions) are progressing rapidly. One particular feature that I just designed and created is the RAM Recovery Tool. If you have ever pressed [2nd][Quit] at a prompt in a BASIC program running under MirageOS, you'll know what I'm talking about. If the TI-OS interrupts Doors CS at any point with error messages, for example from BASIC programs, you would normally lose about 3KB of RAM. However, I have built a feature into the Doors CS loader that detects residual data in RAM and automatically deletes it, reclaiming the lost space and incorrect mem errors. Also, I have made a fast routine that deletes and recreates prgmADCS so that it stays in high usermem; however, when Doors CS quits, the TI-OS BASIC parser doesn't know where to continue; I need someone to explain how the parser (rom call _parseInp) remembers where the next instruction to be parsed is.