Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
[quote user="Reesa"]Where do the crash logs go? I did not see any link to a Debug log from within Pegasus.[/quote]
If you don't get alerted about an auto-saved message there is none. In such a case you should launch PM via the debugger, there should be a respective shortcut in the Start menu folder created for the debugger. Reading the Readme.txt file should give you some hints as well.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Hi everybody,
Wonderful forum here with lots of good hints and information, thank you for creating this place! :-)
This is to ask if anybody else has problems with Pegasus Mail (I use the latest version 4.63, build 325) after Windows 7 updated to Internet Explorer 10. The update was last night, and today Pegasus Mail wouldn't start anymore. I tried reinstalling it, updated IERenderer and BearHtml, no effect. Pegasus Mail opened, so that I could see the folders and the messages inside, but then Windows immediately returned the wonderfully helpful message "Pegasus Mail doesn't work anymore" (roughly translated from German). Finally I removed the last Windows Update, and now Pegasus Mail works again. :-)
Has anybody else experienced the same? If not, it might be a problem with the configuration on my computer. If yes, there's probably something incompatible...
I hope my system won't update itself again now (will turn off automatic updates until this is solved) - I wouldn't know what to do without Pegasus Mail. It's the first and only E-Mail-program I've ever user on my private computers since 1998, and it has grown on me so much that I wouldn't uninstall it for whatever reason. :-)
Cheers
Zata
[quote user="Zata"]Has anybody else experienced the same? If not, it might be a problem with the configuration on my computer. If yes, there's probably something incompatible...[/quote]
I'm running PM on Win 7/64 with IE 10 ever since the latter became available without any problems. Unfortunately we won't be able to help a lot without you trying again and providing more details, the most helpful of which to be a crash dump. Some other possible issues are covered by this older post. You might also try after (temporarily) disabling any AV oder malware protection software, which might need to exempt PM's directories from scanning.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Thank you. I think I can exclude the issues in the older post you mention, I checked it first before creating the new topic here. AV and malware protection can be excluded as well. The only change in configuration between the states "PM working" and "PM crashing" was the Window 7 update to IE 10 (and some lanugage packs that came with the update, but I didn't uninstall these, just the IE 10 update, and now PM works again). Anyway, I've installed MiniDump now, let's see what information it will bring us after the next crash. Thanks again! :-)
Like you, I experienced a problem with Pegasus when an update for Internet Explorer 10 was installed, although mine occurred a month later (on May 10). I am running Windows 7Pro 64-bit Pegasus V 4.63.
At first, I couldn't figure out why attempts to open NEW MAIL messages were greeted with "Pegasus Mail for Windows has stopped working. A problem has caused the program to stop working correctly."
Suspicious that this might have been caused by one or more of nine updates that had been installed, I did a System Restore to May 8. The problem immediately cleared up. Two days later, however, two new updates were downloaded and installed; again Pegasus stopped working. One of these updates was identical to one from May 10 (Internet Explorer 10 for Windows 7 for x64-based Systems).
I uninstalled this update (which restored Pegasus to health) and set the update controls such that no further updates would be installed without my approval. (It was at this time that an IT friend found your post at this community forum; it was gratifying to learn that someone else was having the same problem.)
On May 15, nine "important" updates were ready for installation. Although one referred to Internet Explorer 8, I took a chance and installed all of them. Pegasus continued to function. That evening, several more updates were downloaded, awaiting my approval. One was for IE 10 - following the suggestion found at the following URL, I right-clicked it and chose HIDE ALERT. I allowed all of the others to be installed, one of which was for IE 9.
http://www.ghacks.net/2010/08/11/how-to-block-specific-updates-in-windows-update/
After the system re-booted, Pegasus failed to work. Apparently the IE 9 update causes the same problem as the IE 10 (although IE 8 did not, earlier in the day). So I uninstalled the IE 9 update; and when Microsoft "offered" it again a short while later, I did the HIDE ALERT command for it. So far, Pegasus is working properly
Supposedly HIDE ALERT permanently prevents the two updates from being installed. Five days have now passed and there have been no more attempts to download updates for IE 9 and IE 10. I've re-set the control to allow updates to be downloaded and installed automatically.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Added on December 6, 2013
After having had no trouble since I discovered the culprit for the Pegasus crashes last May (see above), today I began experiencing more crashes. I noticed that Microsoft had automatically installed an update called Internet Explorer 11. Just as I did with the IE 9 and IE 10 updates in May, I uninstalled Internet Explorer 11. This required a re-boot of the computer. Following this, not only have I had no troubles with Pegasus but I note that the Internet Explorer icon on the tool bar has reverted to its original size and shape.
I've changed the preference for Microsoft updates to DOWNLOAD UPDATES BUT LET ME DECIDE WHETHER TO INSTALL THEM. If/when the Internet Explorer 11 update appears again, I'll right-click it to HIDE UPDATE. This should take care of the problem. At that time, I'll change the preference for updates to INSTALL UPDATES AUTOMATICALLY.
Hi Ron,
Argggh, I have the same system/setup as you (Windows 7Pro 64-bit Pegasus V 4.63). But my problem's a little different: Pegasus always crashes when I close any message -- however, it works fine if I use the up/down arrow key to move from one message to another. I tried reverting to IE8, but it didn't help.
Also tried updating the HTML renderer and that didn't help.
If I can just remember not to close any messages, until v5 comes out, I guess I can learn to live with it.
Not happy ...
[quote user="Reesa"]Argggh, I have the same system/setup as you (Windows 7Pro 64-bit Pegasus V 4.63). But my problem's a little different: Pegasus always crashes when I close any message -- however, it works fine if I use the up/down arrow key to move from one message to another. I tried reverting to IE8, but it didn't help. [/quote]
There's a special post for dealing with such issues likes crashes and hangs/freezes at the top of this forum: Please read it and act accordingly so we can figure out what your issue is and what can be done to prevent it from reoccuring.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Hello,
I would appreciate if you could find the time to try using Bearhtml instead of IERenderer for a brief test. To do this: Shutdown Pegasus Mail, and rename IERenderer.fff to something like IERenderer.ffx. Restart Pegasus Mail, and try to re-open the message and retest the closing of the message. After testing simply shutdown Pegasus Mail, and rename IERenderer.ffx to IERenderer.fff and restart Pegasus Mail to resume normal(?) operations. Then please report on the result of the Bearhtml test.
Thank you
Martin
Hi,
I tried Bearhtml and the same thing happened: closing any message caused Pegasus to crash. So I restored IERenderer and installed the Debugger. Where do the crash logs go? I did not see any link to a Debug log from within Pegasus.
Could you please send me a copy of the message that causes crashes. I need the entire message so that the structure of the message can be examined. To do this please follow the simple steps beloew:
1 From the folder message list, select the message and Copy it back to your New Mail directory
2 Create a new message to me at irelam@telus.net
3. Drag & drop the message in the New mail directory from step 1 into the body area of the message created in step 2. When prompted about using an attachment, reply that you want to send an attachment.
4. Click Send to mail the message to me with its attachment
I have not seen mention that this message has already been forwarded to Michael, author of IERenderer, so I will forward it to hime, once I receive the message from you .
Regards,
Martin
[quote user="irelam"]Could you please send me a copy of the message that causes crashes. I need the entire message so that the structure of the message can be examined. To do this please follow the simple steps beloew:[/quote]
Since this doesn't seem to depend on a specific message I really doubt it's got anything to do with a certain message - unless it only affects HTML messages, of course.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Your previous draft for topic is pending
If you continue, your previous draft will be discarded.