Just a quicky .. If your like me, running the SETI client in the background .. and finding CTP2 crawl .. (even more that normal) .. then I recommend you turn it off for the duration of the game.
the SETI software kicks in during Idle CPU time .. and takes 100% CPU. As I only have 64Mb of Ram, and a P2 350Mhz ... running both together has a yakki effect.
64Mb is not enough memory to run CTP2 on its own, nether mind other apps .. so this results in virtual memory (your HD being used as memory .. which is very slow). Problem seems to be, that the SETI client keeps tripping in & out during the AI's turn, forcing the HD to be thrashed about horrifically ... and slowing the whole game down (especially the exit process, which takes upto 2 minutes without SETI running).
Infact, unless you have a top notch machine (which im sure many of you do have) .. I would remove any programs running at the same time (virus checkers/Real player/etc...)
------------------
"Wherever wood floats, you will find the British" . Napoleon
the SETI software kicks in during Idle CPU time .. and takes 100% CPU. As I only have 64Mb of Ram, and a P2 350Mhz ... running both together has a yakki effect.
64Mb is not enough memory to run CTP2 on its own, nether mind other apps .. so this results in virtual memory (your HD being used as memory .. which is very slow). Problem seems to be, that the SETI client keeps tripping in & out during the AI's turn, forcing the HD to be thrashed about horrifically ... and slowing the whole game down (especially the exit process, which takes upto 2 minutes without SETI running).
Infact, unless you have a top notch machine (which im sure many of you do have) .. I would remove any programs running at the same time (virus checkers/Real player/etc...)
------------------
"Wherever wood floats, you will find the British" . Napoleon
Comment