[quote user="bfluet"]

[quote user="PaulW"]WSSetup.dat contains the default base directory which (from the comments) are created upon initial PMail install.  This setting can only be altered manually and not through the program GUI.[/quote]

D'OH!  I did not think to look for a .dat or .ini associated with WSSETUP.  So let me ask this.  The registry entries in the problem PC contained UNC paths that match the one in the wssetup.dat file.  The registry entries in two other PCs contained mapped drive paths.  How would those mapped drive paths have been placed into the registry?  Would it have been from running winpm-32.exe using the mapped drive path without running or prior to running wssetup.exe?

[/quote]

My guess would be that either a full install or wssetup puts them in the registry.

Scenario:  Network install of Pegasus v4.63.  The executables and mailboxes reside on a server.

One Win7 PC has lost Pegasus Mail as the default mailer.  Pegasus will run using a shortcut to winpm-32.exe but no longer responds to mailto links or to attempts to email documents out of apps.

Pegasus Mail is no longer listed in the list of default programs so can not be set as the default mail program.  I have run wssetup.exe and setpmdefault.exe to no avail. 
AV scans come up clean.  Any other suggestions?

[quote user="bfluet"]Any other suggestions?[/quote]

The attached archive contains Registry files (renamed to avoid accidental import) providing the entries to add for setting Pegasus Mail as default mailer and MAPI resp. WSendTo handler: You will need to insert the proper install paths as indicated by the path substitutes in square brackets before importing the entries. I assume you know how to deal with the Registry, but for everyone else happening to read this post: Be extremely careful with modifying the Registry, it might cause fatal system issues!!!

This is valuable.  I think I will export the registry from this machine then do some key comparison to what you provided to see if any light might be shed on why the default mailer capabilities were suddenly lost on this PC and won't automatically reinstall.

Thanks Michael!

I just finished looking into the reg entries on the problem PC.  Found all paths were UNC paths to the location on the old server.  Odd that running WSSETUP from the new server location didn't fix them.  I manually edited and gave a quick test with positive results.  I will have user give it a full test in the morning. 

Michael,

I can't tell you how appreciative I am for the .reg info.  Thank you!

One observation... In reviewing the reg entries I found that the last three in your list did not exist.  I checked my PC and they are not there either.  Perhaps they do not exist when Pegasus Mail is a network install?  Those entries are the ones associated with the key [HKLM\SOFTWARE\Clients\Mail\Pegasus Mail\shell]

[quote user="bfluet"]One observation... In reviewing the reg entries I found that the last three in your list did not exist.  I checked my PC and they are not there either.  Perhaps they do not exist when Pegasus Mail is a network install?  Those entries are the ones associated with the key [HKLM\SOFTWARE\Clients\Mail\Pegasus Mail\shell][/quote]

They don't exist on my non-network install either, and they wouldn't even make sense, only for WSendTo which has its own entries. No idea what I kept them fore after writing the SetPMDefault utility.

[quote user="bfluet"]

I just finished looking into the reg entries on the problem PC.  Found all paths were UNC paths to the location on the old server.  Odd that running WSSETUP from the new server location didn't fix them.[/quote]

WSSetup.dat contains the default base directory which (from the comments) are created upon initial PMail install.  This setting can only be altered manually and not through the program GUI.

[quote user="PaulW"]WSSetup.dat contains the default base directory which (from the comments) are created upon initial PMail install.  This setting can only be altered manually and not through the program GUI.[/quote]

D'OH!  I did not think to look for a .dat or .ini associated with WSSETUP.  So let me ask this.  The registry entries in the problem PC contained UNC paths that match the one in the wssetup.dat file.  The registry entries in two other PCs contained mapped drive paths.  How would those mapped drive paths have been placed into the registry?  Would it have been from running winpm-32.exe using the mapped drive path without running or prior to running wssetup.exe?