Hi,
I'm currently running the Guild Wars 2 Beta updater and just did some runs with debugging on. Now when I search on Google like usual to find out what most messages mean, it's mostly always the same. People saying like: you can ignore those messages etc. Ok, I'm fine with that no problemos
. But I sometimes wonder if anyone except the WINE devs know the answer. People always say evading stuff about those messages. No offense, it's just what came to my attention when looking this stuff up every time I try to find solutions for crashes.
Ok back to the point
. So it's already commonly known that the GW2 updater crashes about every 10.000 files that it has downloaded. The Updater itself gives an internal error about Direct3D memory allocation (overflow?). Further more, I got these recurring messages in my logs. Even tho some messages won't really be "the" problem, I was wondering if anyone ever knows how to like fix errors like "menubuilder".
Here are some recurring messages I found in my logs:
Code:
err:menubuilder:convert_to_native_icon error 0x80070002 creating IWICBitmapDecoder
fixme:heap:HeapSetInformation 0x1c54000 0 0x32fdd8 4
fixme:process:SetProcessDEPPolicy (1): stub
fixme:process:GetLogicalProcessorInformation (0x32f0c8,0x32f6f4): stub
fixme:gameux:GameExplorerImpl_VerifyAccess (0x1a1878, L"C:\\Program Files\\Guild Wars 2\\Gw2.exe", 0x32f598)
fixme:thread:SetThreadStackGuarantee (0x3286f650): stub
fixme:process:GetLogicalProcessorInformation (0x0,0x3306e98c): stub
fixme:process:GetLogicalProcessorInformation (0x3306e9b4,0x3306e98c): stub
fixme:process:GetLogicalProcessorInformation (0x0,0x3306e994): stub
fixme:process:GetLogicalProcessorInformation (0x3306e9bc,0x3306e994): stub
fixme:process:GetLogicalProcessorInformation (0x0,0x3306e988): stub
fixme:process:GetLogicalProcessorInformation (0x3306e9b0,0x3306e988): stub
fixme:winsock:WS_getsockopt WS_SO_CONNECT_TIME - faking results
fixme:d3d:init_driver_info Unable to find a driver/device info for vendor_id=0x10de device_id=0x8a0 for driver_model=3
fixme:win:EnumDisplayDevicesW ((null),0,0x3306ca5c,0x00000000), stub!
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category {33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
err:avicap:query_video_device Video 4 Linux support not enabled
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:d3d:debug_d3dformat Unrecognized 0x434f5441 (as fourcc: ATOC) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x434f5441) in the format lookup table
fixme:imm:ImmDisableTextFrameService Stub
fixme:wtsapi:WTSRegisterSessionNotification Stub 0x60064 0x00000000
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x34fef638): stub
fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4130413, 0000: semi-stub!
Can anyone tell me what stubs do? I read something about that it means WINE tells the system its fine to go on running, but can't actually handle the error/task?
Oh, I fixed this one by re-installing SAMBA (with SMBUp) on my OSX Lion distro:
Code:
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
That's about it for now. I hope someone recognizes some and maybe knows solutions to it
