Thanks again, I tried your suggestions, the sleep statements made no bearing on the situation, as for the command line options, the same options are present whether it hangs or not.
your X display configuration recollection has me thinking in that direction now.
Failure with either no debugging flags or just +crypt results in BLOCK A
Success results in BLOCK A+B, in the case of +crypt, a lot of crypt messages appear in BLOCK B
BLOCK A, appears during failure and success
Code: Select all
fixme:heap:RtlSetHeapInformation 0x110000 0 0x32fda4 4 stub
fixme:heap:RtlSetHeapInformation 0x110000 1 (nil) 0 stub
fixme:heap:RtlSetHeapInformation 0x20f0000 0 0x32fde8 4 stub
fixme:heap:RtlSetHeapInformation 0x20f0000 1 (nil) 0 stub
fixme:process:SetProcessDEPPolicy (1): stub
fixme:ver:GetCurrentPackageId (0x2bbea08 (nil)): stub
fixme:thread:SetThreadStackGuarantee (0x2cbe9d0): stub
fixme:imm:ImmDisableTextFrameService Stub
fixme:winsock:WS_getsockopt WS_SO_CONNECT_TIME - faking results
fixme:crypt:CryptProtectMemory (0x1b28890 512 00000000): stub
fixme:d3d9:D3DPERF_GetStatus (void) : stub
fixme:ntdll:NtQueryInformationJobObject stub: 0x1c8 2 0x3c0ce98 48 (nil)
fixme:ntdll:NtQueryInformationJobObject stub: 0x1c8 9 0x3c0ce28 112 (nil)
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:process:SetProcessDEPPolicy (3): stub
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:imm:ImmDisableTextFrameService Stub
fixme:thread:GetThreadPreferredUILanguages 56, 0x33f624, (nil) 0x33f620
fixme:winsock:WSALookupServiceBeginW (0x33f690 0x00000ff0 0x33f6d8) Stub!
fixme:iphlpapi:NotifyAddrChange (Handle 0x33f568, overlapped 0x2bf9b88): stub
fixme:win:RegisterDeviceNotificationW (hwnd=0x1006e, filter=0x33f748,flags=0x00000000) returns a fake device notification handle!
fixme:win:RegisterDeviceNotificationW (hwnd=0x1006e, filter=0x33f748,flags=0x00000000) returns a fake device notification handle!
fixme:win:EnumDisplayDevicesW ((null),0,0x33edb4,0x00000000), stub!
fixme:advapi:RegisterTraceGuidsW (0x495320, 0x24ef248, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x24a4f04, (null), (null), 0x24ef260): stub
fixme:advapi:RegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000}
fixme:winsock:WSALookupServiceBeginW (0x33dba0 0x00000ff0 0x33dbe8) Stub!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x2bf9b88): stub
fixme:advapi:UnregisterTraceGuids deadbeef: stub
fixme:heap:RtlSetHeapInformation 0x110000 0 0x32fda4 4 stub
fixme:heap:RtlSetHeapInformation 0x110000 1 (nil) 0 stub
fixme:heap:RtlSetHeapInformation 0x20f0000 0 0x32fde8 4 stub
fixme:heap:RtlSetHeapInformation 0x20f0000 1 (nil) 0 stub
fixme:process:SetProcessDEPPolicy (1): stub
fixme:ver:GetCurrentPackageId (0x2bbea08 (nil)): stub
fixme:thread:SetThreadStackGuarantee (0x2cbe9d0): stub
fixme:winsock:WS_getsockopt WS_SO_CONNECT_TIME - faking results
fixme:crypt:CryptProtectMemory (0x1b28890 512 00000000): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x3c0e238,0x00000000), stub!
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x3c0d0a8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x3c0ce98,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:imm:ImmDisableTextFrameService Stub
fixme:wtsapi:WTSRegisterSessionNotification Stub 0x30054 0x00000000
fixme:crypt:CryptUnprotectMemory (0x1b28890 512 00000000): stub
fixme:crypt:CryptProtectMemory (0x1b28890 512 00000000): stub
BLOCK B, follows A only upon success
Code: Select all
fixme:win:EnumDisplayDevicesW ((null),0,0x3c0dc08,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x3c0de68,0x00000000), stub!
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x8aee9a8): stub
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
fixme:d3d9:D3DPERF_GetStatus (void) : stub
fixme:ntdll:NtQueryInformationJobObject stub: 0x2c4 2 0x3c0ce30 48 (nil)
fixme:ntdll:NtQueryInformationJobObject stub: 0x2c4 9 0x3c0cdc0 112 (nil)
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:process:SetProcessDEPPolicy (3): stub
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:imm:ImmDisableTextFrameService Stub
fixme:thread:GetThreadPreferredUILanguages 56, 0x33f624, (nil) 0x33f620
fixme:winsock:WSALookupServiceBeginW (0x33f690 0x00000ff0 0x33f6d8) Stub!
fixme:iphlpapi:NotifyAddrChange (Handle 0x33f568, overlapped 0x2bf9b88): stub
fixme:win:RegisterDeviceNotificationW (hwnd=0x1006e, filter=0x33f748,flags=0x00000000) returns a fake device notification handle!
fixme:win:RegisterDeviceNotificationW (hwnd=0x1006e, filter=0x33f748,flags=0x00000000) returns a fake device notification handle!
fixme:win:EnumDisplayDevicesW ((null),0,0x33edb4,0x00000000), stub!
fixme:win:FlashWindowEx 0x3c0e3e4 - semi-stub
fixme:advapi:RegisterTraceGuidsW (0x495320, 0x24ef248, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x24a4f04, (null), (null), 0x24ef260): stub
fixme:advapi:RegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000}
fixme:winsock:WSALookupServiceBeginW (0x33dba0 0x00000ff0 0x33dbe8) Stub!
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:process:SetProcessDEPPolicy (3): stub
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:advapi:RegisterTraceGuidsW (0x495320, 0x24ef248, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x24a4f04, (null), (null), 0x24ef260): stub
fixme:advapi:RegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000}
fixme:gdi:GdiInitializeLanguagePack stub
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:winsock:WSALookupServiceBeginW (0x3cde0a0 0x00000ff0 0x3cde0e8) Stub!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x2bf9b88): stub
fixme:advapi:UnregisterTraceGuids deadbeef: stub
This got me thinking about the WIN message that shows up at the first entry in BLOCK B.
I was unable to upload the log files for both +win and +crypt both for success and failure, so what should I be looking for in them?