[quote user="mrshyvley"]
Hi,
Just joined the Pegasus forum, and have been using Pegasus since December of 1997, and have always kept up with the new versions as they came out.
I've been using Pegasus on a Windows XP Pro 64bit machine for a couple of years.
I'm presently using version 4.41.
The only issue I have with it during this whole time, is it will frequently (a few times a week out of 24/7 usage) go into a state where it appears from first glance to be working, but upon closer inspection, isn't retrieving any email, and is doing something that's taking about 99% of the processor.
To get out of this state, I have to close the program, then open Windows Task Manager/Processes and manually stop process "winpm-32.exe *32", which is still running and using upwards of 99% of the processor, even though I've closed the program. (when the program is closed when running normally, the "winpm-32.exe *32" process disappears )
I will often notice this when I observe that my screensaver (just the Windows stock "starfield") has stopped, and to get my screen back, it takes awhile to respond to my mouse or keyboard.
Has anybody else ever seen anything like this this? Thanks, Ed
[/quote]
I'd checkout the processor affinity on the winpm-32.exe process. I'd try setting the affinity WinPMail to only one of the CPUs and see what happens. FWIW, I'm using two 64 bit systems, one a Dell and the other a HP and I've not seen anything like this.
[quote user="mrshyvley"]<p>Hi,</p><p>Just joined the Pegasus forum, and have been using Pegasus since December of 1997, and have always kept up with the new versions as they came out.&nbsp;</p><p>
I've been using Pegasus on a Windows XP Pro 64bit machine for a couple of years.</p><p>I'm presently using version 4.41.</p><p>The only issue I have with it during this whole time, is it will frequently (a few times a week out of 24/7 usage) go into a state where it appears from first glance to be working, but upon closer inspection, isn't retrieving any email, and is doing something that's taking about 99% of the processor.</p><p>To get out of this state, I have to close the program, then open Windows Task Manager/Processes and manually stop process "winpm-32.exe *32", which is still running and using upwards of 99% of the processor, even though I've closed the program. (when the program is closed when running normally, the "winpm-32.exe *32" process disappears )</p><p>I will often notice this when I observe that my screensaver (just the Windows stock "starfield") has stopped, and to get my screen back, it takes awhile to respond to my mouse or keyboard.</p><p>&nbsp;
Has anybody else ever seen anything like this this?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,&nbsp; Ed&nbsp;</p><p>[/quote]</p><p>&nbsp;</p><p>I'd checkout the processor affinity on the winpm-32.exe process.&nbsp; I'd try setting the affinity WinPMail to only one of the CPUs and see what happens.&nbsp; FWIW, I'm using two 64 bit systems, one a Dell and the other a HP and I've not seen anything like this.</p><p>&nbsp;</p>