Actually, it's not the processor design itself that is causing the problem.
No this is due to the acutal design of the chip itself. It does have a newer instruction set that isn't being used atm but it isn't 3D now. (rather the newer instruction set isn't 3D now but a different one, whether the chip uses 3Dnow or not I will have to check)
The real problem is that this chip requires the use of newer X86 codes. The software companies, like Microsoft don't want to use it as they really don't need to. The current X86 codes now are working very well, and would take them some extra time to develop newer ones. With this time comes an extra expense, with no real payback. No real payback meens no need to do it.
When a scheduler is designed to be inflexible to only recognize certain hardware abstraction layer elements, it will crash regardless when it finds something it cannot identify. It's not a Crytek problem, I can run those games on the AMD Bulldozer and above CPUs.
A schedule, in the case of a game, is a program that doles out control over a processor and it's resources to the game itself, everything from sound, video rendering, user input, etc., that all is controlled by the scheduler, of course this is an easy way to explain it but I don't want to get too technical for folks that would drown in scheduler operations.
It is the way in which MindArk chose to construct their scheduler, which is the heart of the problem. As many of you have found out, it's related to how many cores EU can see when it is launched that causes the problem. I know on some AMD FX 6xxx and 8xxx series you can set to go "turbo" when you do that certain cores get shutdown, that sometimes allows you to run Entropia.exe without incident assuming you have those 2 patches that were mentioned earlier from Microsoft correctly installed.
Another thing to look at as a work around is setting the processor affinity permanently, yes, that can be done.
If you need to know how to do this, I could write a batch file or leave the text in here for someone to copy in notepad and save it as a ".bat" file.
What you will need, administrative control of the computer you are on, in other words, allowed to go to elevated command prompt.
The command line from the DOS prompt:
start
To find out what is available to you to write your batch file, type the following without the quotes "start /?" and hit enter. It will give you your options to work with, most notably the switch called, "affinity" is what you are after.
Now, how do you run Entropia.exe directly, you need to specify the options EU needs to start with. The easiest way to find that out is to set Entropia.exe to run as Administrator, and when the UAC box comes up, click for more information, the details will tell you what your command line arguments are currently. You need to specify this when doing your "start /affinity" stuff so that when Entropia starts, it will run on a said processor and then start with the options that the client loader would normally send to it.
I would also suggest that you set a switch "/high" to get more processor time for EU, since it's such a hog in that respect.
Got questions, just ask.
