I've been trying to get AC Revelations to run (with skidrow crack), however, the ubisoft launcher keeps crashing (this happens regardless of whether a crack is installed). I've tried to narrow the problem down and I'm noticing a socket gets closed and then called again by a WS_select. The socket is getting closed by a WS_closesocket command which happens right after WSAAsyncSelect is called with (socketid, NULL, 0, 0). I'm suspecting that among these 3 commands, one of them is not working according Microsoft's(not so well written) standards. Sadly I'm no good with these things and would like it if someone could log on irc and help me with this issue.
I'm trying to attach a file but the forum keeps denying me that ability. So far ac, txt and no file extension have failed... ah zip is allowed.
Regardless, here are the last lines until the null pointer exception occurs:
trace:winsock:__WSAFDIsSet (1608,0x189de8e0(0))
trace:winsock:WS_select read 0x189de7dc, write (nil), excp 0x189de8e0 timeout 0x189de7d4
trace:winsock:WS_select read 0x189de7dc, write (nil), excp 0x189de8e0 timeout 0x189de7d4
trace:winsock:WS_select read 0x189de7dc, write (nil), excp 0x189de8e0 timeout 0x189de7d4
trace:winsock:WS_select read 0x189de7dc, write (nil), excp 0x189de8e0 timeout 0x189de7d4
trace:winsock:WS_shutdown socket 0648, how 2 0
trace:winsock:WS2_register_async_shutdown s 1608 type 1
trace:winsock:WS2_register_async_shutdown s 1608 type 2
trace:winsock:WSAAsyncSelect 648, hWnd (nil), uMsg 00000000, event 00000000
trace:winsock:WS_closesocket socket 0648
trace:winsock:WS_select read 0x189de7dc, write (nil), excp 0x189de8e0 timeout 0x189de7d4
wine: Unhandled page fault on write access to 0x00000000 at address 0x682842 (thread 0044), starting debugger...
AC Revelations
AC Revelations
- Attachments
-
- output.zip
- (2.85 KiB) Downloaded 168 times