Jmsimer
Posts: 40
Joined: 7/27/2004 From: Chaska, MN Status: offline
|
Good point, they probably are redundant. However, I have tried it with and without the "affinity" set, and it does not make a difference for this particular error. The "affinity" trick was described a few years ago on this forum. quote:
ORIGINAL: BillBrown Plus I am not entirely sure what WITP_Affinity.exe does, but cpu2 sets the exe to use only cpu #2. From the patch notes: -cpu# : (cpu1, cpu2, cpu3, cpu4) Switches set the cpu affinity for multi cpu systems. It will do nothing for single cores and will default to using all cores if a core is designated which is not there (for example using -cpu3 on a dual core system). We’ve found this to be very useful on some multi-core systems, especially Intel processors. If used alone, the -cpu# switches will keep the game running on the CPU specified all the time. If used with the -SingleCpuStart switch, it will only use that core when starting the game. If used with the -SingleCpuOrders switch, it will stay in single CPU mode for starting and the orders phase, but will run in multicore. If one of the SingleCpu switches is used without a -cpu# switch, it will default to cpu 1 when it is in single core. So it would seem that the two are redundant.
_____________________________
Remember Bataan - Never Forget!
|