UPDATE: July, 2010.
Further to development and testing, the latest released build of Equinox (Build 3860) includes some changes that have improved the performance on win 64 bit platforms in our test environment. We are now no longer experiencing an issue on our 64 bit test systems, so if you are experiencing problems then upgrading to this Build may help.
If you do upgrade and continue to encounter problems then could you please update me with the details?
Thanks, Mark, Head of Support, Compsoft
April 20, 2010. Customers have reported problems running the Equinox client in the 64 bit versions of the following products:
Windows Server 2008 R2
The client may hang during normal operation. The symptoms are that physical memory usage rapidly increases to 100% and CPU usage remains very high for anything up to a number of minutes.
Under Terminal Services, only a small number of clients (3-6) are able to start before similar symptoms occur.
Equinox uses a very small amount of memory, typically less than 10Mb, so it appears currently that there is an unexpected interaction between the Equinox 32 bit process and WOW64 – the 32 bit process interface, most likely either during display processing or memory management. Compsoft R&D has determined that the Equinox client is not attempting to allocate the memory directly. The next step is to produce a minimal test program that will produce the same symptoms, and if this is successful then raise the issue with Microsoft Support.
As this may be a lengthy process, Compsoft advises that customers avoid running Equinox clients in these environments for the time being, and contact the Compsoft support team for detailed advice on their particular situation and requirements.