[quote user="sjmullock"]Are you saying it would be better to send all this information to "beta-reports..." rather than post here? Having asked the question here, should I also send the email off to "beta-reports.."? I didn't think to do this largely because I didn't think I was using a beta version.[/quote]

This account is just for any test results that might be helpful in further development of Pegasus Mail, but it's not a support account in general.

Just upgraded my Pegasus mail 4.41 to 4.63, working on a Windows XP

sp3 machine. Every thing was going fine until I tried to access

noticeboards (does anyone else still use these?). To try and simplify

things I stopped trying to use the noticeboards on the file server and

let the wizard make a me a new noticeboard on my local disk. The results

are the same. I can look at the top level list of noticeboards, but as

soon as I open a noticeboard Pegasus crashes.

So I guess the first question is: Do noticeboards still work for everyone else?

Sorry in advance if this is a known issue - I did try searching the forums.

[quote user="sjmullock"]So I guess the first question is: Do noticeboards still work for everyone else? 

Sorry in advance if this is a known issue - I did try searching the forums.

TIA for any pointers[/quote]

I can't tell whether they work for everybody, but it would be nice if you could provide a crash report (MiniDump) like described in this post for diagnosis and possible fixes.

Where is the winpm-32.exe file you are running located? In that same look location look at noticeboards entry in the pegasus.ini file and see if it points to where noticeboard files are actually located.

Uusally I run an executable located on a file server, The shortcut I use includes a definition for NB (NB=\\Naslite\Disk-1\pegmail\notices) in the command line. This has been in long and successful use when running Pegasus 4.41. However, before asking for help, I also installed Pegasus 4.63 on my local hard disk and ran it from there. I wondered if there was something screwy with my original noticeboard setup, so when running the local copy I did not tell it where to find the noticeboard. Instead I let the wizard set me up a completely fresh noticeboard on the local hard disk. I set up a new topic, using the Pegasus dialog. However the behaviour was then the same. The top level noticeboard appears ok and shows the top level topics (in both cases meaning that Pegasus is pointing at the correct place). When I open a topic, the topic dialog appears, then after a second or so, Pegasus crashes.

I have attached a crash dump from running the local copy of Pegasus. The Minidump extension currently only cuts in when I crash the remote copy. To produce a dump when I run the local copy I used the standalone debugger, so the file I have attached is a .cab. I tried to attach the .dmp (zipped up) from the remote crash also, but it looks like I am only allowed to attach one file at a time.

Dump removed as per suggestion below!

[quote user="sjmullock"]I have attached a crash dump from running the local copy of Pegasus. The Minidump extension currently only cuts in when I crash the remote copy. To produce a dump when I run the local copy I used the standalone debugger, so the file I have attached is a .cab. I tried to attach the .dmp (zipped up) from the remote crash also, but it looks like I am only allowed to attach one file at a time.[/quote]

This dump doesn't provide any useful information related to noticeboards, unfortunately. Aside from this dumps aren't supposed to be published here because they may contain (in an unpredictable manner) personal and system information that you wouldn't want to leak - which is why the dumps are automatically attached to an auto-saved message to be sent to our beta-reports email account (more details to be found in MiniDump's ReadMe file). Additionally the report mail would provide some more system infromation which might be useful for debugging purposes. IOW: I recommend you to remove the attachment from your previous post.

[quote user="idw"]

Additionally the report mail would provide some more system infromation which might be useful for debugging purposes. IOW: I recommend you to remove the attachment from your previous post.

[/quote]

 Ok, thanks for the advice. I've removed the attachment. The email includes:

WinXP - 32bit + Internet Explorer 8.0.6001.18702 +
Pegasus Mail 4.63 + OKI C5600 +
IERenderer 2.4.7.2 (BearHtml 4.6.8.2)

and collecting from info yields:

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

WinPMail version: Version 4.63 (Win32), Dec 22 2011, build ID 325
Language resources: Standard UK English resource set
Extension Manager version: 1.14
Operating mode: Standalone
User name and ID: Admin, 0
Windows version: 5.1
Windows flag word: 0
WINPMAIL.EXE directory: C:\Program Files\pmail\Programs
Home mailbox location: C:\Program Files\pmail\MAIL\Admin
New mailbox location: C:\Program Files\pmail\MAIL\Admin
TMP environment variable: C:\DOCUME~1\Steve\LOCALS~1\Temp
TEMP environment variable: C:\DOCUME~1\Steve\LOCALS~1\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
  - WINSOCK version: (Not loaded)
  - WINSOCK path: C:\WINDOWS\system32\WSOCK32.DLL
Commandline: -A
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: 0
Message size soft limit: 0 bytes
Message size hard limit: 0 bytes
Attachment size soft limit: 0 bytes
Attachment size hard limit: 0 bytes

Are you saying it would be better to send all this information to "beta-reports..." rather than post here? Having asked the question here, should I also send the email off to "beta-reports.."? I didn't think to do this largely because I didn't think I was using a beta version.