I filed a support case with Intel on this issue, and apparently they already knew about it! The problem has been in their issue tracking system for a while, but hasn't been solved. So they were able to reproduce it, and escalate the issue to a higher level. Now here's a silly question: How can a piece of software be released, through multiple revisions, with such a glaring hole??? You can't debug ANY native code without VS.NET 2k3 crashing! How that ever got through Intel's Q/A is beyond me... -- Paul "I drank... WHAT?"