Yes, I saw your post, piet...
I bookmarked it and will be watching to see what kind of response you get. You probably would need to be a bit more specific about the code, that you have some C++ code and that you do a lot of calls to the IPP functions. Profiling isn't a bad suggestion, but in my opinion, my suggestion about handled exceptions wasn't a bad suggestion either, as I think your prior experience had to do with error / status codes and making the app continue, which is not the appropriate thing to do in all situations, but that's not the same thing as proper exception handling.One other thing is that if you can compile with VS, you can enable runtime checks and you may find various uninitialized variables or array bound problems, and whatever else the runtime check option looks for. It's been a while, so I don't remember all that enabling that does, but I do remember that what it found helped reduce and/or eliminate instances where the call to the credit authorization DLL didn't complete due to a crash in the DLL. Customers kinda got cranky when they had double holds on their cards for purchases, so finding what was causing the crashes was a very good thing.
As for the preset, I sent you a PM. Let me know what you think about it. It likely sounds very similar. I think we're in the same general power envelope too.
