Re: High CPU use even when idle
Sherman Wilcox wrote: I should say that my 30-day demo period expired and I'm now just testing out speed with imported mailboxes, etc. Could the expired demo be causing this? Yes, this problem appears only when you use the application after the demo period has expired. It stops if you register PowerMail. Jérôme - PowerMail Engineering - PowerMail is by far the most stable, trouble-free, well-rounded mail application I've seen in over 15 years. I'd buy this application again in a second. The staff at ctmdev is always Johnny-on-the-spot if there's an issue. Simple smooth interface and filtering is great. Once a user sets up the filters they perform almost invisibly. Multiple user environements is great and the ability to have the same user environment in OSX and OS9 (for those of use that still must boot into OS9 to work occassionally) is absolutely wonderful. The only additions I'd like to see are inline attachements and the ability to add more alert sounds to the application. Again, this is an absolutely wonderful application. PowerMail user comment on www.versiontracker.com Download a demo version from www.ctmdev.com -
Re: High CPU use even when idle
On Nov 28, 2003, at 9:37 PM, [EMAIL PROTECTED] wrote: Re-prebind your system. To do this you need a program like Panther Cache Cleaner, Cocktail, (and there's another one the name of which escapes me, but it also allows you to install just one file from a package.) After you do that, repair your privileges (use disk utility for this, but do it from your startup disk not from your install disk) and use some utility to clean out your caches, such as MacJanitor, Panther Cache Cleaner, or Cocktail. I prefer Panther Cache Cleaner, even though I'm still on Jaguar. This was fun, probably useful. I used Tinker Tool System to do it all. But it made no difference in PowerMail: disk is still getting constantly hit, and Activity Monitor reports PM CPU activity at 50%. I should say that my 30-day demo period expired and I'm now just testing out speed with imported mailboxes, etc. Could the expired demo be causing this? -- Sherman
Re: High CPU use even when idle
[EMAIL PROTECTED] / 03.11.28 / 11:37 PM wrote: Re-prebind your system. To do this you need a program like Panther Cache Cleaner, Cocktail, (and there's another one the name of which escapes me, but it also allows you to install just one file from a package.) After you do that, repair your privileges (use disk utility for this, but do it from your startup disk not from your install disk) and use some utility to clean out your caches, such as MacJanitor, Panther Cache Cleaner, or Cocktail. I prefer Panther Cache Cleaner, even though I'm still on Jaguar. Cleaning cache is a good idea, as well as periodic permission check, but if you just want to check the prebindings, you can do it from Terminal: sudo update_prebinding -root / -- - Hiro [PROTECTED] [PROTECTED]
Re: High CPU use even when idle
Re-prebind your system. To do this you need a program like Panther Cache Cleaner, Cocktail, (and there's another one the name of which escapes me, but it also allows you to install just one file from a package.) After you do that, repair your privileges (use disk utility for this, but do it from your startup disk not from your install disk) and use some utility to clean out your caches, such as MacJanitor, Panther Cache Cleaner, or Cocktail. I prefer Panther Cache Cleaner, even though I'm still on Jaguar. I have been trying the demo of PowerMail and was about to buy it. However, it has recently started exhibiting very high CPU usage (50%), even when idle. I've started with a clean install of PM and a clean (empty!) database, and it still does this. There is also quite a lot of disk activity. Any suggestions on how to fix this would be appreciated. -- Sherman Wilcox University of New Mexico
High CPU use even when idle
I have been trying the demo of PowerMail and was about to buy it. However, it has recently started exhibiting very high CPU usage (50%), even when idle. I've started with a clean install of PM and a clean (empty!) database, and it still does this. There is also quite a lot of disk activity. Any suggestions on how to fix this would be appreciated. -- Sherman Wilcox University of New Mexico
