Since some time it's impossible to close Calamus in the usual way.
When I close Calamus I get this:

Description:
A problem caused this program to stop interacting with Windows

Problem signature:
Problem Event Name: AppHangXProcB1
Application Name: Calamus.exe
Application Version: 4.1.0.0
Application Timestamp: 4c095597
Signature of jamming: 3f6d
Type of crash: 32
Waiting for application name: SetPoint.exe
Waiting for version applicable: 0.0.0.0
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2067
Additional signature 1: 3f6d95aaccaac1828e14193ec9b22b6b
Additional signature 2: BE46
Additional signature 3: be46e1d13b8a487d9aeed8812fb95bf1
Additional signature 4: 3f6d
Additional signature 5: 3f6d95aaccaac1828e14193ec9b22b6b
Additional Signature 6: BE46
Additional signature 7: be46e1d13b8a487d9aeed8812fb95bf1
....


I use Calamus SL 2006 R8.
Calamus uses 900 MB ram and 1 core

My setup is as follows:
Windows 7 home premium, service pack 1
HP p6-2030be
Intel Core i5-2500 cpu 3.30 GHz
8 GB RAM64 bits

Avast antivirus free version (up to date)
Zone alarm (latest version)

I wonder if there is a way to cure this?

Martin

How do you ensure that Calamus SL only uses 1 core?

Grüße / Greetings / Groetjes / Salutations,
Ulf Dunkel

I've followed this link <URL:[btoforums.com]; to make Calamus use only 1 core.

Groeten,
Martin

Here is another way how to make sure that Calamus only uses one kernel (sorry, but it is from the German Calamus forum):

[www.calamus.net]

Grüße / Greetings / Groetjes / Salutations,
Ulf Dunkel

I've tried the taskassign methode but alas no cure. I start to think another recently installed/updated program is interfering with Calamus. I noticed in the German Calamus forum someone have had a similar problem. If I understand it well it turned out to be a graphic program.

Kind regards,
Martin