Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
[quote user="tomdriver"]Pegasus began crashing occasionally, so I upgraded to 4.61. The result was more crashes than ever.[/quote]
Here's a detailed "algorithm" for dealing with crashes: Upgrading to version 4.62 should already have solved most of your issues; and yes, you can install it on top of 4.61 even if using a different language than English.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Just updated Novell Netware based Pegasus email. Several users at one location cannot use the REPLY option. When they do the Reply Option window appears and can be modified, but when they click OK, there is a 2-3 second pause and then MS Error Signature window appears. The users previously could reply on older PMAIL version. Not all users on that server are having an issue. No users at another location are having the issue. I have compared the pmail.ini files of two users, one having the issue and on without issue, and can not discern a difference that would account for the problem. All computers are using Windows XP Pro SP3. The Microsoft "Error Signature" identifies the following: AppName: winpm-32.exe AppVer: 4.6.1.0 ModName: ter32.dll ModVer: 15.0.4.5 Offset: 0005918e
Good and Problem users are using the same MIME Character Set: ISO-8859-1
Any help would be appreciated. Everything else seems to be working fine.
Thank you in advance!
[quote user="RFrey"]The Microsoft "Error Signature" identifies the following: AppName: winpm-32.exe AppVer: 4.6.1.0 ModName: ter32.dll ModVer: 15.0.4.5 Offset: 0005918e[/quote]
Does it matter what kind of message they reply to (plain text vs. HTML formatted)? Does it make a difference if the disable IERenderer via its toolbar button? We might be able to figure out some more details if these users could provide a crash dump using the MiniDump extension, but they'd probably need some guidance when doing this, the details are explained in its ReadMe file: You'll probably need to run it via the Pegasus Mail Debugger entry it creates in its Start menu group on installation for getting proper results.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Just updated Novell Netware based Pegasus email. Several users at onelocation cannot use the REPLY option. When they do the Reply Option
window appears and can be modified, but when they click OK, there is a
2-3 second pause and then MS Error Signature window appears. The users
previously could reply on older PMAIL version.
Are the problem users using a graphic in their signatures?
An assistant was trying to resolve the issue and found the following "resolution"
Assistant: I found that going into message replies options, and in some cases not even changing anything, but hitting apply, seems to correct it.
Assistant: Travis changed his option to put < in front of the old message and that corrected his. Seems like any change made to reply options resets the issue. Maybe??? :)
Me: Wow - that sounds too easy...I wonder what config file that modifies. It would seem like it modifies the pmail.ini file which I had modified manually.
Further testing confirmed that making a change to the Tools / Options / Messages and Replies, or in the Reply Options window that appears resolves the issue. Perhaps it was a rights issue on that Netware Network.
oop...The above was accidentally posted on the wrong thread previously...I discovered it today and copied it to here. [:$]
Yes, all of our users have a graphics in their signatures.
Then you might want to check out this utility.
http://community.pmail.com/files/folders/community_add-ons_for_pegasus_mail/entry18437.aspx
1) The link provided above does not resolve.
2) Also, I am onsite today and was told by user that occasionally they still have the issue, but if the check the box when replying to add '>' in front of each line of the message, then it will almost certainly crash. I tried it and it did crash, then when unchecked it, no crash. Then I made some changes to the settings under TOOLS / OPTIONS / OUTGOING / Messages & Replies....such as ON / OFF choices for copy to self, delivery confirmation, etc. and now we can check the box for '>' while replying without issue.
Until a few days ago I had been using Pegasus v. 4.1, I think it was. Pegasus began crashing occasionally, so I upgraded to 4.61. The result was more crashes than ever. Through trial and error I solved the problem by clicking on the IERenderer button and removing the check mark on "Use IERendering". That was early this morniing, and it's not crashed since.
I think you had a problem before updating. Any error messages? On which action did that happen with 4.1 and after update with 4.61?
Aynway - I'm using PM461 for about half a year since some months with IERenderer 2.4.2.13. No crashes at all. Which IE-Renderer is installed in your PM-installation? Did you allready update BearHTML (what you are using now)?
bye Olaf
Your previous draft for topic is pending
If you continue, your previous draft will be discarded.