09-07-2008, 03:34 PM
I am sorry I have to bring-up the same issue. After version 2.3.0.2 was released I tested it primarily in 2 personal computers, out of a total of five, in which it did not work with previous releases and it worked. Unfortunately this was not the case of the remaining 3 computers in which it did not work. Let me mention that I do mean that these 5 computers are actually my personal computers, they use the same software, even the same releases.
I have checked in MSDN (http://msdn.microsoft.com/en-us/library/bb762115(VS.85).aspx) and I found the following rather relevant information, which - I am afraid - I am not in a position to further implement :
If COM is initialized using CoInitializeEx with the COINIT_MULTITHREADED flag, SHBrowseForFolder fails if the calling application uses the BIF_USENEWUI or BIF_NEWDIALOGSTYLE flag in the BROWSEINFO structure.
I am wondering whether there exists a software tool to map the memory at the instance that QM crashes or any other useful debugger tool.
Any advice much appreciated.
I have checked in MSDN (http://msdn.microsoft.com/en-us/library/bb762115(VS.85).aspx) and I found the following rather relevant information, which - I am afraid - I am not in a position to further implement :
If COM is initialized using CoInitializeEx with the COINIT_MULTITHREADED flag, SHBrowseForFolder fails if the calling application uses the BIF_USENEWUI or BIF_NEWDIALOGSTYLE flag in the BROWSEINFO structure.
I am wondering whether there exists a software tool to map the memory at the instance that QM crashes or any other useful debugger tool.
Any advice much appreciated.