Greetings All,

Yesterday I came to the realization that the portable (flash drive) instance of Pegasus Mail that I have been using for years started leaving remnants on host PCs in the form of the HTML image cache. I had figured out how to keep temporary files on the flash drive but an image cache didn't exists when I created this instance and hadn't entered my mind until now.. Leaving remnants bothers me so I am asking for your help in trying to determine whether my concern is global enough to be worth inquiring into alternatives. If you run a portable instance (excluding multi-user network), a response to the following questions would be greatly appreciated..

1. Why do you run uninstalled instead of installed?

2. Where is it run from (portable/flash drive, local HD, other)?

3. If located on a portable or flash drive do you have concerns about leaving temp and/or image cache files on a host PC?

BTW, I am making this request on both the PM-Win list and the Community Forum. There is no need to respond in both places.

Thank you!!!!

--
Brian Fluet

I would just like to add here what IER's code is supposed to do for supporting the "ROAM" command line switch (implemented in Sept. 2011, released with IER 2.4.6.0): If (IER is) configured for using a cache path other than the default (i.e. the system's SysDrive:\users[UserName]\Roaming) and this cannot be located or accessed it will substitute the drive letter of it with the one of which Pegasus Mail was launched (this would then be the mobile device's drive letter if configured at least once manually - no matter which one on later attempts). If this doesn't work for whatever reason IER will try to use the default path, and if that fails to work either it'll finally use the TEMP directory. In all cases these paths will be ending with "Pegasus Mail\ImageCache[PMUser]".

I just finished test this. You done good Michael! Here are the steps I used to test:

• Started with a flash drive letter of F:
• Created \PM_Cache directory in the root of F:
• Started Pegasus Mail
• Changed the IER image cache path to F:\PM_Cache
• *PMAIL crashed on subsequent open of the IER config page. IER config opened ok after restart. New cache path had stuck.
• Opened an HTML formatted message and loaded images.
• IER created the subdirectory structure in F:\PM_Cache of \Pegasus Mail\ImageCache[PMUser]. It was populated with cache files.
• Shutdown Pegasus Mail
• Deleted all cache files but left the directory structure intact.
• Changed flash drive letter to G:
• Started Pegasus Mail
• Opened the same HTML formatted message and loaded images.
• Files were cached in the same directory as above.

Again, well done Michael!

I wish there were a way to automatically address the cache path whenever the ROAM command is detected but that would be an annoyance to everyone using the ROAM command on a fixed installation (I suspect there are a lot). It is enough to know that when using a portable instance, redirecting the temp path and the cache path should be a consideration. Temp files are normally deleted on Pegasus Mail shutdown but an abend can leave them so I prefer they be on the portable device.

Since I never got any feeback on this before and it's pretty old code it's certainly nice to hear that it actually works (except for the crash, of course), thanks Brian!

Does this mean that the ROAM command is included in the shortcut created by new installations (AFAYK)?

Yes, I think so.

I've now modified the browse folder dialog called bei IER's config sreen so you can create new folders from within it and don't need to do it outside of Pegasus Mail if changing to a path that doesn't exist yet. This should prevent the crash from happening when relaunching Pegasus Mail, I hope.