I tried this and it seemed to work for me

Microsoft, AMD and Intel are all aware of the affinity timing issues with 3D applications... here is the permanent fix which will automatically set the timing to one core when a 3D application is launched -and- make WindowsXP apply the correct resources to a dual core processor… which the above fix does not do

http://www.simviation.com/cgi-bin/yabb/YaBB.cgi?board=hardw;action=display;num=1...


EDIT: From the number of views it looks like people think FSX has a dual core patch released for it or something... The fix I posted will not enable multithread, only force Windows to use the procesor correctly.

Hey Nick!

Sometimes,in my oppinion, it seems, that a System Crash is not so bad.
During the re-installation i found the AMD Core Optimizer and the MS Hotfix by searching for the newest drivers.But its still interesting to read these Posts!

Uh, does that apply to HT processors as well? ???

yeh like nick said before if ur an AMD x2 user make sure u have the latest driver and the optimizer...both i have and yet i have to do the affinity thingy... but it works so.....    

if fsx uses a single core by default, they shood make a mod which would apply a certain level of physics to the AI aircraft, so that they dont look like they're attached to a rigid path...

maybe in FSXI...

It doesn't do anything in my socket 370 cpu 

Quote:


4 would be the optimal and a bit overkill but if you have the cash and the right hardware to run it and if you use the system for video editing, 4 will come in handy.

Make sure the motherboard will indeed support 4 gigs of memory @ full speed.

Older motherboards may downgrade the memory timing and speed if more than 2 sticks are in the system regardless of the OS.

Also, some motherboards require certain types of memory be installed to enable full speed operation.. consult the manual to be sure of what you are doing prior to any purchase.

WindowsXP will not recognize more than around 3.2gig and that requires a special switch be applied to the boot.ini file, otherwise it may not see more than 2.8-3gig. Vista and XP x64 will recognize and use everything you can throw at it with general public hardware.

Quote:



It has to do with the efficiency and method in how the core is accessed. I do not have time to post an entire write-up however you can review your question by googling it..

here is something you may find interesting which touches on Intels HT and how it differs from SMP.

http://www.lostcircuits.com/cpu/amd_x2/

indeed it will because FS9 has the same dual core problem

john

Quote:



Its not about the game.. its about the operating system

Any single thread 3D game will run better with a dual core if the XP operating system is properly set up and patched for affinity timing.

Quote:


I didn't see anything about a line of code in the boot.ini file in the thread you linked to above. I downloaded the hotfix and the registry already had that key in it somehow. What else do I need to do to the boot.ini file? It seems like everything is running ok right now as it is. The sim is running on one core while everything else seems to be why the other core has some activity. It really smoothed things up and allowed me to turn the settings up a bit.
Thanks!

Justin

Quote:



Intel is different.. the /usepmtimer switch will only appear in the boot.ini file if you are using AMD and the AMD Dual Core Optimizer.


And for AMD users.. you should not have to edit that line in manually as the AMD software should write that line automatically. The only reason I mentioned it was to be sure the line was indeed in the boot.ini file, which in order to find you must have hidden operating system files disabled.

Typically you will not have to edit the file at all. I just wanted to be sure it was right and to cover all the bases since Windows/drivers can sometimes not register correctly.

Quote:



excellent!

It makes a big difference when Windows is set up correctly for your hardware.

While on the topic of Cores.

Someone on my msn has a server with dual QX6700s Thats 8 cores people.

Quote:


I am aware of what the bulletin says about the hotfix and HT however there has been some controversy over the use of the hotfix with Intel HT. One of the reasons why M$ has not placed that hotfix on Windows update or made it widely known is because it may have an adverse affect on Intel HT and at the time of its release, AMD had not produced an optimizer that would make full use of the hotfix.

Using the hotfix with HT can have both positive and negative affects on systems that make use of logical thread technology. It may make some programs run better and seriously hinder other software. In the conversations I have had around the hotfix and HT, the consensus was it was better to disable HT in the BIOS during use of software which displays negative results with HT enabled than it was to inundate the system with a patch that may not provide the best solution.

HT is not SMP and Microsoft is aware that the hotfix is better suited for SMP use. It does come down to what works best and the only way to know which is better for a system would be to run HT disabled without the patch and then try it with and see what happens.

Many found that simply entering the BIOS and disabling HT prior to MSFS use resolved the performance issues and allowed the user to switch back when finished. At that point the system was free to use software in which HT is of great benefit and may be affected by the hotfix.

Quote:



Thats good!

I just like to err on the side of caution when posting technical information. I would not wish for someone to apply a patch I have suggested that may not work or may create other issues.

Microsoft did not post that patch or make it widely public for the same reason.

Bottom line is, if your willing to try it and assume the risks, ... and it works.. thats what counts.