I confirm what Brian suggests, though life is too short to test it more than once now. That is, full shutdown (not easy on Win 10), reboot, open Chrome, open Pegasus, send a message, close Pegasus. No error.
David
One of our users who makes a habit of exiting Pegasus after each time he uses it is seeing an error message "Runtime Error 216:" followed by a memory address on exiting the program. It seems that he only sees this on exiting Pegasus and as far as we know everything else in the system is working perfectly. He only seems to see this message after exiting Pegasus.
Has anyone else seen this and if so did you find a way to stop it happening?
Thanks
Chris
There are a number of discussions on this forum about this error. The most recent one pointed to an issue caused by a driver update. I suspect the answer is in figuring out what changed on the system just before the error started occurring.
[quote user="Brian Fluet"]I suspect the answer is in figuring out what changed on the system just before the error started occurring. [/quote]
AFAIK it only affects Windows 10 users after its latest update (or whatever MS likes to call it now), and I'm wondering if it only relates to installations having been ported without running the PM installer again. I would really like to know whether re-running the PM installer or doing a fresh PM install could fix this?
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Windows 10 x64 Anniversary build. I don't get any error messages on close but most times Pegasus doesn't refresh my desktop screen leaving the Pegasus window displayed. Not sure if this is related. I get round the problem by not closing Pegasus and leaving it running all day.. Pegasus 4.7 as it was installed in Windows 7 before I updated to W10, not tried any reinstalls.
[quote user="davews"]Pegasus 4.7 as it was installed in Windows 7 before I updated to W10, not tried any reinstalls.[/quote]
I woud really recommend everyone encountering problems on Windows 10 after any kind of system update to try a reinstall first before reporting any issues - but please report back whether it solves them or not in any case.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Nope. Didn't work for me. But I'm not getting an error on closing. Just when I go to open again it says it didn't close properly.
If I close it, everything seems normal. But going to the task manager shows it as still running.
It looks to me that this is an Windows issue rather than being caused by Pegasus. I get the same error when exiting at least two other packages - one of them Dreamweaver - since the latest Windows update.
I guess I should say it closes. Just can't open it again. Going to task manager it shows as still running. Will not open again until I kill it there and it opens with the "didn't close properly" notice. Open it then and have to set preview to open again to view mail.
I have a Runtime error 216 if I send a message via Pegasus but only if I have Firefox either open on the desktop or minimized to the taskbar. For my system there seems to be some problem between Pegasus and FF. OS is Win 10 with latest updates. This did not start with the first year of using Win 10 so it may be a Windows update issue or a Firefox issue.
Similar but not the same. I tried to reproduce havant's report by opening Firefox, which I don't use much at the moment. Pegasus closed OK, but after I sent a msg, Pegasus appeared to close but was immediately reopened by Windows. No error 216 box. I got runtime error 216 by exiting after sending a msg without Firefox running but with Chrome open. Beats me. Windows 10 Pro with all updates.
best
David
FWIW, I keep Firefox (currently v50.1.0) open all day long while simultaneously running three instances of Pegasus Mail (2 of v4.63 (office,shared) and 1 of v4.72 (personal,flash drive)) without issue (Win7) No Chrome though.
David_himself, it would be interesting to know whether you can duplicate the Runtime error after a cold boot. My one experience with a Runtime error that appeared associated with Pegasus Mail did not recur after a cold boot (full shutdown, not just a restart).
