The only other thing I can think of is don't write code that raises exceptions, but sometimes that can be hard.

What kind of exceptions are you dealing with? I would hope you would know what code regions could cause an exception and protect them in one way or another. Exceptions are a sign that you are feeding / using data / parameters that are invalid, which is generally a sign of underlying problems in your code. Fixing those problems will save you frustration in the future.

Also, wrap your low-level and system calls in nicer functions that can be carefully anaylsed and 'try...catch'ed. Then forget about exceptions.

- Splat

***************************************

try
{
//my function to draw a filled circle...
Circle_Draw(x, y, color, radius);
}

//catch ANY exceptions with "..."
catch(...)
{
//unlock surface
DDSBack->Unlock(NULL);

//hide the window so
//I can see the debugger
DDCanvas->Hide();
}

***************************************

It still locked up, but I found where the problem was anyway. I wonder if the debug version of DirectX will help me with that locking up, but hurt my regular game performance???

Borland does have "finally", but in the code examples I saw, the catch(...) appeared to do the same thing(catch ANY exceptions thrown).

------------------
When life hands you lemons, throw them at God's head.

------------------
When life hands you lemons, throw them at God's head.