Hi Ulf ---
I came across some odd behavior. Right after I temporarily lost my DSL Internet connection, Calamus coincidentally started to crash whenever I tried to close the program. The only way to shut it down was to use <ctl><alt><del> and shut it down, although it still reported to be not responding. Even after eliminating it from the running application list, there was still an entry for calamus.exe in the process tab list. To solve it, I simply kept it running for 2 weeks..
Anyway, I now (finally!) have my DSL connection running again, and lo and behold, the problem went away. It's all back to normal, much to my relief.I did not want to have to reinstall.
My question is, does Calamus try to use the Internet when shutting down? or do you have any idea why this might have happened?
If I simply unplug my connection, everything does still work (and close) fine. I cannot exactly recreate the situation that caused this, because it was some incorrect setting at my ISP that caused my loss of connection. I had recently changed my phone number.
Anyway, I'm glad it's solved now. I thought however, there might be a setting somewhere about "check for update" or similar such thing, although I never remember seeing one. And even if it did, I'm sure that a programmer would certainly allow for no (current) connection.
I know it must sound crazy, but the timing coincidence is very odd, and hard to ignore.
Another clue to this might be that when I would use <ctl><alt><del> and try to close Calamus from the application tab, there would be TWO calamus.exe entries. I'd close one (it would then say not responding...), then move to the other, but then the 2nd one would reappear! It was a vicious circle, as they say, and the only way out was to manually power-down. Thus, as I mentioned, I just left it running all the time.
Maybe another user can add an experience, if they lost connection and then also got odd behavior.
Thanks --- I know it doesn't make any sense or logic...
> Another clue to this might be that when I would use
> <ctl><alt><del> and try to close Calamus from the
> application tab, there would be TWO calamus.exe entries.
If you see TWO Calami in your Windows Task Bar or in the Windows Task Manager, then you definitely run TWO Calami. So you will have to inspect and find out why and how you force these two Calami to be started "at once".
The only time there are 2 entries, is after a failed program closure occurred, as described. I'm definitely not starting it twice, and I virtually always work on one document. There is always only one entry when I'm using it.
This behavior must be a rarity, since apparently no one else has experienced it...
However, here's a new oddity I noticed when trying to solve the previous -- I'm using Win XP Home, SP2 with an Athlon XP2500 processor and 1GB.
I start a print job, usually with PDF-Print, and then minimize the program to the task bar while it is at work. I listen for the bell to know when it's done. If the printing ends while the program is still minimized to the bottom of the screen,,something odd then happens.
Leaving Calamus STILL UNDISPLAYED, now go to the Processes tab of the <Ctl><Alt><Del> function. My system reports that Calamus.exe is currently using 99% of the CPU!
As soon as I restore the display of Calamus, and close the Print dialog, it stops all the CPU usage, and returns to Normal. To be clear, this 99% is AFTER the print job has finished.
See if you can recreate this, Ulf, or anyboy else for that matter.. Thanks --
> The only time there are 2 entries, is after a
> failed program closure occurred, as described.
This behaviour is absolutely normal. You run WinXP, which is a 32 bit OS with memory protection. If a task, say Calamus, doesn't quit regularly, it does not disturb other apps but still resists in memory. That's all. I wonder if your Calamus did not close or simply needed a huge amount of time for closing. I often see this behaviour in other monster apps like Mozilla which loves to cover large memory areas, too.
How much RAM do you grant Calamus (defined when you start the app while pressing [Ctrl])?
> I start a print job, usually with PDF-Print,
> and then minimize the program to the task bar
> while it is at work. I listen for
> the bell to know when it's done.
This is pretty normal, too. When Calamus is busy, it is really busy. You will see this high CPU usage when Calamus runs unminimized, too. But it knows when you, the user, want it to do something or just run the app without advising Calamus something to do.
There is no need for minimizing the app while it is busy.