Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Illudil
Posty: 7
Rejestracja: 11 września 2017, 19:51
Lokalizacja: Wrocław
Płeć: Mężczyzna

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: Illudil » 13 września 2017, 15:50

MrPepka pisze:Przejrzyj ten temat:
http://forum.przygodomania.pl/viewtopic.php?f=5&t=5303
I wstaw tu logi (możesz je wrzucić na jakiś serwer np. Dysk Google).


https://drive.google.com/file/d/0B9J4S7 ... sp=sharing

Awatar użytkownika
MrPepka
Przyjaciel forum
Posty: 322
Rejestracja: 08 sierpnia 2016, 15:18
Podziękował(a): 5 razy
Otrzymał(a) podziękowania: 13 razy
Płeć: Mężczyzna

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: MrPepka » 13 września 2017, 16:00

No dobra. Zobaczmy:
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Wed Sep 13 15:45:12.000 2017 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:00:18.000
................................................................
..................
Loading unloaded module list
....
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(12b8.12bc): Access violation - code c0000005 (first/second chance not available)
eax=00000000 ebx=0018eccc ecx=0c7a91d8 edx=65c50dd8 esi=00000002 edi=00000000
eip=773d016d esp=0018ec7c ebp=0018ed18 iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
ntdll!NtWaitForMultipleObjects+0x15:
773d016d 83c404 add esp,4
0:000> !analyze
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Acxtrnal!NS_FaultTolerantHeap::_FTH_ISSUE ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Acxtrnal!NS_FaultTolerantHeap::_FHT_ISSUE ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Acxtrnal!_FTH_ISSUE ***
*** ***
*************************************************************************
Unable to load image D:\TLJ\DDraw.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for DDraw.dll
*** ERROR: Module load completed but symbols could not be loaded for DDraw.dll
*** WARNING: Unable to verify timestamp for atidxx32.dll
*** ERROR: Module load completed but symbols could not be loaded for atidxx32.dll
Unable to load image D:\TLJ\dxgi.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgi.dll
*** ERROR: Module load completed but symbols could not be loaded for dxgi.dll
*** WARNING: Unable to verify timestamp for dxgi.dll
*** WARNING: Unable to verify timestamp for audiere.dll
*** ERROR: Module load completed but symbols could not be loaded for audiere.dll
*** WARNING: Unable to verify timestamp for W_Module.dll
*** ERROR: Module load completed but symbols could not be loaded for W_Module.dll
GetUrlPageData2 (WinHttp) failed: 12002.
Probably caused by : DX_Module.dll ( dx_module+173c7 )

Followup: MachineOwner
---------

0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Acxtrnal!NS_FaultTolerantHeap::_FTH_ISSUE ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Acxtrnal!NS_FaultTolerantHeap::_FHT_ISSUE ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Acxtrnal!_FTH_ISSUE ***
*** ***
*************************************************************************
GetUrlPageData2 (WinHttp) failed: 12002.

FAULTING_IP:
DX_Module+173c7
006e73c7 8b5008 mov edx,dword ptr [eax+8]

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 006e73c7 (DX_Module+0x000173c7)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000008
Attempt to read from address 00000008

CONTEXT: 00000000 -- (.cxr 0x0;r)
eax=00000000 ebx=0018eccc ecx=0c7a91d8 edx=65c50dd8 esi=00000002 edi=00000000
eip=773d016d esp=0018ec7c ebp=0018ed18 iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
ntdll!NtWaitForMultipleObjects+0x15:
773d016d 83c404 add esp,4

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_READ

PROCESS_NAME: game.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000008

READ_ADDRESS: 00000008

FOLLOWUP_IP:
DX_Module+173c7
006e73c7 8b5008 mov edx,dword ptr [eax+8]

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

APP: game.exe

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

FAULTING_THREAD: 000012bc

PRIMARY_PROBLEM_CLASS: NULL_CLASS_PTR_READ

BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ

LAST_CONTROL_TRANSFER: from 00000000 to 006e73c7

STACK_TEXT:
0018f488 00000000 0c7a9148 00000230 0c7a91e8 DX_Module+0x173c7


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dx_module+173c7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: DX_Module

IMAGE_NAME: DX_Module.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 46286bac

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_DX_Module.dll!Unknown

BUCKET_ID: APPLICATION_FAULT_NULL_CLASS_PTR_READ_dx_module+173c7

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:null_class_ptr_read_c0000005_dx_module.dll!unknown

FAILURE_ID_HASH: {3526c867-71da-98c1-4950-2cce70f52cc8}

Followup: MachineOwner
---------

0:000> lmtsmn
start end module name
65ea0000 660b9000 AcGenral AcGenral.dll Tue May 16 17:12:32 2017 (591B16E0)
6f7f0000 6f87d000 AcLayers AcLayers.dll Thu Oct 29 18:40:00 2015 (563259F0)
65c20000 65e79000 AcXtrnal AcXtrnal.dll Thu Oct 29 18:40:15 2015 (563259FF)
74d30000 74dd1000 advapi32 advapi32.dll Fri Aug 11 08:19:39 2017 (598D4C7B)
65a20000 65a23000 api_ms_win_core_synch_l1_2_0 api-ms-win-core-synch-l1-2-0.DLL Sat Jan 14 07:08:37 2017 (5879C065)
75c70000 75c75000 api_ms_win_downlevel_advapi32_l1_1_0 api-ms-win-downlevel-advapi32-l1-1-0.dll Sun Jan 13 22:16:42 2013 (50F3243A)
754f0000 754f3000 api_ms_win_downlevel_normaliz_l1_1_0 api-ms-win-downlevel-normaliz-l1-1-0.dll Sun Jan 13 22:17:02 2013 (50F3244E)
76e50000 76e54000 api_ms_win_downlevel_ole32_l1_1_0 api-ms-win-downlevel-ole32-l1-1-0.dll Sun Jan 13 22:11:08 2013 (50F322EC)
76e60000 76e64000 api_ms_win_downlevel_shlwapi_l1_1_0 api-ms-win-downlevel-shlwapi-l1-1-0.dll Sun Jan 13 22:17:03 2013 (50F3244F)
758b0000 758b4000 api_ms_win_downlevel_user32_l1_1_0 api-ms-win-downlevel-user32-l1-1-0.dll Sun Jan 13 22:11:21 2013 (50F322F9)
75c60000 75c64000 api_ms_win_downlevel_version_l1_1_0 api-ms-win-downlevel-version-l1-1-0.dll Sun Jan 13 22:11:07 2013 (50F322EB)
70550000 7059c000 apphelp apphelp.dll Thu Oct 29 18:41:04 2015 (56325A30)
70520000 7054f000 aswhookx aswhookx.dll Fri Aug 25 16:38:16 2017 (59A03658)
658a0000 65a1a000 aticfx32 aticfx32.dll Sat Sep 02 00:59:20 2017 (59A9E648)
64a00000 655f6000 atidxx32 atidxx32.dll Sat Sep 02 00:51:07 2017 (59A9E45B)
65840000 6586a000 atiuxpag atiuxpag.dll Sat Sep 02 00:44:07 2017 (59A9E2B7)
00360000 003d4000 audiere audiere.dll Mon Apr 16 08:47:26 2007 (46231BFE)
64800000 64836000 AudioSes AudioSes.dll Tue Jun 14 17:21:26 2016 (576020F6)
65890000 65897000 avrt avrt.dll Tue Jul 14 03:04:24 2009 (4A5BD998)
00250000 00281000 Binkw32 Binkw32.dll Thu May 13 04:55:03 1999 (373A3F07)
768d0000 768f7000 cfgmgr32 cfgmgr32.dll Tue May 24 12:28:33 2011 (4DDB8851)
75460000 754e3000 clbcatq clbcatq.dll Tue Jul 14 03:04:49 2009 (4A5BD9B1)
75ae0000 75c01000 crypt32 crypt32.dll Wed Apr 12 17:27:47 2017 (58EE4773)
74c40000 74c4c000 CRYPTBASE CRYPTBASE.dll Fri Aug 11 07:55:46 2017 (598D46E2)
66b50000 66cc5000 d3d11 d3d11.dll Wed Mar 27 23:48:45 2013 (5153774D)
65600000 65807000 D3DCompiler_43 D3DCompiler_43.dll Sat May 22 03:24:09 2010 (4BF73239)
07810000 07899000 D3DImm D3DImm.dll Sun Sep 11 16:43:11 2016 (57D56D7F)
002a0000 002dc000 DDraw DDraw.dll Sun Sep 11 16:42:56 2016 (57D56D70)
75440000 75452000 devobj devobj.dll Tue May 24 12:29:17 2011 (4DDB887D)
64980000 649f2000 dsound dsound.dll Tue Jul 14 03:06:05 2009 (4A5BD9FD)
6f880000 6f893000 dwmapi dwmapi.dll Thu Jul 09 19:37:01 2015 (559EB13D)
006d0000 00a4e000 DX_Module DX_Module.dll Fri Apr 20 09:28:44 2007 (46286BAC)
65a30000 65bf9000 dxgi dxgi.dll Sun Jan 01 16:55:29 2017 (58692671)
66b00000 66b4c000 dxgi_66b00000 dxgi.dll Sun Jan 13 21:20:31 2013 (50F3170F)
00400000 004a1000 game game.exe Fri Apr 20 11:21:46 2007 (4628862A)
75960000 759f0000 gdi32 gdi32.dll Fri May 12 20:03:20 2017 (5915F8E8)
75040000 75275000 iertutil iertutil.dll Sun Aug 13 18:24:02 2017 (59907D22)
75a60000 75ac0000 imm32 imm32.dll Sat Nov 20 13:08:51 2010 (4CE7BA53)
74f30000 75040000 kernel32 kernel32.dll Fri Aug 11 08:22:29 2017 (598D4D25)
75c10000 75c57000 KERNELBASE KERNELBASE.dll Fri Aug 11 08:22:30 2017 (598D4D26)
003f0000 003f7000 l_module l_module.dll Fri Apr 20 11:21:38 2007 (46288622)
759f0000 759fa000 lpk lpk.dll Fri May 12 20:03:20 2017 (5915F8E8)
7c140000 7c243000 MFC71 MFC71.dll Wed Mar 19 06:19:57 2003 (3E77FDFD)
64940000 64979000 MMDevAPI MMDevAPI.dll Sat Nov 20 13:01:22 2010 (4CE7B892)
6f7d0000 6f7e2000 mpr mpr.dll Tue Jul 14 03:07:02 2009 (4A5BDA36)
65e80000 65e94000 msacm32 msacm32.dll Tue Jul 14 03:07:26 2009 (4A5BDA4E)
75330000 7533c000 msasn1 msasn1.dll Sat Nov 20 13:02:17 2010 (4CE7B8C9)
76900000 769cd000 msctf msctf.dll Tue Oct 11 17:19:32 2016 (57FD0304)
7c080000 7c0fc000 MSVCP71 MSVCP71.dll Fri Dec 13 07:39:32 2002 (3DF980A4)
7d000000 7d058000 MSVCR71 MSVCR71.dll Fri Dec 13 07:38:48 2002 (3DF98078)
76d00000 76dac000 msvcrt msvcrt.dll Fri Dec 16 08:45:38 2011 (4EEAF722)
76b70000 76b73000 normaliz normaliz.dll Tue Jul 14 03:09:40 2009 (4A5BDAD4)
773b0000 77530000 ntdll ntdll.dll Fri Aug 11 08:19:45 2017 (598D4C81)
76b80000 76cdd000 ole32 ole32.dll Fri Aug 11 08:19:53 2017 (598D4C89)
758c0000 75951000 oleaut32 oleaut32.dll Mon Apr 17 17:12:40 2017 (58F4DB68)
72660000 72685000 powrprof powrprof.dll Tue Jul 14 03:10:36 2009 (4A5BDB0C)
76ed0000 76edb000 profapi profapi.dll Tue Jul 14 01:12:01 2009 (4A5BBF41)
64840000 64935000 propsys propsys.dll Sat Nov 20 13:05:23 2010 (4CE7B983)
75500000 755f0000 rpcrt4 rpcrt4.dll Fri Aug 11 08:19:45 2017 (598D4C81)
00290000 00299000 S_Module S_Module.dll Fri Apr 20 11:21:37 2007 (46288621)
73730000 7373f000 samcli samcli.dll Sat Nov 20 13:05:52 2010 (4CE7B9A0)
76ce0000 76cf9000 sechost sechost.dll Mon May 25 19:59:00 2015 (556362E4)
769d0000 76b6d000 setupapi setupapi.dll Sat Nov 20 13:06:49 2010 (4CE7B9D9)
6dba0000 6dba3000 sfc sfc.dll Tue Jul 14 03:10:25 2009 (4A5BDB01)
6db90000 6db9d000 sfc_os sfc_os.dll Tue Jul 14 03:10:26 2009 (4A5BDB02)
75c80000 768cc000 shell32 shell32.dll Tue Aug 15 17:10:56 2017 (59930F00)
75a00000 75a57000 shlwapi shlwapi.dll Sat Nov 20 13:06:58 2010 (4CE7B9E2)
65c10000 65c16000 shunimpl shunimpl.dll Sat Nov 20 10:34:31 2010 (4CE79627)
00230000 0024b000 Smackw32 Smackw32.dll Fri Jan 29 22:06:36 1999 (36B222DC)
65c00000 65c0d000 SortServer2003Compat SortServer2003Compat.dll Tue Jul 14 01:15:46 2009 (4A5BC022)
74c50000 74cb0000 sspicli sspicli.dll Fri Aug 11 08:19:45 2017 (598D4C81)
74de0000 74f2b000 urlmon urlmon.dll Sun Aug 13 17:13:31 2017 (59906C9B)
75340000 75440000 user32 user32.dll Thu Nov 10 17:19:40 2016 (58249E1C)
75ac0000 75ad7000 userenv userenv.dll Sat Nov 20 13:08:08 2010 (4CE7BA28)
76db0000 76e4d000 usp10 usp10.dll Wed Aug 16 17:10:49 2017 (59946079)
721e0000 72260000 uxtheme uxtheme.dll Tue Jul 14 03:11:24 2009 (4A5BDB3C)
74b80000 74b89000 version version.dll Tue Jul 14 03:11:07 2009 (4A5BDB2B)
10000000 1004b000 W_Module W_Module.dll Fri Apr 20 11:21:43 2007 (46288627)
75600000 758ab000 wininet wininet.dll Sun Aug 13 17:17:02 2017 (59906D6E)
6f680000 6f6b2000 winmm winmm.dll Sat Nov 20 13:08:34 2010 (4CE7BA42)
71e50000 71ea1000 winspool winspool.drv Sat Nov 20 13:08:43 2010 (4CE7BA4B)
74cb0000 74cdf000 wintrust wintrust.dll Wed Apr 12 17:26:54 2017 (58EE473E)

Unloaded modules:
65870000 6589a000 atiuxpag.dll
Timestamp: Sat Sep 02 00:44:07 2017 (59A9E2B7)
Checksum: 00030E26
ImageSize: 0002A000
652e0000 65671000 D3DCompiler_47.dll
Timestamp: Fri Jul 01 05:23:06 2016 (5775E21A)
Checksum: 003901BA
ImageSize: 00391000
65810000 65a17000 D3DCompiler_43.dll
Timestamp: Sat May 22 03:24:09 2010 (4BF73239)
Checksum: 0020A54F
ImageSize: 00207000
65680000 65a11000 D3DCompiler_47.dll
Timestamp: Fri Jul 01 05:23:06 2016 (5775E21A)
Checksum: 003901BA
ImageSize: 00391000

Masz najnowsze sterowniki do karty graficznej? Próbowałeś przeinstalować grę i wgrać patcha jeszcze raz?

Illudil
Posty: 7
Rejestracja: 11 września 2017, 19:51
Lokalizacja: Wrocław
Płeć: Mężczyzna

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: Illudil » 13 września 2017, 16:22

Właśnie instaluję patcha na świeżej wersji. Napiszę na Gadulcu z jakim efektem.

Edit:
Tak jak myślałem:


"Couldn`t open file 'D:\TLJ\static\static.xarc' (Error id data)
Please do not play any further on these data."

Znów nie ma plików, wydaje mi się że patch usuwa je kończąc instalację.

Awatar użytkownika
MrPepka
Przyjaciel forum
Posty: 322
Rejestracja: 08 sierpnia 2016, 15:18
Podziękował(a): 5 razy
Otrzymał(a) podziękowania: 13 razy
Płeć: Mężczyzna

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: MrPepka » 13 września 2017, 17:00

To chyba pozostaje ci skontaktować się z twórcą patcha (albo poczekaj aż sam się odezwie w tym wątku).

Illudil
Posty: 7
Rejestracja: 11 września 2017, 19:51
Lokalizacja: Wrocław
Płeć: Mężczyzna

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: Illudil » 13 września 2017, 17:49

Napisałem do pi_kor PW, czekam na jakieś info od niego :)

Awatar użytkownika
Urszula
Administrator
Posty: 9399
Rejestracja: 31 grudnia 2011, 12:05
Lokalizacja: Wrocław
Podziękował(a): 84 razy
Otrzymał(a) podziękowania: 109 razy
Płeć: Kobieta

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: Urszula » 13 września 2017, 21:02

Zamknij przy instlacji antywirusa.
___________________________________________________________________________________________________
Moje gry
Stowarzyszenie na Rzecz Rozwoju Dawstwa Szpiku - KRS 0000202597 - przekaż 1% podatku

kontakt w sprawach PrzygodoManii: urszula(at)przygodomania(kropka)pl

Illudil
Posty: 7
Rejestracja: 11 września 2017, 19:51
Lokalizacja: Wrocław
Płeć: Mężczyzna

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: Illudil » 25 września 2017, 16:10

Był błąd w patchu który został usunięty i teraz wszystko działa :)

Awatar użytkownika
pi_kor
Obserwator
Posty: 53
Rejestracja: 05 marca 2017, 00:23
Podziękował(a): 1 raz
Otrzymał(a) podziękowania: 10 razy
Płeć: Mężczyzna
Kontakt:

Re: Najdłuższa podróż - problemy z uruchomieniem - dyskusja

Postautor: pi_kor » 26 września 2017, 12:40

Instalator śmieszek wyrzucał pliki. Już poprawione :D
Patch do The Longest Journey na Windows 7/10 KLIK

kamilpikora.pl


Wróć do „Najdłuższa podróż: the longest journey”

Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 1 gość