[quote user="breezes"]Strange thing though.  Some of those messages were 5 years ole, but the peoblem never happened under Pegasus 4.41.  Why not?
[/quote]

The automatic saving of messages option is there as a precaution against loss as a result of a crash so perhaps an enchancement was made between v4.41 and v4.63 to automatically display auto-saved messages.  The assumption being that if there are any auto-saved message then the start up is a recovery from a crash so more conveniently gets the user back to the message(s) in progress.  This is just conjecture though..

I recently upgraded and moved Pegasus, as part of the process of upgrading and moving my primary operating system.  I had a dual-boot system, Win2K and XP, each on it's own drive.  I changed my primary OS to XP, which meant changing that drive to C:\.

I then installed Pegasus 4.63 onto the XP drive (now C:\), and then transferred  the necessary files from Pegasus 4.41.

Now, when I bring up Pegasus, I get a pop-up, 'Autosaved Messages Found', immediate following 'Restoring Desktop Layout'.  I can click 'ignore', or something to that effect, and go on to a regular Pegasus.  My other choice is to look at the autosaved messages.  There are about 18 of them, all with some content.  I can make them go away at that point, but they re-appear when I bring up Pegasus next time.  As I say, all contain at least part of an email.  There are no "0" content messages.

This is more annoying than anything else, and Pegasus works perfectly otherwise.  I'd like to correct this issue, just to get rid of the annoying factor.  Any suggestions?

When you say " I can make them go away at that point, but they

re-appear..," do you mean you are deleting them but they come back?  If

you aren't deleting them open the Draft manager using either Crtl+O or

File>Open saved messages.  You can work with them there (open, send,

save or delete).

Good call sir. I deleted those messages, going in Run>Open Saved Messages.  I've "re-booted" Pegasus several times now with no recurance of the problem.  I'd consider that one solved.  Thank you.

Strange thing though.  Some of those messages were 5 years ole, but the peoblem never happened under Pegasus 4.41.  Why not?