I just had this annoying problem, and in my case I solved it by going into Explorer, then to the PMAIL folder, then to MAIL, then to the folder I was last using, then ordering all the emails by date, and, sure enough, I found the most recent email sent was listed as being 65,000kb in size.   I simply deleted it and then tried loading Pegasus, and now it has been able to open the new mail folder (without that humongous file there).

So it seems that when Pegasus hangs on "opening new folder", the reason why it hangs is because there's something in that new mail folder that it just can't handle.  So just go to the folder, find the most recent file and that file is most likely to be the culprit, particularly if it's enormous in size.

Just installed as an update, sent it off to the ISP to collect new mail, and there it stopped.  Killed it as a process, called it back, clicked "continue" when it informed me that it was locked, and that's where it sits, eating 50% of CPU capacity.  Killed it again, got the same result.

Ideas? 

[quote user="grankin"]eating 50% of CPU capacity.[/quote]

Go to Tools => Options => Advanced Settings and set Load Windows Internet Services ... to Always, restart Pegasus Mail and try again.

[quote user="idw"]

[quote user="grankin"]eating 50% of CPU capacity.[/quote]

Go to Tools => Options => Advanced Settings and set Load Windows Internet Services ... to Always, restart Pegasus Mail and try again.

[/quote]

"Tools" in Pegasus?  It never gets there.  It says it is opening the new mail folder, but remains on the initial splash screen while eating half of the CPU capacity.  Never gets beyond that.  Meanwhile Chrome pulls in all the webmail anyone might want (well, anyone who is used to doing most mail activity from within Pegasus, despite the fact that my ISP is now "powered by Google" for popmail.

So I am clearly missing something.  More detail, please?

Can you add -o to the end of command line you use to load winpm-32 in order to start in offline mode? You would add space, hyphen, letter 0 and then start winpm-32 and then go to Tools, Options, General, Advanced and check the Always item.

It would be some help if you told us how you use winpmail and if POP3 or IMAP and what version you were  using and how and where it was installed. Did you install the new archive exe to c:\pmail and is that where the former version was also located? Is there any network or any server involved or is it a standalone machine just connecting to your ISP mail server?

[quote user="Jerry Wise"]

Can you add -o to the end of command line you use to load winpm-32 in order to start in offline mode? You would add space, hyphen, letter 0 and then start winpm-32 and then go to Tools, Options, General, Advanced and check the Always item.

It would be some help if you told us how you use winpmail and if POP3 or IMAP and what version you were  using and how and where it was installed. Did you install the new archive exe to c:\pmail and is that where the former version was also located? Is there any network or any server involved or is it a standalone machine just connecting to your ISP mail server?

[/quote]

Added -o to replace the "-roamA.  Got a momentary flash screen and it closed itself.  

 It is version 4.6.1.0, installed as an update, downloaded March 14 @ 12:08 pm, as pop3.  The update overwrote the 4.5.  It runs on a stand-alone machine.  It updated initially, and ran very nicely, with all sorts of nifty new graphics in the toolbars.  I sent a couple of posts successfully.  Then I told it to get new popmail.  That's when it locked up.  Killed it and restarted it, which is where I  first asked for advice.  

 So I - moments ago - went to the downloaded  file and re-ran it, reinstalling 4.6.1.0.  Now, when I try to run it I get the flash screen with "starting ..." and immediately the pop-up appears:  "Pegasus Mail for Windows has encountered a problem and needs to close.  We are sorry for the inconvenience."

I believe you _may_  be a candidate for a full new clean install. First, check using taskman and make sure you only have one copy of winpm-32 running and then close it and any others. Then go to the directory where you have your winpmail installed and zip up all contents are store away carefully. All messages and address books can be restored later after new version and  install are up and running and tested.

Now with all old Pegasus Mail hidden away in compressed archive you can run the 4.61 installer and install to c:\pmail which is the default location. Then you will have to redo all configuration items and hosts information and such necessary to run and make connection to the ISP again. When that all works then we can work on how to restore all messages and address books and the proper locations where they need to be placed in the new install. The very last step will be to attempt to restore any old existing *.cnm new mail files and therein may be one or more  problem message files.

[quote user="Jerry Wise"]

I believe you _may_  be a candidate for a full new clean install. First, check using taskman and make sure you only have one copy of winpm-32 running and then close it and any others. Then go to the directory where you have your winpmail installed and zip up all contents are store away carefully. All messages and address books can be restored later after new version and  install are up and running and tested.

Now with all old Pegasus Mail hidden away in compressed archive you can run the 4.61 installer and install to c:\pmail which is the default location. Then you will have to redo all configuration items and hosts information and such necessary to run and make connection to the ISP again. When that all works then we can work on how to restore all messages and address books and the proper locations where they need to be placed in the new install. The very last step will be to attempt to restore any old existing *.cnm new mail files and therein may be one or more  problem message files.

[/quote]

 There was but one copy of winpm-32 running.  PMAIL is now in my I:\ drive (I:\PMAIL\winpm-32.exe -roam -A, from quick launch, I:\PMAIL\winpm-32.exe -A from "all programs" [1]), and putting a new PMAIL into the C:\ drive would be easy as pie.  Were I to have a clue how to restore everything that'd be lost. [2] 

I thought I solved it via Brute Force - by going to system restore and grabbing a date prior to downloading and installing 4.6.1.0.  So then I called pmail from quicklaunch - and it hangs at "opening new mail folder" and eats 50% of the cpu.  

 [1] When I call pmail from "all programs, it flashes on-screen and then vanishes from the screen and from Process Explorer.

[2]  I'd gladly receive guidance in said restoration, but I am reluctant to wear out my welcome.

[quote user="grankin"]PMAIL is now in my I:\ drive (I:\PMAIL\winpm-32.exe -roam -A, from quick launch, I:\PMAIL\winpm-32.exe -A from "all programs" [1]), [/quote]

Try again after removing the -roam switch, we can get back at this later on. Do you use "on open" new mail filter rules?

[quote user="idw"]

[quote user="grankin"]PMAIL is now in my I:\ drive (I:\PMAIL\winpm-32.exe -roam -A, from quick launch, I:\PMAIL\winpm-32.exe -A from "all programs" [1]), [/quote]

Try again after removing the -roam switch, we can get back at this later on. Do you use "on open" new mail filter rules?

[/quote]

I left it alone and went to bed.  Got up, and there it was, waiting for me.  Deleted the post awaiting in the queued mail folder, closed pmail, then re-opened it ... and it works.  Gonna stick with the old one until the new version 5 is ready to be used..

MANY thanks for your help!