It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
What can I do to play Turok in laptop Samsung NP-P460-AA01PL (graphic: Intel GMA 4500, procesor Intel Core 2 Duo P7350 – 2 GHz)? I’ve modified this computer and now it is equipped in 8 GB RAM – DDR 3 and SSD Blast Patriot 240 GB ? I have Windows 10 Professional 64 bit.

www.mobileman.pl/samsung_p460__np_p460_aa0apl_,474,laptop.html#sthash.Prao4yAb.dpbs

www.jakikomputer.com/?id=4

I know that this computer is not good for playing games – but it isn’t problem for it to play for example other GOG games (for example Rayman 2: The Great Escape and Kingpin: Life of Crime).

I have installed Intel Graphic Accelerator Driver with OpenGl 2.1 and when I have read information about Turok – it is enough to play this game. But when I start Turok – I get information „Error. Exception caught in main: see CRASHLOG.TXT for info”. And in CRASHLOG.TXT I see information (among others):

Operating system: 6.2.9200
2 processors, type 586.
16% memory in use.
2048 MB physical memory.
2048 MB physical memory free.
0 MB page file.
0 MB paging file free.
2048 MB user address space.
1800 MB user address space free.
Access violation at 00000000. The memory could not be read.

Context:
EDI: 0x06a480a0 ESI: 0x06a48078 EAX: 0x07f76658
EBX: 0x000000c8 ECX: 0x07f10068 EDX: 0x00000009
EIP: 0x00000000 EBP: 0x06a480a4 SegCs: 0x00000023
EFlags: 0x00210216 ESP: 0x0019fdbc SegSs: 0x0000002b

Bytes at CS:EIP:
?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??

Is it possible to play Turok with my computer…? If yes – what should I do?
Post edited January 07, 2016 by barjac
No posts in this topic were marked as the solution yet. If you can help, add your reply
This is because of the Win10-Graphics-Driver which is not 100% implemented for the new OS.

The only solution is to going back to Windows 7 with its lates graphic driver...

EDIT: I know, it' almost one year to late, but I'd today the same problem...
Post edited January 04, 2017 by sebi97
avatar
sebi97: This is because of the Win10-Graphics-Driver which is not 100% implemented for the new OS.

The only solution is to going back to Windows 7 with its lates graphic driver...

EDIT: I know, it' almost one year to late, but I'd today the same problem...
Thank you :-)