[quote user="Brian Fluet"]

[quote user="idw"]IOW: The installer "got confused" by mismatching path information. Would you you be willing to test a modfication if I can figure out one, Brian?[/quote]

Certainly [/quote]

I've now modified the installer for using the provided install path instead of the one from the Registry if they differ. Can you please send me an email via IER's About ... dialog so I can send you the (zipped) installer? IER itself hasn't been modified and keeps its version number, and I haven't added a note the history file either, yet.

I just attempted to update IERenderer by uninstalling 2.4.9.7 then installing 2.4.9.9.  Before going any further let me explain that I run two instances of PMail, from my local HD and one from a USB stick.  Neither were running at the time uninstall/reinstall but the flash drive instance was the last one run so the IER installer defaulted to that location (G:\PMAIL\PROGRAMS).  I changed it to C:\PMAIL\PROGRAMS and the install ran fine but now when I run the flash drive instance of PMail it reports IER v2.4.9.9 even though the IERENDERER.DLL file located in G:\PMAI\PROGRAMS\IERENDERER is version number 2.4.9.7.  Is the flash drive instance of PMail using the hard drive installed IER?

Edit:  I see the path of C:\PMAIL\PROGRAMS\IERENDERER\IERENDERER.DLL in the .fff file on the USB drive so how exactly does the /ROAM switch work with IER?

Edit 2:  Just looked at a backup and see the ~a in the path in the backed up .fff file.  It appears the installer replaced the .fff file on the USB drive but replaced the .dll file on the C: drive.  The time/date stamp of that .fff file appears to confirm this.

[quote user="Brian Fluet"]Is the flash drive instance of PMail using the hard drive installed IER?[/quote]

Apparently yes since IER retrieves the version number directly from the DLL.

[quote user="Brian Fluet"]Just looked at a backup and see the ~a in the path in the backed up .fff file.  It appears the installer replaced the .fff file on the USB drive but replaced the .dll file on the C: drive.  The time/date stamp of that .fff file appears to confirm this.[/quote]

The ~a in the path is required for roaming to work. The installer needs to figure out the proper fff-path which it does by reading the Registry: There is no other way to get the proper mailbox path if IER would be installed user specific instead of for all users (this is just a generic approach used by all my extensions using an installer). It is probably possible to use the path information for the latter without reading the existing Registry keys.

IOW: The installer "got confused" by mismatching path information. Would you you be willing to test a modfication if I can figure out one, Brian?

[quote user="idw"]IOW: The installer "got confused" by mismatching path information. Would you you be willing to test a modfication if I can figure out one, Brian?[/quote]

Certainly