Another thing, if you create a spurious runtime error, like calling a function that doesn't exist in the definit function in your macro, when you re-start slickedit with that error present, slickedit only half starts up and in my case, gets an error in autosave shutting down as well. I guess it's hard for slick to handle this any better though.