> Yes it look as some common PC problem.

Please let me know if you find the problem.  It's probably the same problem I have here with my network connection.  I my case I also have a bad CD type drive in my system that my in fact be the problem. ;-(

I install pegasus mail 4.51 over previous version, on windows XP, and now is start of PM wery slow.

can you help me?

Martin

I install pegasus mail 4.51 over previous version, on windows XP, and now is start of PM wery slow.

Strange, startup just looks at the pmail.cfg, pmail.usr and pmail.ini to start a user and then reads the pmail.ini, folstate.pm, stahe,pmj and heirarch.pm files to open the new mail folder and start the filtering.  The only thngs that could slow things down would be the reading of these files and the filtering 9and Content control if you are using it).

Could yuo provide a copy of the Help | About Pegasus Mail | Info?

[quote user="Thomas R. Stephenson"]

I install pegasus mail 4.51 over previous version, on windows XP, and now is start of PM wery slow.

Strange, startup just looks at the pmail.cfg, pmail.usr and pmail.ini to start a user and then reads the pmail.ini, folstate.pm, stahe,pmj and heirarch.pm files to open the new mail folder and start the filtering.  The only thngs that could slow things down would be the reading of these files and the filtering 9and Content control if you are using it).

Could yuo provide a copy of the Help | About Pegasus Mail | Info?

[/quote]

Another reason might be the default printer (driver) selected (if the printer isn't available like on a network, e.g.), although this should only affect the TER editor/reader and hence not delay Pegasus Mail's start-up.

Hi

here is  Info,.

Default printer is on network and work with PM properly.

Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2009, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.

WinPMail version: Version 4.51 (Win32), Jun 23 2009
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Standalone
User name and ID: Martin, 0
Windows version: 5.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\PMAIL
Home mailbox location: C:\PMAIL\MAIL\Martin
New mailbox location: C:\PMAIL\MAIL\Martin
TMP environment variable: C:\DOCUME~1\Martin\LOCALS~1\Temp
TEMP environment variable: C:\DOCUME~1\Martin\LOCALS~1\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
  - WINSOCK version: WinSock 2.0
  - WINSOCK path: C:\WINDOWS\system32\WSOCK32.DLL
Commandline: -i Martin
Active -Z options: 32768
PMR variable: (None)
PML variable: (None)
MAI variable: (None)
NB variable: (None)
Autofiltering folders: 0 (0 active, 0 inactive)
Last new mail count: 35

here is  Info,.

Default printer is on network and work with PM properly.

I see nothing at all wrong with the PMail setup.  However as a test try making the Windows default printer one that prints to a file like a PDF printer.  If it still starts slowly then at least you can rule out the network printer as the cause. 

That said, what is being displayed when PMail is hanging on startup?

Hi

Nearly whole time of start it display message "Starting up - please wait..."

On end of start it display for 1-2 sec. "Opening new mail folder".

Some times PM start quickly. When I exit PM and start again in few minutes, it start in most cases quickly. But if I start it after few hours it take more then 1 minute. 

So test with prinetrs in not representative.

I try 3 printers

Windows XPS document printer

Printer which is not connecting to network just now

and printer which I use as defaut.

Every time it start quickly

Nearly whole time of start it display message "Starting up - please wait..."

On end of start it display for 1-2 sec. "Opening new mail folder".

Some times PM start quickly. When I exit PM and start again in few

minutes, it start in most cases quickly. But if I start it after few

hours it take more then 1 minute. 

So test with prinetrs in not representative.

Ok, this really sounds like some sort of device timeout, it this case a drive or shared volume.  In this case is you immediately closed the program and reopened it it would start almost immediately since the system would remember that the device was not available. 

This one though is tough to solve and should also impact other programs at times as well.  For example, I have a WinXP system as a server and there are times my Dell system has trouble connecting to the shared drive, this happens in Adobe, Excel, EditPad and other programs as well.  I'm also running a Netware client and I suspect that this is part of the problem though.

Hi

Yes it look as some common PC problem.

Thank you

Martin