Hi Gabe, > The harness makes it very easy to "freeze" your app_server. The issue deals > with acquiring the engine and not releasing it (I forget the exact > terminology since it has been so long since I've looked at the stuff). The > harness has a command that acquires the engine. Whenever the app has the > engine, the app_server cannot draw since it can't acquire the engine for > itself. Apparently this somehow also interferes with the app_server > processing input, so trying to tell the harness to release the engine > doesn't > work. Anyway, if you put together some code that acquires the engine, uses > it, and then releases it without requiring user input in the middle, you > should be able to use that sort of code just fine without freezing the > app_server. Ah! Thanks for the helpful hints. Now I know in which direction to look. Best regards, -Stephan