CompuServe Messages

[>> Continued from previous msg] last stack state can be examined before MFC calls exit. (This is in fact a problem under Win16 as well.) For all you MFC developer's attempting to run MultiThreaded apps under NT you MUST test with SMP boxes. Alot of these problems DID NOT really rear their ugly heads until they were tested on an SMP box. (Note: # of processors should ideally match number of max concurrent threads for correct stability) I fear that many "shops" may not have SMPs that will be releasing MFC based multi-threaded NT apps that will not run due to this reality. Note: MS's temporary solution of ONLY KEEPING MFC in your primary thread is NOT A SOLUTION but a stopgap, in my opinion! Stripping your app's resources of their MFC roots just to use them in code of a secondary thread is ludicrous. Any decent C++ program will have so much in the base classes for an object that this becomes quite a phase shift, and a royal pain! Let's all hope and pray that MS will fix MFC 2.0 for NT to be multi-threaded, but if it's a straight port of the DOS code IT WON'T WORK, I guarantee it! Brent Ingraham DCA – NT Dev Team There is 1 Reply.