http://bugs.winehq.org/show_bug.cgi?id=17697
--- Comment #18 from Kenneth Robinette support@securenetterm.com 2010-02-02 11:23:37 --- (In reply to comment #17)
(In reply to comment #16)
(In reply to comment #14)
I then added the atl.dll.AtlModuleRegisterWndClassInfoA() function to the dlls/atl/atl_main.c module and it compiled clean.
You need to add it to the .spec file as well.
I believe I got AtlModuleRegisterWndClassInfoA implemented correctly, however now it looks like AtlAxDialogBoxA() is what is really causing SNetTerm to start. Both AtlAxDialogBoxA() and AtlAxDialogBoxW() are not implemented in any version of Wine. I guess I will just have to use the real Windows XP atl.dll and be done with it.
I added the logic to do a Microsoft minidump when SNetTerm aborts to aid in tracking down the problem. If I use the default Wine atl.dll, SNetTerm will abort on startup (prior to showing the window). I have tracked it down to an ActiveX control being initialiazed in the view of SNetTerm. The following is the stack trace when the SNeTerm aborts. Any ideas how to isolate where in the Wine atl.dll that is causing the problem?
SecureNetTerm!CDataSourceControl::`RTTI Complete Object Locator' isiTerminal!ATL::CComControlBase::FireViewChange+0x2d isiTerminal!ATL::IOleObjectImpl<CTerminal>::DoVerbInPlaceActivate+0x29 isiTerminal!ATL::IOleObjectImpl<CTerminal>::DoVerb+0x62 SecureNetTerm!COleControlSite::DoVerb+0x28 WARNING: Frame IP not in any known module. Following frames may be wrong. 0xfffffffb SecureNetTerm!COleControlContainer::CreateControl+0x77 SecureNetTerm!COleControlContainer::CreateControl+0x5c SecureNetTerm!COccManager::CreateDlgControl+0x21e SecureNetTerm!COccManager::CreateDlgControls+0xfb SecureNetTerm!COccManager::CreateDlgControls+0x55 0x1607fe8 SecureNetTerm!CWnd::WindowProc+0x22 SecureNetTerm!AfxCallWndProc+0x90 SecureNetTerm!AfxWndProc+0x34 user32+0x9c40a user32+0x9cdcd user32+0x9f5e0 user32+0x64960 user32+0x68c42