[quote user="irelam"]PMIcal.exe is a standalone program which is aware of Pegasus Mail through using the Windows Registry for directory locations.  It can be closed at any time without affecting anything else.[/quote]

Understood, and it was closed on the workstation.  Apparently Windows caching held it open on the server as it did with the .dll files.

Last night, when preparing to upgrade BearHTML on our network installation of Pegasus Mail, I checked for open files on the server (Server2008) and discovered many open \pmail\*.dll files being accessed by two users who did not have Pegasus Mail running.  Also showing open by one of these users was pmical.exe.  I physically checked both workstations to make sure neither winpm-32.exe nor pmical.exe were running (used taskmgr).  My observations during this time:

1.  Three users were logged in to the server.  All would have used PMail during the day.

2.  The two users shown accessing the open files are domain admins.

3.  The open files were released only upon log off (these users lock their machines but rarely log off).

3.  The open files were:  d32.dll, FreeImage.dll, HTS32.dll, ICONV.dll, TER32.dll, & pmical.exe

Thoughts anyone?

Thanks to an offlist clue from Jerry Wise I was able to determine that clearing the Windows memory cache released these files.  The question that remains is why the files are only held open for users who are network admins and why only PMail related .dlls.  I may never know the answer to that but at least I have a way to release them without logging off.

The command line to release the Windows memory cache in Windows7 is:

%windir%\system32\rundll32.exe advapi32.dll,ProcessIdleTasks

PMIcal.exe is a standalone program which is aware of Pegasus Mail through using the Windows Registry for directory locations.  It can be closed at any time without affecting anything else.

Martin