An update of sorts...

A partial success... one WinXP PC I upgraded to IE8 and that solved the problem.

Tthe MiniDump is running on the server that's serving most of the WinXP PCs that are having the trouble, and I am waiting to hear if that catches any problems. Those PCs are running IE8 so that removes the instillation as a cure for the trouble that's happening there.

I haven't installed Pegasus locally on a PC yet.

We have an XP machine where Pegasus 4.63(325) crashes on launch 4 times out of 5 with an Inpage error (Windows error not Pegasus) and on the 5th try it takes about 2mins to get to a usable state.

Can anyone shed some light on what I can look at to troubleshoot?

Thanks

This seems to be happening on all our WinXP machines.

Most just freeze on launching Pegasus...

[quote user="rogue7"]This seems to be happening on all our WinXP machines.[/quote]

Since this appears to be a site specific issue I guess everyone else can only provide rather limited help here. Did you read the How to post on top of this forum?

yes I did, I've even tried to run the mini dump software (for whast little use that was) but even on a fresh boot without Pegasus running (not autorunning on boot), it decided that Pegasus was in fact running, and wouldn't go any further.

Inpage errors are Windows errors and it's obvious by the lack of responses to your post that we are clueless as to the association with Pegasus Mail.  In your last post you said "it decided that Pegasus was in fact running, and wouldn't go any further".  What is "it" and what was it that wouldn't go any further? 

[quote user="rogue7"]it decided that Pegasus was in fact running, and wouldn't go any further.[/quote]

Would you be so kind to tell us about your setup? Do you run a local or a shared copy of Pegasus Mail? If the latter you need to ensure that Pegasus Mail doesn't run on any machine plus the (MiniDump) installer needs to have write access to Pegasus Mail's program directory and WINPM-32.EXE since this is the only way the installer can verify that no single instance of Pegasus Mail is running on a network. Unfortunately there's no more specific way for doing it AFAIK.

We're running three offices from one central Mercury which delivers mail to each of the three office's server, from which everyone logs into Pegasus from a single point. We have a variety of WinXP & Win7 (64 & 32 bit) and the problem is happening in two of the offices, and is restricted to most (not all) WinXP machines at this stage

I'm guessing from your post that I should be running the mini dump from the individual office's server?

[quote user="rogue7"]We're running three offices from one central Mercury which delivers mail to each of the three office's server, from which everyone logs into Pegasus from a single point. We have a variety of WinXP & Win7 (64 & 32 bit) and the problem is happening in two of the offices, and is restricted to most (not all) WinXP machines at this stage[/quote]

I still don't quite understand: Mercury is irrelevant in this context. Does everyone logs into Pegasus from a single point mean they don't run a local copy of Pegasus Mail on their respective machine's or not?

[quote user="rogue7"]I'm guessing from your post that I should be running the mini dump from the individual office's server?[/quote]

If Pegasus Mail is only installed on such a server and not on the client machines you're right: You need to install MiniDump on this server like Pegasus Mail itself, it will be loaded automatically whenever users start their instance from there. In some cases it might be required to start Pegasus Mail itself via MiniDump (how this works is explained in MiniDump's readme file).

BTW: What version of IE do these XP users have installed on their client machines? This might be a reason for trouble (IE 8 is strongly recommended  although it should work properly with IE 6 as well). Another one could be a printer(driver). What happens if installing Pegasus Mail locally on such a client machine? Does the crash happen as well?